Pzep1 Claudecode Debug Mode
Instrument running code with fetch-based debug probes so Claude captures live runtime data instead of guessing from static reads.
Overview
pzep1-claudecode-debug-mode is a plugin marketplace for the Ship phase that enables Claude Code runtime debugging via instrumented fetch calls that capture data from executing code.
What is this marketplace?
- Runtime debugging through instrumented fetch calls during real execution
- Captures live data from code paths agents cannot see from source alone
- claude-debug-plugin v2.0.0 bundled in pzep1 marketplace
- Designed as Claude Code debugging plugins and workflows
- Single-plugin marketplace from repository root
Community signal: 28 GitHub stars.
What problem does it solve?
Claude keeps proposing fixes without seeing what your code actually returns at runtime, so you burn cycles on guesses instead of evidenced debugging.
Who is it for?
Solo developers using Claude Code who debug network-backed or fetch-heavy runtimes and want a repeatable capture workflow without standing up full APM.
Skip if: Teams needing enterprise tracing, mobile native crash logs only, or security-sensitive environments that forbid dynamic instrumentation.
What do I get? / Deliverables
After adding the marketplace, you can run instrumented fetch probes so debugging sessions include captured runtime payloads the agent can reason on.
- Captured runtime payloads via instrumented fetch during debug runs
- Shorter guess-and-check loops when pairing with Claude on bugs
- Documented debug-mode workflow reusable across similar failures
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Ship/testing is the primary shelf because the plugin targets runtime debugging workflows right before and after release-quality verification. Testing fits instrumented execution traces and evidence collection during repro runs, not passive log dashboards alone.
How it compares
Runtime capture debug marketplace for Claude Code, not a static linter skill or hosted error monitoring SaaS.
Common Questions / FAQ
Who is Pzep1 Claudecode Debug Mode for?
Claude Code users who debug live execution paths—especially fetch-based I/O—and want the agent to work from captured runtime data.
When should I use Pzep1 Claudecode Debug Mode?
Use it during Ship testing or Operate error hunts when reproduction needs runtime evidence beyond stack traces and static code reading.
How do I add Pzep1 Claudecode Debug Mode to my agent?
Install the pzep1/claudecode-debug-mode Claude Code marketplace, enable the claude-debug-plugin (v2.0.0), and follow its instrumented fetch workflow during repro runs.