Rejecting a file command by sending text sometimes

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When the model asks to run a command, and instead of accepting or rejecting, a message is written, sending that message sometimes doesn’t immediately send it, but rather queues it while the model “gets to think about the tool rejection” without the information in the message.

Steps to Reproduce

Require approval for commands, get the LLM to request a command, send a message instead of accepting / rejecting the command.

Expected Behavior

The LLM should immediately receive the message, and the tool rejection at the same time, without queuing the message.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.33
VSCode Version: 1.99.3
Commit: a84f941711ad680a635c8a3456002833186c4840
Date: 2025-10-03T03:28:06.574Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hi @Michael_Orenstein!

When the Agent is working (including waiting for command approval), messages are queued by default so they’re processed after the current task.

To send your message immediately with the tool rejection, try using Cmd+Enter instead of just Enter when typing your message. This bypasses the queue and sends the message right away.

More details: https://cursor.com/docs/agent/planning#queued-messages

You can change this behaviour in the settings if you prefer otherwise

Thanks for the workaround, but sending the message rejects the tool call, so intrinsically there’s nothing for the agent to do other than read my reply? I would like the messages to queue by default, but when the agent is synchronously waiting on my reply via approval, or rejection, a rejection with extra context should supply the context immediately.

That’s great feedback, I’ll pass it on to the team.

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.