PLATE DOCDebugger
Breakpoints, driven from chat
Debug is one of the six chat modes. You get real breakpoints and stepping, and the agent can read the paused state — variables, call stack, the failing assertion — instead of guessing from a stack trace you pasted.
- F5 start
- F9 breakpoint
- F10 step over
- F11 step into
A debugger, not a log reader
Set breakpoints in the editor, start a session, and step through. The debugger speaks the Debug Adapter Protocol, so language support comes from the same adapters other editors use.
The agent sees what you see
In Debug mode the agent has the paused program state available to it. That turns 'why is this undefined' from a guessing game into a question with an answer.
What it does not do
Debug lives in the chat column. The separate Debug tab in the app is hidden, and language coverage depends on the debug adapter for your stack.