Multi-Project Multi-Agent

  • Desktop, mobile and web
  • All plans

What it does

AgentsRoom runs several AI coding agents, on several projects, in parallel, inside one window. The left sidebar lists every project grouped by zone (Work, Personal, Side Projects, Freelance, Learning, or any zone you create by drag and drop). Opening a project shows its room: the agents on the left, the focused agent's terminal in the centre, the side panel (review, dev commands, browser, prompts) on the right. Every agent has a role with a fixed colour and avatar, its own terminal session that keeps running and keeps its scrollback while you work elsewhere, and a live status dot: pulsing yellow while thinking, green when done, pulsing red when it waits for you, grey when idle. Each project row aggregates how many agents are working, done or waiting, and takes the colour of the agent currently thinking, so activity is visible from the corner of your eye.

Video (1 min 24 s): Multi-project, multi-agent, shown in the real app. Three Claude Code agents work on a shop project and a fourth on its API; from the API project, the shop's tile in the top bar turns red and the needs input pill lists the waiting agent with its project; one click brings you back to it, the two others finished meanwhile, and it gets back to work after your answer.

Where to find it

  • The projects home (no project selected) shows every project as a card; the sidebar shows them grouped by zone with live counters. Filters there sort by machine (All machines, This machine) and a Duplicates filter shows only projects with a duplicate name.
  • Click a project to enter its room. The open projects then sit as tiles at the top of the window, left of the project name; each tile carries a status badge: pulsing red when one of its agents waits for you (with the number of unread agents inside), orange while one works, green when its agents are idle. Hovering a tile shows Open <project> and its Cmd+number.
  • Inside a room, the sidebar shows Running agents counters (Needs you, To review, Working) once several agents are open, then the agents filed under Needs you, To review, Working, Available and Inactive. Clicking a role of the Inactive list starts that agent.
  • Title bar: since 2026-09-28 the Recent agents row lists the open agents of every open project, most recently opened first, grouped by project, to jump back in one click (see Recent Agents), next to the needs-input pill (see Needs Input Inbox).
  • Hover the project's name (title bar or the top of its column) and a small floating pill appears under it, since 2026-10-28: a pencil renames the project on the spot and a copy button copies its name. Double-clicking the name renames it too, and the right-click menu keeps Rename. When the title bar runs out of width, that project's Open folder, Statistics and Project settings icons join the same pill.

How to use it

  1. Open a project from the sidebar, add agents with Add agent (role, provider, model) or the Quick agent lightning button.
  2. Give each agent a task in its composer. Switch project or agent at any time: sessions stay alive in the background.
  3. Watch the sidebar: red pulse means an agent is waiting for you, the coloured left border and shimmer mean an agent is working.
  4. From another project, the red badge on a project tile and the N needs input pill of the title bar say an agent waits elsewhere: click the pill, then the agent in its Waiting for input list (it names the project and shows the question), and you land on that agent with its question card open.
  5. Move a project to another zone by dragging its row; drop it on a new zone name to create one.

Keyboard navigation (Settings > Keyboard shortcuts > Project and agent navigation): Up / Down move between agents of the open project, Left / Right and Tab / Shift+Tab move between open projects, Cmd (or Ctrl) + Option + arrow does the same from inside a focused terminal, which otherwise keeps its arrows and Tab for the CLI. Only projects already open are cycled.

Direct jumps (Settings > Keyboard shortcuts), always active, independent of the navigation toggle: Next project waiting for you (Cmd+Shift+J on macOS, Ctrl+Shift+J on Windows and Linux, rebindable) opens the next project in sidebar order where an agent waits for your answer, right on that agent; press it again to reach the next one. Jump to a project lists every project with a Not assigned button: click it, press a chord, and that chord opens the project directly. The same chord can be set from the project itself: Project settings > Keyboard shortcuts > Open this project. Both fire from anywhere in the window, terminals and editors included, but not under a dialog or the command palette.

