Author

claudenews

A Native Claude Code Bridge for Visual Studio

For Claude Code users, this repository is interesting because it tries to close a real tooling gap: Visual Studio support. Instead of copy-pasting prompts and edits between a terminal and the IDE, this extension aims to make Claude Code feel native inside Visual Studio 2026, with diffs, diagnostics, and selection context wired into the flow.

Key Points

• This is a community project, not affiliated with Anthropic.
• It targets Visual Studio 2026 only for now.
• The project is an extension called “Claude Code for Visual Studio”.
• It does not replace Claude Code; it bridges the Claude Code CLI into Visual Studio.
• The core promise is a native diff window with a single accept/reject decision inside Visual Studio.
• It also supports:
  • Reject with feedback so Claude can revise the edit
  • Auto-accept mode for letting edits apply without opening the diff
  • Compiler diagnostics sharing for C# and C++
  • Selection context so Claude knows what file and lines you’re looking at
  • A live panel showing connection status, edit decisions, and token usage/cost estimates
• The extension launches Claude Code in a terminal already connected to the IDE, so there is no /ide step needed in the normal flow.
• Under the hood, it is a protocol bridge, not an agent reimplementation.
• It starts a localhost WebSocket server, writes a lockfile, and launches claude with IDE integration enabled.
• It installs a small PreToolUse hook in the workspace so proposed edits are routed through Visual Studio’s diff as the approval gate.
• It claims to make no model calls and no network calls of its own.
• Privacy-wise, the bridge binds to 127.0.0.1 and validates an auth token on every connection.
• The repo notes several limitations:
  • It works only with Visual Studio 2026
  • The protocol is undocumented and version-fragile
  • Diagnostics require a loaded project, not just a loose file
  • Token stats may lag on chat-only turns
  • Cost figures are only estimates
• Installation is via the Visual Studio Marketplace or by sideloading a .vsix.
• The repository says it has been tested against claude 2.1.173.
• The repo is small and early-stage: 1 commit, with a handful of folders and support files, plus a roadmap and changelog.

My Take

What strikes me is how practical this is. The big idea isn’t “Claude in Visual Studio” in some vague marketing sense; it’s “make the IDE the place where edits are reviewed, diagnostics are seen, and selection context is preserved.” That’s exactly the kind of integration that can make Claude Code feel less like a terminal toy and more like a real development tool.

I think the most compelling part is the single approval gate. If you’ve used AI coding tools long enough, you know how annoying duplicated confirmation flows can be: one prompt in the terminal, another decision in the IDE, and then you’re just context-switching for no good reason. A native diff with accept/reject/reject-with-feedback is the right shape.

That said, the repository is refreshingly honest about the sharp edges. The undocumented protocol dependency is the big worry. This might be a great integration today and a brittle one after a Claude Code update tomorrow. I’d be curious whether the maintainers can keep pace with upstream changes without spending all their time chasing protocol regressions.

I also like that the project is explicit about not making its own model calls. That matters. It keeps the extension in the “bridge” category instead of turning it into a second AI product with its own hidden behavior. For people who already trust Claude Code’s CLI workflow, that’s probably the right boundary.

The diagnostics integration is probably the feature I’d actually try first if I were a Visual Studio user. Getting compiler errors into the agent loop is one of those things that sounds minor until you’ve watched a model flail because it never saw the build output. Selection context is similarly small but useful. Those details are what make an assistant feel like it’s operating inside your IDE instead of just chatting at it.

The auto-accept toggle is a little more suspicious to me. Useful, yes, especially for repetitive edits or cleanup work. But I think it’s also the kind of feature people overuse once they trust the tool, and then spend time auditing changes they didn’t really understand. I’d use it sparingly, probably only after I had a strong feel for the repo and the agent’s behavior.

Overall, this looks less like a flashy new AI product and more like infrastructure work — and that’s a compliment. If you live in Visual Studio and already want Claude Code in your workflow, this is exactly the sort of bridge that could remove friction in a meaningful way.

Reference: GitHub - firish/claude_code_vs

同じ著者の記事

An open-weights Chinese model beat Claude, GPT-5.5, and Gemini in a coding contest

If you build with Claude or Claude Code, this is the kind of result that forces a reset. The interesting part isn’t just that an open-weights Chinese model won a programming challenge — it’s that the winner came from a messy, real-time, server-connected task where code quality, strategy, and failure modes all mattered. In Rohana Rezel’s ongoing AI Coding Contest, Day 12 used the Word Gem Puzzle: a sliding-tile word game with a TCP server, a 10-second limit per round, and objective scoring. Kimi

