A model's reasoning trace is useful and long. Reasoning gives it somewhere to go: open while it streams in, collapsed to a one-line summary once it finishes, and quiet enough throughout that it never competes with the answer beside it.
Streaming, then settled
While the trace arrives, the panel is open and the summary shimmers. When the stream ends it collapses to the time it took.
The request asks for the total across both regions, but the two
tables report in different currencies. I need to convert before summing, and
the rate should be the one on the invoice date rather than today's — otherwise
the November figures move every time the report is re-run.
The resting state
Collapsed by default once complete. With no duration to report, the summary falls back to a plain label; pass label to say something more specific than how long it took.
The request asks for the total across both regions, but the two
tables report in different currencies. I need to convert before summing, and
the rate should be the one on the invoice date rather than today's — otherwise
the November figures move every time the report is re-run.
The request asks for the total across both regions, but the two
tables report in different currencies. I need to convert before summing, and
the rate should be the one on the invoice date rather than today's — otherwise
the November figures move every time the report is re-run.
The request asks for the total across both regions, but the two
tables report in different currencies. I need to convert before summing, and
the rate should be the one on the invoice date rather than today's — otherwise
the November figures move every time the report is re-run.
Expanded
The trace sits on a rail in secondary text. It is deliberately plainer than the response it belongs to — the reader came for the answer, and opened this only to check the working.
The request asks for the total across both regions, but the two
tables report in different currencies. I need to convert before summing, and
the rate should be the one on the invoice date rather than today's — otherwise
the November figures move every time the report is re-run.
Two decisions worth knowing
The auto-collapse yields to the reader. Opening on stream and closing on completion is right until someone opens the panel themselves — after that, the stream ending no longer moves it. A panel that shuts while you are reading it is worse than one that stays open.
Only the summary is a live region. A trace announced token by token floods a screen reader. The body is ordinary expandable content and the announcement covers the boundaries instead: thinking, then thought for so long.