[Bug] VSCode Extension 2.0.0: Severe Keyboard Accessibility Regression

Status Fixed / completed
Maintainer reply ✓ Yes — hackyon-anthropic
Activity 6 comments · opened Sep 30, 2025 · closed Oct 4, 2025
💡 Likely answer: A maintainer (hackyon-anthropic, collaborator) responded on this thread — see the highlighted reply below.

Bug Description
i had to uninstall the 2.0.0 version of the vscode extension and reisntall version 1.0.127 because the new version was a nightmare to manage from the keyboard, and forced me to use my mouse by losing focus all the time. this is an unacceptable tradeoff for an IDE-centric tool. it is nicr looking and it is more readable, but it is almost unusable by doubling the time it takes me to do anything by using it. i have disabled automatic updates, and would need to read reviews before installing a new version, otherwise i risk to be slowed down again. it does not even allow me to send feedback. i would consider all this a massive regression. please consider solving specific programmer UX issues before deploying specific UI solutions.

Environment Info

  • Platform: darwin
  • Terminal: vscode
  • Version: 1.0.127
  • Feedback ID: 417d1521-a4ef-4ce7-8c4a-ba127057d44e

Errors

[]

View original on GitHub ↗

6 Comments

github-actions[bot] · 11 months ago

Found 2 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/8177
  2. 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

frwrdnet · 11 months ago

This is not a keyboard command issue. this is a keyboard focus issue. items in the extension, including buttons, lose focus and are difficult (if not impossible, but haven't tried that long) to regain focus, which forces me to use the mouse (or to learn new keyboard commands, which are not obvious or well explained for a new user).

i can help with more information, and help debug if needed, but this is a UX issue not (only) a code issue.

hackyon-anthropic collaborator · 11 months ago

hey @frwrdnet - sorry to hear you're running into trouble with some focus issues. Do you happen to have any repro steps? We can add some fixes if there are specific repro steps.

In the meantime, you should be able to keep using claude from the terminal without re-installing the older version (simply open up the built-in terminal, and run claude).

alecours · 11 months ago
hey @frwrdnet - sorry to hear you're running into trouble with some focus issues. Do you happen to have any repro steps? We can add some fixes if there are specific repro steps. In the meantime, you should be able to keep using claude from the terminal without re-installing the older version (simply open up the built-in terminal, and run claude).

@hackyon-anthropic
I am having the same issue, we must downgrade... As soon as it's installed, (any version above 1.0.127) and that vscode is running, you just have to open a big file use the mouse and select text until it scroll and that your pc glitch out because rg is spamming)

!Image

btw here i have nothing else open then a file (saved where claude could open), but the extention is not even running....
and i have procmon with filter on "rg.exe" to show how bad it is.... and i selected a couple paragraph only.. when i select 1500 lines, let me tell you everything start to glitch out !

it feels like a rg.exe is spawn for each char selected in vscode workspace where claude code would open when you click on the extension icon to open it

---

That said the simple fact to have any version that are above 1.0.128 make rg spam like hell even with claude code extension not open.

The only "true" fix that got it fixed for me (and i think i have decent specs on my Windows 10 PC.) is when i downgraded to 1.0.127 it is the vscode extension and ripgrep

frwrdnet · 11 months ago

hey @hackyon-anthropic , sorry it took me so long to reply, i was on a deadline. also, apologies for my previous tone, it seems i got very irritated but i really like your service and appreciate all your hard work. i also realise you're stretching the functionality of vscode extensions to the limit, a purpose i'm sure they weren't designed for, so kudos on your work anyway. also, thanks for acknowledging user's feedback.

i installed the updated version (2.0.5) today and quickly tested it. here's a video: https://postimg.cc/1fJfhgKV. you'll notice the point where i move the mouse around the response buttons, that's when the keyboard focus was gone from the buttons and i had to move my mouse to reach it. it seems it's happening less. it was a quick test, but it's a new version you deployed, so i'll assume it has been improved and soon will be solved. if i notice the issue again, i'll open a new bug.

github-actions[bot] · 10 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.