JanJ
November 12, 2025, 4:27am
1
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Now when I do Cmd+N I get a new prompt, not a new empty file?
Yet the File menu still shows Cmd+N for a new text file.
Steps to Reproduce
Open Cursor
Cmd+N
Expected Behavior
Cmd+N should open a new file as per the File menu shortcut.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.0.69
VSCode Version: 1.99.3
Commit: 63fcac100bd5d5749f2a98aa47d65f6eca61db30
Date: 2025-11-07T18:21:29.650Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0
Does this stop you from using Cursor
No - Cursor works, but with this issue
deanrie
(Dean Rie)
November 12, 2025, 4:42am
2
Hey, thanks for the report. This could be caused by an extension or macOS/app intercepting the CMD+N shortcut.
Please check:
Safe mode test (no extensions):
Close Cursor
Run from terminal: cursor --disable-extensions
Try CMD+N - does it work correctly?
Check keyboard shortcuts:
CMD+Shift+P → “Preferences: Open Keyboard Shortcuts”
Search for cmd+n to see what it’s bound to
Search for “New Untitled File” to confirm it still has CMD+N
Also check the “When” column for any conditions
Check macOS system shortcuts:
System Settings → Keyboard → Keyboard Shortcuts
Look for any global or app-specific shortcuts using CMD+N
Try:
Manually reassign the shortcut in Keyboard Shortcuts to see if it works
Let me know if CMD+N works with extensions disabled. That’ll help determine if it’s an extension conflict or a Cursor keybinding change.
JanJ
November 12, 2025, 4:59am
3
If I remove the Cursor shortcut override, the default behavior works fine again, but Cursor should not override the default (as in specified on the File menu) behavior.
system
(system)
Closed
December 4, 2025, 5:00am
4
This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.