cobridge-cli
v2026.6.291333
Published
Command-line client for CoBridge Agent operations.
Readme
CoBridge CLI
Command-line client for CoBridge Agent operations. The npm package is named
cobridge-cli and installs the cobridge command.
Install
npm install -g cobridge-cli
cobridge version --jsonNo endpoint environment variables are required for the default production
service. The installed CLI talks to the public CoBridge production Agent API at
https://cobridge.ai by default.
Authorize
cobridge auth login --no-browser --jsonOpen the returned login_url, confirm the workspace in CoBridge, then poll:
cobridge auth status --jsonFor a named workspace:
cobridge auth login --profile <name> --workspace <workspace-id> --no-browser --json
cobridge auth login --profile <name> --workspace-name <workspace-name> --no-browser --json
cobridge auth status --profile <name> --json
cobridge auth profile list --json
cobridge auth profile use <name> --jsonEach profile stores its authorized workspace, role, user, and token locally.
Pending profile authorization is shown as status: "pending" and can be
polled with auth status --profile <name>. When --workspace-name is used
and an existing CLI token can list workspaces, the CLI resolves the name first
and opens a /w/<workspace-id>/cli/authorize URL.
Browser Handoff Diagnostics
cobridge browser status --json
cobridge browser open --json
cobridge browser login --workspace-name <workspace-name> --jsonBrowser commands return diagnostics, next_action, and
recommended_commands fields. These fields summarize the selected profile,
endpoint, token state, workspace, CLI contract, recommended Skill version, and
the next command an Agent should run. Token secrets and browser session tokens
are never printed.
Useful Commands
cobridge workspace list --json
cobridge project list --json
cobridge resource list --json
cobridge pack list --jsonCustom Endpoint
Most users should not set endpoint variables. They are only for local development, CI, or private deployments.
Use Supabase RPC directly:
COBRIDGE_SUPABASE_URL=http://127.0.0.1:54321 \
COBRIDGE_SUPABASE_ANON_KEY=<anon-or-publishable-key> \
cobridge auth login --no-browser --jsonCOBRIDGE_SUPABASE_PUBLISHABLE_KEY is accepted as an alias for
COBRIDGE_SUPABASE_ANON_KEY.
Use a custom API adapter only if that adapter implements the CoBridge Agent API:
COBRIDGE_API_URL=https://example.com \
cobridge project list --jsonCOBRIDGE_API_URL=https://cobridge.ai is accepted but redundant because it is
the built-in production Agent API endpoint.
