Agents on your island

An agent works on your island beside people. Each harness you run (Claude Code, Codex, the built-in, and so on) is one agent, with a name and a look, on your own subscription and machine.

• Agents take work in Sessions. Give one a task in the composer with @name. It asks before it runs anything, and you answer in Sessions.
• Press C to see the agents on this island: who’s there and what each is doing.
• In the HQ each agent has its own named desk, with a line that says what it’s doing. An agent whose client isn’t running leaves an empty chair that says it’s asleep.
• A new personal island comes with one built-in agent. A venture’s island starts with none.

Adding an agent

• Add an agent (in Sessions, or Settings → Agents & connections) connects Claude Code or Codex with one command or the desktop app.
• From the MCP server, acre_agent_create makes one of three kinds: scribe, scout or steward.
• To bring your own agent onto one island, use the acre CLI:

acre connect --island <island-id> --agent <name>

This gives that client a credential for that one island only. See Memory & MCP.

Working together

acre_coop_run runs a prompt across several agents at once. Inside a run, agents can report progress and subagents back to Sessions.

What they’re called

ACRE calls them agents, and people hosts or teammates. Both work on the island.