Command allowlist prompting for strange commands

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

when doing a git commit, it asks for command allowlist for ‘n’.
notice in the below command, there are ‘n’ in quotes. that’s tripping up the allowlist.

see screenshot.

git commit --trailer “Co-authored-by: Cursor [email protected]” -m "BI-14072 Delete negative transactionsnnAdd script to back up and delete negative "

Steps to Reproduce

not sure, happens randomly. maybe depends on the text of the full command.

Expected Behavior

it shouldn’t prompt, i already have git commit as allowlist.
also, what does ‘n’ mean

Screenshots / Screen Recordings

hovering over allowlist shows this:

Operating System

Windows 10/11

Version Information

Version: 2.4.31 (system setup)
VSCode Version: 1.105.1
Commit: 3578107fdf149b00059ddad37048220e41681000
Date: 2026-02-08T07:42:24.999Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the report. I can see the screenshots, this is a bug in the allowlist parsing.

What’s happening: PowerShell uses `n as an escape sequence for a newline. The allowlist parser doesn’t handle PowerShell-specific syntax and treats the n after the backtick as a separate command, which is why you’re seeing the prompt.

The team is aware of the allowlist parsing issue. Your report helps raise the priority.

As a workaround, try switching Cursor’s terminal from PowerShell to Git Bash or cmd. Then the agent won’t use `n for line breaks, and the issue should go away:

  • Ctrl + Shift + P → “Terminal: Select Default Profile”
  • Select Git Bash or Command Prompt

Let me know if that helps.

1 Like

thank you!

generally, is Git bash recommended even on windows?

PowerShell is the default and fully supported terminal on Windows, so it’s totally fine. Git Bash also works, but some users on Windows run into issues with it because of sandbox restrictions.

So if PowerShell works fine for you, I’d stick with it. The allowlist parsing bug is on our radar, and switching terminals is more of a temporary workaround, not a long-term recommendation.

If the allowlist prompt is really getting in the way, you can try Git Bash, but keep in mind you might hit other edge cases. Let me know if anything else comes up.

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