Preflight Checklist
Problem Statement
I rely on Visual Studio 2026 for C++ and Win32 system-level development (e.g., global hooks, drivers) because its debugger and toolchain are superior to VS Code/JetBrains for this specific stack.
Currently, claude-code only offers native plugins for VS Code and JetBrains. To use Claude Code with Visual Studio 2026, I am forced to run it in a detached terminal window. This creates significant friction:
- No Integrated Diff: I have to review complex code changes in the terminal text stream instead of Visual Studio's native Diff/Merge GUI.
- No Context Awareness: Claude cannot automatically see my open files, selected code, or compiler diagnostics (error list). I have to manually copy-paste errors or file contents.
- Context Switching: Constant Alt-Tab between the IDE and the terminal breaks flow.
Proposed Solution
Create a native VSIX extension for Visual Studio 2026 that provides feature parity with the existing VS Code extension:
- Integrated Chat Panel: A dockable tool window within VS 2026.
- Native Diff Viewing: When Claude proposes changes, show them using Visual Studio's native Diff window for review/accept/reject.
- Context Synchronization: Automatically share active file content, cursor selection, and build errors/warnings with the agent.
/ide Command Support: Allow terminal sessions to link to the active VS instance.
Alternative Solutions
- Current Workaround: Running
claude CLI in an external terminal (Windows Terminal) or the VS Integrated Terminal. This is suboptimal due to the lack of GUI diffs and auto-context.
- Switching IDEs: Trying to move the C++ project to VS Code just for Claude support, but this sacrifices the advanced debugging capabilities of Visual Studio 2026 required for Win32 development.
Priority
High - Significant impact on productivity
Feature Category
Other
Use Case Example
Scenario: Debugging a Win32 Keyboard Hook
- I am debugging a
SetWindowsHookEx crash in hook.cpp inside Visual Studio 2026.
- I hit a breakpoint where a variable
pKey is null.
- Ideally: I open the Claude Code panel inside VS, select the crashing function, and ask: "Why is pKey null here?".
- Claude analyzes the selected code and the current file context automatically.
- Claude proposes a fix (adding a null check).
- I click "Review", and VS opens its native Diff window showing the change.
- I click "Accept", and the code is updated without me ever leaving the IDE.
Additional Context
Visual Studio remains the de-facto standard for Windows native development. Ignoring it excludes a large portion of systems engineers and C++ game developers.
Preflight Checklist
Problem Statement
I rely on Visual Studio 2026 for C++ and Win32 system-level development (e.g., global hooks, drivers) because its debugger and toolchain are superior to VS Code/JetBrains for this specific stack.
Currently,
claude-codeonly offers native plugins for VS Code and JetBrains. To use Claude Code with Visual Studio 2026, I am forced to run it in a detached terminal window. This creates significant friction:Proposed Solution
Create a native VSIX extension for Visual Studio 2026 that provides feature parity with the existing VS Code extension:
/ideCommand Support: Allow terminal sessions to link to the active VS instance.Alternative Solutions
claudeCLI in an external terminal (Windows Terminal) or the VS Integrated Terminal. This is suboptimal due to the lack of GUI diffs and auto-context.Priority
High - Significant impact on productivity
Feature Category
Other
Use Case Example
Scenario: Debugging a Win32 Keyboard Hook
SetWindowsHookExcrash inhook.cppinside Visual Studio 2026.pKeyis null.Additional Context
Visual Studio remains the de-facto standard for Windows native development. Ignoring it excludes a large portion of systems engineers and C++ game developers.