Claude Code / AI Coding Tools

Claude Code Sends Prompt-Caching Beta Header to Custom Endpoints Even When Disabled

Fix Claude Code sending prompt-caching beta header to custom API endpoints (ANTHROPIC_BASE_URL) when caching is disabled Includes evidence for Claude Code troubleshooting demand.

Source-backed Last updated May 13, 2026 1 source Needs local verification

Category: AI Coding Tools
Error signature: API error 400: The provider does not support the prompt-caching-scope-2026-01-05 beta header
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 13, 2026
Verification status: Source-backed
Evidence: 1 public source URL

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 Claude Code, 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

API error 400: The provider does not support the prompt-caching-scope-2026-01-05 beta header is a Claude Code failure pattern reported for developers trying to fix claude code sending prompt-caching beta header to custom api endpoints (anthropic_base_url) when caching is disabled. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue #21644 in anthropics/claude-code: With enablePromptCaching=false and useAnthropicBetaHeaders=false set in VS Code settings.json, and a custom ANTHROPIC_BASE_URL that doesn't support prompt-caching-scope-2026-01-05, the beta header is still sent, causing API errors when using claude-4.5-opus model.

Common causes

Even when users explicitly disable prompt caching in VS Code settings (claudeCode.enablePromptCaching: false) and unset beta headers (claudeCode.useAnthropicBetaHeaders: false), Claude Code v2.1.23 still sends the 'prompt-caching-scope-2026-01-05' beta header to custom API endpoints. This breaks integration with self-hosted or proxy API servers that don't support the beta.
GitHub issue #21644 in anthropics/claude-code: With enablePromptCaching=false and useAnthropicBetaHeaders=false set in VS Code settings.json, and a custom ANTHROPIC_BASE_URL that doesn't support prompt-caching-scope-2026-01-05, the beta header is still sent, causing API errors when using claude-4.5-opus model.

Quick fixes

Confirm the exact error signature matches API error 400: The provider does not support the prompt-caching-scope-2026-01-05 beta header.
Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

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 API error 400: The provider does not support the prompt-caching-scope-2026-01-05 beta header exactly before applying the quick fix.
Compare the failing environment with Claude Code 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 API error 400: The provider does not support the prompt-caching-scope-2026-01-05 beta header mean in Claude Code?

API error 400: The provider does not support the prompt-caching-scope-2026-01-05 beta header indicates the workflow described by "Claude Code Sends Prompt-Caching Beta Header to Custom Endpoints Even When Disabled" 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 API error 400: The provider does not support the prompt-caching-scope-2026-01-05 beta header?

Check whether this cause matches your environment: Even when users explicitly disable prompt caching in VS Code settings (claudeCode.enablePromptCaching: false) and unset beta headers (claudeCode.useAnthropicBetaHeaders: false), Claude Code v2.1.23 still sends the 'prompt-caching-scope-2026-01-05' beta header to custom API endpoints. This breaks integration with self-hosted or proxy API servers that don't support the beta.

Is the API error 400: The provider does not support the prompt-caching-scope-2026-01-05 beta header guidance source-backed?

The "Claude Code Sends Prompt-Caching Beta Header to Custom Endpoints Even When Disabled" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for API error 400: The provider does not support the prompt-caching-scope-2026-01-05 beta header?

For "Claude Code Sends Prompt-Caching Beta Header to Custom Endpoints Even When Disabled", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." 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 API error 400: The provider does not support the prompt-caching-scope-2026-01-05 beta header?

For "Claude Code Sends Prompt-Caching Beta Header to Custom Endpoints Even When Disabled", collect the failing Claude Code command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.