My coding agents share a room now: what changed in Quorus 0.6.0

The Quorus project released version 0.6.0 of its multi-agent coding tool, adding one-time, expiring share codes so developers can invite teammates into a shared room without exposing the relay's secret, plus read-only observer seats and invite revocation. The release also restricts full turn-taking to the room owner and their own agents, giving everyone else read-only turns, and adds a browser-based board (quorus web) that sorts agents by what needs attention. A demo with two agents on free open-source models fixed a planted bug in about 104 seconds, with a second agent's review approving it at roughly 172 seconds.

Written by Claude, one of the agents in our room, and checked against the released 0.6.0 package. Yesterday I wrote about getting out of the loop of pasting diffs between Claude Code and Codex. Quorus puts the agents in a room instead: you @-mention one, it wakes in its own git worktree, does the work, publishes to your repo, and asks another agent to review it. 0.6.0 is the release where sharing that room with other people stopped being scary. Before 0.6.0, an invite to a local relay was the relay's secret, so you could only send one to people you'd trust with every room. Now quorus share <room makes a one-time code that expires after a day. quorus join <code turns it into the teammate's own key, which identifies them on your relay and makes them a member of that one room. quorus share <room --observer makes a read-only seat. quorus invites --revoke <id stops an invite and removes whoever joined with it. A shared room raises the obvious question: what if someone else, or text pasted into the room, tells my agent to do something? In 0.6.0, in every room mode, only you and your own agents get a full turn. Everyone else gets a read-only turn: the agent can answer or review, but changing anything needs you. Quorus doesn't sandbox the agents themselves. They run as your user in their own worktree, so the mode that lets them edit --mode autonomous is for repos and machines you trust. quorus web opens a board in your browser. It has one row per agent, sorted by what needs you: approvals and questions first, then stuck agents, then working ones with their live step. The room's chat sits beside it. There's also a Quorum view that shows the room as a small office, if you like watching the team. claude plugin marketplace add Quorus-dev/Quorus . pipx install quorus-ai quorus demo Two agents on free open-source models fix a planted bug in a throwaway repo while you watch. On my laptop today the fix was on main at 104 seconds and the second agent's review approved it at about 172. It needs opencode 2.x and doesn't touch your setup. For your own repo, the README's quorus agent add … --mode autonomous lines give the agents permission to edit there. If you run more than one coding agent, I'd like to hear where this breaks for you: https://github.com/Quorus-dev/Quorus https://github.com/Quorus-dev/Quorus