[BUG] three UX issues in Claude Code for VS Code
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?
I've encountered three UX issues in Claude Code for VS Code that impact daily workflow and keyboard-driven interaction.
What Should Happen?
1. Input box doesn't auto-focus on chat open
Steps to reproduce:
- Open Claude Code chat panel in VS Code
- Try to type immediately
Expected behavior: Input box should auto-focus when the chat panel opens, allowing keyboard input without clicking
Actual behavior: Input box is not focused. Must click manually to type. No keyboard shortcut exists to focus the input box.
---
2. Input focus lost when switching windows
Steps to reproduce:
- Open Claude Code chat panel in VS Code
- Click the input box (or it should be focused)
- Switch to another window/application
- Return to VS Code
Impact: Breaks keyboard-only workflow; requires mouse interaction every time
Expected behavior: Input box should retain focus or re-focus when returning to VS Code
Actual behavior: Input box loses focus. Must click it again to continue typing.
Impact: Interrupts workflow when multitasking
---
3. Long Claude messages overflow and become unreadable
Steps to reproduce:
- Ask Claude Code a question that generates a longer response
- Observe the message in the chat panel
Expected behavior: Full message should be visible with proper text wrapping and scrollable area
Actual behavior: Message covers the entire chat area; only ~1 line is visible. Rest is cut off or hidden.
Impact: Cannot read full responses from Claude
Error Messages/Logs
Steps to Reproduce
open vscode, press alt + ctrl + B
Claude Model
Sonnet (default)
Is this a regression?
No, this never worked
Last Working Version
latest
Claude Code Version
latest
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
VS Code integrated terminal
Additional Information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