Hey, thanks for the report. We checked the ID you shared and also looked at your account overall.
On the main concern first. There is no silent redirect to a cheaper model. When you select Composer 2.5, your requests are actually served by Composer 2.5. Routing confirms that both before 20.06 and after. There is no shadow redirect after some usage volume. Also, the survey popup, if you answered it, does not affect anything. It is telemetry only, it does not change the model or its behavior.
What you are describing, same model but lower quality, is most often not a model switch. It is usually about the session context like context window size, how the chat history has built up, how the task is phrased, and which files made it into context. This is especially noticeable during long refactors. A couple things that usually help:
- Start a new chat for a new task so you do not carry a bloated context
- Explicitly pull the right files or docs into context, for example that UI library via an @ link, if you notice the model is forgetting it
If you catch a specific reply that is clearly bad, please send the request ID from that exact message. Use the 3 dots on that specific assistant reply in chat. Then the team can review that session directly. Unfortunately, a general it got worse trend cannot be diagnosed from a single ID.
It can also help to read this thread: Share your Thoughts on Composer 2.5!. We are collecting feedback on the model there.