Facade CodeFacade 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.
When to use this pattern
Use this when several agents are building features and you want one place to check progress and handle questions. They can all run locally, or some can work on remote machines over SSH. The manager acts as the team’s single point of contact: it gathers updates from those agents while they continue their own work.
Why this division of work helps
- Follow several features in one conversation. Ask the manager for an overview. It gathers updates from the feature agents and tells you where each feature stands.
- Find out what needs attention. It checks the terminals for errors, quota messages, and unanswered questions. It asks the relevant agent for details when needed.
- Keep up while you are away. Connect your phone to the manager’s session to check progress, answer questions, and send new instructions.
1. Start the manager
- Keep the editor open for the projects you want to follow. Keep SSH connections active for any agents on remote machines.
- Use an existing Claude Code agent as the manager, or create one with New Agent.
This example uses Claude Code as the manager. The feature agents are already running and keep their own CLIs and models.
| Role | CLI | Model | Effort |
|---|---|---|---|
| Manager | Claude Code (claude) | opus | high |
| Feature A — already running locally | Codex (codex) | gpt-6-sol | high |
| Feature B — already running over SSH | Codex (codex) | deepseek-v4.1-flash | xhigh |
| Feature C — already running over SSH | Muse Code (muse) | muse-spark-1.3 | high |
In your project, open Facade, click New Agent, and choose Claude Code for the manager. Set the model with /model opus and effort with /effort high.
With YOLO enabled, the manager can reach all agents connected through your Facade home. This setting also changes CLI approval behavior; see Agent permissions for details.
2. Ask it to follow the other agents
Send this prompt to the manager:
Use Facade to follow the other agents.
Every five minutes, read their terminals and check their progress. Ask the agents directly if anything is unclear.
Tell me when an agent hits an error, gets stuck, or needs my input.
When I ask for progress, summarize where each feature stands.3. How it follows the team
- Find the feature agents
- Check their progress regularly
- Ask questions and report problems
- Continue from your phone
- The manager finds the feature agents and schedules a check every five minutes.
- At each check, it reads their terminals. If progress is unclear, it asks the relevant agent.
- It reports problems and brings you questions that need a decision.
- You answer in the manager’s session, and it passes your response to the feature agent. You can ask for an overall progress report at any time.
The manager tells you when the checks are scheduled. Keep its session running; checks may be delayed while the manager is busy.
4. Continue from your phone
In the manager’s Claude Code session, run:
/remote-controlFollow the prompts, then open the session link or scan the QR code on your phone.
Ask the manager about progress, answer its questions, or send updated requirements. It continues following the feature agents through Facade.
Keep the manager’s computer awake and online, with Claude Code running. See Continue from your phone for account requirements and connection help.
Optional: Add a PM or tech lead for project decisions
For routine decisions, you can start a product manager (PM) or tech lead (TL) agent and pin it in Facade. Discuss the project’s direction, priorities, technical constraints, and past decisions with it. Leave implementation and debugging to the feature agents so these conversations stay focused on decisions.
If you add both, tell the manager how to involve them:
Send routine product questions to @PM and technical questions to @TL through Facade.
Have them decide based on the project direction we agreed on, then pass their answers to the feature agents.
Ask me when a question changes that direction or they cannot agree.When a PM or TL session gets long, ask it for a handover covering the project’s direction, past decisions, the reasons behind them, and open questions. Give the handover to a new PM or TL, then tell the manager which agent to contact.
Use it in your project
- Adjust the check interval, or ask the manager to focus on the features that need attention.
- Feature agents can keep working on their current machines. The manager reads their terminals and messages them through Facade.
- Give separate projects their own managers. Each manager follows its project’s agents, and you check in with the managers.
Keep Claude Code as the manager when using Remote Control. The feature agents, PM, and TL can use other CLIs and models. For saved launch settings and other providers, see Agent settings, Claude Code with another provider, and Codex with another provider.