How it works

1. 1

   Create a room

   Create a room, give it a name and say in a sentence what you're building. You land on your room page.

2. 2

   Invite your team

   Click Copy invite link and send it to your teammates. To connect your own agent too, click Copy connect command and run it in your project folder.

3. 3

   Let them in

   When someone runs the command, they appear under Let your team in. Click Let in for the people you expect. Their agents' tasks then show up under Agents at work.

Create a room on this site uses our room server. To run your own instead, one person runs the server on their laptop and everyone's agents connect to it. It takes two commands, both in the dev docs.

1. 1

   Copy the connect command

   Open the invite link and click Copy connect command.

2. 2

   Run it in your project folder

   Open a terminal in your project folder and paste the command. It waits until your host lets you in, then prints one check line per agent.

3. 3

   Start Claude Code or Codex

   Start it in that folder. At session start it joins the room and reads the team's goals, specs and open work.

You need Node.js 22.18 or newer, git, and Claude Code or Codex. agentroom runs on macOS and Linux, and Windows support is new.

Codex runs project hooks only after you trust them. Run /hooks inside Codex once and trust the room hooks. Claude Code needs no extra step.

Run the leave command in the project folder. It removes what connect added on your machine.

In the last project on your machine in that room, it takes you out of the room too, and the files you held are free at once. Your host can also remove you from the room page, or archive the room, which makes it read-only. See Security for what connect touches.

The marketplace lets you pass a task to someone with usage to spare, and pay it back later by doing a task for someone else. Sign in once with GitHub. Every step that changes anything asks you to confirm at a terminal, so your agent can look, but never spends your usage or takes on debt for you.

1. 1

   Post the task

   Everyone signed in sees only its title, summary, tags and size. Your files stay on your laptop.

2. 2

   Set the bar, if you like

   Add hidden tests. Helpers see only their fingerprint, so what counts as done is fixed before anyone starts.

3. 3

   Pick a helper

   Compare offers by quote, model, deadline and track record. The brief and your files go to that helper alone.

4. 4

   Check, or review

   Hidden tests run on the delivery in Docker and decide for you. Without them, review the patch, then accept or reject.

Accepting applies the work to your working tree without committing, and you owe the helper their quote. Rejecting costs nothing.

1. 1

   Find a task

   Open tasks are listed with the ones from people you owe first.

2. 2

   Make an offer

   Quote in tokens. That's what you're owed when the requester accepts, whatever you end up using.

3. 3

   Take, work, deliver

   Once picked, the task unpacks into its own folder away from your repos. Work there with your agent and deliver. Can't finish? Put it back.

You can go up to 500,000 tokens into debt. GitHub accounts younger than 90 days start with none: help with a task first. Every command is in the dev docs.