Recommended: install the rdbg-debugger plugin for Claude Code with two slash-commands — all five Windows binaries bundled, MCP wired up, zero-config. The standalone binary zip is below for expert users who want to drive the daemon from their own tooling.
rdbg-debugger plugin v0.19.34 (for Claude Code) RecommendedThe shipped install path for AI-agent integration: install into Claude Code with two slash commands, then drive rdbg with any prompt. Bundles all five Windows binaries (no separate download), plus skills, slash commands, and an autonomous bug-hunter subagent. The MCP bridge auto-switches daemons per launch based on the target's PE machine type, so one config drives both Win32 and Win64 targets. Other MCP-capable agents can wire rdbg-mcp.exe in directly via their own MCP config.
:: In Claude Code:
/plugin marketplace add https://sundaymorning.app/rdbg/.claude-plugin/marketplace.json
/plugin install rdbg-debugger@rdbg
You're enrolled in the beta stream. The beta plugin uses the same name as production (rdbg-debugger), so installing it replaces your production install on this machine.
:: In Claude Code:
/plugin marketplace add https://sundaymorning.app/rdbg/.claude-plugin/marketplace-beta.json
/plugin install rdbg-debugger@rdbg-beta
Direct downloads (latest beta build, gated by your account's beta access):
The ?apiKey= on the marketplace URL is injected automatically when you're signed in — the beta endpoint requires it. Don't share the rendered URL: anyone with that key inherits your beta access until you reset it.
The same plugin tree the marketplace serves, packaged as a zip for offline mirrors, air-gapped installs, or extracting the bundled bin/ binaries to wire MCP into your own tooling. Use the marketplace install above when you can.
Standalone protocol.md + JSON Schema for clients building their own driver.
Once the binaries are on PATH, the version check confirms everything's wired:
> rdbgd64 --version
0.19.34
> rdbgd32 --version
0.19.34
> rdbgc --version
0.19.34
:: Trivial console round-trip - launches a tiny test target
:: under the matching daemon. Pick by target bitness.
> rdbgd64 --test-launch bin\test-targets\hello\hello.exe
> rdbgd32 --test-launch bin\test-targets\hello32\hello.exe
Now jump to Getting started for your first real debug session, or the Agent guide if you're driving rdbg from a script or autonomous tool.
The five-minute quickstart walks you from a blank session to your first breakpoint hit, with the matching daemon picked for you.