[BUG] OpenRouter Costs Went Way Up in 3.38.0

[traviscollins]

Problem (one or two sentences)

Version 3.38.0 caused a huge jump in OpenRouter usage costs.

Context (who is affected and when)

I've been using RooCode daily for many months. Recently I noticed a huge jump in costs for even very small conversations when using OpenRouter. Other users have noticed the same.

https://www.reddit.com/r/RooCode/comments/1py193v/did_something_change_with_roocode_prior/

I believe it is related #10341

Reproduction steps

1. Configure OpenRouter connection
2. Perform a small conversation
3. Downgrade to 3.37.1
4. Perform the same small conversation - not price difference

Expected result

No change in costs

Actual result

Huge jump in costs

Variations tried (optional)

No response

App Version

3.38.0

API Provider (optional)

OpenRouter

Model Used (optional)

Claude Sonnet 4.5

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

I've analyzed this issue and confirmed the root cause. PR #10341 removed the OpenRouter "middle-out" transform feature, which was previously enabled by default. This transform uses context compression to reduce token usage and costs.

What was removed in PR #10341:

• The transforms: ["middle-out"] parameter was removed from API calls to OpenRouter
• Previously, this was enabled by default via (this.options.openRouterUseMiddleOutTransform ?? true)
• The user setting checkbox was also removed from the UI

Proposed Implementation Plan:

I recommend restoring the middle-out transform functionality with a simple, always-on approach:

1. Modify src/api/providers/openrouter.ts: Re-add the transforms parameter to the completionParams object:

   const completionParams: OpenRouterChatCompletionParams = {
     // ... existing params ...
     transforms: ["middle-out"],  // Always enable context compression
     // ... rest of params ...
   }

2. Update tests: Add test coverage for the transforms parameter being included in API calls

This approach:

• Restores cost savings for all OpenRouter users immediately
• Keeps the implementation simple (no UI toggle needed)
• Follows the previous default behavior where it was enabled by default

Alternative approaches (if you prefer):

• A: Restore the user setting checkbox to allow users to disable it if needed
• B: Add an "advanced settings" toggle for power users who want more control

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[GSJWilliams]

I haven't been able to compare v3.37.1 directly to v3.38.0 yet, but I do feel like costs are much higher today. This is compared to several months of heavy, enterprise work (5-10 hours a day) with no change in my workflow whatsoever.

I've been tracking my Roo usage for a few months now, and I wonder if the pricing changed on Friday. This is all primarily with Claude Sonnet 4.5 usage.

[traviscollins]

I did some additional testing. It seems the bug might be in 3.37.0 or .13.36.0 has much lower running costs. A few tests showed 3.37.1 had costs more in like with 3.38.0This is a pretty serious problem. On Dec 29, 2025, at 2:20 PM, Joshua Williams ***@***.***> wrote:GSJWilliams left a comment (RooCodeInc/Roo-Code#10374) I haven't been able to compare v3.37.1 directly to v3.38.0 yet, but I do feel like costs are much higher today. This is compared to several months of heavy, enterprise work (5-10 hours a day) with no change in my workflow whatsoever. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>