Feature: Add LSP diagnostics support to see IDE errors/warnings

Feature Request

Add support for LSP diagnostics so Claude Code can access errors and warnings from the IDE's Problems panel.

Use Case

When working with code, users often have compilation errors or linter warnings visible in their IDE. Currently, Claude Code cannot see these diagnostics and users must manually copy-paste errors.

Being able to see diagnostics would allow Claude Code to:

• Proactively identify and fix errors
• Understand the current state of the codebase
• Provide more contextual assistance

Technical Details

LSP protocol supports diagnostics via:

• textDocument/publishDiagnostics — server pushes diagnostics to client
• Diagnostic information includes: severity, message, range, source

Since Claude Code already has LSP integration (goToDefinition, findReferences, hover, etc.), adding diagnostics support should be feasible.

Current Workaround

Users must manually copy errors from the Problems panel into the chat.

Environment

• OS: Windows 10
• IDE: Cursor / VS Code
• Languages affected: Any language with LSP support (TypeScript, Python, Rust, Go, etc.)