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?
- Keep up and chime in: open
/agents(ctrl+oin the terminal client) or the canvas in the web client to see running agents, read their transcripts, and message any of them yourself. - Reports: a child's answer arrives in their parent's conversation when they finish. Agents can also write to each other while they work.
- Agree on a check: ask for one that must pass first, such as "have them
make sure
go test ./...passes before they report back". They report back once that command exits0, not before. - Limits: by default, children nest at most 3 levels deep, with up to 12
open children per parent. Configure these with
subagents.maxDepthandsubagents.maxOpenChildren. Each accepts a limit from 1 to 1000, or-1for no cap. When a child is done and closed, their transcript and files are kept.
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?
- Checkouts are created under
$ALBEDO_HOME/wt/<repo-slug>/<name>withjjorgit.jjwins when both manage the repository, unless you ask for git. - An agent in a worktree starts in the same subdirectory you were in.
- Worktrees are never deleted automatically, even when their agent closes. Ask Albedo to remove the ones that are merged or abandoned.
Shared work, schedules, and workspaces
- Work ledger (
/work): a task list shared by you and every agent in the workspace, with the statusesopen,active,blocked,done, andcancelled. Edit it with/work, or ask an agent to track their tasks there; they are told about your changes. - Schedules (
/schedule): run a prompt once (add in:300 ...), repeatedly (add every:3600 ...), or as an idle heartbeat (heartbeat every:1800 ...), with intervals from 60 to 31,536,000 seconds. Heartbeats skip an agent that is busy. Once and recurring prompts steer a running ordinary turn at its next step. An exclusive turn finishes before another input joins. - Linked workspaces (
/link): link related repositories or folders so memory, journals, and work items are searchable across the group while each workspace keeps its own writes. Agents in the group are told when a workspace joins, with a summary of the memory it brings. - Paperclips (
/paperclips): agents note what cost them real work, such as a bug in a tool or an unclear instruction. Review those notes here and acknowledge, answer, resolve, or dismiss them. The agent hears your answer. - Branching and side questions: use
/forkto branch a session from a checkpoint,/treeto rewind before a user message, and/btwto ask a side question without interrupting a running turn.
See Agents, Worktrees, and Workspaces for daemon implementation details.
Previous mcp servers Next artifacts