Real debugger for AI coding agents (not print statements)
Problem
AI coding agents (Claude Opus, Codex, etc.) debug by inserting print statements instead of using breakpoints, step-through execution and variable inspection — a 30-year regression from the IDE debuggers human developers already had in the 90s. In a Reddit thread asking which dev tools are still missing in 2026, a 30-year games programmer complains that debugging 'has gone back to the stone ages' because agents cannot attach to a real debugger, and another commenter explicitly asks for 'a way for an agent to debug'.
Opportunity
A tool/protocol that lets coding agents drive proper debuggers (breakpoints, stepping, variable mutation) instead of print-edit-rerun loops, exposing debugger primitives as agent tools. Would cut token waste, debug loop time and hallucinated fixes for the entire agentic coding market.
Market analysis
The pain is real and widely felt, but the MCP ecosystem has already moved: multiple debugger-MCP bridges exist, including an official Microsoft project, so the 'first mover' window is closing fast.
Market · Agentic-coding developers (Claude Code, Codex, Cursor users); large and fast-growing segment with strong token-waste pain.
Pricing · Existing tools are free/open-source (VS Code extensions, MIT-licensed MCP servers); monetization would need an enterprise/team layer (debug telemetry, CI integration).
Pros
- + Genuine, frequently voiced pain: print-statement debugging wastes tokens and time.
- + MCP makes the integration surface standard; a solo builder can ship a bridge quickly.
- + Works language-agnostically on top of the Debug Adapter Protocol.
Cons
- − Microsoft's own DebugMCP plus several community bridges already cover the core use case for free.
- − IDE-tied solutions dominate; a terminal-first or cross-IDE differentiator is the only opening.
- − Frontend/agent vendors are likely to absorb this natively, shrinking the third-party window.
Existing / similar tools
Source
r/softwareengineer (Reddit)
The hard part is not exposing breakpoints over MCP — that has been done at least four times — but making debuggers token-efficient for agents. A stepping session generates far more observation data than a print statement, so a naive bridge can cost more tokens than the loop it replaces. The real differentiator would be a debugger surface designed for LLM consumption: bounded variable snapshots, diff-only state changes between steps, and automatic breakpoint pruning when a hypothesis is disproved. Without that, agents may rationally keep choosing print statements even when a debugger is available.