Provider Overview
CCS supports CLIProxy OAuth providers plus Claude accounts and API profiles (including Alibaba Coding Plan, OpenRouter, Novita, GLM, MiniMax, and more). This guide helps you choose the right provider for your needs.Provider Categories
OAuth Providers
OAuth Providers - Zero API keys, browser callback, device-code, or browser-polling loginPerfect for beginners and quick setup
Claude Accounts
Multiple Subscriptions - Isolated Claude instancesWork/personal separation, concurrent sessions
API Profiles
Direct API Access - Bring your own keysCustom endpoints, self-hosted models
Quick Decision Guide
Choose your path:1
New to CCS? Start with OAuth
Recommended: Codex for browser OAuth, or Kiro if you want a free Builder ID path
- No API keys needed
- Good baseline for your first session
- Auto token refresh on supported providers
- Multi-account support
2
Have Claude Pro/Team? Use Claude Accounts
Best for: Multiple Claude subscriptions
- Work/personal isolation
- Concurrent sessions
- Team collaboration
- Existing subscription leverage
3
Need Custom Endpoints? Use API Profiles
Best for: Self-hosted models, custom APIs
- Full control over endpoints
- Self-hosted model support
- Custom headers/authentication
- Built-in presets such as OpenRouter, Novita, and Alibaba
Authentication Methods Comparison
Browser Callback vs Device Code vs Browser Polling
Kiro also supports optional auth-code and IDC flows via
--kiro-auth-method.
GitLab Duo also supports PAT login via --gitlab-token-login.
Example: Browser Callback Flow
All Providers Comparison
Providers At A Glance
- Gemini
- Kiro
- GitHub Copilot
- Codex
- xAI (Grok)
- Kimi
- Antigravity
- Claude
- Qwen
- iFlow
- MiniMax
- Alibaba Coding Plan
- Novita AI
- Requesty
Google Gemini - Google OAuth route
For command examples and setup flow, open the dedicated Gemini provider page.Full Documentation →
Claude Accounts
Run multiple Claude subscriptions simultaneously with separate account profiles:
Example:
API Profiles
Direct API access with custom endpoints and keys:
Example:
Additional Current CLIProxy OAuth Providers
These providers are current and supported in CCS today even though they arrived after the older nine-provider docs pass:Feature Matrix
All Providers Feature Comparison
Authentication Features
Provider Selection Guide
By Use Case
Beginner (First Time)
→ Codex or Kiro
- No API keys needed
- Good first-run coverage in CCS docs
- Codex works well for browser OAuth
- Kiro offers a free Builder ID route
Work/Personal Separation
→ Claude Accounts
- Isolated sessions
- Concurrent use
- Separate subscriptions
- Professional workflow
CI/CD Pipeline
→ GHCP (deprecated compatibility, device code)
- Headless-friendly
- No browser needed
- Scriptable auth
- Quota management
Free Tier Only
→ Kiro
- CodeWhisperer via AWS Builder ID
- Device-code friendly
- No paid subscription required
Premium Models
→ Claude Accounts or Codex
- Claude Pro/Max account workflows
- Codex paid-plan model access
- Strong review and implementation coverage
- Clear first-party documentation
Long-Context Tasks
→ MiniMax
- 1M token context window
- Large codebase analysis
- Document processing
- API key authentication
Self-Hosted Models
→ API Profiles
- Custom endpoints
- Local LLMs
- Full control
- Privacy-focused
AWS Ecosystem
→ Kiro
- CodeWhisperer integration
- AWS Builder ID device code by default
- IDE token import
- Free Builder ID
OpenAI Workflow
→ Codex
- Cross-plan-safe GPT-5 Codex defaults
- GPT-5.3 Codex / GPT-5.2 Codex when available
- OpenAI ecosystem
Alibaba Cloud / Cost-Efficient Coding
→ Alibaba Coding Plan
- Qwen3 Coder Plus/Flash
- 1M token context
- 5.00 per M tokens
ccs api create --preset alibaba
By Authentication Preference
Prefer Browser OAuth?- Gemini, Codex, Antigravity, iFlow, Claude, GitLab Duo, plus optional Kiro auth-code / Google flows
- Kimi, Kiro (default), Kilo AI, Qoder, xAI (Grok), deprecated GHCP compatibility
- Cursor, CodeBuddy
- GitLab Duo (
--gitlab-token-login)
- API Profiles
- Claude Accounts (uses Claude CLI’s built-in OAuth)
By Cost Model
Free Tier Available:- Gemini - Gemini 2.5 Pro (free Google account)
- Kiro - CodeWhisperer (AWS Builder ID)
- Gemini 3 Pro - Paid Google account
- GHCP - Deprecated GitHub Copilot compatibility for existing setups
- Codex paid / preview models - Paid Codex plan required for
gpt-5.5andgpt-5.3-codex;gpt-5.3-codex-sparkis research preview for ChatGPT Pro subscribers - Antigravity - Subscription
- Claude - Anthropic subscription
- iFlow - Subscription
- Claude Accounts - Claude Pro/Team
- API Profiles - You manage costs
- Alibaba Coding Plan - Qwen3 Coder (from $0.30/M input)
- Novita AI - Anthropic-compatible preset with hosted routing
- Requesty - OpenAI-compatible gateway preset
- OpenRouter - 300+ models, pay per use
Multi-Account Management
All OAuth providers support multiple accounts:- Email-Based (Most Providers)
- Username-Based (GHCP)
- Filename-Based (Kiro)
- xAI (Email Or Filename)
- Provider-Managed IDs
- Profile-Based (Claude)
Codex, Gemini, Antigravity, iFlowAccount ID: Email prefix (
john@gmail.com → john)Storage Locations
All providers store data in~/.ccs/:
Common Commands (All Providers)
Authentication
Account Management
Execution
Configuration
Provider-Specific Features
Gemini Unique Features
- ✅ Automatic CLIProxy-managed token refresh
- ✅ Auto project rotation on quota exceeded
- ✅ Interactive model picker (4 models)
- ✅ Free tier (Gemini 2.5 Pro)
Kiro Unique Features
- ✅ Token import from Kiro IDE (
--import) - ✅ Browser mode control (
--no-incognito) - ✅ AWS Builder ID device code by default
- ✅ Free tier (Builder ID)
GHCP Deprecated Compatibility Features
- ✅ Built-in device-code OAuth flow
- ✅ Quota display (
--quota) - ✅ Device code for headless servers
- ✅ GitHub integration
More Current CLIProxy Providers
- ✅ Cursor provider path lives under
ccs cursor --auth - ✅ GitLab Duo supports browser OAuth and PAT login
- ✅ CodeBuddy is supported as a browser-polling provider
- ✅ Kilo AI is supported as a device-code provider
- ✅ Qoder is supported as a device-code provider with model picker
- ✅ xAI (Grok) is supported as a device-code provider;
grokis its CLI alias
Antigravity Unique Features
- ✅ Multi-model access (Claude + Gemini)
- ✅ Claude Opus 4.6 Thinking (latest flagship)
- ✅ Claude Sonnet 4.6 Thinking
- ✅ Interactive model picker
Claude Accounts Unique Features
- ✅ Concurrent sessions (different profiles)
- ✅ Separate account directories by default
- ✅ Unlimited profiles
- ✅ Work/personal separation
Next Steps
Gemini Provider
Free tier, proactive refresh, 4 models
Kiro Provider
AWS CodeWhisperer, IDE import, free tier
GHCP Provider (Deprecated)
Compatibility path, device code, quota display
Codex Provider
GPT-5 Codex defaults, paid-plan models, plan-aware fallbacks
xAI (Grok) Provider
Device-code OAuth,
xai provider ID, grok CLI aliasAntigravity Provider
Claude Opus 4.6 Thinking, multi-model picker
Claude Provider
Direct Anthropic OAuth access
Alibaba Coding Plan
Qwen3 Coder via API key
iFlow Provider
Various models available
Cursor Provider
Current CLIProxy Cursor provider path
GitLab Duo
Browser OAuth or PAT login
CodeBuddy
Tencent CodeBuddy provider
Kilo AI
CLIProxy device-code provider
Qoder Provider
Qoder coding provider
MiniMax Provider
1M context window, long-context tasks
Novita Provider
Anthropic-compatible preset, default
deepseek/deepseek-v3.2Requesty Provider
OpenAI-compatible gateway, default
openai/gpt-4o-miniClaude Accounts
Multiple subscriptions, concurrent sessions
API Profiles
Custom endpoints, self-hosted models
Alibaba Coding Plan
Qwen3 Coder, 1M context, cost-effective
FAQ
Can I use multiple providers simultaneously?
Can I use multiple providers simultaneously?
Yes! Different providers are the simplest way to avoid reusing the same provider or proxy lane:
Which provider is best for beginners?
Which provider is best for beginners?
Kiro or Codex - pick the one that matches the account you already have:
Can I switch between accounts without re-authenticating?
Can I switch between accounts without re-authenticating?
Yes! All OAuth providers support multi-account with instant switching:
Which providers work without a browser (CI/CD)?
Which providers work without a browser (CI/CD)?
- GHCP - Deprecated compatibility with built-in device-code flow
- xAI (Grok) - Native device-code OAuth (
ccs xai --auth --headless) - All OAuth Providers - Headless mode (
--headless, copy URL manually) - API Profiles - No browser needed (API keys only)
Can I use the same account across multiple machines?
Can I use the same account across multiple machines?
Yes for OAuth providers - tokens sync automatically if you:
- Copy
~/.ccs/cliproxy/auth/to new machine - Re-authenticate on new machine (tokens specific to each machine)
Which providers support concurrent sessions?
Which providers support concurrent sessions?
- Different providers: Concurrent; usually the easiest way to keep sessions separate
- Same provider, different accounts: Concurrent (if supported by backend)
- Claude Accounts: Concurrent with different profiles; same profile is allowed but reuses the same account directory
- Same provider, same account: Provider-specific; may reuse the same provider/proxy session instead of giving full isolation
