Skip to main content

How to Disable or Remove Cursor Shortcuts

Introduction​

When using both Cursor and VSCode, you may encounter conflicts with terminal commands and shortcuts. This guide will help you manage these conflicts and restore your preferred settings.

Terminal Command Conflicts​

'code' Command Issue​

By default, installing Cursor overrides VSCode's 'code' command. Here's how to handle it:

Windows Users​

  1. Navigate to Cursor's bin directory: 
    %localappdata%\Programs\cursor\resources\app\bin
  2. Solutions:
    • Delete files: code and code.cmd
    • Rename them to: code_old and code_old.cmd
    • Adjust PATH priority to prefer VSCode

macOS Users​

  1. Reinstall VSCode's 'code' command: 
    # Remove Cursor's version
    rm /usr/local/bin/code

    # Reinstall VSCode command
    # Open VSCode and run 'Shell Command: Install 'code' command in PATH'

Managing Shortcuts​

Keyboard Shortcuts​

  1. Access Settings:

    • Open Command Palette (Ctrl/Cmd + Shift + P)
    • Search for "Keyboard Shortcuts"

  2. Common Conflict Resolution:

    • Terminal clear command
    • File navigation
    • Code folding

Custom Configuration​

Create or edit keybindings.json:

{
    "key": "cmd+k",
    "command": "workbench.action.terminal.clear",
    "when": "terminalFocus"
}

Best Practices​

Setting Up Your Environment​

  1. Determine primary IDE usage:

    • VSCode for specific tasks
    • Cursor for AI-assisted development

  2. Configure Command Line Tools:

    • Set default terminal commands
    • Establish consistent shortcuts

Maintaining Multiple IDEs​

  1. Keep both IDEs functional:

    • Use cursor command to launch Cursor
    • Use code command to launch VSCode

  2. Workspace Organization:

    • Separate projects by IDE
    • Document IDE-specific settings

Troubleshooting​

Common Issues​

  1. Command Not Found:

    • Verify PATH settings
    • Check command installation
    • Restart terminal

  2. Shortcut Conflicts:

    • Check keyboard settings
    • Check system-level shortcuts
    • Update conflicting bindings

Quick Fixes​

  1. Command Line Issues:

    # Check command location
    which code
    which cursor

    # Verify PATH
    echo $PATH

  2. Shortcut Issues:

    • Reset keyboard shortcuts to defaults
    • Clear custom bindings
    • Rebuild shortcut cache

Advanced Configuration​

Custom PATH Settings​

  1. Edit shell configuration:

    # For bash (~/.bashrc or ~/.bash_profile)
    export PATH="/path/to/vscode/bin:$PATH"

    # For zsh (~/.zshrc)
    path=('/path/to/vscode/bin' $path)

  2. Priority Management:

    • Put preferred IDE path first
    • Update PATH order as needed

System-Level Settings​

  1. Environment Configuration:

    • Set default applications
    • Configure file associations
    • Manage command aliases

  2. IDE-Specific Settings:

    • Separate config files
    • Separate workspaces
    • Custom configuration files