Everything AgentsRoom does for you
Each feature is built to save you time and keep you in control. Browse them all below.
See every feature in action
Each feature below ships with a short video walkthrough. Click the play button on any card to start watching.
Run a fleet of agents
Many projects, many AI agents, one window
The visual cockpit to drive Claude, Codex, GitHub Copilot CLI, Cursor and 10 other agent CLIs in parallel across all your projects at the same time. Color-coded roles (DevOps orange, Frontend cyan, QA red, Architect blue), animated status dot on every agent card, working/done counters per project, pulsing red flag the moment an agent gets stuck. You know in one second which agent is working on which project, which one finished, which one needs your reply. No more 12 terminal tabs, no more guessing where you left off. The multi-project, multi-agent grid your Claude Code sessions always deserved.
“cannot find my old exports”
support chat“export is buried in a submenu”
public form“please add dark mode”
demoted ticketThe idea board that sorts your user feedback
Throw support messages, feature requests and half-formed notes into the Radar and they come back grouped by theme, deduplicated, and counted by the number of people who asked. Read the same corpus four ways: themes, impact/effort matrix, opportunity solution tree, semantic map. Users vote and comment on the public board, an AI product manager proposes the next ticket, and a ripe idea becomes a backlog ticket while a ticket you will not build goes back to being an idea.
Drag a task, spawn an agent
Kanban board for your AI agents. Create tasks, drag them to In Progress, and an agent starts working immediately. Track every feature visually: who does what, what is done, what is next.
Your clients drive the backlog, your agents ship it
Expose your project backlog as a public or private feedback portal. Clients submit bugs, request features, upvote tickets, leave comments, and every ticket lands directly in the same AgentsRoom backlog your AI agents execute against. Feedback-driven AI development, widget + Chrome extension included.
“Add a button somewhere on the profile screen”
Scope this ideaScope fuzzy feedback into a mockup before you build
One click on a feedback ticket spawns a Product Manager AI agent that reads your codebase and builds a mockup faithful to your real product, with the requested change in context. Validate the idea and clarify it in a two-way conversation on the same ticket, all before any development starts. Scoping never starts the task and never sends a notification.
Agent Teams: a real tech crew, scripted
Chain your AI agents like a real engineering team. Drop nodes on a visual canvas (Dev, QA, PM, Security, DevOps), connect them, and AgentsRoom orchestrates the handoff: feature summary, diff, risks, test hints. Pick how the roles run: one agent that morphs from role to role and keeps the whole context, or one live agent per role that talk to each other while they work, in any direction. Conditional edges, feedback loops, max-cycles guard. The n8n-style workflow editor your AI dev team was missing.
Recipient busy, message held
Your agents write to each other, from any CLI
The saved agents of a project become permanent members with a real address and a real inbox. Any of them can write to another, whatever CLI it runs on, and the message is stored on disk before delivery is even attempted. An agent that is offline, a CLI that crashes or an app restart never loses one: it waits, and it arrives, with a receipt that says it was actually read.
Agent Morphing: switch roles, keep the context
Change your running agent's role on the fly. PM becomes Fullstack Developer becomes QA, in the same session, with the full conversation context preserved: no respawn, no re-explaining. Morph into any of the 14 built-in roles, The Agency experts or community agents, with a fresh eyes option for critical reviews and a morph trail of every role the agent has been. One agent, a whole team, whatever CLI agent you run.
- read auth/session.ts
- ruled out the cookie approach
- trying the token refresh
Fork an agent, keep the whole conversation
One click on a running AI agent creates a twin that already has its entire conversation: same role, same CLI, same model, same context. On Claude, Codex and Grok it is the CLI's own fork of the session; everywhere else the twin starts fresh with the parent's transcript handed to it, and the app says so on screen. Run both consoles in parallel on separate conversations, or open the Ask bubble in the composer to put a question to a read-only copy of the agent, answered in streaming while its terminal keeps working and its history stays untouched.
Build, share and install AI coding agents
AgentsRoom is not one assistant, it is a whole roster of agents. Start with 14 built-in roles, add specialist agents from The Agency, or build your own custom agent with its own system prompt. Then share an agent with a teammate in one drag through the chat, or publish it to the community so everyone levels up together. Every agent works with Claude, Codex, GitHub Copilot CLI, Cursor or any of the 10 other agent CLIs AgentsRoom supports.
Describe the task, get the right agent
Not sure which agent to use? Type what you want to do and AgentsRoom suggests the best-suited agent: from your room, the built-in roles or 260+ catalog experts, each pick with a one-line reason. One click adds it, opens its terminal and pre-fills your task.
Schedule your AI agents like a cron, without the cron
Scheduled Tasks runs your AI coding agents on a recurring schedule, with no cron expression to write. Program a Claude Code or Codex session to review pull requests every morning at 8 and again at 6, scan crash logs every night, check dependencies every Monday or ship a weekly changelog. Pick a frequency (every N minutes, hourly, daily at one or several times of day, weekly, monthly, or on your AI plan's quota window), a prompt and an agent role. Each run spawns a background agent in your project, sends you a notification, catches up missed runs on the next launch and keeps a reopenable history. A cron alternative built for recurring AI development workflows, provider-agnostic across Claude Code, Codex and Antigravity.
Your agent starts when something actually happens
Webhook Triggers start an AI coding agent on an outside event instead of a clock. Each trigger gets a public URL and a signing secret you paste into GitHub, GitLab, Slack, Linear, Sentry or any service that can POST JSON. A pull request opens, a build breaks, a crash is reported, and the agent is already reading it. The signature is verified, an optional filter decides what deserves a run, a burst limit keeps a noisy service from starting twenty agents, and the payload becomes prompt variables. An event that lands while the app is closed is queued and replayed on the next launch, and with several machines only one takes it. Event-driven automation for developers, without a polling loop burning tokens on the answer no.
Your dev agent delegates the test to a cheaper QA agent
When a feature is done, the dev agent (Claude Opus, Codex) calls a single MCP tool and hands the validation off to an ephemeral QA agent running on a cheaper model (Claude Haiku, Codex mini). The QA agent drives the embedded browser, asserts the result and reports a clean pass or fail. You stop paying premium prices for browser clicks, and you stop bloating the dev agent's context with screenshots and DOM dumps. The right model at the right price for each step.
Talk to your agents your way
Draw it, and the agent sees what you mean
Sketch is a drawing canvas built into the agent composer. Open a blank canvas to sketch a mockup or a diagram, or open a screenshot to annotate it: circle the bug, draw an arrow, highlight the region. The drawing is attached to your message and sent to your AI coding agent. A picture is worth a thousand words, so stop describing the visual bug and draw it, without ever leaving the terminal.
Screenshot to agent, in one shortcut
Send a screenshot to your AI coding agent without ever leaving the keyboard. Hit the configurable shortcut (Cmd+Shift+2 by default, Ctrl+Shift+2 on Windows and Linux) or the composer's screenshot button, drag a box around the bug, and the screen capture attaches itself to your message. No external screenshot app, no saving the file to disk, no dragging it into the composer. Capture the screen region, the agent sees it, you keep your flow.
Dictate your prompts, your agent codes
Voice dictation is built right into the agent composer. Click the microphone, speak your prompt, and the speech-to-text transcription drops into the draft at your cursor. No separate dictation app, no copy-paste between windows. There is no transcription model to pick, it is chosen from the length of your recording, dictate in any of 19 languages plus auto-detect, and watch a live voice waveform while you record. On mobile, speech recognition runs on-device and the text is relayed to your focused desktop agent. Typing a long, precise prompt takes minutes, dictating it takes seconds: more context to your agent, fewer clarification round-trips, fewer wasted tokens. Nothing is sent automatically, the transcript lands in the draft so you review, edit and send with Enter. Voice dictation for Claude, Codex, GitHub Copilot CLI, Cursor and 10 other agent CLIs, the fastest way to write a precise prompt.
Talk to your agents, hear them talk back
Voice Mode is a two-way voice conversation with your AI coding agent. Tap once, speak, and the agent answers out loud in a natural voice, no typing, no reading walls of terminal output. Turn on hands-free and it keeps listening for your next turn, so you can pace the room, sip your coffee, or watch the build while you talk through the plan. You ask where the refactor stands, it tells you. You say run the tests and report back, it does and speaks the result. Pick the reply voice (alloy and more), keep a beep cue between turns, and let language auto-detect so you speak in your own words. Voice Mode runs on the AgentsRoom backend (speech-to-text in, text-to-speech out) and works the same with Claude, Codex, GitHub Copilot CLI, Cursor and 10 other agent CLIs. It is the most natural way to stay in the loop with a long-running agent without being chained to the keyboard.
Voice credits are now shared between dictation, Voice Mode and Read Aloud.
The terminal selection panel gains a Listen button for anything you highlight.
The status bar keeps a control chip for as long as a read is playing.
Listen to your docs instead of reading them
Read Aloud is text to speech built into AgentsRoom. Click the speaker in the markdown preview and a README, a spec or a three-hundred-line changelog is read out loud in a natural synthetic voice. Highlight anything in a terminal and hit Listen. Right-click to hear your agent's last answer, pulled from its conversation transcript rather than scraped off the screen. Code blocks, markdown tables and bare file paths are stripped before a single word is spoken, so you hear prose and not punctuation. In a hurry? The same button offers a condensed read: an AI summary is written first and that summary is what you hear, sized to a spoken length you pick, ten seconds, thirty or a minute. A forty-minute changelog answered in ten seconds. Progress bar, time left, pause, resume and a control chip in the status bar that outlives the window you started from. It came from a dyslexic developer who was copy-pasting our markdown preview into an external text-to-speech tool, and it earns its keep on tired eyes too.
Stack your messages, send them in order
A message queue built into the composer. Stack several prompts above the input and send them to your AI agent one at a time, in the order you choose, instead of one overloaded mega-prompt. Each queued message gets a short AI-generated title and keeps its screenshots and attachments. Drag to reorder, reopen to edit, send on demand. A queued message can also carry a clock, or follow your subscription instead of the wall clock: send it the moment the quota comes back, or shortly before a 5-hour, daily, weekly or monthly window resets, so a long code review runs on the credits that were about to expire.
Your phone, a remote for your AI agents
The Mobile Companion turns your phone into a remote for your desktop AI agents. Dictate a prompt or attach a file to the focused composer over the end-to-end encrypted relay. Share screenshots from any iOS or Android app and choose their project, with the current project selected, then send to an agent or save in its backlog. A closed agent starts automatically. Backlog photos are stored with the task in your account, even when the desktop is off. Works with Claude Code, Codex CLI and other supported providers.
Your personal assistant, one sentence away from your phone
The assistant is the one agent of your AgentsRoom account you can reach from anywhere. Say "Talk to Bot" to Siri, press the iPhone Action button, tap an Android widget or tile, the Assistant tab of the app, or share a text to it: the app opens the assistant's screen with the microphone already listening, transcribes what you said with the AgentsRoom speech-to-text into the composer in case a name came out wrong, and sends it over the end-to-end encrypted relay to your desktop. There, the assistant runs through the agent CLI you already use, with your MCP connectors (mail, calendar, messaging) and the AgentsRoom tools that reach every project: it reads and files backlog tickets anywhere, launches an agent on one, drafts a reply in your voice, and confirms before anything visible to someone else. It starts a fresh conversation every day and, if you allow it, remembers you in a private memory of its own that your project agents never see. The answer comes back as a push, and when a long task ends the desktop calls you by your first name. Called "Personal assistant" by default, renamable, custom avatar, one settings page on both screens.
Save and reuse your best prompts
Organize prompts in folders, per project. Share them with your team via git. Keep personal prompts private with automatic gitignore. Send any prompt to an agent in one click.
Modular procedures, any runtime
Save Claude SKILL.md skills, attach them to tasks or agents, and export to Cursor, Codex, Windsurf or Aider on demand. Trigger-based routing means the right procedure loads automatically.
The shared brain of your codebase
Your agents write down what they learn: decisions, architecture, pitfalls, conventions. It survives the session, and every agent and teammate on the project reads the same memory.
Write your prompt like you write an email
A prompt editor pinned to the AgentsRoom footer. Draft long, structured prompts for your AI agents in a real text area. Your draft is always there when you come back, even after you quit the app. One click sends the whole thing to the focused agent, and one click saves a good draft as a reusable prompt for your team.
Prompts that call other prompts
A prompt in your library can link to other prompts and pull their content in when it runs. Write the shared rules once (your stack, your conventions, your review checklist), then reference them from every task prompt instead of copying them again and drifting. Chains resolve at send time, so the agent receives one complete brief, and updating the shared block updates every prompt that inherits it.
From a Figma frame to shipped UI
Capture any frame straight from the Figma canvas with the AgentsRoom Chrome extension, drop it on a backlog ticket or an agent prompt, and let the agent build it against your real components. The design travels as an image plus your written intent, so nothing depends on a Figma MCP server being up, authenticated or compatible with your file. The capture stays attached to the ticket, so the agent that picks it up later still sees exactly what was asked.
Stay in control, in real time
See every agent at once, side by side
Split your workspace into multiple panes and watch several AI coding agents work at the same time, side by side. Drag one agent's terminal onto another and drop it on an edge: left or right splits into columns, top or bottom stacks into rows, iTerm2 style. Switch the whole layout between horizontal and vertical in one click. Each pane keeps its agent's role color, avatar and live status, the focused pane gets a highlight ring, and your split layout is restored exactly when you reopen the app. Run Claude Code on the backend in one pane, Codex on the frontend in another, a Antigravity QA agent in a third, and keep an eye on all of them without ever tab-hopping. The multi-pane split screen your parallel agents were missing.
See who is working, right now
Color-coded status indicators on every agent card. Yellow pulsing dot when thinking, green when done, red when waiting for your input. Elapsed time and current activity displayed in real time.
Your agents' status, always in sight
A floating, always-on-top island shows whether your Claude Code, Codex and Antigravity agents are idle, working or waiting for input, even when AgentsRoom is in the background. When an agent finishes, a notification surges next to the island. Click it and you land straight on the right agent in the right project. Stop alt-tabbing to check.
Catch an AI agent before it starts hallucinating
AgentsRoom watches a built-in canary on every agent: the one-line status each agent writes at the end of every turn. When an agent stops updating it for two turns in a row, that is the classic early sign of context rot and degradation, so AgentsRoom raises a warning above the terminal before the hallucinations begin. One click restarts the agent on a clean context, and a tip reminds you to compact the conversation. Works with Claude Code, Codex and every provider.
The runaway process finder for AI coding agents
An AI agent spawns a real system process for every tool call it makes: a search, a build, a script. Most finish in seconds, some never do, and those keep holding gigabytes of RAM at 0% CPU until the machine crawls. On one measured session, seven stuck processes claimed 41.8 GB on a 16 GB laptop, swap sat at 95%, and ending them returned 15.5 GB instantly. Process Guard sweeps the child processes of your agents once a minute and flags one only when it is large, old AND idle on the processor, so a real build is never mistaken for a stuck one. It measures the true memory footprint, compressed and swapped-out pages included, because a stuck process can show 20 MB while holding 8 GB. Orphaned processes that outlived their agent are caught too. Your dev command terminals, the shell and the agent CLI itself are never touched, and nothing is terminated unless you ask.
The right AI model for every task, picked automatically
Adaptive Mode reads your prompt before you send the first message and suggests the most cost-effective model for the job. A quick fix or a translation routes to a light, cheap model like Claude Haiku; a deep refactor or an architecture design routes to a heavyweight like Claude Opus. One click applies it, live-switching a running session or saving it for next launch. Works with Claude, Codex and Antigravity. Stop overpaying with a flagship model on trivial tasks: spend less per task and run more tasks per day on the same plan.
Know exactly which agent finished
Unread indicators per project and per agent, like a messaging app. Desktop and mobile push notifications when an agent completes or needs input. No more guessing.
Per-session Claude Code token usage, live, with cache hit rate
Every Claude agent terminal in AgentsRoom shows a live Claude Code token usage meter. The badge turns red on heavy consumption. Click it to open the session monitor : input tokens, output tokens, cache writes, cache reads, cache hit rate, message count, models routed, session duration, plus contextual tips to lower your token consumption. All local, read straight from ~/.claude/projects/ JSONL.
Project statistics: time, prompts and cost per project
Open the project statistics panel on any project and read time open, active and idle time, average active agents, prompts, agents opened, tokens and cost. A per-day activity chart and a per-agent breakdown table turn raw agent work into project analytics for billing, retros and cost control.
Current week (all models) is at 76% (alert set at 75%). Resets Sep 24, 04:00
A notification before the usage limit, not after
AgentsRoom reads the quota bars Claude Code, Codex, GitHub Copilot CLI, Grok Build, Kimi Code, Cursor, Antigravity, OpenCode Go and the Z.AI Coding Plan publish, session, weekly, per model or per limit group, for every account you are signed in to, and puts a bell next to each one. When a bar crosses a threshold, 50% and then 75% by default, you get a native desktop notification, a push in the AgentsRoom mobile app, or both. Right-click a bell to pick thresholds for that bar or mute it. The reminder is sent once per quota window and rearmed at the reset, so an 80% bar is one banner, not one every refresh.
Review and validate the work
Every commit keeps the conversation that wrote it
AI agents have no memory between sessions, so the reasoning behind a commit usually dies when the terminal closes. Commit Context attaches the full agent conversation behind each commit as an unlisted gist and adds an Agent-Conversation link to the commit message. The next agent or teammate opens that link and recovers the why behind the change: the prompts, the decisions, the constraints, the edits. Context is the value an agent needs to be precise, so AgentsRoom keeps it attached to your git history. Secrets are redacted before upload, the link is unlisted, and you can also create gists by hand on gist.agentsroom.dev. Works with Claude Code, Codex, GitHub Copilot CLI, Cursor and 10 other agent CLIs.
Commit messages written from your real diff
Stop typing "wip". Click the sparkle on the commit field and AgentsRoom reads the git diff of the files you are committing, then writes one clean message in Conventional Commits format. Type a rough draft like "fix temp pdf", get it back as a proper commit message. Your team's format rules, set once per project, are applied on every generation.
Diff per agent & task
When multiple agents work in parallel, filter code changes by agent. See only one agent's modifications, review their diffs in isolation, and commit each contribution separately. Clean git history, zero confusion.
Your agents click, type and test the browser
AgentsRoom ships a built-in browser inside every project, plus an AgentsRoom Browser MCP server. Your QA agent navigates your localhost site, clicks, types, takes screenshots, reads console logs and verifies the feature is actually working before handing off. Real browser automation for Claude Code, no Playwright config to write.
Review all changes, file by file
Navigate every file modified by your AI agents with arrow keys. See side-by-side diffs with syntax highlighting. Ask Claude questions about any change. Commit when you are ready.
Your dev environment
Share localhost with a public HTTPS URL
Expose your local dev server to the internet instantly. Pick a custom subdomain, get a public HTTPS link, and share your work with anyone, no deploy needed. Free ngrok alternative built into AgentsRoom.
browser_select_target "Chrome · Pro"browser_select_target "Chrome · Personal"browser_navigatebrowser_clickbrowser_screenshotYour agents drive your real Chrome, one target per account
The AgentsRoom extension turns each Chrome profile into a named browser your agents can drive: Pro, Personal, Client, each with its own cookies and signed-in accounts. An agent picks its target by name, opens a fresh tab there and clicks, types, reads the console and takes screenshots, while another agent works on another account at the same time. The Chrome can sit on another machine of yours: the extension talks to the AgentsRoom relay, end-to-end encrypted, the same transport the mobile app uses. It is an MCP server, so Claude Code, Codex, GitHub Copilot CLI, Cursor and 10 other agent CLIs get the same tools. The embedded browser stays the default target.
A project terminal you drive from your pocket
A real per-project terminal manager built into AgentsRoom. Remember every command (backend, frontend, mobile bundler, Docker, worker, database) and launch them in one click. Detach the window onto a second monitor, or trigger commands from mobile over 4G/5G : your computer becomes a dev server you drive remotely. The modern alternative to iTerm2, Warp, Ghostty, Kitty, Alacritty, WezTerm, Hyper, Tabby and Terminal.app, designed for project work.
One search bar for everything in your project
AgentsRoom holds your agents, your skills, your prompts, your scheduled agents and webhook triggers, your backlog, your dev commands, your SSH and database connections, and the repository itself. The command palette searches all of it from one field, opened with Cmd K on macOS or Ctrl K on Windows and Linux. Matching is fuzzy, so missing letters and missing accents still find what you meant, and results come back grouped by category instead of one flat list. A prefix character narrows a search to a single source, the arrow keys move, Enter opens, Escape puts you back where you were. Files honour .gitignore, commits come from the branch you are on, and the index is built in the background the first time you open the palette, never while the app is launching. Nothing you type is sent to a server.
Restore agents and terminals on next launch
Quit AgentsRoom at the end of the day, choose to restore agents and terminals tomorrow, and reopen the app the next morning to find every AI agent, every dev terminal, every long-running dev server and every working directory exactly where you left them. One checkbox on quit, one click on launch, zero friction. Pick up where you left off and start coding in seconds instead of rebuilding your environment for an hour.
An IDE your AI agents can pilot, not just chat with
Four MCP servers (Backlog MCP, Terminal Commands MCP, Prompt Library MCP, Browser MCP) expose the AgentsRoom IDE itself to Claude, Codex, GitHub Copilot CLI, Cursor and 10 other agent CLIs. Agents can read and update the backlog, reply to public backlog tickets, run saved dev commands (and create new ones), reuse or save prompts, and drive the embedded browser to verify their work. Manual when you want, automated when you don't. The unique edge that turns AgentsRoom into an agent-controllable IDE.
Run your agents straight on a remote server, over SSH
AgentsRoom is an SSH connection manager and a built-in SSH terminal in one. Save your VPS and remote servers once, connect with an SSH key or a password, then run Claude Code, Codex or Antigravity CLI directly on the remote machine, no separate SSH client to open. Pin a connection per project so a project that lives on a remote box always opens its terminal over the right SSH connection. Run heavy builds, GPU jobs or long-lived agents on a powerful server while you keep the same cockpit, status tracking and notifications on your laptop.
Secrets your agents can use but never read
API keys, tokens and passwords live in a machine-local vault encrypted through your OS keychain, in a single file written owner-only and atomically. You reference a secret by name, and AgentsRoom resolves it at launch, in the main process, into the environment of the command being started. An agent can list the names and ask for one to be injected, and there is no code path that returns a value to an agent, to the interface or over MCP. Nothing is synced to a server, and a machine without a usable keychain gets a refusal rather than a file in clear text.
Let agents query your databases, read-only by default
Save your MySQL, PostgreSQL and MongoDB connections with host, port, user, database and TLS, then reach the ones that are not publicly exposed through an SSH tunnel or an AWS SSM port-forwarding session built on the connections you already saved. Every connection starts read-only : a write needs both a writable connection and an explicit confirmation, and a connection flagged as production makes that confirmation harder. One statement per call, stacked statements refused, result sets capped. Agents query over MCP by naming a connection, so the password never reaches them. Your connections follow your account from one machine to the next, and a database can be exported to a file, imported back, or copied straight onto another server, with a backup of the target taken first.
Reach an RDS database in a private subnet, without a bastion
Your Amazon RDS instance has no public endpoint, no inbound SSH and a security group that only lets the application in. AgentsRoom reaches it through an AWS Systems Manager port-forwarding session : it asks the operating system for a free loopback port, runs aws ssm start-session with the AWS-StartPortForwardingSessionToRemoteHost document through a managed EC2 node, and waits until that port really accepts a TCP connection before connecting its database client. No bastion host to patch, no VPN to provision, no endpoint and password copied into a chat message. Authorization comes from the AWS profile already configured on your machine, so no key is stored by the app, and the forwarded port is bound to 127.0.0.1 only. MySQL, PostgreSQL and MongoDB, so RDS MySQL, RDS PostgreSQL, Aurora and DocumentDB.
$ curl POST /api/dev-inboxes/…/push
{"title":"Deploy finished"}
202 Accepted
Deploy finished
api v2.4 is live in production
Push notifications from cURL
Send a push notification to your iPhone or Android phone with one cURL call from a deploy script, a CI job or a cron task. Send-only revocable keys, no duplicates on retries, works with your computer off.
cron@billing-api06:00
Nightly invoicing report
412 invoices sent, 0 failed
A developer email inbox per project
Give each project its own receiving email address for service alerts, cron reports and app emails. Plain-text reading on desktop and mobile, revocable address, optional sharing with your team.
Know why your agent CLI would not start
An agent CLI that dies at launch usually says nothing useful, and the cause is buried in a command you never typed. AgentsRoom records the exact command it ran, tags every flag with the setting that injected it, reads what the CLI printed, and answers in plain language: what broke, and the ordered steps to fix it. Deterministic checks like a missing binary or a rejected flag are answered instantly without any AI call, redaction happens on your machine, and nothing is ever executed for you.
Bring your GitHub and GitLab repositories in
Connect GitHub or GitLab once, see the repositories you actually have access to, tick the ones you want and clone them in a single pass. Each one lands as a project with its path already set, ready to receive agents. Authenticate with a token or reuse the gh or glab session already signed in on your machine, point at your own self-hosted GitLab host if you have one, and keep everything local: the token is encrypted on disk and clone credentials are never written into your git config.
Anywhere, with any agent
Control your agents from your phone
Start agents, type in the terminal, send prompts, and monitor progress from your iPhone or Android. Real-time sync with end-to-end encryption between your desktop and your mobile device.
3 agents working
- BackendRate limiting on the API12 min
- FrontendDark mode for settings7 min
- QACheckout end-to-end tests3 min
Every agent you run, on your lock screen
One Live Activity for your whole room of AI coding agents, whatever the CLI and whatever the computer: a status ring with each agent, its task and a live timer, on the iPhone lock screen, in the Dynamic Island, on Apple Watch and in StandBy. When an agent needs you, its question comes first, and on iPhone that is the only update that plays a sound. Answer a Claude Code question or permission request from the lock screen, behind Face ID. When the room goes quiet, a summary card shows the duration, the agents, the files and the lines changed. Names, tasks and questions are end-to-end encrypted. Home and lock screen widgets, a quota widget, and a live notification with a Live Update on Android. Free for everyone.
Switch between Claude, Codex, GitHub Copilot CLI, Cursor & 10 other agent CLIs
Use 14 AI coding providers in the same project. Pick a provider per agent, switch mid-conversation, and keep your full context with automatic handoff. Claude, Codex, GitHub Copilot CLI, OpenCode, Antigravity CLI, Aider, Grok Build, Mistral Vibe, Kimi Code, Amp, oh-my-pi, Freebuff, Devin, Cursor: all in one app.
Several Claude Code accounts, one app, zero shell gymnastics
Use a Work Claude account, a Personal one, a client account, all at the same time in AgentsRoom. Pin one account per project, override per agent. Sign in directly from the Settings panel, no terminal trick required. Compatible with CCS profiles too.
Several Codex accounts, one app, zero shell gymnastics
Use a Work Codex account, a Personal one, a client account, all at the same time in AgentsRoom. Pin one account per project, override per agent. Sign in via codex login directly from the Settings panel, no terminal trick required.
GROK_HOME~/.grok-work~/.grokSeveral Grok accounts, one app, zero logout
Use a work Grok Build account, a personal one and a client account at the same time in AgentsRoom. Pin one account per project or per folder, override per agent. Sign in with grok login straight from the Settings panel, no GROK_HOME to export by hand.
CURSOR_CONFIG_DIR~/.cursor-work~/.cursorSeveral Cursor accounts, one app, zero logout
Use a work Cursor account, a personal one and a client account at the same time in AgentsRoom. Pin one account per project or per folder, override per agent. Sign in with cursor-agent login straight from the Settings panel, no CURSOR_CONFIG_DIR to export by hand.
Hit a usage limit, keep working
When the Claude, Codex or Grok Build account an agent runs on reaches the quota threshold you set, a quota rule hands the work to another account you are already signed in to and it carries on: the same session with its full context, no restart and no waiting for the 5-hour or weekly window to reset. The exhausted account is benched until its quota comes back, then rejoins the pool by itself. It turns several smaller subscriptions into something that behaves like one much bigger plan, and it keeps unattended runs alive: a scheduled task at 2am no longer dies silently at the limit.
Use Claude Code and Codex together, on both quotas
A quota rule shares your new agents between Claude Code and Codex, or between two Claude accounts, in turn: one ticket out of two, or 10% of the Claude session then 10% of the Codex week. Agents already running keep their tool, a full provider skips its turn, and the rule can be limited to the backlog tickets of one project. Other rules act at a threshold: switch to Codex when Claude is almost full, use a lighter model, block or redirect launches, run a trigger, or move running agents to another account.
A task runs while your computer is off
Trigger a coding task from the desktop app or from your phone, and it runs on a disposable machine in the cloud instead of your laptop. A cloud agent is a job, not a remote session: the machine clones the repository, runs Claude or Codex headless, commits, pushes a dedicated branch and writes a report, then destroys itself. Since the meeting point is git, nothing on your side has to stay awake, so a user report can land on your public backlog, become a cloud run started from the backlog tab of your phone, and reach production through your own CI/CD without a single computer of yours being switched on. When the run ends you validate the branch, relaunch it in the cloud, or continue locally in a normal session with the context already filled in.
Every project, every machine, one window
You do not code on a single computer anymore. There is the office desktop, the laptop at home, maybe a build server in the corner. Remote Fleet links them into one unified view so every project and every Claude, Codex or Antigravity agent shows up in a single window, whichever machine it actually runs on. Each machine keeps running its agents locally, and the fleet view aggregates their status, terminals and projects. Cross-device orchestration travels over an exclusive end-to-end encrypted relay, so your code and your agent output never leave your machines in the clear.
Take over a running agent from your phone
The agent keeps running on your desktop, through its own CLI, on your machine. Your phone becomes the remote: read the terminal as it streams, answer a permission prompt, send the next instruction, fire a saved prompt, move a backlog ticket, open a tunneled dev server in the phone browser. Push notifications tell you the moment an agent finishes or gets stuck waiting for you, so a long task no longer chains you to the desk. Everything travels over the AgentsRoom end-to-end encrypted relay.