Secure, agentic collaboration.

Install the CLI with npm install -g consortium, then start agents through it instead of calling them directly — run consortium in place of claude, codex or gemini. Your existing agent credentials, settings and project files are used as-is, and there is nothing else to configure.

Consortium Code, Claude Code, Codex, Gemini CLI, Grok, opencode, Pi, OpenClaw and Hermes. Consortium wraps the agent CLI rather than integrating with one model provider, so the same persistence, handoff and notification behaviour applies to all of them, you keep using your own credentials for each, and running several side by side is the normal case.

Start it through Consortium rather than directly. The agent runs under a persistent daemon, so the session belongs to the daemon rather than your terminal window: closing the terminal, losing Wi-Fi or sleeping the laptop leaves the run going, and you reattach from desktop, browser or phone. Terminal sessions use tmux where it is installed.

Yes. Your phone joins the same live session, so when an agent asks permission to run a command you get a push notification and can approve or stop it from wherever you are. The desktop records who approved it and from which device, and both surfaces show the same transcript as it happens.

Yes. Sessions live in an organisation workspace rather than on one person's machine, so members with access can attach to a running session, see what the agent has done, and approve or stop it — without shell access to the computer it runs on. Sharing is a property of the workspace, so who can see a session is set in one place.

Yes. The marketplace installs MCP servers and skills — Linear, Sentry, Notion, Stripe, Supabase, Figma, Atlassian and dozens more — most with one-click sign-in, and your agents can use them in cloud sessions and on your own machines. Each connector can be switched on or off per session.

Yes. The External API at api.consortium.dev takes scoped personal access tokens or OAuth apps, and covers sessions, machines and artifacts, with signed webhooks for events like a completed run. There are official TypeScript and Python SDKs and a published OpenAPI document.

Your code executes on your own machine — Consortium is a control surface, not a hosted runtime. Session content that syncs between your devices is encrypted in transit and at rest, and you choose who holds the key. New accounts default to escrow custody: your account key is sealed to a server key and stored, so we can restore it when you sign in on a new device — which also means we are able to unseal it. Choose end-to-end custody instead and the key exists only on your devices, the relay can never read your content, and nobody can recover it for you if you lose your recovery phrase. Accounts created before 2026-09-07 are end-to-end and were not migrated. The encryption library is MIT-licensed and auditable.

Yes. The free tier is the full local product: unlimited sessions on as many of your own machines as you like, with your own model credentials, and no credit card is required. Paid tiers add remote access to your machines from other devices, managed cloud machines, more storage and monthly usage credits.

Consortium is open core. The encryption library, browser protocol and TypeScript, Python and extension SDKs are MIT-licensed; the CLI, app and browser core are under Business Source License 1.1, each release converting to Apache 2.0 four years after it ships; the backend server is proprietary. The server can run on your own infrastructure so no session data transits hardware you do not control — contact licensing@consortium.dev for commercial self-hosting terms.