You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
OpenRouter runner enables provider fallbacks for every selected model #9196
The OpenRouter runner writes options.provider.allow_fallbacks: true for every model entry in the generated opencode.json. The component's retry semantics are described as retrying the same model; enabling provider fallbacks lets OpenRouter route a request to a backup provider, so a retry or a normal run can execute against a different provider than the one selected.
Expected behavior
The runner should keep allow_fallbacks disabled when the contract is to retry the selected model, as the parent revision did. If fallback routing is desired, it should be explicit configuration, not unconditional for every model.
and invokes opencode ... -m openrouter/x-ai/grok-4.6. The parent revision emitted allow_fallbacks: false for the same input, and the target commit changed the value from false to true.
The value is hardcoded for every entry in modelEntries. The commit fix: Reset OpenCode retries after progress changed the line from false to true while its stated intent is to reset retries after progress, not to enable cross-provider fallback.
Impact
Every OpenRouter component run now permits backup-provider substitution. A request can be served by a different provider (with different pricing, data handling, or model revision) even though the user selected a specific model. Retry behavior no longer matches the "same model" contract and can mask provider-specific failures.
Suggested fix
Restore allow_fallbacks: false for the per-model options, or expose it as an explicit component input and default to false. Add a test asserting the generated opencode.json has allow_fallbacks: false unless the component explicitly opts in.
Activity