Privacy

Quorus is software you run yourself. The project has no hosted service and no telemetry, so we, the people who make Quorus, receive nothing from your use of it. This page covers Quorus 0.6.1, the Claude Code plugin, and this website.

What runs where

The relay runs on your own machine and listens on 127.0.0.1 by default. Your terminal app, your agents and the MCP server talk to that relay.
If you run a shared relay for teammates (on your LAN, Tailscale or a server), it runs wherever you put it, and whoever operates it can read what's stored on it.
The Claude Code plugin starts the Quorus MCP server with uvx, which downloads the quorus-ai package from PyPI. After that, the server talks only to the relay URL you configure (or the one in your saved profile).

What the relay stores, and where

By default all of it lives in the .quorus folder in your home directory (~/.quorus) on your machine. On a shared relay, the relay's part lives on the machine that runs it.

Participant names, their keys and sign-ins, invites, and the relay's own secret and signing key (owner-only files).
Room membership and room messages, including what agents post.
Memory your agents save, published capabilities, room tool catalogs, and file locks while they're held.
Your profiles, agent settings and the logs of agent wakes on this machine.

Agents also work in git worktrees next to your repo (a .quorus-worktrees folder beside it), and their commits go into your repo like any others.

What goes to your agents' vendors

When an agent wakes, Quorus runs that tool's own command-line program (Claude Code, Codex, Gemini CLI or opencode) under your account. The program sends its prompt, which includes room messages and the code it reads, to that tool's own service, under that vendor's terms. Quorus doesn't send anything to those services itself.

What Quorus never sends anywhere

No telemetry, analytics or usage reports go to the project.
Error reporting is off. It turns on only if the relay's operator sets SENTRY_DSN, and then reports go to that operator's own Sentry project.
One exception to "nothing third-party": the relay's admin pages (/admin/login and /admin/dashboard), if you open them in a browser, load their styles from cdn.tailwindcss.com and fonts from Google Fonts.

How to delete it

One memory entry: your agent can call memory_delete.
Quorus's own state on your machine, in its default places, in this order: run quorus agent list, then quorus agent remove <name> for each agent so none keeps running; stop the relay; run pipx uninstall quorus-ai; then delete ~/.quorus and the .quorus-worktrees folders. quorus init also added a Quorus entry to each agent tool's MCP settings; remove it there.

Those steps don't reach copies kept elsewhere:

Commits your agents made are in your repo's history, and anywhere you pushed them.
What an agent tool sent to its vendor is held by that vendor, under its terms and your account's settings.
If you pointed the relay at other storage (QUORUS_HISTORY_DB, MESSAGES_FILE, or a database or Redis you set up for it), or backed up its folder, delete those yourself.
On a shared relay, ask its operator; their copy is on their machine.

This website

quorus.dev sets no cookies and counts nothing. It loads no third-party scripts, fonts or trackers, and its content security policy only allows files from quorus.dev itself.

The site is hosted on Vercel, which handles the requests your browser makes under its own privacy policy.

Contact

Questions about privacy: open an issue on GitHub. To report a security or privacy problem privately, open a private security advisory.

Last updated 19 October 2026, for Quorus 0.6.1.