papoo.work

Chinese Startup Launches Smart Glasses: Why Claude Developers Should Care

A Chinese startup launching smart glasses is interesting not just as gadget news, but as a sign that the next consumer AI interface may be something you wear rather than something you type into. For Claude and Claude Code developers, that matters because it points toward a world where multimodal assistants, real-time context, and on-device interaction could become normal product requirements. The source article says a Chinese startup has launched smart glasses. The post appears in Reddit’s r/Fut

papoo.work

Anthropic’s Claude Corps Is an AI Fellowship for the Nonprofit Front Lines

Anthropic’s new Claude Corps is interesting because it turns “AI for good” from a vague slogan into a concrete deployment model: train people, place them inside nonprofits, and pay them to do real work for a year. For Claude and Claude Code builders, this is less about a flashy product launch and more about a serious bet that the best way to spread AI capability is through embedded, human-supported implementation. Anthropic is launching Claude Corps, a national fellowship for early-career pe

papoo.work

Reddit Post About Data Rigor

From a Claude / Claude Code developer’s perspective, this source is interesting mostly because it isn’t actually a substantive article at all — it’s a Reddit page that appears to be blocked behind a verification gate. That makes it a small but real reminder that a lot of “source material” on the internet is increasingly inaccessible unless you pass platform checks first. The source URL is a Reddit post in `r/artificial`. The visible page title is “Reddit - Please wait for verification.” The

papoo.work

Claude Is Learning Chemistry, and That Matters More Than It Sounds

From a Claude / Claude Code developer’s perspective, this is interesting because it’s not another vague “AI will change science” claim. It’s a concrete benchmark in a domain where precision, provenance, and readable reasoning actually matter, and Anthropic is showing Claude doing useful work on a real chemistry workflow: NMR interpretation. Anthropic says it’s working with synthetic, computational, and analytical chemists to make Claude better at chemistry. This first white paper focuses on a ch

papoo.work

AI Coding Agents and the Hidden Leakage Problem

From a Claude / Claude Code developer’s perspective, this is exactly the kind of story that should make people pause before treating coding agents as “just faster autocomplete.” The title points to a subtle but important risk: agent workflows can create unintended leakage paths, which is the sort of failure mode that matters a lot once you start connecting models to real codebases, secrets, tools, and external services. The source article is about AI coding agents and a “secret leakage”

papoo.work

An Open-Source Tool for Validating Code Changes

For Claude and Claude Code users, tools that sit between “the model wrote code” and “the code is safe to merge” are where a lot of practical value lives. This Reddit post appears to be about an open-source validation tool for code changes, but the extracted source content here is effectively just the title/placeholder, so there isn’t enough substance to fairly summarize the product itself. The source is a Reddit post titled: “An open-source tool for validating code changes.” The body content ava

papoo.work

LLM Observability in the Real World

From a Claude or Claude Code developer’s perspective, the basic idea behind this post is genuinely interesting: someone tried to build an observability platform specifically for LLM applications. That’s the kind of tooling that becomes important fast once you move from “cool demo” territory into shipping agentic systems people actually rely on. The source text itself is extremely sparse, so there isn’t much product detail to unpack. Still, the fact that this showed up in an AI-focused subreddit

papoo.work

Reddit Snippet About “Coding with Claude” Is Too Thin to Trust, but Still Tells a Story

From a Claude / Claude Code perspective, this is interesting mostly for what it *doesn’t* give us: the Reddit source body is essentially a verification placeholder, not an actual report. That means there’s no substantive claim to evaluate, which is a frustrating but very real part of tracking fast-moving AI product chatter. The source is a Reddit post in `r/artificial`. The title suggests the post was about Anthropic’s “Code with Claude” and “coding” demonstrations. The extracted body contains o

papoo.work

Andrej Karpathy Joins Anthropic: Why Claude Builders Should Care

For anyone building with Claude or Claude Code, a move like this is interesting even when the public details are thin. Andrej Karpathy is one of the most recognizable names in modern AI, so the signal here is less about a single announcement and more about where serious talent may be clustering around frontier model work. The source is a Reddit post titled “Andrej Karpathy just joined Anthropic.” The extracted article body does not include supporting details beyond that claim. Because the source

papoo.work