OpenRouter / AI Coding Tools

OpenRouter Provider Ignores Selected Model — Silently Falls Back to Default

Fix OpenRouter provider ignoring the user-selected model and falling back to the default Anthropic model Includes evidence for OpenRouter troubleshooting demand.

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

Category: AI Coding Tools
Error signature: OpenRouter provider ignores selected model and falls back to claude-sonnet-4-6
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 15, 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 OpenRouter, 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

OpenRouter provider ignores selected model and falls back to claude-sonnet-4-6 is a OpenRouter failure pattern reported for developers trying to fix openrouter provider ignoring the user-selected model and falling back to the default anthropic model. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

OpenRouter provider fails to preserve selected model parameter. Silently uses default Anthropic model instead. Users are charged for OpenRouter credits but receive responses from a different model.

Common causes

When using OpenRouter provider, the selected model (e.g. openai/gpt-4o) is not preserved. The plugin silently falls back to claude-sonnet-4-6 without warning. Users pay for OpenRouter credits but get wrong model.
OpenRouter provider fails to preserve selected model parameter. Silently uses default Anthropic model instead. Users are charged for OpenRouter credits but receive responses from a different model.

Quick fixes

Confirm the exact error signature matches OpenRouter provider ignores selected model and falls back to claude-sonnet-4-6.
Check the OpenRouter 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 OpenRouter provider ignores selected model and falls back to claude-sonnet-4-6 exactly before applying the quick fix.
Compare the failing environment with OpenRouter 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 OpenRouter provider ignores selected model and falls back to claude-sonnet-4-6 mean in OpenRouter?

OpenRouter provider ignores selected model and falls back to claude-sonnet-4-6 indicates the workflow described by "OpenRouter Provider Ignores Selected Model — Silently Falls Back to Default" 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 OpenRouter provider ignores selected model and falls back to claude-sonnet-4-6?

Check whether this cause matches your environment: When using OpenRouter provider, the selected model (e.g. openai/gpt-4o) is not preserved. The plugin silently falls back to claude-sonnet-4-6 without warning. Users pay for OpenRouter credits but get wrong model.

Is the OpenRouter provider ignores selected model and falls back to claude-sonnet-4-6 guidance source-backed?

The "OpenRouter Provider Ignores Selected Model — Silently Falls Back to Default" 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 OpenRouter provider ignores selected model and falls back to claude-sonnet-4-6?

For "OpenRouter Provider Ignores Selected Model — Silently Falls Back to Default", 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 OpenRouter provider ignores selected model and falls back to claude-sonnet-4-6?

For "OpenRouter Provider Ignores Selected Model — Silently Falls Back to Default", collect the failing OpenRouter command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.