What problem does it solve? Diagnosing why Python code misbehaves is hard when tracebacks and print statements don't reveal the root cause, especially in tests, long-running daemons, and subprocesses that can't be restarted cleanly. ## Core Features & Use Cases - Interactive pdb debugging: Drop into a REPL with breakpoint(), launch scripts under python -m pdb, and use the full pdb command set (step, breakpoints, stack navigation, expression evaluation). - Remote debugging with debugpy and remote-pdb: Attach to already-running processes via DAP on port 5678, inject into a live PID, or open a terminal pdb session over TCP with remote-pdb. - Post-mortem and test debugging: Inspect locals at crash sites with pdb.post_mortem, and debug pytest failures with --pdb while avoiding the xdist hang. - Use Case: A gateway subprocess deadlocks in production-like conditions. Add remote_pdb.set_trace() in the handler, trigger the request, connect with nc 127.0.0.1 4444, and inspect the suspended frame and pending asyncio tasks. ## Quick Start Add a breakpoint() call at the suspicious line in my Python file and walk me through inspecting variables when execution pauses there.
