Skip to main content

Provider Overview

CCS supports 9 OAuth providers plus Claude accounts and API profiles (including Alibaba Coding Plan, OpenRouter, Novita, GLM, MiniMax, and more) across 3 authentication methods. This guide helps you choose the right provider for your needs.

Provider Categories

OAuth Providers

9 OAuth Providers - Zero API keys, browser or device-code 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: Gemini (free tier available)
ccs gemini "your first query"
# Browser opens → Sign in → Start coding
  • No API keys needed
  • Free tier available (Gemini 2.5 Pro)
  • Auto token refresh
  • Multi-account support
2

Have Claude Pro/Team? Use Claude Accounts

Best for: Multiple Claude subscriptions
ccs auth create work
ccs auth create personal
# Use both simultaneously in different terminals
  • Work/personal isolation
  • Concurrent sessions
  • Team collaboration
  • Existing subscription leverage
3

Need Custom Endpoints? Use API Profiles

Best for: Self-hosted models, custom APIs
ccs config
# Add API profile with custom endpoint + API key
  • Full control over endpoints
  • Self-hosted model support
  • Custom headers/authentication
  • Built-in presets such as OpenRouter, Novita, and Alibaba

Authentication Methods Comparison

Browser OAuth vs Device Code

FeatureBrowser OAuthDevice Code
SetupBrowser opens automaticallyManual URL copy
SpeedInstant (3-5 seconds)Manual (10-20 seconds)
Headless ServersRequires --headless flagNative support
ProvidersGemini, Codex, Antigravity, iFlow, ClaudeGHCP, Qwen, Kimi, Kiro (default)
Token RefreshAutomatic (proactive)Automatic (on-demand)
Best ForLocal development, desktopCI/CD, remote servers
Kiro also supports optional browser auth-code flows via --kiro-aws-authcode and --kiro-google-login, but the default flow is AWS device code. Example: OAuth Flow
ccs gemini "task"
# → Browser opens → Google login → Token cached → Session starts
Example: Device Code Flow
ccs ghcp "task"
# → Device code displayed → Copy URL/code → Token cached

All Providers Comparison

OAuth Providers (9 Total)

Google Gemini - Best for beginners
FeatureDetails
ModelsGemini 3 Pro (High/Preview), Gemini 2.5 Pro, Gemini 3 Flash
Free Tier✅ Yes (Gemini 2.5 Pro)
Auth MethodBrowser OAuth (Google SSO)
Multi-Account✅ Yes (email-based)
Model Picker✅ Interactive --config
Quota Display✅ Auto project rotation
Token Refresh✅ Proactive (5 min before expiry)
Best ForBeginners, free tier users, fast responses
ccs gemini "your query"
ccs gemini --config           # Change model
ccs gemini --auth --add       # Add account
Full Documentation →

Claude Accounts

Run multiple Claude subscriptions simultaneously with isolated sessions:
FeatureDetails
Setupccs auth create <profile>
Multi-Account✅ Unlimited profiles
Concurrent Sessions✅ Each profile runs independently
Session Isolation✅ Complete (credentials, history, state)
SubscriptionRequires existing Claude Pro/Team
Best ForWork/personal separation, team collaboration
Example:
# Create profiles
ccs auth create work
ccs auth create personal

# Use simultaneously
ccs work "implement feature"      # Terminal 1
ccs personal "side project"        # Terminal 2 (concurrent)
Full Documentation →

API Profiles

Direct API access with custom endpoints and keys:
FeatureDetails
Setupccs config → Add API profile
Custom Endpoints✅ Full control
Self-Hosted Models✅ Supported
API Key ManagementManual (you provide keys)
Model ConfigurationProvider-dependent
Best ForCustom APIs, self-hosted models, advanced users
Example:
# Configure via dashboard
ccs config

# Add profile:
# - Name: myapi
# - Endpoint: https://api.example.com/v1/chat
# - API Key: sk-...
# - Model: custom-model-name

# Use profile
ccs myapi "your query"
Full Documentation →

Feature Matrix

All Providers Feature Comparison

ProviderFree TierMulti-AccountModel PickerQuota DisplayToken RefreshHeadless Mode
Gemini✅ Proactive
Kiro✅ Auto
KimiVaries✅ Auto✅ Device Code
GHCP✅ Auto✅ Device Code
Codex✅ Limited✅ Auto
Antigravity✅ Auto
Claude✅ Auto
Qwen✅ Auto
iFlow✅ Auto
MiniMaxManual
Alibaba Coding PlanManual
Novita AIManual
Claude AccountsN/AN/A
API ProfilesVariesVariesManual

Authentication Features

ProviderAuth MethodAccount IDToken ImportBrowser Control
GeminiBrowser OAuthEmailIncognito default
KiroDevice code + optional browser authFilename✅ IDENormal (no incognito)
KimiDevice CodeEmailN/A
GHCPDevice CodeGitHub usernameN/A
CodexBrowser OAuthEmailIncognito default
AntigravityBrowser OAuthEmailIncognito default
ClaudeBrowser OAuthEmailIncognito default
QwenDevice CodeEmailIncognito default
iFlowBrowser OAuthEmailIncognito default
MiniMaxAPI KeyProfile nameN/A
Alibaba Coding PlanAPI KeyProfile nameN/A
Novita AIAPI KeyProfile nameN/A
Claude AccountsOAuth (Claude)Profile nameN/A
API ProfilesAPI KeyProfile nameN/A

Provider Selection Guide

By Use Case

Beginner (First Time)

→ Gemini (free tier)
  • No API keys needed
  • Free tier available
  • Easy setup (browser only)
  • Good documentation

Work/Personal Separation

