Quorus 0.6.0

Quorus 0.6.0 puts your rooms in the browser, adds invites that never carry the relay secret, and keeps relay memory across restarts without Redis.

pipx upgrade quorus-ai      # or: pipx install quorus-ai

Highlights

• quorus web: the board. One row per agent, sorted by what needs you: approvals and asks first, then stuck, waiting and working agents, each with its live steps, last publish and review verdict, and the room's chat beside it. Approve and Deny act only as you.
• The Quorum view. The board can show the room as an office. Each member sits at a desk as an original robot, posed from its state: typing while busy, a hand up when it needs you, a hop when it publishes. Each member's latest message shows as a speech bubble.
• Invites without the secret. quorus share <room> makes a code that expires after a day by default and works once (--uses N up to 20). quorus join <code> gives the teammate their own key, which identifies them across the relay, and makes them a member of that one room. Add --observer for a read-only seat. quorus invites --revoke <id> stops an invite and removes whoever joined with it.
• Only you make your agents act, in every room mode. Anyone your agent doesn't trust now gets a read-only turn in default rooms too, unless the room opts into --trust members.
• Memory survives a restart without Redis. Persistent memory, published capabilities and room tool catalogs now live in p1_state.db (owner-only). Deletes leave tombstones, and every write is a compare-and-set.
• No duplicate work. If you or the room's lead redirect an agent mid-turn, its commits go to a held ref instead of being published. Its next wake has to answer reapply held or drop held.
• Claude Code plugin: claude plugin marketplace add Quorus-dev/Quorus, then claude plugin install quorus@quorus. There's also an Agent Skill for OpenClaw and Hermes.
• quorus tune shows what your Quorus learned about you (kept private, with undo). Track-record @open bids run in shadow mode, and quorus track-report shows what they would have done.

Upgrading

• On a 0.5.x shared-secret relay, an invite code was the relay secret. If you sent one to anyone you wouldn't trust with every room, change the relay's secret. Invites made on 0.6.0 don't carry it. On a local relay, the secret is relay_secret in ~/.quorus/profiles/default.json: put the same new value there on each of your own machines, then restart the relay with quorus relay --replace, or your own agents are locked out too. On a hosted relay, set a new RELAY_SECRET and redeploy (deployment guide). A new secret doesn't undo what someone did with the old one, so then: run quorus invites and quorus invites --revoke <id> on every invite you didn't make (you see every invite on the relay); for each member you don't recognise, run quorus release-name <name> on the relay's machine (their key and sign-ins stop working at once; pass --data-dir if the relay keeps its state somewhere other than the default); then quorus kick <room> <name>. The old key alone can't rejoin a room; a room's creator or an admin can still add members directly.
• quorus invite-link and quorus invite-token print the relay secret, so they now need --with-secret.

Known issues

• Deleting a room doesn't purge its members' memory rows from the local SQLite store (p1_state.db). They can't be read, because every memory read needs an existing room and membership, but they stay on disk. The fix is in 0.6.1.

The full list, including the fixes, is in CHANGELOG.md.