Build to operate

The verified journey from building an agent with AgentsKit to running it with governance, audit, cost, and HITL on AgentsKit OS.

AgentsKit OS is the production destination in the AgentsKit ecosystem. Use this journey when you already know how to build an agent and need to run it with real controls.

Journey

Build with AgentsKit — define tools, adapters, and agent behavior on the foundation library.
Start faster from the Registry when a ready agent matches the problem, then own and adapt the source.
Ship the experience with AgentsChat when users need a conversational interface across clients.
Guide ownership with Doc Bridge so agents and contributors land on the correct edit roots and checks.
Apply discipline with the Playbook before merging agent-produced changes.
Operate on AgentsKit OS — permissions, egress, audit ledger, cost budgets, HITL approvals, and deployment modes (managed cloud, self-hosted desktop, terminal/CLI).

Clean quickstart proof

# 1) Read the public docs entry point
open https://akos.agentskit.io/docs/getting-started
 
# 2) Install the CLI (see the CLI guide for the current package name and channel)
akos --help
 
# 3) Confirm the authentication and health commands are available
# The verified help surface lists both `auth status` and `status`.
akos --help

What “operate” means here

Control	Why it matters
Identity + RBAC	Only authorized principals run or approve agent actions
Egress allowlists	Agents only call approved tools and destinations
HITL gates	Risky steps pause for a human decision
Signed audit	Every material action is reconstructible later
Cost budgets	Spend is visible and policy-bound
Deployment modes	Same contracts for managed cloud and self-hosted

Maturity honesty

Released public docs and CLI surfaces are what this journey covers.
Experimental package APIs may change; treat them as internal operator knowledge unless a release notes them as stable.
If a capability is planned or unavailable, the assistant and docs must say so rather than inventing a path.

Next steps

Getting Started — web, desktop, and CLI entry.
How a run works — trigger to signed audit ledger.
CLI command reference — verbs and capabilities.
Using the app — screen-by-screen operator guide.