Numbered jumps: Cmd+1 to Cmd+9 (Ctrl+1 to Ctrl+9 on Windows and Linux) open the project at that position in the project list on screen at that moment. Inside a project, that is the row of open projects at the top of the window, from left to right. With the full project list unfolded, the sidebar collapsed to its rail, or the Recently opened list of the home screen, it is that list from top to bottom, following its sort, folded folders, search and filters. The shortcut does exactly what a click on that project does (a locked project shows the upgrade prompt). The collapsed rail lists the open projects in the same order as the row of open projects, so collapsing or expanding the sidebar never changes which project a number opens. A number with no project at that position does nothing. Hovering an open project in the sidebar shows its number shortcut in the tooltip (only for the first nine positions).

Shortcut hints: hold Cmd (macOS) or Ctrl (Windows, Linux) alone for a moment and every control that has a keyboard shortcut shows it: the number of each project (Cmd+1 to Cmd+9) on its tile or row, the search button of the title bar (Cmd+K), the screenshot button of the composer (with its own global shortcut, when that shortcut is on), the New project buttons (Cmd+N) the waiting-agents badge of the title bar (Next project waiting for you, Cmd+Shift+J) and the Bug button of the footer (Cmd+Shift+B). Pressing any other key, or releasing Cmd / Ctrl, hides them. They do not show under a dialog or the command palette. Turn them off in Settings > Keyboard shortcuts > Show shortcuts while holding Cmd / Ctrl.

Right-click a project in the sidebar for its menu; Copy path puts the full path of its folder on the clipboard.

Closing a project: the close cross on a project tile or card asks for confirmation first when the project still has an open agent session (even idle) or an open command terminal: "Close project ...? Its open agent sessions and command terminals will close. Work in progress may be interrupted." Cancel keeps everything running; a project with nothing live closes at once. Once closed, a message from another agent no longer restarts one of its agents (it waits until you open the project again); what you set up yourself, scheduled tasks and triggers, still runs. To freeze those too, use Pause on the project (see Project pause).

Settings

  • projectAgentCycleShortcut (global, Settings > Keyboard shortcuts, "Custom agent shortcut"): the chord that jumps to the next active agent; default Tab, add Shift for the previous one.
  • attentionProjectShortcut (global, Settings > Keyboard shortcuts, "Next project waiting for you"): the chord that opens the next project where an agent waits for you. Empty = default (Cmd+Shift+J on macOS, Ctrl+Shift+J elsewhere).
  • projectJumpShortcuts (global, Settings > Keyboard shortcuts, "Jump to a project", and Project settings > Keyboard shortcuts, "Open this project"): one chord per project, keyed by repository project id. A chord must hold Cmd, Ctrl or Alt, or be a function key; one chord opens one project only. Default: none.
  • Both are stored on your account and follow you to every computer you sign in to. They are written with Mod for the command key, so Cmd+1 set on a Mac becomes Ctrl+1 on Windows and Linux.
  • shortcutHintsEnabled (global, Settings > Keyboard shortcuts, "Show shortcuts while holding Cmd / Ctrl"): draw each shortcut on its control while Cmd / Ctrl is held alone. On by default, stored on your account.
  • notificationSound and needsInputSound (global, Settings > Notifications): play a sound when an agent finishes a turn or needs input.
  • sendNotificationsToPhone (global, Settings > Notifications): mirror desktop notifications to the paired phone.

Agent tools (MCP)

  • projects_list: every project of the account, so an agent can read a sibling project's backlog, memory, skills or prompts with the project argument.
  • agents_list / agents_get: the saved agents of a project and their configuration.
  • agents_list_live: which agents currently have a live console, their status and what they are working on.
  • agents_spawn / agents_resume / agents_close: open a new throwaway agent, bring a saved one back on its previous conversation (or, with allowFresh, on a new one when it has none: how an agent starts a colleague of another project without you switching to it), in this project or in another open project. agents_close ends a console of the agent's own project, plus the throwaway agents it spawned itself in another project; another project's other consoles are closed by you, from that project.
  • usage_overview: anonymous census of running consoles by status and provider, plus provider quotas.

Providers

All providers, no difference: Claude Code, Codex CLI, GitHub Copilot CLI, Antigravity CLI, OpenCode, Aider, Grok Build, Mistral Vibe, Kimi Code, Amp, oh-my-pi, Freebuff, Devin and Cursor can run side by side in the same project. Colour and avatar follow the role, not the CLI; a provider mark sits on the avatar, and the card shows which CLI account an agent runs on when several are signed in.

