Skip to content
Workflow

Run multiple coding agents on one repository

Keep implementation, review and documentation in separate conversations that can communicate, without treating a shared working tree as isolated storage.

The path through the task
  1. Divide the work
  2. Connect the tabs
  3. Review the combined result

Before you start

  • A repository open in Empryo with a known starting Git state.
  • Separate responsibilities and explicit file ownership for concurrent writers.
  • A worktree for tasks that need an independent branch or checkout.

Work through it

  1. Split by responsibility

    Open named tabs for implementation, review or documentation. Ask for a child tab when its work should stay attached to the parent; each child has its own model, history and visible conversation.

    Check: Give each writer a file scope. Keep review read-only until you decide how to apply findings.

  2. Coordinate instead of copying chats

    Use link messages to exchange findings, ask for an answer or hand off a summary. Inspect active file claims before touching a file another tab is editing.

    Check: Resolve contested ownership with the other tab rather than assuming a warning means isolation.

  3. Integrate deliberately

    Review the final diff and run the project checks across the combined change. Use a worktree when two tasks cannot safely share the checkout.

    Check: Keep another tab’s unfinished work out of your commit. Do not bypass cross-tab Git protection.

Choose the right separation

Independent tab

A separate ongoing conversation with its own model and history.

Child tab

A task attached to a parent, with visible nesting and explicit handover.

Worktree

A separate Git checkout and branch when shared files would conflict.

A prompt to adapt

Replace the task details with your own. This is a suggested instruction, not a recorded result or a security policy.

Suggested prompt
Open a child tab to review this change without editing files. Give it the acceptance criteria and ask it to send findings back through link. Keep implementation in this tab; do not commit or close the review tab automatically.

Keep these boundaries clear

Open the detailed guides

Checked against the documentation on .