Breakpoints & State Inspection

Breakpoints pause application execution so you can inspect memory, variables, and logic flow.

Setting Breakpoints#

Gutter Click: Click in the margin next to any line number in the editor. A breakpoint glyph appears.
Toggle Off: Click the breakpoint glyph again to remove it.

When a debug session is active, the editor syncs breakpoints to the active debug adapter.

Open the Debug panel via the + (Add Pane) menu or start a debug session to view the Breakpoints section:

Verified Status: An icon indicates whether the debug adapter has verified the breakpoint (circleCheck vs unverified circle).
Jump to Location: Click any breakpoint entry in the list to open the source file and navigate directly to the line.
Breakpoints Menu: Click the header action menu to manage breakpoints globally:
- Enable All: Re-enables all breakpoints if they were muted.
- Mute All: Temporarily deactivates all breakpoints so execution does not pause, while preserving their locations.
- Remove All: Deletes all registered breakpoints from the workspace.

Each breakpoint row has two buttons:

Edit condition (funnel): the debugger stops only when the expression is true, e.g. count > 3.
Edit log message (speech bubble): the debugger logs the message instead of stopping. Put expressions in braces, e.g. count = {count}.

Leave the field empty to remove it. Support depends on the debugger; the Flutter plugin evaluates both.

When execution hits a breakpoint:

Editor Highlight: The paused line highlights with the breakpoint execution color.
Stacktrace: The Stacktrace panel displays the call hierarchy. Select any stack frame to switch inspection context.
Variables: The Variables panel organizes accessible variables into scope tabs (e.g. Locals, Globals). Expand structured variables to view child fields and runtime values.
Debug Output: The Output panel displays log output leading up to the pause.