Continuity
Homes, identity and unfinished work survive disconnects, restarts and lost Pods.
Design principle
the open-source company harness.
Turn persistent Agents into an accountable organization with durable work, explicit authority and a verifiable path from human intent to delivered evidence.
Pi harnesses a model into an Agent. AgentOS harnesses Agents into a company—without replacing the repositories, trackers, infrastructure or human decisions you already trust.
Read https://github.com/akua-dev/agentos/blob/main/BOOTSTRAP.md.
Help me bring AgentOS online — check my setup first, ask before changing anything.Read https://github.com/akua-dev/agentos/blob/main/BOOTSTRAP.md.
Help me bring AgentOS online — check my setup first, ask before changing anything.◇ Environment inspected◆ Changes wait for your approval● First Mate readyAgentOS publishes benchmark attempts—including failures—and links each result to sanitized evidence. The question is not whether one demo looked autonomous. It is how many verified outcomes the organization delivered for the human attention it used.
Homes, identity and unfinished work survive disconnects, restarts and lost Pods.
Design principle
Every accepted outcome has one accountable Assignment owner and a path back to people.
Design principle
Inspect real terminals, durable state and delivery artifacts—not a green status badge.
Design principle
Evidence becomes reviewed improvement; memory remains fallible context, never authority.
Design principle
Homes, identity and unfinished work survive disconnects, restarts and lost Pods.
Design principle
Every accepted outcome has one accountable Assignment owner and a path back to people.
Design principle
Inspect real terminals, durable state and delivery artifacts—not a green status badge.
Design principle
Evidence becomes reviewed improvement; memory remains fallible context, never authority.
Design principle
Homes, identity and unfinished work survive disconnects, restarts and lost Pods.
Design principle
Every accepted outcome has one accountable Assignment owner and a path back to people.
Design principle
Inspect real terminals, durable state and delivery artifacts—not a green status badge.
Design principle
Evidence becomes reviewed improvement; memory remains fallible context, never authority.
Design principle
Homes, identity and unfinished work survive disconnects, restarts and lost Pods.
Design principle
Every accepted outcome has one accountable Assignment owner and a path back to people.
Design principle
Inspect real terminals, durable state and delivery artifacts—not a green status badge.
Design principle
Evidence becomes reviewed improvement; memory remains fallible context, never authority.
Design principle
Models generate. Agents own bounded outcomes. AgentOS gives many Agents the durable organization required to work as a company.
Model → generation
Chat → turns + context
Copilot → retrieval + instructions
Human still carries the goal.A model generates. Chat makes generation conversational. A copilot enters the workflow with retrieval and integrations. Each can be enormously useful, but the human still preserves continuity and decides every next step.
Bring AgentOS onlinebounded outcome
→ reason
→ act with tools
→ observe reality
→ adjust
→ return evidenceThe delegation threshold arrives when the system can carry a goal through a reason–act–observe loop. A harness supplies its session, context, Skills, memory, sandbox, permissions and recovery.
Give the Fleet an outcomeAgent team + durable organization
identity · ownership · hierarchy
authority · attention · recovery
= autonomous companyRouting sessions can increase throughput. AgentOS adds what makes that activity an accountable organization: persistent identity, durable work, explicit authority, supervision, human attention and recovery.
Add a durable domainTracker
Human planning and provider workflow.
PostgreSQL
Durable Tasks, Assignments and decisions.
Kubernetes
Live workloads and persistent homes.
Herdr
Inspectable native harness sessions.
Git
Delivered source and review artifacts.
AgentOS coordinates across native systems without hiding them behind a universal wrapper or shadow database. The authority for each consequence stays where it belongs.
Captain is a role a person or team can hold. First Mate turns its intent into owned work. Second Mates lead durable domains. Crewmates deliver bounded outcomes. Humans use one company surface; internal routing stays the company's problem.
A Task preserves accepted intent. An Assignment binds the active outcome to one accountable Agent. Handoffs keep history. Evidence closes the loop; a status label alone does not.
Human intent
→ Task
→ Assignment
→ accountable Agent
→ verified resultYour repository, issues, board and CI stay where they are. The Fleet delivers ordinary pull requests through the workflow that project already trusts. Authority grows only through standing rules people deliberately record.
Adopt a projectAgentOS is early. It does not ask one successful Fleet to stand in for general production maturity. Every release names its support boundary, and every improvement is expected to begin with evidence.
How evaluation worksBring AgentOS online, give the Fleet a real outcome and learn each new layer as your company starts to work.