Default to 1M context models and add model selector#90
Conversation
|
1m is a good shout! I'm not sure about changing the model, I think Sonnet is generally a good default. But I think it might be nice to make it easier to change the model when you need/want to in a chat. One option that comes to mind:
One downside here would be if you want to send a follow up with a different model. That might be ok - you can stop it if you don't want to wait, then you get idle state and can change the model. We could also add a model selector in the top right, across from the status bubble. That could either be there all the time (so we have status top left, model selector top right), or we could have it only there when there's a non-idle status taking the left status bubble space, and then come back to the left when idle. WDYT? |
Replace the static model name display in the status bar with an interactive model picker when idle. Tapping shows a menu to switch between Sonnet, Opus, and Haiku for the current chat session. - ChatStatusBar: idle state shows a Menu-based model picker with sparkle icon and chevron indicator - ChatViewModel: add modelOverride property that takes precedence over the global default from Settings - ClaudeModel: update Sonnet and Opus raw values to 1M context variants (sonnet[1m], opus[1m]) - Keep Sonnet as the global default per maintainer feedback Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
e4dbc4a to
ba57035
Compare
|
Reworked the PR based on your feedback:
The override is ephemeral (per chat session, not persisted). Selecting the same model as the global default clears the override. The picker shows a sparkle icon + model name + chevron to indicate it's tappable. |
|
Looks great, thankyou! |
Summary
opus[1m]andsonnet[1m]CLI aliases to enable 1 million token context windowsTest plan
opus[1m]andsonnet[1m]aliases work with local Claude CLIGenerated with Claude Code