detachbox
PagesRun several agents at once on separate projects

Run several agents at once on separate projects

The API needs a migration, the web app a new page and the docs a rewrite. Three agents do all three at once, each in its own repository on its own subscription, and you follow every one of them from one list.

Terminals: every agent terminal of every project. The counter shows two that need you: one asking to apply a migration, one stopped on its limit until 3:10. Two more are done, four working.

You need: a size with room for the terminals you want at once: 3 on Start, 5 on Pro, 8 on Max.

1. Bring each repository in as a project

On Projects, pick New project once per repository and choose Clone. Each project gets its folder under /work and a home folder of its own, so the logins and keys of one never reach another.

2. Give each project its default launch

On each project's page, pick Set the default launch: the agent and what it runs on. Mix them to fit the work: Claude Code on your Claude subscription for the API, Codex on ChatGPT for the web app, OpenCode on a DeepSeek key for the docs.

3. Start them side by side

Pick Launch on each project, or open New terminal on Terminals, where every saved launch is one click. Give each agent its task. They run in separate terminals and never wait for each other.

4. Move between them

  • Alt+1, Alt+2, Alt+3 open the first three terminals of the list; Alt+↑ and Alt+↓ step through them.
  • The list keeps your order as agents change state, so each key opens the same agent until you move its row.
  • The counts bar on top filters to the ones that need you.
  • Rename a terminal by double-clicking its name, so "api · migration" reads at a glance.

5. Two agents in one project

Terminals of one project share its folder. Give two agents of one project different parts of the code, or put each on its own branch in its own git worktree inside the project, such as git worktree add .worktrees/search -b search.

6. Keep an eye on the limits

The header chips show how much of each subscription the agents have used. With one agent per subscription, a limit on one never stops the other two. For longer runs, rotation spreads one launch over several subscriptions.