[MacOS]Please fix keyboard shortcut to CursorDown for Ctrl-N in composer

Hi, thanks for reporting an issue with Cursor.

Before you report this, we’d appreciate if you can search this forum to see if this issue has already been reported.

If you have done so, please check this box.
on

Describe the Bug

Why does Ctrl + N open a new composer instead of doing cursorDown?
Seriously, I’ve disabled every other Ctrl + N shortcut except cursorDown.

Yet it still stubbornly ignores the expected behavior. WHY?

Steps to Reproduce

  1. Open Keyboard Shortcuts with Ctrl + Shift + P.
  2. Disable every single Ctrl + N shortcut except cursorDown.
  3. Open composer using Command + I, type something, and then press Ctrl + N.
  4. Watch in frustration as it defiantly opens a new composer instead of moving the cursor down.

Expected Behavior

Ctrl + N should just perform the cursorDown action. Simple. No new composers, no surprises.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

cursor --version --verbose
0.44.11
fe574d0820377383143b2ea26aa6ae28b3425220
arm64

Additional Information

PLEASE FIX<
THIS IS VERY IMPORTANT<
FOR ANYONE WHO USES MACOS<
YOU SHOULD NOT OVERRIDE Ctrl-N OTHER THAN MOVE CURSOR DOWN<

Contact: [email protected]
Thank You (if you read)

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

7 Likes

You can ask Cursor for all of its keybinds, and have it give you and walk you through the settings.

As such:

Here’s a suggested response:


Hi there! I understand you want to set up Ctrl+N for cursor movement (similar to Emacs-style navigation). Here’s how you can customize this in Cursor:

  • Open Cursor’s Keyboard Shortcuts settings:

  • On macOS: Cmd + K, Cmd + S

  • Or go to Code → Preferences → Keyboard Shortcuts

  • Search for “cursorDown” in the shortcuts search bar

  • To add the Ctrl+N binding:

  • Click the + icon next to the “cursorDown” command

  • Press Ctrl+N

  • This will add it as an alternative binding

You can add this to your keybindings.json file directly:

keybindings.json

Apply

{

“key”: “ctrl+n”,

“command”: “cursorDown”,

“when”: “textInputFocus”

}

Note: If you’re getting conflicts with other shortcuts, you may need to:

  • Remove any conflicting bindings first
  1. Ensure the “when” clause is specific enough to only trigger in text editing contexts

For other Emacs-style bindings, you might also want to add:

  • Ctrl+P for cursor up

  • Ctrl+F for cursor right

  • Ctrl+B for cursor left

2 Likes

I’ve tried for Ctrl + N, which still refuses to work:

// Remove existing ctrl+n bindings that could conflict
[
    // Add new bindings for composer/chat panels
    {
        "key": "ctrl+n",
        "command": "cursorDown",
        "when": "textInputFocus && (focusedView == 'workbench.panel.composerViewPane2.view' || focusedView == 'workbench.panel.aichat.view')"
    }
]

// Modified bindings for chat/composer input
{
    "key": "ctrl+n",
    "command": "cursorDown",
    "when": "inChatInput || composerInput || chatInputFocus"
}

// General input focus bindings
{
    "key": "ctrl+n",
    "command": "cursorDown",
    "when": "inputFocus && !editorTextFocus && !suggestWidgetVisible && !inQuickOpen"
}

Ctrl + P works perfectly. It’s just Ctrl + N that’s being unreasonably stubborn. Any ideas? Or, better yet, a fix?

im on windows, so I cant test this, but does this help:

Here are the Mac-specific instructions for managing Cursor’s keybindings:

  1. View All Keybindings:

    • Press ⌘ + K, ⌘ + S (Command + K, Command + S)
    • Or navigate through: Cursor → Preferences → Keyboard Shortcuts
  2. To Export Current Keybindings:

    • Open the Keyboard Shortcuts editor
    • Click the “…” (three dots) in the top-right corner
    • Select “Show Current Keybindings”

