CCS can delegate execution to alternative CLI targets beyond Claude Code. The Droid adapter routes profiles to the Droid CLI using the same CCS configuration system.
Set target: droid on any API, variant, or composite profile to always route that profile to Droid without needing the --target flag:
# API profileprofiles: my-api: provider: openai target: droid # Always use Droid for this profile# CLIProxy variantcliproxy: variants: my-variant: provider: gemini target: droid # Routes this variant to Droid CLI# Composite variantcliproxy: variants: my-composite: composite: true opus: gemini sonnet: agy target: droid # Routes composite to Droid CLI
Per-profile target is NOT supported for profile types: cliproxy, copilot,
and account. Legacy glmt compatibility profiles now follow the normal
settings-profile flow after runtime normalization, but new setups should still
migrate to glm or km.
ccs glm --target droid # Run GLM on Droid (explicit flag)ccs km --target droid # Run Kimi for Coding on Droidccsd glm # Same via ccsd aliasccs glm # Run GLM on Claude (default)ccsd codex "prompt" # Run Codex on Droidccsd km "prompt" # Run Kimi API profile on Droid