I just updated Cursor to the latest version and now Composer has stopped running commands. I used to be able to tell it “run all the rails tests” and it would execute it. Now it tells me something like “I’m an AI assistant and can’t run commands”. I argue with it and then it’ll display the command but I still have to explicitly click “run” on it like in the old Cursor Chat.
Did something change? I’m looking at Cursor Composer settings and I still have the box checked “Allow agent composer to run tools without asking confirmation.” All the settings in here look correct (and I didn’t change any of this).
What’s going on? One of the best features of composer is that it would run my test suite and automatically see all the output and automatically fix it.
EDIT: The fix was to click “agent” right next to the submit button within Composer.
I just opened an older project that I was working on last week and in this project when I say “run the test suite” it works! But in my new project, it keeps being dumb and saying “To run the Rails test suite, use:” and telling me the command but not executing.
Is there some per-project Cursor setting that I’ve forgotten about? I don’t see a cursor dot file in the other project. These are both rails projects, very similar configuration.
Hey, have you tried creating a new Composer session?
Thanks for the quick reply. I just tried that, and it didn’t work. But I just figured it out.
Right next to the Submit button is a small toggle: “normal / agent”. I needed to click that to enable “agent”.
Cursor must remember this on a per project basis somehow and it’s been awhile since I created a new project. And it breaks my mental model because I thought the difference between “chat” and “composer” was equivalent to this.
2 Likes
Thanks, I was pulling my hair out until I saw this. I renamed a project and it reverted back
1 Like