u/Remote-Breadfruit204

A problem (and opportunity) came when I found myself using the debugger in Visual Studio, adding console logs and then hand-feeding those values to the Claude CLI to get it to debug a tricky bug with the correct context. So, I started building a bridge between Visual Studio's debugger automation and the CLI. A few weeks later Claude was setting breakpoints in my files, stepping through them, watching variables mutate at different frames, and telling me where a bug was hiding that it would have probably skimmed past while reading my code.

The part in the clip: Claude can drive the debugger itself, set breakpoints, step, read locals, and find bugs by running the code instead of reading it, and every edit it makes opens in a dedicated diff viewer with an accept / reject permission request. The clip shows it catching a bug that's invisible in the output by watching a counter fail to reset.

Would genuinely appreciate your feedback on this!

Marketplace: Claude Code for Visual Studio - Visual Studio Marketplace
Source + docs: GitHub - firish/claude_code_vs

Claude Code has official IDE plugins for VS Code and JetBrains but nothing for Visual Studio. There's an open GitHub issue with a lot of +1s, so I built it.

It speaks the same protocol the official plugins use, so the CLI connects automatically. Claude's edits open in Visual Studio's native diff window with Accept / Reject / Reject-with-feedback instead of terminal prompts. It also auto shares your compiler errors and current selection as context, and there's a panel with live token tracking for the session.

It doesn't make any model calls of its own, it just drives the IDE half.

Code and a quick 30-second visual demo: https://github.com/firish/claude_code_vs 

Would be grateful if anyone takes the time to actually check it out and share feedback!

There's an open issue (https://github.com/anthropics/claude-code/issues/15942) on the Claude Code repo asking for Visual Studio support with a bunch of +1s, and it's been sitting there.

I made one that implements the same IDE protocol the official VS Code and JetBrains plugins use, so the Claude CLI just connects to it.

The main thing it does: when Claude proposes an edit, it opens in Visual Studio's actual diff viewer and you Accept or Reject right there. You can also reject with a reason and it takes another pass. No terminal y/n prompts and no manual copy pasting.

It also feeds your compiler errors (C# and C++) and current selection to Claude automatically, so it has context without you pasting anything. There's a panel showing connection status and token usage for the session.

Repo: https://github.com/firish/claude_code_vs
Marketplace: https://marketplace.visualstudio.com/items?itemName=firish.bridgev1

Would be grateful if anyone takes the time to actually check it out and share feedback!