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
Box silently uses some predefined models when some other model is chosen with OpenRouter as the provider.
Go to the console, create a box with claude code harness, choose, say, DeepSeek V4 Flash from OpenRouter. It will say that it successfully created the box, yet Claude Code falls back to Opus 4.8. If you do it with Codex, it will silently fallback to GPT-5.3-codex.
I realized this when i used my own OpenRouter key, and its logs reported me different models than i used and my credit is gone way faster. I thought it is because of BYOK but the following image is a box with Upstash Managed model provider.
see that console claims it to be deepseek and local logs tell otherwise.
I do not think it is related only to OpenRouter btw, i think this is because of a local model list in the source code since these fallback models were the latest models when box was first introduced. Below is a concise report from my agent. I know that this is not related to this SDK repo but i think this is the best way to reach out.
Bug: Claude Code silently ignores selected OpenRouter model
Using @upstash/box@0.7.0 with an Upstash-managed key:
The Box metadata records the requested DeepSeek model, but Claude Code’s session JSONL records:
anthropic/claude-opus-4.8
Reproduced with both DeepSeek R1—an official OpenRouterModel value—and DeepSeek V4 Flash. It also reproduces through the raw /v2/box REST API, without the SDK.
Expected: execute the selected model, or reject unsupported combinations before inference.
Actual: silently executes and bills an unrelated Opus model.
By the way, apart from this issue, it would be great if we were able to see which harness it is when we are inspecting a specific box on console. It is visible on the boxes list, yet when i click on one of them, there is no indicator stating which harness it is.
Activity
mtahasylmz commentedon Aug 21, 2026
I do not think it is related only to OpenRouter btw, i think this is because of a local model list in the source code since these fallback models were the latest models when box was first introduced. Below is a concise report from my agent. I know that this is not related to this SDK repo but i think this is the best way to reach out.
Bug: Claude Code silently ignores selected OpenRouter model
Using
@upstash/box@0.7.0with an Upstash-managed key:The Box metadata records the requested DeepSeek model, but Claude Code’s session JSONL records:
Reproduced with both DeepSeek R1—an official
OpenRouterModelvalue—and DeepSeek V4 Flash. It also reproduces through the raw/v2/boxREST API, without the SDK.Expected: execute the selected model, or reject unsupported combinations before inference.
Actual: silently executes and bills an unrelated Opus model.
Example retained Boxes:
romantic-mongrel-63475— DeepSeek R1sterling-gorilla-09237— DeepSeek V4 Flashmtahasylmz commentedon Aug 21, 2026
By the way, apart from this issue, it would be great if we were able to see which harness it is when we are inspecting a specific box on console. It is visible on the boxes list, yet when i click on one of them, there is no indicator stating which harness it is.
buggyhunter commentedon Aug 30, 2026
@mtahasylmz thanks for the report, working on it rn
buggyhunter commentedon Aug 31, 2026
@mtahasylmz it should be fixed rn
can you give a try?
mtahasylmz commentedon Aug 31, 2026
@buggyhunter now it works thank you
there's a smaller problem. probably a stale prompt. the agent is somehow convinced that available models are
Opus 4.8, Sonnet 4.6, and Haiku 4.5.yet there is no problem with reaching to gateway and analyzing them. so it can query available models and change to a different one seamlessly.