Repository navigation
Agent inbox phase 2: board view, tool-call counts, failed turns and team views (after #349) #471
Description
Follow-up to #349. Step 1 (Inbox row in the sidebar plus a list with Needs you / In progress / Done, existing data only, my own Bots only, Done kept 7 days) ships in the PR that closes #349. These parts were left out on purpose:
Board and cards
- Three-column board view with a List / Board toggle; narrow windows fall back to the list.
- Per-card tool-call count and a one-line latest activity.
- A short first-run guide.
- Reject that can be confirmed or undone (RFC acceptance line); step 1 rejects at once, like the chat card.
More data
- Failed turns without a task record. There is no host record of a failed turn yet; this should share one event source with Proactive reminders 1/3: event reminders (approval waiting, failed, finished) in app and desktop #353 (finish/fail notifications) instead of adding a second one.
- Approving from the inbox an approval that DSH's own card answers in a Bot's own chat (step 1 shows Open only, since there is no shared answer for it), and task actions on the card (accept a result, answer an input request); step 1 has Open only for those.
- Tasks from non-FlyBot runtimes ([RFC] 跨运行时 Agent 对话与协作：以 OpenCode 为首个试点的目标、需求与两种方案 #198).
Team (phase 2)
- Views: Assigned to me / Assigned by me / Team overview, using the
assigner,owner,executingBotfields every step-1 card already carries (all set to me now). - Friends' Bots and a granted Bot's downstream, reassignment with an audit trail. Depends on [Team] Gate cross-owner agent routes by per-Bot grants (default deny; superseded the publication gate) #51, Team mode via groups: task layer step 1 - responsible-owner authority, FLYBOT-TASK envelope, workBotId #149, [Team] Recover task handoffs without duplicate work #55, [Team] Add a human-readable authorization and task audit trail #57.
Decided (2026-10-21, Chief): v1 is the read-only count board only — per-card tool-call count, failed turns, the existing Needs you / In progress / Done groups, and the one-line latest activity. The three-column board with a List / Board toggle is v2. Spec of record: the triage comment of 2026-10-21.
Activity
Birfy commentedon Oct 20, 2026
Maintenance triage (2026-10-20 09:56 Asia/Shanghai, main
465357e): still needs-human; depends on #349 step 1 (PR #472) landing. Question for the owner: what comes next for the Agent inbox?agent-readyonly after the owner's answer.Birfy commentedon Oct 20, 2026
Owner decision (2026-10-20): option (a) as recommended — failed turns also appear in the inbox, sharing the event source with #353 notifications; each card gets a one-line latest-activity row. Board view and tool-call counts deferred; team view waits for #51/#149/#55/#57.
Add Agent inbox step 1: Inbox row with Needs you / In progress / Done (…
Birfy commentedon Oct 20, 2026
Claimed by maintenance run (2026-10-20 11:55 Asia/Shanghai, main
a7adfe0): developing on branchfeat/471-inbox-failed-turnsin Birfy/FlyBot, following the Owner decision above (first slice only).Birfy commentedon Oct 20, 2026
Minor details decided while implementing the first slice (2026-10-20 12:01 Asia/Shanghai, PR #491,
Part of #471since the deferred items stay open here):work.ended, the ended-turn entries the Proactive reminders 1/3: event reminders (approval waiting, failed, finished) in app and desktop #353 notifications already use; no new host record or endpoint.Latest: …with the full text on hover: a task's newest note, else the tool its Bot runs there now (running turns and tasks only), else the chat's last line; hidden when it would only repeat the title or reason.Birfy commentedon Oct 20, 2026
First slice of #471 is on main via #491 (Agent inbox: failed turns + latest-activity line on each card; Part of #471).
Removing
agent-working/ assignee for now. Also removingagent-readyand addingneeds-human— board view, tool-call counts, and team views were deferred and need a fresh owner confirmation before more development.Confirmation needed — what next for Agent inbox phase 2?
Recommendation: (d) — finish the social cluster (#499/#498/#496/#506/#500 companions) first; revisit board/tool-counts after that. Reply with a/b/c/d (or a mix) and we will re-label
agent-readyonly after you confirm.12 remaining items
Birfy commentedon Oct 22, 2026
Claimed (2026-10-22, branch
feat/471-inbox-board).Scope for this pass, per the spec of record (triage 2026-10-21): the v1 read-only count board — one
N tool callsline per card, for that card's own place (the Bot's own chat, or that one group), counted over the current or the last ended turn there. One source: thetool/calleventscore/src/host/turns.jsalready folds; the count rides the existingworksnapshot (bots/rooms/ended), so no new polling and no new event source. Nothing shown for 0 or unknown; grouping, the 7-day Done cap,needsCount, the latest-activity line and the read-only Open action stay exactly as they are.Not in this pass (v2, needs the owner): the three-column board, the List/Board toggle and its narrow-window fallback.
Birfy commentedon Oct 22, 2026
Triage label record (2026-10-22) — #627 scope A.
agent-workingwas set at01:30:05Z(agent-readyremoved). The claim comment at01:30:03Znamesfeat/471-inbox-boardbut carries noWritten-by:/Posted-by:.Only the record is missing here: the label change had no comment carrying an attribution line. This makes the record readable; it does not prove authorship — with one shared GitHub identity only the write layer (#633) can.
Written-by: Triage
Birfy commentedon Oct 22, 2026
Triage label record (2026-10-22):
agent-workingremoved — v1 shipped in PR #669 (1958157a, merged 03:50:06Z).v2 (the three-column board with a List / Board toggle) is still the user’s call, so the label is
needs-humanand nothing is in flight.agent-pris not set either: #669 is merged and no follow-up PR is open.Timeline: per-Bot turn outcomes and recent failures (ThinkFlowLab#531)
Show each Agent inbox card's tool-call count (ThinkFlowLab#471) (Thin…
Let one task lead assign group cards and start the assignee in the gr…