Mobile

Present. The iOS / Android app shows the same projects, agents, colours, statuses and counters through the end-to-end encrypted relay, receives push notifications for finished turns and blocked agents, and can start an agent, type in its terminal and answer its questions; the session itself runs on the desktop.

The keyboard shortcuts (navigation, project jumps, shortcut hints) are desktop only: the phone has no keyboard chords, and its needs-input list already opens a waiting agent in one tap.

Limits

  • The number of agents is bounded by your machine and your provider quotas, not by AgentsRoom; 10 to 20 agents in parallel is common on a recent machine.
  • Status is inferred from what the CLI prints and from the agent's own end-of-turn report; a CLI update that changes its screen text can occasionally delay a status change until AgentsRoom is updated.
  • The project border takes the colour of the first thinking agent only; several simultaneous roles are not blended.
  • Cross-project reads by agents are read-only; dev commands never cross projects.
  • One folder, one row: a folder can only be opened once, and the list folds any extra row pointing at the same folder onto a single one when it loads. A row with no folder on this computer is not a duplicate, it is a repository of your account opened on another machine, and its badge names that machine ("On" followed by the computer's name).

Common questions

  • Do my agents keep running when I switch projects? Yes. Sessions live in memory with their scrollback and reattach when you come back.

  • I am in another project: how do I see that an agent is waiting for me? The tile of its project, at the top of the window, turns pulsing red, and the title bar shows a needs input pill. Click the pill: the Waiting for input list names the agent and its project; click it to land on its question. Is there a video that shows it? Yes, four agents on two projects, in the real app: https://youtu.be/zZUWXFlCP-Y

  • How many agents can I run? As many as the machine and your provider quotas allow; each agent is its own CLI process.

  • Can I change a role's colour? Roles have fixed colours so they stay recognisable everywhere; a Custom agent can carry its own colour.

  • Two agents touch the same file, what then? Enable a git worktree per agent so each works in its own copy and branch (see Git Worktrees).

  • Can an agent look at another project? Yes, read-only, through projects_list and the project argument of the read tools.

  • Why did the same project show up twice, or three times, in my sidebar? Because the same folder had been registered under more than one identity on your account, usually after a folder was re-added or a project split, and deleting the extra rows brought them back at the next launch. The list now folds the rows of one folder onto a single one by itself, on the desktop and on the phone, and deleting a duplicate no longer removes the surviving project from your account. Update, and the extra rows go on the next launch.

  • My project only exists on another computer, is that a duplicate? No. A project of your account whose folder is not on this machine is listed once with a badge naming the computer it lives on, and cannot be launched from here.

  • Do my project shortcuts follow me to another computer? Yes, they are saved on your account. A shortcut made with Cmd on a Mac uses Ctrl on Windows and Linux.

  • How do I get to the project where an agent is waiting for me without cycling through all of them? Press Cmd+Shift+J (macOS) or Ctrl+Shift+J (Windows, Linux): it opens the next project with a waiting agent, on that agent. Change the chord in Settings > Keyboard shortcuts > Next project waiting for you.

  • Cmd+3 opened a different project than the third one on screen, or Cmd+1, Cmd+2 and Cmd+3 did nothing at all. Fixed: Cmd/Ctrl+1 to 9 follow the projects as they are displayed, starting with the row of open projects at the top of the window while you work in a project, not the order projects were created in. Version 1.203.0 missed that row once it moved to the top of the window, so the numbers did nothing. Update the app.

  • I closed a project by accident, did it stop my agents? Since the confirmation was added, a project with live agents or command terminals asks before closing; Cancel stops nothing.

  • How do I know which number opens which project, or which shortcut a button has? Hold Cmd (macOS) or Ctrl (Windows, Linux) for a moment: each project shows its number and each button with a shortcut shows it. Release the key to hide them. Turn it off in Settings > Keyboard shortcuts > Show shortcuts while holding Cmd / Ctrl.

  • Can I give a project its own keyboard shortcut? Yes. Settings > Keyboard shortcuts > Jump to a project, or Project settings > Keyboard shortcuts > Open this project: click the button and press the chord (it needs Cmd, Ctrl or Alt, or a function key). Backspace while recording, or the reset icon, removes it.