Ship a feature with a team of agents.
One session plans the feature. Two child sessions build it, each in its own worktree, one on Claude Code and one on Codex. The parent reads what they did and tells you what's left.
- Developers
- Coding mode
- Claude Code
- Codex
- Worktrees
How it goes
- Step 1
Open a Coding session on your repository. Press the chip in the session header to add the planning skills to the repository.
The planning skills chip in the session header. - Step 2
Describe the feature. The session writes a plan in phases, with the files each phase touches.
The plan, in phases, in the transcript. - Step 3
Ask it to start a child session for each phase, each on a new worktree, and to give the second phase to Codex.
The parent with its two children and their worktrees. - Step 4
The children appear nested under the parent in the sidebar. Open either one to watch it, or send it a message while it works.
The children nested in the sidebar, one on Codex. - Step 5
When a child finishes, the parent reads what it did and reports back.
Still 18The parent's report after both children finish. Window 1280 × 800 at 2×. Light and dark.The parent's report. - Step 6
Review each branch the way you normally would, and merge.
A child can start a child of its own, and that's as deep as it goes.
More use cases
Let it work overnight
An automation triages the issues every night. In the morning, its runs are waiting to be read.
Steer from Telegram or Slack
Approve a permission request from Telegram, and start a session from a Slack message.
A folder as a workspace
A Productivity session over a folder of notes, with a runbook for the week and notes that link to each other.