[Feature Request] Option to hide VS Code diagnostic messages from the LLM
Status Fixed / completed
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 5 comments · opened Sep 4, 2025 · closed Sep 5, 2025
Feature Description
The diagnostic messages from VS Code are so limited (and often erroneous) that I'd rather Claude not have access to them at all, but I haven't found a way to disable _that specific feature_ of the IDE integration.
(I do not want to just disable the whole IDE integration. I like the other features, like having Claude know what lines I have selected in the editor.)
Environment Info
- Platform: linux
- Terminal: vscode
- Version: 1.0.102
- Feedback ID:
5 Comments
Found 1 possible duplicate issue:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
That issue does seem relevant, but insufficient - I have already added
mcp_ide_getDiagnosticsto my "deny" list, but the diagnostic info is still sent to the LLM whenever I submit a prompt.Hey,
That's a great point.
I don't think there's a specific setting just for diagnostics, but I found a potential workaround by digging through the changelog. It looks like you can disable the automatic IDE connection entirely with an environment variable.
Try running this in your terminal before starting
claude:According to the changelog for version
1.0.61, this should stop Claude Code from automatically hooking into VS Code when it starts up in the integrated terminal. If it's not connected to the IDE, it shouldn't be able to receive the diagnostic messages.The downside is that you'll likely lose the other IDE features too, like the diff viewer and automatic selection context. But if the diagnostics are causing more harm than good, it might be a worthwhile trade-off for you.
Hope this helps
Why was this closed as completed? Is there now a way to configure this?
Disabling the integration entirely is not an actual solution here. It's a workaround. If I wanted to do that I wouldn't have opened this issue in the first place.
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.