Interactive Debugging (WinDbg/CDB REPL)

Interactive debugging is driven by orchestrating the CDB debugger through an agent, using run_command to launch the process and send_command_input to issue commands like g, t, bp, dv, and q for execution control and state inspection.

During an automated debugging session, you can send commands like bp for breakpoints, t for stepping, dv to inspect locals, and q to quit, allowing the agent to manage execution and inspect memory and stacks interactively.

Yes, launching the CDB debugger through a build_env wrapper is required to initialize the environment before the agent starts driving the interactive debugging session with run_command and send_command_input.

The best way to handle a hung CDB session or lost CommandId is to follow the skill's end-to-end workflow for cleanup and recovery, ensuring the debugger process is terminated and the environment is reset for a new session.

Yes, you can use this method for incident investigation on Windows applications, as it supports step-by-step execution, memory analysis, and state inspection to diagnose issues during development and post-incident.