[FEATURE] VS Code Extension: Keyboard shortcut to focus prompt
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Command-escape opens claude code and focuses the prompt input, but it always starts a new chat.
I have not found a way to focus the prompt input for the existing chat via keyboard shortcut.
Proposed Solution
Include a function to bind a keyboard shortcut to that will focus the input in the current chat.
Secondarily, a related bug fix would be to not lose focus in the prompt input when switching apps and switching back again.
Alternative Solutions
command-escape: not viable, as it opens a new chat every time
switch to the correct split via keyboard shortcut, and hit tab: sometimes this works, but other times it focuses the edit mode selection and I have to hit shift-tab to get the actual prompt. So at best, this is two keyboard shortcuts, but can be more
Similarly, switching back to vscode from another app, if the claude split is already focused, I can hit tab, but it usually focuses the edit mode button and I have to hit shift-tab to get back
Priority
Medium - Would be very helpful
Feature Category
Configuration and settings
Use Case Example
- I'm reviewing code that Claude just wrote in
header.html - I notice a typo and manually fix it with my cursor in the editor
- Now I want to ask Claude to continue with the next task
- Currently: I must use my mouse to click back into the Claude prompt field
- Desired: Press
Cmd+Shift+L(or any configurable shortcut) to instantly focus the prompt
This becomes especially frustrating during rapid iteration where I'm frequently switching between:
- Reading Claude's code suggestions in the editor
- Making small manual adjustments
- Prompting Claude for the next step
The constant context switching to mouse breaks flow state and slows down development velocity.
Additional Context
_No response_
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