Break into live sessions, redact sensitive output before it reaches the model, and a brand-new documentation site. A year and a month in, with 1.4k stars and a community that keeps showing up.

Last time I had a proof of concept. This time I closed the gap: remote debugging and Windows kernel debugging, straight from VS Code, powered by the same engine as WinDbg. It's open source and on the Marketplace.

I only wanted a faster remote debugging workflow for a service running in a VM. Instead, I ended up learning DAP, wrapping WinDbg, and building a working first proof of concept debugger adapter for VS Code.

Adding Prompts API support and streamable-http transport to mcp-windbg.

AI-powered crash analysis gets a major upgrade with PyPI availability, live debugging sessions, and community-driven improvements. One-command installation is finally here.

Because manually squinting at hex dumps is so last century. Let me show you how AI-assisted debugging is leaving WinDBG's command line in the dust.