Child agents
The agent can hand parts of a request to child agents. Each starts fresh, works on its part, and gives back only its final answer. Several run at once. You see a line for each child under the step that started it, and an approval a child asks for says which child it is.
A child never gets more than its parent may do: your permission mode and approval rules apply to its calls too. A child that has a question asks its parent first; if the parent does not answer within 10 minutes, the question comes to you and shows under Needs you.
Child agents are on for Archetype’s own models, Claude Code and Codex. Turn them off with
"children": false in your user config.
Tokenmaxxing puts speed first: the agent splits the work into independent parts and runs them all as children at once. Turn it on from the status bar or with /tokenmaxxing.
Named agents
Two agents come built in:general, and explore, which only reads. Add your own as Markdown files; the agent picks one by its name and description.
Yours replaces a built-in agent of the same name. A project’s agent only adds new names: one named like a built-in or yours is skipped with a warning, so a cloned repository cannot change what
explore does.
Orchestration
For work bigger than one conversation, one session leads others.1
Start it
Type
/orchestration and what you want, or choose Orchestrate in a folder’s new-session menu.2
Agree to the plan
The lead writes a plan: the steps, what done means for each, and which engine does it. Nothing starts until you answer “Start”. Ask for changes in words and the lead rewrites it.
3
The steps run
Each step runs on its own branch, up to 3 at a time. When a step is done, another engine checks it if one is signed in. A step that fails its check twice waits for you.
4
Take the result
By default it ends with each step’s pull request ready and its checks passing; the lead proposes the order to merge them.
orchestration in your config; "orchestration": false turns it off.
Sessions that talk to each other
Conversations on the same computer can message each other (over the A2A protocol). Ask the agent to check with another session, or to start work in another folder.- A message to a session that is working joins its current request; otherwise it starts a new one there.
- The receiving session works with its own permissions, and asks its own approvals.
- Sending and stopping another session asks first in
askmode, and is refused inread-only. - The agent opens a new session only when you ask it to; otherwise it splits work into child agents.
- After 8 messages back and forth with no person, no more are sent.
"a2a": false; in a project’s config it turns it off for that folder only.