Yesterday day while working IN AGENT MODE I started getting responses in the chat saying that commands cannot be executed because I need to switch to Agent Mode. I tried switching ask and then going back but it still Agent mode stays grayed out. I’m new to this so I don’t know if it’s something I did/clicked inadvertently or if it’s an issue with Cursor…. Need help, my project has come to a standstill…
Hi @George_Hillman would it be possible for you to share a screenshot or replicate somehow for example using a loom?
Here’s a screenshot. Notice that it’s in the middle of a chat where Agent mode is working fine, then it’s not. Notice the Agent button - should it be highlighted or is that normal? What would make Cursor not be able to see that it’s still in Agent mode?
Hey, thanks for the screenshot. It really helped. I can clearly see the issue. The Agent button is selected at the bottom of the chat, but the model thinks it’s in Ask mode.
The fastest fix is to open a new chat Cmd+I and make sure Agent is selected before you send the first message. That usually fixes the state mismatch. Continuing in a chat where this already happened usually won’t help. It won’t fix itself.
If it keeps happening even in new chats, try fully restarting Cursor (Cmd+Q, then open it again).
Can you share your Cursor version? (Cursor menu > About Cursor, top left.) The team is tracking this issue, and your report with the screenshot really helps with prioritizing it.
Let me know if creating a new chat gets you unblocked.