dev-hummingbird-sneakers
v0.2.0-dev.20260426012917
Published
Remote control and session sharing CLI for AI coding agents
Readme
Consortium
Code on the go — control AI coding agents from your mobile device.
Free. Open source. Code anywhere.
Installation
npm install -g consortiumUsage
Claude (default)
consortiumThis will:
- Start a Claude Code session
- Display a QR code to connect from your mobile device
- Allow real-time session sharing between Claude Code and your mobile app
Gemini
consortium geminiStart a Gemini CLI session with remote control capabilities.
First time setup:
# Authenticate with Google
consortium connect geminiCommands
Main Commands
consortium– Start Claude Code session (default)consortium gemini– Start Gemini CLI sessionconsortium codex– Start Codex mode
Utility Commands
consortium auth– Manage authenticationconsortium connect– Store AI vendor API keys in Consortium cloudconsortium notify– Send a push notification to your devicesconsortium daemon– Manage background serviceconsortium doctor– System diagnostics & troubleshooting
Connect Subcommands
consortium connect gemini # Authenticate with Google for Gemini
consortium connect claude # Authenticate with Anthropic
consortium connect codex # Authenticate with OpenAI
consortium connect status # Show connection status for all vendorsGemini Subcommands
consortium gemini # Start Gemini session
consortium gemini model set <model> # Set default model
consortium gemini model get # Show current model
consortium gemini project set <id> # Set Google Cloud Project ID (for Workspace accounts)
consortium gemini project get # Show current Google Cloud Project IDAvailable models: gemini-2.5-pro, gemini-2.5-flash, gemini-2.5-flash-lite
Options
Claude Options
-m, --model <model>- Claude model to use (default: sonnet)-p, --permission-mode <mode>- Permission mode: auto, default, or plan--claude-env KEY=VALUE- Set environment variable for Claude Code--claude-arg ARG- Pass additional argument to Claude CLI
Global Options
-h, --help- Show help-v, --version- Show version
Environment Variables
Consortium Configuration
CONSORTIUM_SERVER_URL- Custom server URL (default: https://api.consortium.dev)CONSORTIUM_WEBAPP_URL- Custom web app URL (default: https://app.consortium.dev)CONSORTIUM_HOME_DIR- Custom home directory for Consortium data (default: ~/.consortium)CONSORTIUM_DISABLE_CAFFEINATE- Disable macOS sleep prevention (set totrue,1, oryes)CONSORTIUM_EXPERIMENTAL- Enable experimental features (set totrue,1, oryes)
Gemini Configuration
GEMINI_MODEL- Override default Gemini modelGOOGLE_CLOUD_PROJECT- Google Cloud Project ID (required for Workspace accounts)
Gemini Authentication
Personal Google Account
Personal Gmail accounts work out of the box:
consortium connect gemini
consortium geminiGoogle Workspace Account
Google Workspace (organization) accounts require a Google Cloud Project:
- Create a project in Google Cloud Console
- Enable the Gemini API
- Set the project ID:
consortium gemini project set your-project-idOr use environment variable:
GOOGLE_CLOUD_PROJECT=your-project-id consortium geminiGuide: https://goo.gle/gemini-cli-auth-docs#workspace-gca
Migrating from consortium-local
consortium-local was the original entry point for launching Consortium Code
against the local agent. It still ships as a thin shim that prints a deprecation
banner and forwards to consortium code, but it will be removed in the next
major release. Update any scripts, aliases, or CI jobs to use the new surface:
# Before
consortium-local # auto-launch Consortium Code
consortium-local --resume <id>
# After
consortium code # direct launch of Consortium Code
consortium code --resume <id>
# Or — if you want the new no-args interactive menu:
consortium # opens the TUIThe new top-level surface adds:
consortium— interactive menu (no-args default) covering Consortium Code, session management, register-machine, switch-workspace, daemon control, and auth. Seeconsortium --helpfor keyboard shortcuts.consortium code [--resume <id>]— direct launch (whatconsortium-localused to do).consortium switch-org [--org <slug>]— change the active workspace.consortium whoami [--json]— print the current auth / workspace context.
If you run consortium-local in automation and can't tolerate the banner on
stderr, set CONSORTIUM_HIDE_DEPRECATION_WARNING=1 to silence it while you
migrate.
Troubleshooting
If the CLI exits silently, fails to launch, or reports an unsupported platform, run consortium doctor and follow the guide at docs/cli-troubleshooting.md. Common fixes:
- musl / Alpine / old glibc — run the pre-built docker image:
docker run -it --rm -v "$PWD":/workspace -v "$HOME/.consortium":/root/.consortium ghcr.io/consortium/cli:stable EACCESduring install —npm install -g --unsafe-perm consortium- Wrong arch —
npm install -g consortium-code-$(node -p "process.platform + '-' + process.arch") - Headless server / auth hangs —
consortium auth login(device-code flow)
Logs live in ~/.consortium/logs/ (boot trace, launch preflight, crash dumps, daemon logs).
Contributing
Interested in contributing? See CONTRIBUTING.md for development setup and guidelines.
Requirements
- Node.js >= 20.0.0
For Claude
- Claude CLI installed & logged in (
claudecommand available in PATH)
For Gemini
- Gemini CLI installed (
npm install -g @google/gemini-cli) - Google account authenticated via
consortium connect gemini
License
MIT
