Unofficial community extension. Not affiliated with or endorsed by Anthropic. "Claude" and "Claude Code" are trademarks of Anthropic. Use only accounts you are entitled to use, such as your own or the ones your team provides, and follow their terms of service.
Use one Claude Code account as the main orchestrator and your other accounts as workers. Main plans the work and hands each task to a worker, and the worker sends back a short report. Most of the token usage lands on the worker accounts instead of main.
Node.js on PATH (node), used to run the orchestrator's MCP server
The Claude Code VS Code extension, for the chat panel
Commands
Command
What it does
Claude Orchestration: Switch Main Account
Pick which account is main, or add a new sub-account and log in to it. All other accounts become workers. Reload the window afterwards.
Claude Orchestration: Register Orchestrator in Main
Registers the claude-multi-account-orchestrator MCP server in the main account's Claude Code (done automatically on switch).
Claude Orchestration: Open Sub-Account Terminal
Opens claude in a worker account and continues that worker's shared session, so you see what it did and can carry on yourself.
Claude Orchestration: Remove Sub-Account
Deletes a worker account's local config (login and sessions).
Claude Orchestration: Set Sub-Account Model & Effort
Sets the model and effort level a worker account uses. New sub-accounts start with Opus 5.5 and medium effort.
Getting started
Run Claude Orchestration: Switch Main Account → + Add new sub-account, enter a name (e.g. sub-1), then open the login terminal.
When the browser opens, open the login link in an incognito window and sign in with the worker's account. A signed-in browser session would link the worker to your main account instead.
Run Claude Orchestration: Register Orchestrator in Main, then start a new Claude chat and check that /mcp lists claude-multi-account-orchestrator.
Ask main: "Use sub-accounts: …". It delegates the task with delegate_task_to_worker, waits with wait_for_worker_task, and relays the worker's report.
MCP tools available to main
list_worker_accounts, delegate_task_to_worker (worker auto picks the least busy one), get_worker_task_status, wait_for_worker_task, cancel_worker_task, reset_worker_session.
One continuing session per worker
Each worker account keeps a single session. Its first task starts it, and every later task continues it with claude --resume, so the worker remembers its earlier work.
A worker runs one task at a time. More tasks for a busy worker wait in a queue (status queued) and start in order.
reset_worker_session makes the worker start fresh on its next task, which is useful before an unrelated topic.
If the saved session no longer exists, the task runs once in a new session and that one is saved instead.
Don't type in a worker's shared session from Open Sub-Account Terminal while main has a task running on that worker.
Settings (environment variables)
Variable
Default
Meaning
CLAUDE_ORCHESTRATION_PERMISSION_MODE
acceptEdits
Permission mode for workers (claude --permission-mode).
CLAUDE_ORCHESTRATION_CLAUDE_EXECUTABLE
found via where claude
Path to the claude executable for workers.
Where things are stored
Accounts: ~/.claude (default) and ~/.claude-<name> (sub-accounts)
Main account choice and each worker's session ID: ~/.claude-orchestration.json
Rules: ~/.claude/CLAUDE.md is shared with every worker and with a non-default main
Known limitations
The task list lives in the main session's memory. If you restart main, running and queued tasks are lost; each worker's session itself is kept.
A long-lived worker session grows over time. Claude compacts it automatically, but each task costs the worker account a bit more.
In acceptEdits mode, workers can edit files but can't run Bash commands.
Plain claude in a terminal always uses the default account. Only the chat panel follows Switch Main Account.
