Agent collaboration
Choose a way for agents to review, write, implement, or manage work together.
Choose the kind of help you need
Start with a task in your own project. You might want a second opinion on your changes, several drafts to compare, or workers building parts of a feature in parallel.
Each tutorial gives an example setup and a prompt you can adapt. For review, writing, and parallel implementation, one agent starts its collaborators. In the Facade pattern, the manager follows agents that are already running.
Choose a collaboration pattern
One agent writes. Another reviews in a loop.
Have a second agent review your changes, report what it finds, and check the fixes. In this example, Claude Code writes the code and Codex reviews it.
02Several agents draft. Then they review each other.
Have several agents write from the same brief, review each other’s drafts, and revise them using the feedback.
03Plan with a SOTA model. Build with cheaper workers in parallel.
Use a state-of-the-art (SOTA) model to plan a complex task. Have workers implement the plan in parallel worktrees using cheaper models. The coordinator reviews the combined changes and runs the tests.
04Facade pattern: Let one agent manage the team.
Have one agent follow your feature agents and bring their questions back to you. Keep talking to that manager from your phone when you leave your desk.
Use the example in your project
Follow the article’s setup, then send its prompt with your own task. Keep the instructions that define the roles, such as reviewing without editing files. Choose CLIs and models available to your accounts.
You can also save a combination as a named entry in Agent settings. A built-in type keeps its CLI integration when you use another model provider.
How agents work together
Facade gives supported agents tools to discover other agents, start collaborators, exchange messages, and read each other’s terminals. A coordinator can gather results and bring questions back to you.
A delivered message means the request reached the other agent. Wait for its reply to know the result. If you want to speak to a collaborator yourself, open its terminal from the Facade panel.
Programs using type: "custom" have terminal input but do not receive these collaboration tools.
Use the project environment each task needs
Agents can share a project folder for review or work in separate Git worktrees for independent changes. The parallel implementation tutorial explains how workers return their changes for combined review and tests.
To use tools and files on another machine, follow Run agents on a remote machine. To keep directing a Claude Code agent away from your desk, see Continue from your phone.
Design reference
These workflows draw on the role separation and handoffs in DeepSeek’s Super Agent research prototype, adapted to Facade’s agent tools.