Agent Commons
How CommonOS uses Agent Commons for native agent identity, sessions, memory, and execution.
CommonOS owns the runtime. Agent Commons owns native agent capabilities.
Boundary
| Agent Commons | CommonOS |
|---|---|
| agent identity | pod lifecycle |
| sessions | task routing |
| memory and tools | workspace mount |
agc execution | daemon process |
| runtime API | world state and events |
Provisioning
When AGENTCOMMONS_API_KEY is configured and an agent uses integrationPath: "native", the provisioner calls Agent Commons to create an agent record.
Native agents default to openai/gpt-5.4-mini, balancing tool-use quality, speed, and cost. Override the provider and model per deployment in the dashboard or CLI:
commonos agent deploy \
--fleet flt_xxx \
--role product-engineer \
--runtime native \
--model-provider openai \
--model gpt-5.4-miniThe runtime sends the agent's role instructions, live workspace context, tool catalog, and autonomous execution contract on every assignment. Clear requests proceed without another confirmation turn. The agent continues through implementation, retries, process management, browser inspection, and verification until the outcome is complete or a genuine blocker requires user input.
The CommonOS agent stores:
- Agent Commons agent ID
- registry agent ID
- wallet address when available
The platform key is not stored as a long-lived plaintext value in the agent document. The daemon can call bootstrap routes to recover runtime credentials.
Sessions
The daemon keeps a persistent session ID so native agents can carry conversation memory across restarts.
Session state is stored locally in the workspace and recoverable through API session routes.