For the Emacs-style navigation, here’s a macOS-compatible keybindings.json configuration:

[
    {
        "key": "ctrl+n",
        "command": "cursorDown",
        "when": "textInputFocus && !suggestWidgetVisible"
    },
    {
        "key": "ctrl+p",
        "command": "cursorUp",
        "when": "textInputFocus && !suggestWidgetVisible"
    },
    {
        "key": "ctrl+f",
        "command": "cursorRight",
        "when": "textInputFocus"
    },
    {
        "key": "ctrl+b",
        "command": "cursorLeft",
        "when": "textInputFocus"
    }
]

To modify your keybindings:

  1. Open Command Palette (⌘ + Shift + P)
  2. Type “Open Keyboard Shortcuts (JSON)”
  3. Add the above configurations

Note: If you want to see all default keybindings in Cursor:

  1. Open Command Palette
  2. Type “Open Default Keyboard Shortcuts (JSON)”
  3. This will show you all built-in keybindings

For the Composer panel specifically, you might want to add:

{
    "key": "ctrl+n",
    "command": "cursorDown",
    "when": "textInputFocus && (focusedView == 'workbench.panel.composerViewPane2.view' || focusedView == 'workbench.panel.aichat.view')"
}

Mac-Specific Notes:

  • Remember that on Mac, (Command) is different from ^ (Control)
  • The keybindings use ctrl instead of cmd to maintain Emacs-style consistency
  • If you’re having issues with system shortcuts, you might need to check System Preferences → Keyboard → Shortcuts to ensure there are no conflicts
  • The file location for keybindings on Mac is typically: ~/Library/Application Support/Cursor/User/keybindings.json
1 Like

not working for me

Drat.

I think there is a huge vacuum of opportunity in the Forging of the UX within Cursor through its Agentic YOLObility to have the bot update Cursor IDE settings and such…

It just is a little too sycophantic/eager_to_claim_success that it often bullshits one into a corner…


1 Like

good idea ! @cursorteam

The same case for me. Please fix that @cursorteam

2 Likes

Now that Ctrl+A is mapped to “Select All,” it’s super annoying for Unix keyboard shortcut lovers…
Any solution?

2 Likes

cursor --version --verbose
0.45.9
cce0110ca40ceb61e76ecea08d24210123895320
arm64

Still not fixed :construction:

In my case, `Ctrl+A` works normal as move cursor to line start, you can check my key bindings below:

NOT WORK IN THE NEW VERSION

cursor --version --verbose
0.45.9
cce0110ca40ceb61e76ecea08d24210123895320
arm64

That’s really sad they didn’t fix it in this new version.

1 Like

It was prolly in the release notes I must have missed…

1 Like

thanks for reporting this! just so i understand correctly, you’d like to override ctrl + n so it doesn’t open a new composer/noop?

1 Like

On macOS, Ctrl + N/P/B/F move the cursor (down/up/left/right) like arrow keys, and Ctrl + A/E jump to the start/end of a line, this works system-wide. Windows users rely more on arrow keys, so this feels unfamiliar. The issue is that Cursor forces overrides Ctrl + N/A, breaking this natural flow, which is frustrating for Mac users.

2 Likes

Ctrl+k is also overridden on macOS. It is used to delete from the cursor position to the end of the line. All existing shortcuts can be found under Text-editing shortcuts here: Mac keyboard shortcuts - Apple Support

1 Like

@ericzakariasson

The Feb 21 update still hasn’t fixed the Ctrl+N mess in Composer.

:weary: My prompts are vanishing left and right …

we’re moving away from cmd+n in 0.46, so hopefully should be resolved!

1 Like

Will Ctrl-N Ctrl-P work for moving up/down in this list in version 0.46?

2 Likes

This is still an issue in 0.46. Ctrl+k (as well as a/e/f/b/p) works well which is great, but ctrl+n still creates a new chat :sob:.

1 Like