Find and fix a VS Code shortcut conflict

01Record the exact mismatch

Write down which command you intended, the keys you pressed and what happened instead. Include whether the editor, terminal or another control had focus.

VS Code provides conflict inspection and keyboard troubleshooting tools. Use those before assigning a random new combination. A problem limited to one context may involve a conditional binding, rather than a duplicate that applies everywhere. A small, repeatable example is more useful than a broad report that all shortcuts are broken.

02Inspect the rules before editing

1. Find the command in the shortcut editor and inspect its assignment and competing entries. Note whether a rule is a default, personal change or extension-related binding.
2. Preserve the original rule. Make one modification and repeat the same test. If it resolves the issue, also check the other command that previously used those keys. Avoid deleting an entire keymap to repair one uncertain behavior, since that can remove useful settings and introduce unrelated changes.

03Keep the fix narrow and reversible

A useful rule has a clear purpose and context. A broad replacement may work in one editor while interfering with terminal input or another language workflow.

Include keyboard layout when reporting punctuation or interpretation issues. Share the smallest relevant configuration and reproduction, without private project details. The documented customization model helps investigate conflicts, but it does not certify every extension or prove an unusual combination is unused across the whole Mac.