Skip to main content

​
CLIProxy API Integration

CCS uses CLIProxyAPI and CLIProxyAPIPlus to power OAuth-backed provider routing. In the current CCS UI, that capability is split across three routes, not one generic page.

​
Current Surface Map

RouteWhat lives thereUse it when
/cliproxyOAuth overview workspaceprovider status, variants, quick setup, routing, account actions
/cliproxy/ai-providersAI Providers workspaceAPI-key and connector routes that belong inside CLIProxy
/cliproxy/control-panelembedded control panelupstream management-center features that CCS does not re-skin

​
OAuth Overview Workspace

CLIProxy overview workspace
The /cliproxy route is the main CCS-owned control surface. It includes:
  • a provider rail for authenticated OAuth providers
  • a variant list for CCS-managed provider variants
  • a proxy status widget and backend label
  • quick setup for guided first-time configuration
  • provider editors for accounts, models, targets, and routing
  • deep links such as ?provider=claude and ?action=auth for focused flows

​
Supported OAuth Providers

ProviderStatusNotes
ClaudeOAuthAnthropic Claude with quota support
GeminiOAuthGoogle Gemini via OAuth
CodexOAuthOpenAI Codex routing
AntigravityOAuthmulti-account routing
GitHub CopilotOAuthCopilot account routing with quota support
KiroOAuthAWS Builder ID / IDC-driven Kiro access
QwenOAuthAlibaba Qwen Code
iFlowOAuthalternative AI routing
KimiOAuthMoonshot Kimi OAuth-backed routing

​
Quota-Supported Providers

agy · claude · codex · gemini · ghcp

​
Model Catalogs And Pickers

CCS treats CLIProxy management model definitions as the primary catalog source. The dashboard resolves model metadata in this order:
  1. live CLIProxy management catalog
  2. cached catalog snapshot
  3. static CCS fallback catalog
That keeps the overview workspace usable even when the proxy is briefly unavailable. 
ccs cliproxy catalog
ccs cliproxy catalog refresh
ccs cliproxy catalog reset

​
Routing Strategy

CCS exposes the proxy-wide routing strategy directly instead of inferring it from account mix.
StrategyBehaviorGood fit
round-robinspread requests across matching healthy accountseven usage and predictable distribution
fill-firstdrain one healthy account before touching backupskeep backup accounts cold until needed
CCS keeps round-robin as the default until you change it explicitly. 
ccs cliproxy routing
ccs cliproxy routing explain
ccs cliproxy routing set fill-first
ccs cliproxy routing set round-robin

​
AI Providers Workspace

/cliproxy/ai-providers is now the dedicated home for non-OAuth upstreams that still belong to the proxy layer. Use it for:
  • API-key families such as Gemini, Codex, Claude-compatible, and Vertex routes
  • named OpenAI-compatible connectors
  • advanced route composition with prefixes, proxy overrides, headers, and model aliases
Use API Profiles instead when you want a CCS-native profile with its own .settings.json.

​
Control Panel Embed

/cliproxy/control-panel embeds the upstream management center inside the CCS dashboard shell.
  • Local mode reverse-proxies management.html through the dashboard server to avoid cross-origin and port issues
  • Remote mode uses the saved remote proxy config and bootstraps auth into the iframe when a management token is available
Use this page when the upstream management center already exposes the exact operation you need and CCS has intentionally chosen not to duplicate it.

​
Target Metadata

Variants on the overview route can carry a CCS target:
TargetCLIMeaning
claudeClaude Codedefault target
droidFactory Droidalternate runtime for compatible flows
ccs cliproxy create my-droid --provider gemini --target droid
ccs cliproxy edit my-droid --target droid
The target is CCS metadata layered on top of CLIProxy-managed routing.

​
Quick Start

ccs config
# Sidebar -> CLIProxy
Start on /cliproxy for OAuth-backed providers. Move to /cliproxy/ai-providers when you need API-key or connector routes. Open /cliproxy/control-panel when you need the upstream management-center surface.