claude-code icon indicating copy to clipboard operation
claude-code copied to clipboard

[FEATURE] VS Code Extension: Keyboard shortcut to focus prompt

Open fitzage opened this issue 2 months ago • 3 comments

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

  1. I'm reviewing code that Claude just wrote in header.html
  2. I notice a typo and manually fix it with my cursor in the editor
  3. Now I want to ask Claude to continue with the next task
  4. Currently: I must use my mouse to click back into the Claude prompt field
  5. 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

fitzage avatar Oct 08 '25 13:10 fitzage

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/8977
  2. https://github.com/anthropics/claude-code/issues/8545
  3. https://github.com/anthropics/claude-code/issues/8427

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

github-actions[bot] avatar Oct 08 '25 13:10 github-actions[bot]

On Mac OS, turn on Voice Control. Then say "Click Message Input" or "Click Ask Claude" (if empty)

Voice Control with headphones is coding heaven.

And I think this is a bug because when you switch back to the Claude Code pane in VSCode (e.g., CMD+2) the focus should really be set to the Message Input field. The other workaround is TAB, Shift+TAB which is kinda wonky and points out that this is really a bug to fix not a feature, because if you can tab, backtab to what you want then why wasn't it focused to begin with.

Till then, just use Voice Control Heaven and thank you so much to the wonderful accessibility person who named the field "Message Input" ❤️

firepick1 avatar Oct 27 '25 20:10 firepick1

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

github-actions[bot] avatar Dec 08 '25 10:12 github-actions[bot]