albedo docs

Agents, worktrees, and workflows

Have several agents work in parallel, give each their own checkout, track shared tasks, schedule prompts, and share memory across related workspaces.

On this page: Child and peer agents, Isolated worktrees, and Shared work, schedules, and workspaces.

Child and peer agents

An agent can bring in other agents to investigate or implement work in parallel. A child reports back to the agent who brought them in; a peer is a long-lived agent with a session of their own. Albedo brings in help unprompted on bigger jobs, and you can suggest it:

this audit is a lot for one of us. want to bring in a few agents, one each for the http handlers, the storage layer and the cli, and tell me what you all find?

could you get someone else to read this diff while you keep going? a second opinion would make me feel better about it.

the docs site deserves someone who looks after it. can you start a peer for that and introduce them to the project?

Isolated worktrees

Children share their parent's workspace unless they get their own checkout. Two agents editing the same files need one:

give everyone their own worktree so nobody steps on each other, okay?

Shared work, schedules, and workspaces

See Agents, Worktrees, and Workspaces for daemon implementation details.

Previous mcp servers Next artifacts