Ryu Hi Thimows, Your repro looks useful. I’d make the next test isolate three things: SDK forwarding, Gateway routing, and provider-specific behavior. First, remove Gateway caching from the minimal repro so the only variable is reasoning: Then pin one provider at a time instead of letting Gateway choose dynamically: If reasoning: 'none' is still ignored when pinned to a single provider, that points to a model/provider capability or mapping issue. If it only happens with automatic routing, then the issue is more likely Gateway selecting providers that do not handle the same reasoning control consis
Thimows Thanks for your reply @ryux1! one important clarification: this is a regression. reasoning: 'none' previously disabled visible reasoning with this same integration. It recently stopped working and is now affecting our production apps: agent steps take substantially longer and consume far more tokens than expected. I ran the requested isolation using ai@7.0.31 and @ai-sdk/gateway@4.0.23, with Gateway caching removed: A mocked transport confirmed the SDK forwards both "reasoning": "none" and the Gateway only option in the outbound request. Automatic routing selected Fireworks and still streamed
Ryu Hi Thimows, Thanks, that narrows it down a lot. With the mocked transport confirming the SDK forwards reasoning: "none", and both pinned providers still emitting visible reasoning, I’d stop looking at caching or automatic routing. This now looks like either a Gateway provider-translation regression or a provider-side regression that Gateway is exposing for both routes. The most useful bug report package is probably: And then include those generation IDs plus one small captured stream sample showing the reasoning part and the final usage object. The Fireworks mismatch is especially important: v