Run logs and output
Filter a run's log by level and category, find text in it, and read what the graph printed to stdout and stderr.
The Run logs panel on a run's page has two tabs. Logs is the execution log; Output is what the graph printed, with a line count. It opens on Output when the run printed something.
Log levels
Errors, Warnings, Info, Debug, and Trace each show that level and everything more severe. Choosing Debug or Trace also sets the detail recorded for the next run.
Categories and the toolbar
- Category chips (Stdout, Stderr, Print, Flow, State, Exec, Heap, Frame, LLM, Tool, …) narrow the log when it holds more than one category.
- Find… searches the log; Enter / Shift+Enter move between matches, and "Show only matching lines" hides the rest.
- Follow output, Soft wrap, Show timestamps, and Show line numbers change the display.
- Alt+↑ / Alt+↓ jump to the previous or next problem.
- Copy visible rows copies what the filters leave; Download log saves run-log-<id>.log; Clear console can be undone.
Output: stdout and stderr
The Output panel filters by All, stdout, or stderr, with counts. PRINT, LOG, ACTION, METRIC, and TRACE nodes write to stdout; a failing node writes to stderr.
Related
- Read a run's pageRunning & debuggingWhat each panel of a run's page shows — summary, controls, path, logs, output, and the execution trace.
- Read run history and tracesRunning & debuggingThe runs list, per-run traces and logs, and the run pages hanging off a graph.
- Debug with breakpointsRunning & debuggingPause execution at a node, step, inspect agent memory, and manage breakpoints across graphs.
More in Running & debugging · Search all help