Docs

Agent OS

Mission orchestration with Temporal, Kafka, specialist workers, and governed workstations.

Agent OS is the long-running platform behind Agents Code: API, workers, modules for mission, planning, development, review, QA, knowledge, workstation, and governance.

Architecture in brief

  • API accepts CreateMission and emits events.
  • mission-worker orchestrates lifecycle with Temporal (MissionWorkflow).
  • Specialist chain: planning → architecture/tech lead → developer → reviewer → QA.
  • Knowledge workers publish into Neo4j, Qdrant, and catalog integrations.
  • Employees are declarative (YAML + prompt.md + schema).
  • Runtime prepares sessions; workstations execute on the repo.

Governance surfaces

The governance UI exposes missions/runs, employees, sessions, timeline, audit, infrastructure, MCP tools, and project onboarding — so operators can see what agents did and why.

Pilot principles

  • States include awaiting_approval for human gates.
  • Prompts live outside core domain code; LLMs only through a dedicated package.
  • Domain stays decoupled from Kafka/Temporal adapters (hexagonal / DDD).