Cline CLI / AI Coding Tools

Cline CLI v3.0.2 LiteLLM provider sends to /responses endpoint instead of /chat/completions — 404 Not Found on compatible proxies

Developer using Cline CLI with LiteLLM-compatible corporate proxy gets 404 errors because CLI uses wrong API endpoint; VS Code extension works fine but CLI does not Includes evidence for Cline CLI troubleshooting demand.

Source-backed Last updated May 22, 2026 2 sources Needs local verification

Category: AI Coding Tools
Error signature: litellm provider hardcodes protocol:"openai-responses" causing requests to go to /v1/responses instead of /v1/chat/completions; many LiteLLM-compatible proxies implement only /chat/completions resulting in 404 Not Found
Quick fix: Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.
Updated: May 22, 2026
Verification status: Source-backed
Evidence: 2 public source URLs

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Cline CLI, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

litellm provider hardcodes protocol:"openai-responses" causing requests to go to /v1/responses instead of /v1/chat/completions; many LiteLLM-compatible proxies implement only /chat/completions resulting in 404 Not Found is a Cline CLI failure pattern reported for developers trying to developer using cline cli with litellm-compatible corporate proxy gets 404 errors because cli uses wrong api endpoint; vs code extension works fine but cli does not. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub cline/cline#10781 opened May 15 2026 by Giton22. Cline CLI v3.0.2 uses protocol:openai-responses for litellm provider while VS Code extension correctly uses client.chat.completions.create(). PR #10826 linked by mturac May 17 fixing the routing. Category mapping: Cline CLI is an AI coding tool per SKILL.md category mapping. High commercial value because it blocks paid model access behind common enterprise proxy setups.

Common causes

GitHub cline/cline#10781 opened May 15 2026 by Giton22. Cline CLI v3.0.2 uses protocol:openai-responses for litellm provider while VS Code extension correctly uses client.chat.completions.create(). PR #10826 linked by mturac May 17 fixing the routing. Category mapping: Cline CLI is an AI coding tool per SKILL.md category mapping. High commercial value because it blocks paid model access behind common enterprise proxy setups.

Quick fixes

Confirm the exact error signature matches litellm provider hardcodes protocol:"openai-responses" causing requests to go to /v1/responses instead of /v1/chat/completions; many LiteLLM-compatible proxies implement only /chat/completions resulting in 404 Not Found.
Check the Cline CLI account, local tool state, and provider configuration involved in the failing workflow.
Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match litellm provider hardcodes protocol:"openai-responses" causing requests to go to /v1/responses instead of /v1/chat/completions; many LiteLLM-compatible proxies implement only /chat/completions resulting in 404 Not Found exactly before applying the quick fix.
Compare the failing environment with Cline CLI versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does litellm provider hardcodes protocol:"openai-responses" causing requests to go to /v1/responses instead of /v1/chat/completions; many LiteLLM-compatible proxies implement only /chat/completions resulting in 404 Not Found mean in Cline CLI?

litellm provider hardcodes protocol:"openai-responses" causing requests to go to /v1/responses instead of /v1/chat/completions; many LiteLLM-compatible proxies implement only /chat/completions resulting in 404 Not Found indicates the workflow described by "Cline CLI v3.0.2 LiteLLM provider sends to /responses endpoint instead of /chat/completions — 404 Not Found on compatible proxies" failed in a AI Coding Tools context. Start by confirming the exact signature and the component that emitted it.

What should I check first for litellm provider hardcodes protocol:"openai-responses" causing requests to go to /v1/responses instead of /v1/chat/completions; many LiteLLM-compatible proxies implement only /chat/completions resulting in 404 Not Found?

Check whether this cause matches your environment: GitHub cline/cline#10781 opened May 15 2026 by Giton22. Cline CLI v3.0.2 uses protocol:openai-responses for litellm provider while VS Code extension correctly uses client.chat.completions.create(). PR #10826 linked by mturac May 17 fixing the routing. Category mapping: Cline CLI is an AI coding tool per SKILL.md category mapping. High commercial value because it blocks paid model access behind common enterprise proxy setups.

Is the litellm provider hardcodes protocol:"openai-responses" causing requests to go to /v1/responses instead of /v1/chat/completions; many LiteLLM-compatible proxies implement only /chat/completions resulting in 404 Not Found guidance source-backed?

The "Cline CLI v3.0.2 LiteLLM provider sends to /responses endpoint instead of /chat/completions — 404 Not Found on compatible proxies" page is labeled source-backed. It has 2 public source URLs from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for litellm provider hardcodes protocol:"openai-responses" causing requests to go to /v1/responses instead of /v1/chat/completions; many LiteLLM-compatible proxies implement only /chat/completions resulting in 404 Not Found?

For "Cline CLI v3.0.2 LiteLLM provider sends to /responses endpoint instead of /chat/completions — 404 Not Found on compatible proxies", avoid applying "Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging litellm provider hardcodes protocol:"openai-responses" causing requests to go to /v1/responses instead of /v1/chat/completions; many LiteLLM-compatible proxies implement only /chat/completions resulting in 404 Not Found?

For "Cline CLI v3.0.2 LiteLLM provider sends to /responses endpoint instead of /chat/completions — 404 Not Found on compatible proxies", collect the failing Cline CLI command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.