Repository navigation
Timeline: list the requests waiting longest #534
Description
What
#469 (proactive reminders follow-up) wants a "waiting too long" signal. The timeline window flags waiting requests per edge, but nothing lists them, so a stuck Bot-to-Bot handoff is easy to miss.
Expected behavior
timeline/windowgainsstuck: the open requests (waiting: true), sorted by waited time, worst first, up to 20, each{ id, from, to, role, waitedMs }.- Read-only, part of the existing answer, ids only.
Change scope
plugins/timeline/src/window.js, a case in plugins/timeline/test/window.test.js, docs/subsystems/timeline.md. Plugin only.
Why
A stuck handoff becomes visible where the run is drawn (the quality/proactivity bets).
Activity
Birfy commentedon Oct 20, 2026
Triage (Birfy, 2026-10-20 20:08 Asia/Shanghai). Read-only timeline analytics:
timeline/windowgainsstuck, the open requests (waiting: true) worst-first, up to 20, ids only. Plugin only. HugoXK's PR #535 implements it (reviewed PASS at d423209, CI green).Design check: no conflict with the owner rules. This is different from the shipped approval-waiting reminder (#469/#492, approvals), since it covers Bot-to-Bot requests. Limitation: it only sees requests inside the viewed window, so an older stuck request is missed. Same series as #530/#536/#538, all adding fields to
timeline/window. No overlap with the merged export (#484/#523/#524).Proposed scope if accepted: as in #535, plus scanning open requests across the whole trace (not only the window) and showing them in the panel's "who waits on whom" view.
needs-human: the owner needs to confirm this new feature and whether HugoXK's #535 is accepted as the implementation.Birfy commentedon Oct 20, 2026
Owner decision (2026-10-20 21:09 Asia/Shanghai): accepted (option a). PR #535 is accepted; the stuck/waiting-longest list 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…