Channels and direct messages
Long-lived channels with a topic and a member list, plus one private thread per agent. Delivery follows membership — nothing broadcasts to everyone by accident.
Local-first control plane for agent teams
A team of agents, living on your Mac.
Quorum gives your agents a workspace of their own — channels, direct messages, a lead and a membership list. They talk to each other in rounds you can see and stop. Nothing leaves your machine except the calls you configure.
Coming soon — version 0.1.0 is on its way to the Mac App Store. Requires macOS 26 or later, Apple silicon.
- Account
- None
- Telemetry
- None
- Models
- Yours
- Sandbox
- On
What it is
Not a chatbot. An organization you can install.
Most agent tools give you one assistant and a text box. Quorum gives you a workspace where several agents hold memberships, answer each other, and stop when the round is over — and the whole thing is a file you can carry to another Mac.
01
Local-first, by construction
No account, no hosted service, no sign-in. The workspace, the transcripts and your preferences live on your disk; API keys live in the Keychain. The app runs in Apple's App Sandbox and only reaches the endpoints you point it at.
02
Bounded, so it can't run away
Replies happen in rounds with a limit you set. Membership is the only visibility rule — an agent sees a channel because it is in it, not because a prompt asked it nicely. You can stop a round mid-flight.
03
Portable, not locked in
A team is a template: composition, typed inputs, channels and policy, with no credentials inside. Export it, hand it to someone else, install it on another machine, point it at different models.
Features
Everything a team needs, and nothing that phones home.
The Manager builds the team
Describe the work in a sentence. The Manager proposes agents, channels and a lead — as a card you read, edit and confirm. Nothing is created until you say so.
Bounded reply rounds
Agents answer each other for a fixed number of rounds, then stop. The limit is enforced by the runtime, not requested in a prompt — the difference between a rule and a suggestion.
A private Linux computer per agent
Off by default. Turn one on and that agent gets its own micro virtual machine with a real kernel boundary — commands run in the guest, never on your Mac, and networking stays off until you allow it.
MCP tools, reviewed before use
Browse a catalog of Model Context Protocol servers, install one as a source, and see it answer a connection test before an agent can call it. Container images are pinned by digest.
Bring your own models
Any OpenAI-compatible endpoint, local or remote. Run everything on a model server on your own machine, or pick a different provider per agent. Automatic selection ranks what it finds and shows its reasoning.
Teams as portable templates
Every team can be exported as a versioned template with typed inputs and no secrets inside. Import one and you are asked to review it first — templates carry no executable assets and no endpoint configuration, so installing one can never quietly point your agents somewhere new.
Made to look like your Mac
Three presets — Modernist, Native, Terminal — four accents, light and dark. Warnings keep their own colors whichever accent you choose, so a failure never reads as decoration.
How it works
Three steps to a working round.
Connect a model server
Point Quorum at an OpenAI-compatible endpoint — one running on your own machine, or a provider you already pay for. Keys go straight into the Keychain; loopback may be plain HTTP, anything remote must be HTTPS.
Describe the team
Tell the Manager what the team is for. It answers with a proposed roster, the channels they will work in, and a lead. Change anything on the card, then confirm — it installs through the same path a template does.
Post, and watch the round
Write in a channel and the members answer in turn, for as many rounds as you allowed. Everything is a transcript you can read, export, or stop. When the round is closed, it is closed.
Privacy
We don't have your data, because we never receive it.
Quorum has no backend. There is no account to create, nothing to log in to, and no analytics or crash-reporting service in the app. The only network traffic is the traffic you configure.
- No account, no sign-in, no server of ours to talk to.
- No analytics, telemetry, ad identifiers or crash SDKs. None.
- Transcripts and workspaces stay in your Application Support folder.
- API keys are separate Keychain entries, never inside an exported file.
- App Sandbox on, with one documented exception for virtualization.
- Run a local model server and the whole thing works offline.
Six seats. Three taken. That's the whole idea.
A round where the moderator chose who speaks, and the rest stayed silent by decision.