Repository navigation
Prototype the span tree and span details #995
Description
Parent
What to build
A /prototype session designs two things, borrowing from MLflow's trace view:
- the span tree that grows out of the Console's Waterfall, showing a Command's Runs, stages, sessions, model calls and tool calls;
- each span's details in the Peek panel.
The design, with any snippet that encodes it more precisely than prose, is recorded on #996. It's for a human because the prototype is designed with you, in a session of its own.
Acceptance criteria
- A design for the span tree and span details, at phone and laptop widths, is recorded on The span tree and span details in the Console #996.
Activity
JacobStephens2 commentedon Oct 22, 2026
Verdict
The question: what should the span tree that grows out of the Waterfall, and a span's details in the Peek panel, look like at phone and laptop widths?
Layout E, a tree with a timeline and the slowest calls, with Peek layout 3, a summary card. The design is recorded on #996 under "Design (settled in #995)".
The prototype
src/console/span-tree-prototype/on theissue-995-prototypebranch, at edf2d3d. It holds five tree layouts (?variant=A–E) and three Peek layouts (?details=1–3) on a copy of the Waterfall page, over real Session traces.extract.pyrebuilds the git-ignored fixture from any Command records. The branch is throwaway and never merges to main.JacobStephens2 commentedon Oct 22, 2026
Done: the design is recorded on #996 ("Design (settled in #995)"), together with what the static prototype didn't show and the build must decide. The prototype stays on the
issue-995-prototypebranch.