Setting model to composer 2.0 in automations on cursor.com always fall back to composer 2.5
Steps to Reproduce
Select an automation on the automations page on cursor.com
Switch the model from composor 2.5 to composor 2 in the drop-down selection box
The save button on the right-top of the page become click-able, click and then a hint of “Agent saved successfully” show up at the left-bottom
Refresh or re-enter will still show composor 2.5, trigger the automation through corresponding Github operation and inspect the automation run shows also composor 2.5. But If I switch to haku instead, for example, the switch will be saved successfully.
Hey, thanks for the clear report and screenshots. I can reproduce it.
This looks like a save-time rewrite. composer-2 is marked as deprecated in favor of composer-2.5, so when you save the automation, the model gets silently rewritten. The save shows success, but after reload it rolls back. It does not happen for other models because they are not included in this migration mapping.
I reported this internally. I can’t share an ETA for a fix yet, but I’ll post an update in the thread as soon as I have one.
There is no workaround right now. If you can solve the task on composer-2.5, you’ll need to stay on it for now. If you specifically need composer-2 (for example if the behavior difference is critical for your pipeline), let me know which tasks, that will help us prioritize.
