Tool Call Timeline
Tool Call Timeline orders the calls in one task and summarizes running, attention, completed, and problem counts. It answers where the task is blocked; it does not replace a searchable audit log.
Read repository instructionsfilesystem · AGENTS.md84 msSucceeded
Find permission implementationssearch · 18 matches312 msSucceeded
Run regression testsshell · npm test -- permissions8.4 sRunning
PASS policy.spec.ts RUNS permission-boundary.spec.ts
Update protected snapshotsfilesystem · 2 filesWaitingConfirmation needed
When to use it
Use a timeline when a task contains at least two independently meaningful calls and a person needs to understand sequence, current blockage, or the source of a problem. Render a single Tool Call directly. Cross-session search, filtering, and export belong in an audit log.
Only stable, earlier calls collapse by default. Running, awaiting, failed, and newest calls remain visible so compactness never hides an actionable state. data-visible-calls sets how many newest calls remain when history is collapsed.
Summary and controller
getSummary() returns total, active, attention, completed, problems, and a derived state. Attention outranks problems, and problems outrank running, so an item that needs a person is never obscured by work that happens to continue elsewhere. expandHistory() and collapseHistory() synchronize history items, action visibility, and a persistable preference event.
Accessibility
The list retains real DOM order. Use one aria-live="polite" summary instead of announcing every stream chunk. Collapsed history leaves the accessibility tree. Name the control “Show earlier calls,” not an ambiguous “More.”