VS Code extension: access to IDE panels (Problems, Terminal, etc.)

Feature request

When running as the VS Code extension, Claude Code currently has limited visibility into the IDE — it can see the active file and receives diagnostics after edits, but cannot read VS Code panels like Problems, Terminal output, Source Control, or Extensions.

Use case

A user asked me to address all items in their VS Code Problems tab. I had no way to see what was listed there, so I had to:

1. Guess which linters/checkers might be producing diagnostics
2. Run CLI equivalents manually (tsc --noEmit, eslint, mypy, ruff)
3. Ask the user to copy-paste the Problems panel contents

It turned out the issues were hint-level diagnostics from the GitHub Actions extension — something I could have identified immediately with panel access, but instead required multiple back-and-forth exchanges.

Suggestion

Expose read access to key VS Code panels for the extension-based Claude Code agent:

• Problems panel — the most impactful; lets Claude see exactly what diagnostics the user sees, including extension-specific ones that CLI tools don't reproduce
• Terminal output — useful when the user references something they just ran
• Extensions list — helps Claude understand which tools are generating diagnostics

Why this matters

The IDE integration is one of the main reasons users choose the VS Code extension over the CLI. But without panel access, Claude often can't see what the user sees, leading to unnecessary round-trips and guesswork. This gap is especially confusing for users who expect the extension to have full IDE awareness.