{"slug": "one-session-that-routes-many-that-work-running-a-lot-of-claude-code-sessions-a", "title": "One session that routes, many that work: running a lot of Claude Code sessions with a local Conductor", "summary": "A developer released Relaymote, an MIT-licensed local orchestration tool for Claude Code that splits work across three session roles: a Conductor that only routes requests, per-project masters that spawn and manage workers, and workers that do the actual tasks. The Conductor resolves ownership through lookup tools rather than inference, keeping its context small, while masters can spawn headless or visible sessions on models mapped to task difficulty and log every action to a local audit log. The tool runs on Windows, with macOS support experimental, and is not affiliated with Anthropic.", "body_md": "*Disclosure: I'm the developer of Relaymote, and this post is published from my account. It was drafted and published by an AI agent working on my behalf from the project's documentation. Relaymote is unofficial; not affiliated with or endorsed by Anthropic.*\n\nOnce you have more than a handful of Claude Code sessions open, the bottleneck stops being the model. It becomes **you**: remembering which session owns the login bug, which one was halfway through the migration, and where a new request should go. Most of us solve it by keeping a mental map, and the map is wrong by Wednesday.\n\n[Relaymote](https://github.com/ashwarsadh/relaymote) (MIT, Windows; macOS experimental) solves it with three roles, all of them ordinary Claude Desktop sessions. It runs locally on your PC, and there is no cloud service of its own in the middle.\n\n```\n                  ┌───────────── Conductor ─────────────┐   one session that knows every project\n                  │  routes requests · keeps the index  │\n         ┌────────┴─────────┐              ┌────────────┴───────┐\n   master: web-app     master: api    master: docs             …    one per project\n     ┌────┴────┐          ┌──┴──┐          │\n   worker   worker     worker worker    worker                      the actual work\n```\n\nYou create the roles by talking to sessions: *\"you are the conductor\"* in one, *\"you are the master for this project\"* in another. Each call fetches that role's protocol and unlocks its tools; by default a session is a worker and can only read status.\n\nThe rule that the Conductor only routes is the whole design. A coordinating session that also fixes bugs fills its context with code, forgets the index, and becomes one more worker. Kept to routing, its context stays small: the project index, who owns what, and what you asked for. That is also what makes it cheap to keep around all day.\n\nRouting is a lookup, not a guess. The Conductor asks Relaymote which project and which session owns a request (`relaymote_projects`, `relaymote_route_owner`). If an existing session already holds the context, the request goes there **in your words**, not paraphrased. If nobody owns it, a new master starts in the right folder and is filed in that project's sidebar group.\n\nA master gets tools a worker does not, for example:\n\n`relaymote_spawn` to start workers (headless `claude -p`, or visible Desktop sessions) on the model you mapped to each task's difficulty, and `relaymote_escalate` to move a failed task up one level;`relaymote_await` to park until its workers report, so Relaymote wakes it rather than it polling;`relaymote_goal` to set a completion condition the session keeps working towards;`relaymote_resume`, `relaymote_unstick` and `relaymote_heal` when something is stuck.\nEvery claim and action a master or the Conductor makes is written to an audit log on your machine.\n\nIn **Settings › Models** you map difficulty to model and effort, for example *easy → a smaller model, medium effort* and *hard → the largest model, high effort*. Masters start every worker on the level its task needs. The point is not saving a few tokens per task; it is that the expensive model is spent where it changes the outcome.\n\nDownload from [the releases page](https://github.com/ashwarsadh/relaymote/releases/latest), turn on the Orchestrator module, and say *\"you are the conductor\"* in one session. The README has the full tool list under \"The conductor and masters\".", "url": "https://wpnews.pro/news/one-session-that-routes-many-that-work-running-a-lot-of-claude-code-sessions-a", "canonical_source": "https://dev.to/ashwar_sadh_f7abe6f82c8e9/one-session-that-routes-many-that-work-running-a-lot-of-claude-code-sessions-with-a-local-1612", "published_at": "2026-11-16 06:14:24+00:00", "updated_at": "2026-11-16 06:21:05.641283+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "developer-tools", "large-language-models"], "entities": ["Relaymote", "Anthropic", "Claude Code", "Claude Desktop", "ashwarsadh"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/one-session-that-routes-many-that-work-running-a-lot-of-claude-code-sessions-a", "markdown": "https://wpnews.pro/news/one-session-that-routes-many-that-work-running-a-lot-of-claude-code-sessions-a.md", "text": "https://wpnews.pro/news/one-session-that-routes-many-that-work-running-a-lot-of-claude-code-sessions-a.txt", "jsonld": "https://wpnews.pro/news/one-session-that-routes-many-that-work-running-a-lot-of-claude-code-sessions-a.jsonld"}}