Configuration
The plugin exposes a Command Code settings page. Its connection fields are written to the llm-commandcode configuration section and take effect on the next request without a restart.
| Setting |
Purpose |
apiKey |
Direct API key configuration |
apiKeyEnv |
Credential reference; defaults to COMMANDCODE_API_KEY |
| API base |
Command Code API endpoint |
| Working directory |
Working directory used for requests |
| Request timeout |
Request timeout |
| Stream timeout |
Streaming timeout |
The model catalogue is fetched from GET {apiBase}/provider/v1/models and cached at ~/.commandcode/models-cache.json.
Credentials and commands
The API-key lookup order is config.apiKey, the credential reference named by apiKeyEnv, the launch environment, then ~/.commandcode/auth.json. The last file is created by the official CLI after authentication.
The documented authentication path requires Node.js 22 or newer:
npm i -g command-code@latest installs the CLI.
cmd login is used on macOS and Linux.
cmdc login is used on native Windows.
The browser-based login stores the key in ~/.commandcode/auth.json. A key can instead be created in Command Code Studio and entered in Settings → Command Code, or supplied through COMMANDCODE_API_KEY.
Model and request behaviour
The commandcode route uses POST /alpha/generate. Its live catalogue displays each model’s minimum plan, an active deal or FREE, an Image marker for Vision models, and a context size such as 1M, 256K or 262K. Models are ordered by plan tier: Go, GOAT, Pro, then Provider/Max.
Reasoning-effort controls are available for models that the official catalogue marks with supported levels. Other reasoning models think automatically. Vision-capable models receive image input through the DSH attachment service; text-only models reject image input with UNSUPPORTED_CONTENT.
Requirements and scope
This is an unofficial community integration. Use requires a Command Code account and API key or subscription, and Command Code’s terms apply. The plugin is not affiliated with Command Code, Inc. Its documented external files are ~/.commandcode/models-cache.json and, when CLI authentication is used, ~/.commandcode/auth.json.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub