Cursor Debug Mode–style debugging for Claude Code — slash /dmd:start. NDJSON logs, dmd CLI, optional HTTP ingest (dmd serve).
Stop dmd-related background servers — slash /dmd:stop. Sends SIGTERM to PIDs in .claude/dmd-ingest.pid and dmd-demo.pid (same cwd as dmd path).
Brings Cursor's Debug Mode to Claude Code. A plugin that guides Claude through hypothesis-driven debugging — hypothesize, instrument, collect logs, verify — via /dmd:start.
Requirement: Bun
git clone https://github.com/laiso/claude-code-dmd.git
cd claude-code-dmd/demo
claude --plugin-dir ..
Then run /dmd:start and tell Claude "the app has bugs." Claude takes it from there. See demo/README.md for the bug list and details.
To use with your own project: claude --plugin-dir /path/to/claude-code-dmd from your project root. Plugins docs
/dmd:start walks Claude through a structured loop:
#region agent log markers.claude/debug-<session>.logThe dmd CLI manages sessions and log files under .claude/. For browser-side logging, dmd serve runs a small localhost HTTP ingest (default 127.0.0.1:8792) that accepts POSTs at /ingest and writes to the same log file.
{"message":"Repro: bulk discount stacks incorrectly","hypothesisId":"H1","timestamp":1712223334444}
Full CLI reference, environment variables, and ingest details: spec/dmd-cli-and-runtime.md
127.0.0.1; do not expose publiclydmd remove or dmd remove-allbun install
bun run typecheck
dmd = debug mode (unrelated to dlang/dmd) · spec · Plugins docs
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub laiso/claude-code-dmd --plugin dmdAgentic memory — search and summarize past sessions, plans, and memory across projects
Systematically debug issues with step-by-step troubleshooting approaches.
Systematic debugging and root cause analysis framework - four-phase investigation process ensuring understanding before fixes
Runtime debugging for Claude Code via instrumented fetch calls and a bundled local debug server.
Ask Claude Code to help you debug an issue
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions. Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.