Active model is not visible enough, and model choice has real billing consequences
Status Open
Maintainer reply None cached
Activity 0 comments · opened Aug 14, 2026
Active model is not visible enough, and model choice has real billing consequences.
Fable can be selected (or left selected from a previous session) without any persistent indicator of which model is running. Because different models consume plan limits at very different rates, a user can burn through a Max plan's session budget in minutes without ever seeing which model caused it — and then be pushed toward API billing.
Two asks:
- Show the active model persistently in the UI by default, not only inside
/model. - Warn on model switch when the new model has materially different rate-limit consumption, and surface consumption per model in usage reporting.
Whatever the intent, the current design means the most expensive choice is also the least visible one. That reads badly, and it costs users money they didn't knowingly agree to spend...
.....................I am sure your commercial team knows this................................