Colours, fonts and layout as the UX-059 mock, light and dark: the step
colour tokens, the time axis with gridlines, and a step's details in a
pane beside the list. The details show a model call's tokens, context,
input and output; a tool's arguments, approval wait and how it was
allowed; a check's questions and the call it judged.
The step endpoint now returns a tool call's arguments, its approval
wait, and for a check the step it judged.
Phase 1 screens from UX-059 (OB-1 steps timeline, OB-2 step details,
OB-4 session usage), reading the engine's recording endpoints.
- A Steps button in the session header opens the panel in the right
rail's full-view slot. Turn picker; tiles for Total and every time
bucket that is not zero, plus Other when it is 1% or more; the
auto-approve line; every step of the turn on one time axis, nested
steps (helper calls, a check's model call) under their parent.
- Clicking a row shows its details: status, timing, model and provider,
first reply time, finish reason, tokens split by type (a count not
reported shows as a dash, never 0), the decision path and who decided,
the transcript message, and the exact request and response.
- The Usage tab: input, output and cache share, the at-least and
failed or over-limit lines, by purpose, by model (in, cache, out) and
context now. /usage gains the per-model parts and totals for it.
- The panel refreshes on live step events and at a turn's end.
The Issues tab (OB-3) is Phase 2.
Phase 1 read side (ocw-context docs/observability/phase-1/technical-design.md
§6.3, §7.1, §12).
- coworker/observability/calculator.py: the token pill, the "at least"
marker, failed and over-limit calls, by purpose and model, cache share,
and each turn's time buckets. The shared golden test now also checks
expected-numbers.json: 30 of 30.
- GET /v1/sessions/{id}/turns (turns with stamp, buckets and usage),
/turns/{turn_id}/steps (a light list in canonical order),
/steps/{step_id} (one step in full: content, the exchange rebuilt from
its pieces, the transcript message it points at cut at 4 KB, its audit
rows and child steps) and /usage (the session's numbers and context
fill). A session recorded before Phase 1 answers recorded: false.
- While a turn runs, the recording events go to the session's sockets as
{"type": "step", "events": [...]}, batched every 100 ms.
Not yet: sending an explore helper's steps only when its step ends, and
computing /usage from the store's columns instead of the loaded recording.