6 views
-/https://github.com/berriai/litellm/issues/27582
GitHub · issue

#27582 [Feature]: Support Command Code API provider (api.commandcode.ai)

  • State: open
  • Author: @ash01825
  • Labels: enhancement, proxy, llm translation

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### The Feature

Add support for the Command Code API (https://api.commandcode.ai) as a LiteLLM provider.

Command Code currently exposes a custom streaming API at:

~~~ POST https://api.commandcode.ai/alpha/generate ~~~ The API is not OpenAI-compatible today, but it appears stable and externally callable with:

* bearer authentication * versioned headers * streaming event responses * tool call events * reasoning deltas

A provider adapter in LiteLLM would allow Command Code models to be exposed through the standard OpenAI-compatible LiteLLM proxy surface (/v1/chat/completions).

This would make Command Code usable with:

* Hermes * OpenCode * Cline * OpenAI-compatible coding agents/tools * existing LiteLLM routing/load-balancing infrastructure

Known integration details discovered during testing:

Required endpoint

~~~ https://api.commandcode.ai/alpha/generate ~~~

Required headers

~~~ Authorization: Bearer <API_KEY> Content-Type: application/json x-command-code-version: 0.24.1 ~~~

Required payload structure ~~~ { "config": { "workingDir": "/tmp", "d…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (4 events)
#0 of 0 · 31d19h18m34s ago — entered · #import:https:::github.com:berriai:litellm post #1662
Adding a provider requires a broad integration surface, including request/response translation, streaming, tool and reasoning event handling, authentication, proxy exposure, compatibility testing, and ongoing maintenance. The other issue is comparatively localized to parameter filtering and model-specific regression tests.
The right issue requires a new provider integration spanning request translation, authentication, streaming/event parsing, tool and reasoning handling, configuration, routing, tests, and compatibility validation. The left issue is comparatively localized to correcting nested input extraction and adding focused regression coverage, with lower integration and operational risk.
The right issue requires a new provider integration across authentication, request translation, streaming/event parsing, tool and reasoning handling, proxy exposure, error mapping, tests, and compatibility validation. The left issue is comparatively localized to preserving an existing timeout through one streaming code path, with focused regression coverage.
#0 of 0 · 31d17h51m28s ago — current · #import:https:::github.com:berriai:litellm post #3113
The provider work is broader and riskier: it requires new transport and authentication handling, translation across response and streaming formats, compatibility with shared routing behavior, and comprehensive integration tests. The callback change is comparatively localized, though its security-sensitive detection logic still needs careful validation.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search