Skip to content
Consortium

Overview

Consortium is a mobile and web client for coding agents. Run consortium instead of claude (or codex, gemini, grok, pi) on your computer, and the session becomes reachable — end-to-end encrypted — from your phone, browser, or any other signed-in device. Approve tool calls, redirect the agent, or take the keyboard back with one keypress.

The pieces

Section titled “The pieces”
ComponentRole
Consortium CLI + daemonWraps the agent CLIs on your machine; hosts sessions; injects credentials at spawn
Consortium AppWeb (app.consortium.dev) and desktop client; mobile apps coming soon
Consortium ServerEncrypted sync, device auth, billing, and the External API
Model proxyOptional managed inference, billed in credits
SDKsOfficial TypeScript and Python SDKs for the External API

Where agents run

Section titled “Where agents run”

On your machines. A session is rooted in a directory on a computer you control — your laptop, a desktop at home, a server you provisioned. The server never runs your agent and never sees your session content in plaintext; it brokers encrypted state between your devices. (See Security & encryption for the precise boundary.)

How a session flows

Section titled “How a session flows”
  1. You run consortium claude in a repo (or start a session on any online machine from the app).
  2. The daemon registers the session; encrypted state syncs to your devices.
  3. You drive it from wherever you are — terminal or app. Sending a prompt from the app switches the session to remote mode; pressing any key in the original terminal takes it back.
  4. History persists (encrypted) until you delete it; the session survives daemon restarts and network drops.

What Consortium is not

Section titled “What Consortium is not”
  • Not a cloud sandbox. There is no hosted agent runtime today; compute is yours.
  • Not a model reseller lock-in. BYOK traffic goes directly from your machine to your vendor, unmetered. Managed credits exist for when you’d rather not manage keys.
  • Not a black box. The client and encryption code are source-available; the encryption design is documented and blunt about its limits.

Where next

Section titled “Where next”