On a new agent tab, if model starts with Auto, it automatically changes to Composer 2.5 on submission
It then suggests user to change to ‘auto’ (undercase). On first click, it keeps using Composer 2.5. On second click, changes to a non-existent ‘auto’ model.
Hey, thanks for the detailed report and the video, it really helps.
Both issues you described are known:
Auto switches to Composer 2.5 in a new chat after you hit the usage limit for fancy models.
The switch to auto button doesn’t switch back correctly. On the first click it stays on Composer 2.5, on the second click it switches to a model that doesn’t exist.
Both bugs have been reported internally. I can’t share an ETA yet, but I’ll post an update in the thread once I have one.
Temporary workaround: pick the model you want manually via the model picker, not via the banner suggestion button. If anything else comes up, let me know.
Hey, I get it, this bug is really annoying. Both issues are known and already reported internally, but I can’t share a fix timeline yet. As soon as I have an update, I’ll reply here.
For now, the workaround is to pick the model manually in the model picker, not via the suggestion button in the banner. That way it won’t switch to a model that doesn’t exist.
Hey @LLCampos, here’s the promised update on this thread.
The issue with the “Switch to auto” button in the limit message, the one that was setting the non-existent lowercase “auto” model, has been fixed on our side. Nothing needs to be done there.
If lowercase “auto” is still showing in the model picker from older versions, just select Auto in the picker once. After that, the value should stay correct.
One more thing, could you check whether Auto still switches to Composer 2.5 in a new chat after hitting the usage limit? If everything works fine now, no need to reply. If it still happens, please share a few words about what you’re seeing, that would help.