[BUG] Keyboard shortcuts Option+Cmd+K and Option+K not working in Claude Code VSCode extension since v2.1.6
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Keyboard shortcuts Option+Cmd+K and Option+K for inserting @ mentions do not work in the VSCode extension since version 2.1.6.
When pressing these shortcuts with editor focus, nothing happens - the @ mention insertion doesn't trigger.
The keybindings appear in VSCode but the commands don't execute.
What Should Happen?
Pressing Option+Cmd+K or Option+K while the editor has focus should insert an @ mention at the cursor position, allowing quick file/symbol references in the Claude Code chat.
Error Messages/Logs
No error messages appear. The shortcuts simply don't trigger any action.
Keybindings configuration shows:
{
"key": "alt+cmd+k",
"command": "claude-vscode.insertAtMention",
"when": "editorTextFocus"
}
{
"key": "alt+k",
"command": "claude-code.insertAtMentioned",
"when": "editorTextFocus"
}
Note: Command names are inconsistent (claude-vscode.insertAtMention vs claude-code.insertAtMentioned) which may indicate a refactoring issue.
Steps to Reproduce
- Install Claude Code VSCode extension v2.1.6 or later
- Open any file in the editor
- Ensure the editor has focus (editorTextFocus is true)
- Press Alt+Cmd+K (or Alt+K)
- Observe that nothing happens - no @ mention is inserted
Claude Model
Not sure / Multiple models
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.5 (or earlier - shortcuts worked before 2.1.6)
Claude Code Version
2.1.6
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
The issue seems to be related to command name changes during refactoring. The keybindings reference two different command prefixes:
claude-vscode.insertAtMentionclaude-code.insertAtMentioned
This naming inconsistency suggests the commands may have been renamed but the keybinding definitions weren't updated to match the actual registered command names.
This issue has 9 comments on GitHub. Read the full discussion on GitHub ↗