Module trace

Module trace 

Source
Expand description

2026-09-26: Per-iteration trajectory file: the prompt, then each turn’s reasoning, text, tool calls and finish reason, and each tool result, as plain text so diff of two runs shows the first turn at which they split. The outcome columns (webserver_ok, steps, turns) can agree while the trajectories differ.

Owner: bench, agentic. Invariants:

  • The file is written beside the sandbox (run-07 gives run-07.trajectory.txt), never inside it: the agent’s read, glob and grep tools and the scorer’s has_tests walk the sandbox.
  • A write failure is logged and never returned as an error.

Structs§

Trace