→ Claude Accounts
  • Isolated sessions
  • Concurrent use
  • Separate subscriptions
  • Professional workflow

CI/CD Pipeline

→ GHCP (device code)
  • Headless-friendly
  • No browser needed
  • Scriptable auth
  • Quota management

Free Tier Only

→ Gemini or Kiro
  • Gemini: 2.5 Pro (Google free)
  • Kiro: CodeWhisperer (AWS Builder ID)

Premium Models

→ Antigravity
  • Claude Opus 4.6 Thinking
  • Claude Sonnet 4.6
  • Gemini 3 Pro
  • Interactive model picker

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
  • 1.00/1.00/5.00 per M tokens
  • ccs api create --preset alibaba

By Authentication Preference

Prefer Browser OAuth?
  • Gemini, Codex, Antigravity, iFlow, Claude, plus optional Kiro auth-code / Google flows
Prefer Device Code?
  • GHCP, Qwen, Kimi, Kiro (default)
Prefer API Keys?
  • API Profiles
Prefer No External Auth?
  • 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)
Requires Subscription:
  • Gemini 3 Pro - Paid Google account
  • GHCP - GitHub Copilot subscription
  • Codex paid-only models - Paid Codex plan required for gpt-5.2-codex, gpt-5.3-codex, or gpt-5.4
  • Antigravity - Subscription
  • Claude - Anthropic subscription
  • Qwen - Subscription
  • iFlow - Subscription
Use Existing Subscription:
  • Claude Accounts - Claude Pro/Team
Bring Your Own:
  • API Profiles - You manage costs
  • Alibaba Coding Plan - Qwen3 Coder (from $0.30/M input)
  • Novita AI - Anthropic-compatible preset with hosted routing
  • OpenRouter - 300+ models, pay per use

Multi-Account Management

All OAuth providers support multiple accounts:
Gemini, Codex, Antigravity, Qwen, iFlow
# Add account
ccs gemini --auth --add

# List accounts
ccs gemini --accounts

# Output:
# * john (john@gmail.com) - default
#   work (alice@company.com)

# Switch account
ccs gemini --use work

# Rename account
ccs gemini --nickname personal
Account ID: Email prefix (john@gmail.comjohn)

Storage Locations

All providers store data in ~/.ccs/:
~/.ccs/
├── cliproxy/
│   ├── auth/                           # OAuth tokens
│   │   ├── gemini-john@gmail.com.json
│   │   ├── kiro-github-ABC123.json
│   │   ├── ghcp-kaitranntt.json
│   │   └── ...
│   ├── accounts.json                   # Account registry (all OAuth providers)
│   └── config.yaml                     # CLIProxy configuration
├── instances/                           # Claude account profiles
│   ├── work/
│   └── personal/
├── gemini.settings.json                 # Provider-specific settings
├── agy.settings.json
└── config.yaml                          # Global CCS config

Common Commands (All Providers)

Authentication

# Initial auth (browser opens)
ccs <provider> --auth

# Add new account (preserves existing)
ccs <provider> --auth --add

# Logout (clear tokens)
ccs <provider> --logout

# Headless mode (manual URL)
ccs <provider> --headless

Account Management

# List all accounts
ccs <provider> --accounts

# Switch default account
ccs <provider> --use <nickname>

# Rename current account
ccs <provider> --nickname <new-name>

Execution

# Execute query (interactive session)
ccs <provider> "your prompt"

# One-shot mode
ccs <provider> "quick question" --one-shot

Configuration

# Provider-specific config (if available)
ccs <provider> --config

# Global dashboard
ccs config

Provider-Specific Features

Gemini Unique Features

  • ✅ Proactive token refresh (5 min before expiry)
  • ✅ 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 Unique Features

  • ✅ Built-in device-code OAuth flow
  • ✅ Quota display (--quota)
  • ✅ Device code for headless servers
  • ✅ GitHub integration

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)
  • ✅ Complete session isolation
  • ✅ 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

Dual auth, device code, quota display

Codex Provider

GPT-5 Codex defaults, paid-plan models, plan-aware fallbacks

Antigravity Provider

Claude Opus 4.6 Thinking, multi-model picker

Claude Provider

Direct Anthropic OAuth access

Qwen Provider

Specialized coding model

iFlow Provider

Various models available

MiniMax Provider

1M context window, long-context tasks

Novita Provider

Anthropic-compatible preset, default deepseek/deepseek-v3.2

Claude Accounts

Multiple subscriptions, concurrent sessions

API Profiles

Custom endpoints, self-hosted models

Alibaba Coding Plan

Qwen3 Coder, 1M context, cost-effective

FAQ

Yes! Each provider runs isolated sessions:
# Terminal 1
ccs gemini "task A"

# Terminal 2
ccs codex "task B"

# No conflicts
Gemini - Free tier available, easy setup, no API keys needed:
ccs gemini "your first query"
# Browser opens → Google login → Start coding
Yes! All OAuth providers support multi-account with instant switching:
ccs gemini --use work      # Switch to work account
ccs gemini --use personal  # Switch to personal
# No re-auth needed
  • GHCP - Built-in device-code flow
  • All OAuth Providers - Headless mode (--headless, copy URL manually)
  • API Profiles - No browser needed (API keys only)
Yes for OAuth providers - tokens sync automatically if you:
  1. Copy ~/.ccs/cliproxy/auth/ to new machine
  2. Re-authenticate on new machine (tokens specific to each machine)
Better: Re-auth on each machine for security.
  • Different providers: Always concurrent (isolated)
  • Same provider, different accounts: Concurrent (if supported by backend)
  • Claude Accounts: Concurrent (different profiles)
  • Same provider, same account: Not recommended (session conflicts)