Agent inbox phase 2: board view, tool-call counts, failed turns and team views (after #349)

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 and wait for an owner decision on order and scope:

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, executingBot fields 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.

Question for the owner: which of these comes next, and is the board (columns + tool-call count) still wanted after using the step-1 list?

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?

(a) Recommended: failed turns in the inbox from one shared event source with Proactive reminders 1/3: event reminders (approval waiting, failed, finished) in app and desktop #353 notifications, plus a one-line latest activity per card; the board view and tool-call counts later, only if still wanted after using the step-1 list. Team views stay blocked 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.
(b) Board view (List/Board toggle, columns, tool-call counts) next.
(c) Defer all of phase 2 until team mode starts.
agent-ready only after the owner's answer.

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 (…

Claimed by maintenance run (2026-10-20 11:55 Asia/Shanghai, main a7adfe0): developing on branch feat/471-inbox-failed-turns in Birfy/FlyBot, following the Owner decision above (first slice only).

Minor details decided while implementing the first slice (2026-10-20 12:01 Asia/Shanghai, PR #491, Part of #471 since the deferred items stay open here):

Event source: failed-turn cards read 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.
When a failed turn needs you: while it is the latest ended turn in its place (a Bot's own chat, or that Bot in one group), younger than 7 days (same window as failed tasks), and the Bot is not running or waiting for an approval there. A later finished turn in that place clears it; no separate dismiss button. That chat is then not also listed under Done.
Card text: status Failed (existing pill), title = the chat's last line (fallback The last turn did not finish), reason = the failure text from the notification entry, Open only.
Keeping it: the host list stays the last 20 ended turns, plus each place's latest failure past those (≤ 50, ≤ 7 days), so busy Bots elsewhere do not push an unresolved failure out. Still process-local: a restart forgets it, like the notifications.
Latest activity row: one muted line 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.

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 removing agent-ready and adding needs-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?

Option	Scope
a	Board view (List/Board toggle, columns) + per-card tool-call count + short first-run guide
b	Failed-turn event source shared with finish/fail notifications (#353) + richer card actions
c	Team views (Assigned to me / by me / Team overview) — depends on grants work
d	Defer all of the above until the social/invite backlog clears

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-ready only after you confirm.

Agent inbox: show failed turns and a latest-activity line on each card (

Merge origin/main into feat/473-schedule-last-run-retry

Merge origin/main into feat/355-email-to-self

Merge origin/main into feat/469-waiting-reminder-toggles

Navigation Menu

Repository navigation

Agent inbox phase 2: board view, tool-call counts, failed turns and team views (after #349) #471

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Agent inbox phase 2: board view, tool-call counts, failed turns and team views (after #349) #471

Description

Activity

Birfy commented on Oct 20, 2026

Birfy commented on Oct 20, 2026

Birfy commented on Oct 20, 2026

Birfy commented on Oct 20, 2026

Birfy commented on Oct 20, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions