Node Inspect Debugger Use for Node.js debugging that needs inspector access: hidden locals, async hangs, flaky tests, child processes, startup races, memory growth, or CPU hot paths. Default to first. Use Chrome DevTools Protocol only when you need scripted breakpoints, automated state capture, heap snapshots, or CPU profiles. Quick start - Pause on entry: - TypeScript: - Existing PID: then - Inspect target list: - OpenClaw CLI path: - OpenClaw test path: Debugger REPL - Continue/step: , , , , - Breakpoints: , , , , - Inspect: , , , - Current scope: , then evaluate locals directly; exits repl…