Architecture
Workspace model
How AgentsKitOS organizes agents, flows, triggers, and runtime state inside a workspace.
A workspace is the top-level unit. Every CLI command operates against a workspace, and every flow run is scoped to one.
Files
agentskit-os.config.ts— TypeScript config, Zod-validated viadefineConfig(). Declares providers, default models, vault adapter, audit sink, sandbox runtimes.workspace.yaml— declares agents, flows, triggers, memory backends, RAG blocks. Layered on top of the config. (ADR-0003)agentskit-os.lock— byte-reproducible lockfile pinning every package + manifest hash. Generated byagentskit-os lock. (RFC-0002).agentskitos/— runtime dir. Git-ignored.
Multi-tenant
The workspace model supports multi-client isolation natively. Marketing agencies, SaaS operators, and healthcare deployments use this for per-client audit, cost reporting, and BrandKit overrides.
What lives where
| Concern | Location |
|---|---|
| Provider keys | Vault (encrypted at rest) |
| Agent definitions | workspace.yaml |
| Flow DAGs | workspace.yaml or flows/*.yaml |
| Tool inventory | tools[] block + plugins |
| Checkpoints | .agentskitos/sqlite/ |
| Traces | .agentskitos/traces/ (or remote OTel sink) |
| Audit log | .agentskitos/audit/ (or remote sink) |