Add Claude Code as a Quick Fix option in VSCode diagnostic popup (lightbulb menu)

Resolved 💬 4 comments Opened Mar 26, 2026 by bhaviknagar Closed Apr 25, 2026

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

Currently, when a diagnostic warning appears in VSCode (e.g., from SonarQube/SonarCloud, ESLint, TypeScript, etc.), tools like Windsurf and GitHub Copilot show a "Fix with AI" option directly in the Quick Fix popup. Claude Code does not appear there.

To fix a warning with Claude Code today, I have to:

Manually read the warning
Copy it or describe it in the chat
Type a prompt explaining what to fix
This is a significant UX gap compared to competing tools. A single click in the lightbulb menu would make Claude Code much faster and more practical for day-to-day coding.

Proposed Solution

Register Claude Code as a VSCode code action provider so it appears in the Quick Fix / lightbulb popup for diagnostics. A simple "Fix with Claude" option in the menu would be enough to close this gap.

The IDE MCP integration already reads diagnostics via getDiagnostics — this feels like a natural next step.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Developer tools/SDK

Use Case Example

I was working on a React app and SonarCloud flagged a warning on line 1 of vite.base.config.js:

Prefer node:path over path. sonarqube(javascript:S7772)

With Windsurf, I can click the lightbulb → select "Windsurf: Explain Problem" or fix it — all without leaving the editor or typing anything.

With Claude Code, I have to:

Read and copy the warning manually
Switch to the Claude Code chat panel
Type a prompt describing the issue
Wait for a response
This is too many steps for something that should be a single click.

Additional Context

<img width="882" height="208" alt="Image" src="https://github.com/user-attachments/assets/4cece924-c9e5-4723-ace7-2ce9c6f23da8" />

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