Models aren't changing correctly

[norto22]

Description

I've set the both Opus 4.7 and Sonnet 4.6 models in the Pilot Shell settings page, restarted Pilot and CC, but when it's going through each step when it needs to change model, I am hit with the error:

"API Error: Extra usage is required for 1M context · run /extra-usage to enable, or /model to switch to standard context"

I believe this means it's trying to use the Sonnet 4.6 model with 1M context, but that's billed as extra usage. I don't want that, I want it all included in my Max 20x plan.

I have 1M context disabled in Pilot settings.

Steps to Reproduce

1. Start a task with Opus 4.7
2. Move to a step requiring a model change (Sonnet 4,6 in this case)
3. Observe API error, it continues with Opus 4.7 if I send a 'Continue' message

Expected vs Actual Behavior

I expect it to correctly swap to the Sonnet 4.6 model, as outlined in my settings, and not try to use the 1M context Sonnet 4.6, which is billed on top of the Max 20x plan.

Environment

• OS: Ubuntu 24.04
• Claude Code version: v2.1.126
• Pilot version: v8.5.2
• Tier: Solo

Error Output

API Error: Extra usage is required for 1M context · run /extra-usage to enable, or /model to switch to standard context

Checklist

• I am using the latest version of Pilot Shell
• I have searched existing issues to avoid duplicates
• I can reproduce this consistently with the steps above

EDIT: I only checked Open issues, I see there are some closed from older CC versions, still doesn't seem to be a reliable workaround though without removing Sonnet completely, and given how fast tokens are used now, would really like to be able to use Sonnet. Plus, I have 1M context disabled, so Opus shouldn't be using 1M either, so model changes should still work.

[norto22]

Upon further testing, it seems to always want to call the 1M context Sonnet model. Can we change it to call the regular context Sonnet model instead?

[buddhamangler]

im hitting this exact same issue, I don't understand because in the settings I turn off the 1M context, but yet when it switches to implementation I get the errror. For right now I manually switch to /model claude-sonnet-4-6 and just say continue, but it is annoying. As a paying customer, I would love to hear from @maxritter on this.

to be clear, with 1M in settings off and Opus 4.7 (not 1M) configured as my model , I execute /spec "xxx", once it asks if I approve to move to implementation (with sonnet 4.6 configured as my implementer), I get the error noted in this issue.

I can see this is related to #132

If this is some limitation with the way claude works, I just want to know how am I supposed to handle it internally. The answer can't just be...turn on 1M and switch all models to Opus (which the settings UI seems to indicate). I drain too many tokens in this mode.