Cursor Keybindings

Cursor Keybindings

Overview

Configure keybindings for discoverability and accessibility without masking safety-critical editor commands or creating team-specific ambiguity.

Prerequisites

• Existing team/editor shortcut conventions and a recoverable keybindings backup.
• A non-sensitive test workspace for validating conflicts.

Instructions

1. Search existing bindings before assigning a shortcut and prefer documented Cursor defaults when practical.
2. Use workspace/team conventions for shared documentation; keep personal ergonomics local.
3. Test conflict behavior in a sample workspace and retain an easy reset/revert path.
4. Document custom bindings needed for pair programming, training, or support.

Output

• A tested keybinding change with conflict result and recovery instructions.

Error Handling

Examples

Assign a personal shortcut to a Cursor command only after checking the Keyboard Shortcuts UI for conflicts, test it in a sample project, and retain the previous keybindings entry. Do not overwrite a documented team shortcut without agreement.

Complete keyboard shortcut reference for Cursor IDE. Covers AI-specific shortcuts, standard editor commands, and customization. All shortcuts shown as macOS / Windows-Linux.

AI Feature Shortcuts

Primary AI Shortcuts

Context & Suggestions

Chat Management

Essential Editor Shortcuts

Navigation

Editing

Panels & Views

Customizing Keybindings

Via UI

1. Cmd+K Cmd+S to open Keyboard Shortcuts editor
2. Search for the command (e.g., "accept cursor tab")
3. Click the pencil icon next to the keybinding
4. Press your desired key combination
5. If conflict detected, choose to override or cancel

Via JSON

Open keybindings.json: Cmd+Shift+P > Open Keyboard Shortcuts (JSON)

[
  {
    "key": "cmd+enter",
    "command": "editor.action.inlineSuggest.commit",
    "when": "inlineSuggestionVisible"
  },
  {
    "key": "ctrl+shift+k",
    "command": "aichat.newchat",
    "when": "editorFocus"
  },
  {
    "key": "cmd+k cmd+a",
    "command": "editor.action.selectAll",
    "when": "editorTextFocus && !editorReadonly"
  }
]

Vim Mode Compatibility

If using the Vim extension with Cursor:

// keybindings.json -- resolve Vim conflicts
[
  {
    "key": "ctrl+l",
    "command": "aichat.focus",
    "when": "!vim.active || vim.mode == 'Normal'"
  },
  {
    "key": "ctrl+k",
    "command": "cursor.edit",
    "when": "editorTextFocus && !vim.active"
  }
]

Common Vim conflicts:

• Ctrl+K conflicts with Vim's digraph mode
• Ctrl+L conflicts with Vim's clear/redraw
• Ctrl+I conflicts with Vim's jump forward

Solution: Remap Cursor AI shortcuts to avoid Vim's control sequences, or use when clauses to scope by Vim mode.

Cheat Sheet (Print-Friendly)

╔══════════════════════════════════════════════╗
║  CURSOR AI SHORTCUTS (macOS)                 ║
╠══════════════════════════════════════════════╣
║  Cmd+L       Chat panel                     ║
║  Cmd+K       Inline edit (select first)     ║
║  Cmd+I       Composer (multi-file)          ║
║  Cmd+Shift+L Add selection to chat          ║
║  Tab         Accept Tab suggestion          ║
║  Cmd+→       Accept suggestion word-by-word ║
║  Esc         Dismiss suggestion             ║
║  Cmd+Y       Accept inline edit             ║
║  Cmd+Shift+P Command Palette               ║
║  Cmd+P       Quick Open file                ║
╚══════════════════════════════════════════════╝

Enterprise Considerations

• Keybinding policies: Teams can share a keybindings.json in the project repo (.vscode/keybindings.json)
• Accessibility: Cursor supports screen readers and keyboard-only navigation via standard VS Code accessibility features
• Corporate keyboards: International keyboard layouts may require different mappings for Cmd+K/L/I

Resources

• Cursor Keyboard Shortcuts
• VS Code Keybindings
• Vim Extension