In this categoryCursor · 26
- How to Install Cursor and Import VS Code Settings (6 Minutes)Start
- Cursor Setup Guide: From Install to Your First AI Edit
- How to Set Up Project Rules in the .cursor/rules Folder
- How to Set Up Codebase Indexing in Cursor
- How to Enforce Project Conventions with Cursor Rules
- How to Write a Team Rule That Applies Only to Certain Files
- How to Migrate a Legacy .cursorrules File to the New Rules Folder
- How to Use Cursor Rules to Guide AI Edits
- How to Set Project Rules in Cursor
- How to Add a .cursorrules File to Steer Cursor
- How to Customize Cursor Keyboard Shortcuts
- How to Edit Multiple Files at Once with Cursor Composer
- How to Use Cursor Tab Completion Effectively
- How to Edit Code Inline with Cmd+K in Cursor
- How to Add Context to Cursor Chat with @ Mentions
- How to Choose and Switch AI Models in Cursor
- How to Add Library Docs as Context with @Docs in Cursor
- How to Generate and Maintain Tests with Cursor Composer
- How to Undo a Composer Change with Checkpoints in Cursor
- How to Use Cursor Agent Mode to Build a Feature End to End
- How to Connect an MCP Server to Cursor
- How to Refactor Across Your Whole Codebase in Cursor
- How to Query Your Database from Cursor with a Postgres MCP Server
- How to Let Cursor Run Commands Automatically (and Keep It Safe)
- How to Build a Full Feature Across Frontend and Backend with Composer
- How to Debug an MCP Server That Will Not Connect in Cursor
How to Customize Cursor Keyboard Shortcuts
Open the keyboard shortcuts editor, rebind a conflicting key, and tweak the AI command keys to suit your hands.
Cursor ships with sensible defaults, but its AI commands sometimes collide with extension shortcuts you already use. The keyboard shortcuts editor lets you rebind anything, including the AI keys for inline edit and chat. This guide resolves a conflict and changes a binding.
What you need
- Cursor installed
- A shortcut you find awkward or that conflicts with an extension
- Two minutes
Step 1: Open the shortcuts editor
Open the command palette and run Preferences: Open Keyboard Shortcuts. This opens a searchable table of every command and its current binding.
Step 2: Find the command
Search for the action you want to change. To rebind, double-click the row, press the new key combination, and Enter. If the keys are already used, Cursor warns you about the conflict so you can decide which command keeps them.
Step 3: Edit the JSON directly
For full control, open the keybindings.json file from the small page-and-pencil icon in the top right of the editor. Each entry is a key, a command, and an optional when clause that limits where it applies.
[
{
"key": "cmd+i",
"command": "cursor.inlineEdit",
"when": "editorTextFocus"
},
{
"key": "cmd+k",
"command": "-cursor.inlineEdit"
}
]Step 4: Test the new binding
Close settings, open a file, and press your new key. If nothing happens, check the when clause; a binding only fires when its condition is true, like the editor having focus.
Result: inline edit now lives on a key that does not fight your other extensions, and the change persists in keybindings.json that you can sync or copy to another machine.
Watch related tutorials
33:42
41:18
28:05
3:12
26:54
39:10New guides in your inbox
Fresh step-by-step how-to guides as we publish them. One email a week, no more.