Repository navigation
Timeline: which tools each Bot used, and how often they failed #538
Description
What
The timeline lists each tool call inside a turn, but nothing summarizes which tools a Bot relies on or how often they fail, so a flaky tool or connector is hard to notice.
Expected behavior
timeline/windowgainstoolUse: per Bot lane, its tools as{ name, calls, failed }, by call count (top 20), names cleaned and capped.- Read-only, part of the existing answer, metadata only.
Change scope
plugins/timeline/src/window.js, a case in plugins/timeline/test/window.test.js, docs/subsystems/timeline.md. Plugin only.
Why
Tool/connector reliability becomes visible where the run is drawn (#357; #359 connectors).
Activity
Birfy commentedon Oct 20, 2026
Triage (Birfy, 2026-10-20 20:08 Asia/Shanghai). Read-only timeline analytics:
timeline/windowgainstoolUse, per Bot{ name, calls, failed }, top 20, names cleaned. Plugin only. HugoXK's PR #539 implements it (reviewed PASS at c5e47a5, CI green).Design check: no conflict with the owner rules (metadata only, no args or output). It is derivable from
turns[].tools, and no panel view reads it yet. Same series as #530/#534/#536, with no overlap with the merged export (#484/#523/#524).Proposed scope if accepted: as in #539, plus a small per-Bot tool table in the panel (calls/failed), which makes connector failures visible (#359).
needs-human: the owner needs to confirm this new feature and whether HugoXK's #539 is accepted as the implementation.Birfy commentedon Oct 20, 2026
Owner decision (2026-10-20 21:09 Asia/Shanghai): accepted (option a). PR #539 is accepted; the per-tool usage/failure data must also be visible in the dashboard/panel, not only in the timeline/window API.
Timeline: stuck requests, tool use and team health (combined) (ThinkF…