Skip to main content

​
GLMT Deprecation

ccs glmt is deprecated and no longer a supported public product surface. It remains available only as a compatibility path for legacy scripts and configs that still use the old profile name or legacy glmt.settings.json payloads.

​
Use This Instead

NeedSupported commandNotes
Z.AI API profileccs glmDirect Z.AI API profile for standard GLM usage
Reasoning-first Kimi API profileccs kmDirect Kimi for Coding profile
Long-context Kimi via OAuthccs kimiCLIProxy OAuth provider for device-code auth

​
Migration

  1. Replace ccs glmt invocations in scripts, snippets, and local aliases with ccs glm or ccs km.
  2. For new setups, create glm or km from the dashboard or with ccs api create --preset glm|km.
  3. Keep legacy glmt only until old automation, bookmarks, and docs links are updated.

​
Legacy Behavior That Still Exists

  • ccs glmt now routes through the normal settings-profile flow after CCS normalizes legacy proxy-only settings to the direct GLM endpoint at runtime.
  • Existing glmt.settings.json files remain readable during migration.
  • CCS still prints explicit deprecation warnings so old scripts are not silently treated as a supported product surface.
  • No new setup or feature guidance is published for GLMT.

​
When You Might Still Encounter GLMT

  • Existing shell scripts or CI jobs still call ccs glmt
  • Old settings files still include glmt.settings.json
  • Historical links still point to this page