Debugging

The IDE currently provides Python, Node, Java and Go debugging entries. DAP is a protocol, not evidence that every language adapter is integrated into the IDE.

Prerequisites

• Python: install Python and debugpy yourself. Verify the selected interpreter can import the package.
• Node: install Node.js and js-debug yourself. Ensure js-debug-dap is on PATH; the current entry starts that command directly.
• Java: install the JDK and jdt.ls with the java-debug plugin. The current debug view uses attach: enter the target JVM's JDWP host and port (default 127.0.0.1:5005) and enable JDWP on that JVM. The kernel obtains the DAP port from the language service; it is distinct from the JDWP port.
• Go: install Go and Delve (dlv) and ensure the command is on PATH. Compile with go build -gcflags="all=-N -l" -o app . first (use app.exe on Windows) and enter the executable path in the program field. The current entry uses exec mode, not a .go source file. The kernel starts dlv dap automatically on a dynamic 127.0.0.1 port; no manual server startup is required.

Paths, runtime versions, working directory and program arguments must match your project. Protocol support does not install adapters. VS Code launch.json can be used for manual comparison, without guaranteed import or extension compatibility.

Sessions

Set a launch configuration and breakpoints in the debug view, launch or attach to the target, inspect variables, stack and output, then continue, step or stop. Available capabilities depend on the adapter and program. For connection failures, check paths, processes, ports and adapter logs without exposing secrets.

Debugging starts or connects to processes with local permissions; it is not strong-isolation execution. Review and test AI-generated fixes.

Terminal and sandbox · Configuration