[BUG] VSCode Extension missing MCP IDE Diagnostics tool and /bug command

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?

Problem Summary

The VSCode Extension for Claude Code is missing critical IDE integration features that are:

1. Mentioned in the system prompt but not available
2. Available in the CLI version but not in the extension

Issue 1: MCP IDE Diagnostics Tool Not Available

Expected: The mcp__ide__getDiagnostics tool should be available to retrieve IDE diagnostics (Pylance errors, warnings, etc.)

Actual: Tool returns error: No such tool available: mcp__ide__getDiagnostics

Evidence:

• System prompt mentions: "Use mcp__ide__getDiagnostics instead of pylint command for linting and type checking" (from CLAUDE.md project instructions)
• When attempting to use: mcp__ide__getDiagnostics(uri: "file:///path/to/file.py") returns tool not found error

Issue 2: /bug Command Not Available

Expected: According to docs, the /bug command should be available for feedback

Actual: /bug command does not exist in available slash commands list

Irony: Cannot report bugs via /bug because /bug is missing 😅

Issue 3: Worse IDE Integration than CLI

Observation: The CLI version of Claude Code can connect to IDEs and access diagnostics, but the VSCode Extension (which runs inside the IDE) has worse IDE integration.

Expected: The VSCode Extension should have equal or better access to IDE features:

• Language Server Protocol diagnostics
• Pylance/TypeScript errors and warnings
• IDE configuration and settings
• Workspace symbols and references

Impact: Users have to manually copy-paste diagnostic errors or use workarounds like pylint which may not be installed.

What Should Happen?

Expected Behavior

VSCode Extension should have MCP tools for IDE integration, specifically:

• mcp__ide__getDiagnostics - Get Pylance/LSP diagnostics
• /bug - Report bugs from within the tool
• Other IDE integration features available in CLI version

Error Messages/Logs

Steps to Reproduce

1. Open a file in VSCode with the Claude Code extension
2. Introduce a type error (e.g., wrong type annotation)
3. Ask Claude: "Check IDE diagnostics for this file"
4. Claude attempts: mcp__ide__getDiagnostics(uri: "file:///.../file.py")
5. Result: Tool not found error

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude Code for VS Code v2.0.2

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

This creates a paradox where the external CLI tool has better access to IDE internals than the native IDE extension. The extension should be the first-class citizen for IDE integration.