The Business Agent Harness: Why Running a Company Is Harder Than Writing Code
A business agent harness goes beyond editing files in a terminal. Anakin treats the Workspace as the autonomous operating engine of a company: it finishes requests end to end, lets 20+ teammates work in one live session, requires owner sign-off for high-stakes actions, keeps secrets out of model context, fails closed on security, and records decisions in an auditable ledger.
Frequently asked questions
What is the difference between a coding agent harness and a business agent harness?
A coding harness helps one developer read and edit a repository. A business harness runs operations for an organization: it validates and executes transactions, persists state, notifies other systems, syncs the ledger, supports a whole team, and enforces roles, approvals and audit trails.
Who pays for usage when several team members share one workspace?
The host workspace owner. Every prompt token, tool call, sandbox run and agent turn is billed to the owner quota pool, so invited members never spend their personal credits.
How does Anakin keep secrets out of the model context?
Vault credentials are used through governed capabilities. Each call requires an active vault, a binding, a stated purpose and a host allowlist, so the model can use a key without ever seeing its value.
What happens when a webhook signing secret is missing?
The request is rejected. Inbound webhooks and CRM gateways fail closed and never fall through to execution.
Sources: live catalog, resource model, integration guide.