Debugger
Debug a program on your runner with breakpoints, or ask the column's agent about it.
Opening one
Add a Debugger column from Start, or with Debug here from the + on an agent's, a terminal's or an editor's bar, which opens it right after that column, in its folder. Debug, on a row in Processes, runs that process in a Debugger column; the row's Start takes it back. Lines an agent links to, and lines selected in an editor, have Open in debugger.
Starting a program
Write a command as you'd run it in a terminal, like go test ./orders -run TestTotal or pnpm dev, and Start. The column offers the project's own commands first. Language works it out from the command, or pick one; Pause at the first line stops before anything runs. Or attach to a running process, by its pid or the port its debugger listens on.
It debugs Go, Rust, JavaScript, TypeScript, Bun, Python, Java and PHP. What a language's debugger needs is installed on the runner once you Approve it in the column. A step that runs the system's package manager says so first.
Debugging
The toolbar continues (F5), pauses (F6), steps over (F10), into (F11) and out (Shift+F11), restarts, and stops (Shift+F5). Click beside a line number to set or remove a breakpoint, and give a breakpoint a condition to stop only when it's true. Under the source are the call stack, the variables, the breakpoints and the program's output. Pick a frame in the stack to look at it.
Debug something else, in the toolbar, starts over with another program.
Asking
The composer evaluates an expression in the paused frame, or asks the column's agent; its icon says which, and a click on the icon flips it. The agent finds out from the program itself, its stack, variables and expressions, and drives it as you do. A change to the code it suggests comes as a card to Approve or Deny, and runs once the program restarts.
The column's agent is set in Settings, Agents: the same as new agents, or its own coding agent, model and access.
Agents and nvim
Agents debug here too. orven debug open <command> opens a Debugger column beside the agent, debugging the command, and orven debug break, continue, next, step, vars and eval work it. orven debug help lists the rest. Installs and changes to your code still wait for you.
In nvim, in a terminal a Debugger column was opened from, its breakpoints show as signs and the paused line is highlighted. :Orven debug sets breakpoints and steps from there.