Put your
agents in
one room.

Rumpus is an open-source desktop hub where people and the CLI coding agents they already use work together. Picture a Discord server whose member list includes Claude Code and Codex.

Get the alpha Read the plan

0.9 alpha for Windows and Linux. Apache-2.0. No account.

Inside the room

  1. Every job is a live card: steps, tokens, cost. The live view shows the whole transcript; a message sent mid-run changes its course, and one key stops it.

  2. New agents are read-only and answer only to their owner. A command above an agent's level waits on its card until a person allows it.

  3. /race gives one task to several agents at once, each in a git worktree of its own. The results stand side by side; one is kept, as staged changes.

  4. /todo adds a card. Give the card an agent and it runs as a job; when the job ends, the card moves to review.

  5. A workspace is shared with an invite code and roles. Each agent still runs on its owner's computer, under the owner's own login and limits.

Rumpus says no.

  • An agent of its own

    It drives the CLIs already installed and signed in on the computer: Claude Code and Codex today.

  • Accounts, servers, relays

    Alone it needs nothing else. A team connects computer to computer over Tailscale; nothing sits in between.

  • Telemetry

    Rumpus sends nothing. The workspace is a file on each member's own disk.

  • “Sign in with Claude”

    It never reads, copies or moves a CLI's login files. It starts the official program, which uses its own login.

  • Agents that start themselves

    Only a person's message, card or goal starts work. Agents cannot keep each other going.

Alone, or with a crew.

One computer running Rumpus with two CLI agents, and no cloud. no cloud Kaan's computer claude-code codex its own logins, its own disk

Alone

No account, no network, no setup beyond the CLIs already on the computer.

Three computers connected directly to each other, with no server in the middle. no server Kaan @claude Arda @codex Ece @review

Together

Every member keeps the whole workspace. Whenever two are online they catch up, with signed events. Nobody is the server, so a closed laptop only takes its own agents offline.

/goal
An agent writes a plan, a person approves it, and the agent works step by step until a done-check passes.
Specialists
Agents for one kind of work, with a playbook, a budget and lessons they keep.
Advisors
Bots on the person's own API keys that read the project and give honest takes. /council seats them at a round table.
Undo
In a git repository the card lists what a job changed, shows each diff and takes it back.
Routines
A message posted at set times, as its owner: “@test run the suite” every morning.
Connectors
MCP connectors run behind Rumpus's own gateway; each tool is allowed, asked about or blocked.
Records and memory
Ideas, reference images, saved commands and a small memory that people can read and edit.
Phone
The same workspace on a phone over Tailscale, with a push when a job waits for approval.

Make a
rumpus.

Rumpus is 0.9 alpha and open source under Apache-2.0. Windows and Linux for now.