What problem does it solve? Python bugs in tests, long-running daemons, and subprocesses are hard to inspect when tracebacks alone don't reveal wrong values, and restarting a misbehaving process isn't an option. ## Core Features & Use Cases - Interactive pdb debugging: Set breakpoints with breakpoint(), step through code, inspect locals, and run post-mortem analysis on exceptions. - Remote debugging with debugpy: Attach to already-running processes via DAP on a TCP port, including PID-based injection for daemons and gateways. - Terminal-friendly remote-pdb: Get a plain (Pdb) prompt over nc for agent-friendly debugging without IDE setup. - Use Case: A gateway subprocess misbehaves in production-like conditions. Add remote_pdb.set_trace() in the handler, trigger it, 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 suspect line in my Python file and walk me through inspecting the variables when it hits.