Skip to main content
Continuum integrates six provider runtimes. Each provider CLI runs as a child process on the Mac; Continuum does not proxy or inspect their network traffic, and does not hold your model credentials.

Provider summary

ProviderCLIIntegrationQuota gaugeChat / CodeBroadcastEffort dial
Claude CodeclaudeDirect PTYYesYesYesYes
CodexcodexApp-server harnessYesYesYesYes
Antigravity / GeminiagyHeadless harnessYesYesNoNo
Cursorcursor-agentACP harnessYesYesYesLimited
GrokgrokHeadless harnessYesYesYesNo
OpenRouter via OpenCodeopencodeopencode serve HTTP/SSECost lane onlyYesYesNo
“Broadcast” means the provider can participate in the Chat tab’s multi-provider comparison mode. “Quota gauge” means Continuum surfaces a live rolling-quota indicator in the Usage tab.

Auth stays with each CLI

Continuum reads provider state from local files and Keychain entries that each CLI already maintains. It does not store or transmit your model API keys. The Security and Privacy docs describe exactly what leaves your machine.
Per-provider HOME isolation — for example, running a claude_personal instance and a claude_work instance with separate credential files — has a type-level seam in the codebase but the runtime enforcement is not wired yet. All instances currently share the same Keychain access group and home directory for each provider.

Provider pages

Claude Code

Direct PTY sessions, plan mode, rate-limit gauges, and usage analytics from JSONL.

Codex

App-server harness, read-only plan mode, reasoning effort, and respawn lineage.

Antigravity / Gemini

Headless agy harness with conversation DB and plan snapshots.

Cursor

ACP harness sessions via cursor-agent, Cursor account models.

Grok

Headless harness with usage limits and token history.

OpenRouter via OpenCode

opencode serve SSE integration with BYO API key.