[BUG] VS Code Extension - Excessive ripgrep usage when navigating open files via arrow keys
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?
When navigating open files and changing line number using the arrow keys, Claude Code runs excessive ripgrep commands, clogging up our server. It seems that Claude Code runs the ripgrep command on any line change in general. This did not happen in version 1.0.127 of the extension. It started happening with the 1.0.128 update and continues to happen in the newest version (2.0.2). Claude code is not even open or active and this is happening.
What Should Happen?
It should not run ripgrep commands on every line change.
Error Messages/Logs
Steps to Reproduce
1) Install latest version of the Claude Code VS Code Extension.
2) Open a file.
3) Cycle through lines in the file quickly, such as holding down one of the arrow keys.
Watch as ripgrep commands flood the VS Code server and usage spikes.
Claude Model
Not sure / Multiple models
Is this a regression?
Yes, this worked in a previous version
Last Working Version
1.0.127
Claude Code Version
1.0.126
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
6 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
it turns out we're querying a VSCode API that spins up a lot of ripgreps. should have a fix out by early next week!
Submitted a fix for this already, should be rolled out over the next day or two!
Awesome, thank you!
This should be fixed in v2.0.10. Please give it an update (from within the VSCode extension listing page) and let me know if you continue to see this issue. Thanks!
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.