Skip to main content

Module trace

Module trace 

Source
Expand description

Trace shapes: one user-visible turn, its header, and its spend.

Structs§

MainUsage
The task token slice of a trace: the main agent and its subagents (call_kind=main across every thread), no cache split or cost (those live on the total Usage).
TraceDetail
One trace with its spans. In the composite session response links are session-scoped (top level); the single-trace endpoint sets Links to the edges touching that trace.
TraceItem
One user-visible turn’s header. session_id / harness ids are not duplicated here — they belong to the session.
TraceListResponse
The summaries list for one session. schema stamps the projection generation the rows were derived against — the same stamp the composite carries — so every trace-grain response is self-describing, not just the composite.
TraceUsage
A trace’s total token/cost rollup. Fields are pinned (no omitempty) so the object shape is uniform across traces.