Echoing what @liquefy said! Looks like the command runs and is on the allowlist. If you click in the upper right (the arrow in a square) and look at the terminal, do you see output?
@Colin Why interface asking me to approve files if it still running the command and not finished yet? Weird…
Please do not answer: it is ok. It is not ok and I described why it is not Ok. If a development team does not have enough time to analyze the problem, just say that: we do not have time yet. That is understandable.
But if you say it is Ok when it is not in hope to close as much tickets as you can, that makes me angry/upset.
For example you could categorize this as: “Scheduled for later”. This is understandable.
What I would expect in this situation is that the chat made changes to the files earlier in the conversation.
I was just trying to clarify what the UI is trying to communicate. Let’s assume good intent and good faith here. It’s good feedback that the “Waiting for approval” text appears to refer to the terminal command (which appears stuck), and I’ll pass it on.
I assume the interface should show something for “All cases” all the times. Or some communication state to AI API. eg. connection is still open, sent/received data etc.
First, I want to apologize and acknowledge that @KES was right to question the UI behavior. We’ve merged several race condition fixes that should resolve the UI state issues. These fixes will be included in version 2.4. If you’d like to try them now, they’re available on Nightly (Cursor Settings > Beta).
Might not make sense to stay on that version while it’s still cooking, but it would be extremely valuable to know if you run into the same issue there where it should () be fixed.
Hello,
Just providing additional feedback here:
This started to happen to me a few moments ago, after the update of cursor, which happened silently. I usually use Sonnet 4.5, and had not realised that Cursor switched the chat to GPT 5.2 during the update.
Choosing Sonnet 4.5 again fixed the situation and I was able to approve the commands.
Hope this helps.
I am running on Mac OS Sequoia 15.4.1
Version: 2.3.35
VSCode Version: 1.105.1
Commit: cf8353edc265f5e46b798bfb276861d0bf3bf120
Date: 2026-01-13T07:39:18.564Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.4.0
) be fixed.
