A custom provider for pi that connects to the Command Code Provider API.
Disclaimer: This is an unofficial, community-maintained integration. It is not affiliated with, endorsed by, or supported by Command Code. You need your own Command Code account and API key or subscription. Command Code's terms, availability, and pricing apply.
pi install npm:pi-commandcode-providerStart or reload pi, then authenticate:
/loginSelect Use a subscription, then Command Code. Complete the browser flow and choose a model with /model.
Install the same package in Oh My Pi:
omp plugin install pi-commandcode-providerRestart OMP or run /reload, then use /login and select Use a subscription followed by Command Code.
Run /login in pi or OMP. Select Use a subscription, then Command Code. The browser flow stores the returned credential in the host's auth file.
If automatic transfer from the browser fails, copy the API key shown by Command Code and paste it into the terminal prompt.
export COMMANDCODE_API_KEY="user_..."The provider also reads existing credentials from:
~/.commandcode/auth.json~/.pi/agent/auth.json~/.omp/agent/auth.json
Supported examples:
{
"apiKey": "user_..."
}{
"command-code": {
"type": "api",
"key": "user_..."
}
}{
"commandcode": "user_..."
}Open /model and select one of the models provided by Command Code. Model availability changes over time and is refreshed from the Provider API when the extension loads.
Reasoning metadata is enriched only for models whose Command Code effort support is known. Those models register a model-specific thinkingLevelMap, so pi and OMP expose only supported levels. A selected supported level is sent as the documented params.reasoning_effort field; off, unsupported levels, and newly discovered models without metadata do not add reasoning fields to the request. No prompt instructions are injected.
List Command Code models from the terminal:
pi --list-models commandcodeIn OMP, use:
omp modelsFor non-interactive OMP requests, use a provider-qualified model ID shown by omp models. For example:
omp -p "hello" --model commandcode/deepseek/deepseek-v4-flashThe provider fetches the current model catalog from:
https://api.commandcode.ai/provider/v1/modelsThe last successful catalog is cached at <agent-dir>/commandcode-models.json. For pi this is ~/.pi/agent/commandcode-models.json by default. Compatible hosts such as OMP use their own agent directory.
If the endpoint is temporarily unavailable, the provider uses the cached catalog. On a first offline start without a cache, pi still loads, but Command Code models remain unavailable until the connection is restored and /commandcode-refresh succeeds.
While pi is running, use these provider commands without restarting:
/commandcode-refreshfetches and re-registers the current model catalog. Overlapping refreshes are coalesced, and a failed refresh keeps the last valid catalog active./commandcode-statusshows redacted discovery diagnostics, including the source, model count, timestamps, cache path, endpoint, and warning.
The following environment variables are intended for tests, local mocks, and compatible API endpoints:
COMMANDCODE_API_BASECOMMANDCODE_MODELS_URLCOMMANDCODE_MODELS_CACHECOMMANDCODE_MODELS_TIMEOUT_MS(defaults to 10 seconds; invalid or non-positive values use the default)
This provider currently advertises and accepts text input only. The extension uses Command Code's legacy /alpha/generate protocol, while the public Provider API documentation describes image parts for its documented /provider/v1 endpoints. The legacy request path has no documented image-part contract, and the model catalog fixture exposes model IDs and context lengths but no image capability or limit fields.
To avoid silently dropping or changing image data, the provider rejects image content in user messages and tool results before making a network request. It does not claim image capability or define image-size/count limits. This limitation can be revisited when Command Code documents image parts and limits for the protocol used here.
The Command Code Provider API does not currently include prices in its model catalog. This extension therefore keeps a static table for models with known prices so pi can display estimated request costs.
Models missing from that table display zero cost in pi. This does not mean that Command Code will bill the request at zero. Check the current Command Code pricing before relying on the displayed value.
Update installed pi packages:
pi update --extensionsRemove the provider:
pi remove npm:pi-commandcode-providerFor OMP:
omp plugin upgrade pi-commandcode-provider
omp plugin uninstall pi-commandcode-providerStart an isolated pi instance with only the current checkout installed and no existing Command Code credentials:
npm run pi:isolatedRun /login inside pi. Temporary credentials, configuration, and sessions are deleted when pi exits.
Start the current checkout with your existing pi credentials and only Command Code models in the model picker:
npm run pi:authenticatedBoth commands accept additional pi arguments after --, for example npm run pi:authenticated -- --model claude-sonnet-4-6.
See CONTRIBUTING.md for local setup and tests. See RELEASE.md for the release process.
MIT