Secure, agentic collaboration.

A consortium is a group that comes together to accomplish what none of its members could alone — from the Latin consors, "one who shares a common lot". The product is named for what it does: it puts the people on a team and the AI coding agents they run into one shared workspace, so the work passes between them instead of being trapped on one person's laptop.

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

An agent runs on a team member's machine but is reachable inside the shared workspace, so it behaves like a participant rather than a background process. One person can start a run, a second can review or redirect it from a phone, and the agent keeps working through both — because the session belongs to a persistent daemon rather than to whoever opened the terminal.

Start it through Consortium rather than directly: run consortium in place of claude, codex, gemini or whichever agent you use. Consortium runs the agent 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; you reattach from desktop, browser or phone. Terminal sessions use tmux where it is installed.

Consortium Code, Claude Code, Codex, Gemini CLI, Grok, opencode, Pi, OpenClaw and Hermes. Consortium wraps the agent CLI rather than integrating with a specific model provider, so the same persistence, handoff, notification and encryption behaviour applies to all of them, and new agents are added as adapters rather than rewrites.

No. Consortium is a control surface over whichever agent CLI you already run, using your own credentials for that agent. Switching from one agent to another does not change how you reach your sessions, and running several different agents side by side is the normal case rather than an edge case.

Vendor remote-control features tether a mobile view to a live local process: if that process exits or the network drops for long enough, the session ends. Consortium runs the session under a persistent daemon that outlives both, works across every supported agent instead of one vendor's, and adds organisations and shared workspaces for teams. It is also open core and can be self-hosted.

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 server can run on your own infrastructure so no session data transits hardware you do not control. The client and encryption code are source-available under the repository licence; contact licensing@consortium.dev for commercial self-hosting terms.

Yes. The free tier includes persistent sessions and access from every device, with up to three concurrent sessions across three of your own machines, and no credit card is required. Paid tiers add unlimited sessions and machines, managed machines, more storage and monthly usage credits.

Install the CLI with npm install -g consortium, then start agents through it instead of calling them directly. There is nothing else to configure — your existing agent credentials, settings and project files are used as-is.

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.