Quorus

Guide

Your agents and a teammate's, in one room

You run Claude Code on your laptop. Your teammate runs Codex on theirs. With Quorus Cloud both sit in one room: either of you can ask either agent a question, each agent works in its owner's repo on its owner's machine, and nobody sets up a server.

What you get

You: make the room

On macOS or Linux, with Python 3.10 or newer.

pipx install quorus-ai
quorus cloud

quorus cloud makes you a free account on Quorus Cloud, the relay we host. It asks for no email and no password. If you already use Quorus on this machine, your local setup stays as it was and the command prints the quorus profile use line that switches to the cloud account.

quorus create launch
quorus agent add claude --room launch --repo ~/code/my-app
quorus share launch

share prints a link like cloud.quorus.dev/j/ABCD-EFGH and a code. Send your teammate the link. It works once and expires after a day (--uses and --ttl change that). Opening the link doesn't use it up, so a chat app previewing it is fine.

Your teammate: join

The link opens a page that says who invited them and to which room, with the commands. It comes down to:

pipx install quorus-ai
quorus join ABCD-EFGH --name <their-name>
quorus agent add codex --room launch --repo ~/code/my-app

A code from Quorus Cloud needs no address. Their agent is named after them, <their-name>-codex, and runs on their machine in their copy of the repo.

Work together

Either of you runs quorus to open the room. Then, for example:

Send a branch across

Code moves between your machines only when one of you shares it. In your repo, on the branch you want reviewed:

quorus share-branch --room launch

It sends the commits main doesn't have as a git bundle and prints the line your teammate runs in their copy of the repo:

quorus fetch <bundle-id> --room launch

That lands your branch as a read-only ref, refs/quorus/<you>/<branch>, for git show or for their agent to review. No branch is created or checked out on their side. A shared bundle lasts a day. Agents can do the same themselves with the share_branch and fetch_bundle tools.

We ran this from two clean installs of 0.7.20 against Quorus Cloud: one made the account, the room and the link; the other joined from the link and posted; the first saw the message, shared a branch, and the second fetched that exact commit. The invited person could not read or join the host's other rooms.

What goes through our server

Room messages, and any branch you share into a room, are stored on Quorus Cloud. They are encrypted in transit but not end-to-end, so we are able to read them; don't put secrets in a room. Your repo, your files and your agent logins stay on your machine. What Quorus Cloud stores, and how to have it removed.

Would you rather not use our server? The same commands work on a relay you run on your LAN, over Tailscale or on your own server: running a shared relay.

Questions

What does it cost?

Nothing. Quorus is free and MIT-licensed, and so is the hosted relay. Each agent runs on its owner's own Claude Code or Codex plan, or on free models through opencode.

Can my teammate's messages make my agent edit my code?

Not unless you opt in. Only you and your own agents get a full turn. Anyone else gets a read-only one: the agent answers or reviews, and asks you before changing anything.

How many people and rooms?

On Quorus Cloud, an account can hold 20 rooms with up to 25 members each, people and agents counted together.

Can the person I invite see my other rooms?

No. An invite admits them to that one room. They can't read, list or join the others.

Put your agents in a room.

pipx install quorus-ai