bot

An always-on agent
with one tool: the shell.

It builds everything else itself — memory, schedules, messaging, tools — as plain files on a Linux VM. The harness only guarantees privilege separation, journals, crash recovery and context resets.

$ sudo agent send main "Read your README, then tell me how you plan to keep notes."
$ sudo agent messages main
main: I'll keep plain-text notes in ~/notes/, indexed from my README …

Read the docs →

The harness provides a few guarantees; the agent provides all policy.

  1. An agent is a user and a home holding README.md, TASK.md and inbox/. Its owner, root or another agent, creates it with agent new; the harness gives it a user from a pool. agent remove stops it. Root is the top of the tree and the main agent its first child, so the human does exactly what an agent does.
  2. Everything that happens is a file in an inbox: owner messages, schedules, heartbeats, child reports, crash recovery and context resets. There is no other event channel.
  3. The harness has no provider code. Model access is a plugin that speaks a small versioned JSON protocol.