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

Activity

1. Birfy

   added

   enhancementNew feature or requestNew feature or request

   needs-humanThe agent loop stopped; a person must decide (reason in the last comment)The agent loop stopped; a person must decide (reason in the last comment)

   area:uiWeb/desktop UI and copyWeb/desktop UI and copy

   on Oct 20, 2026
2. Birfy commented on Oct 20, 2026

   

   Birfy

   on Oct 20, 2026

   CollaboratorAuthor

   More actions

   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.
3. Birfy commented on Oct 20, 2026

   

   Birfy

   on Oct 20, 2026

   CollaboratorAuthor

   More actions

   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.
4. Birfy

   added

   agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a templateMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a template

   and removed

   needs-humanThe agent loop stopped; a person must decide (reason in the last comment)The agent loop stopped; a person must decide (reason in the last comment)

   on Oct 20, 2026
5. Birfy

   added a commit that references this issue on Oct 20, 2026

   Add Agent inbox step 1: Inbox row with Needs you / In progress / Done (…

   ...

   c7898dd
6. Birfy

   added

   agent-workingAn agent has claimed this issue (the claim comment names the branch)An agent has claimed this issue (the claim comment names the branch)

   on Oct 20, 2026
7. Birfy

   self-assigned this

   on Oct 20, 2026
8. Birfy commented on Oct 20, 2026

   

   Birfy

   on Oct 20, 2026

   CollaboratorAuthor

   More actions

   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).
9. Birfy commented on Oct 20, 2026

   

   Birfy

   on Oct 20, 2026

   CollaboratorAuthor

   More actions

   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.
10. Birfy commented on Oct 20, 2026

    

    Birfy

    on Oct 20, 2026

    CollaboratorAuthor

    More actions

    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.
11. Birfy

    removed

    agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a templateMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a template

    on Oct 20, 2026
12. Birfy

    removed their assignment

    on Oct 20, 2026
13. 13 remaining items

    Load more
14. Birfy

    added

    needs-humanThe agent loop stopped; a person must decide (reason in the last comment)The agent loop stopped; a person must decide (reason in the last comment)

    area:automationScheduled tasks and automationScheduled tasks and automation

    and removed

    needs-humanThe agent loop stopped; a person must decide (reason in the last comment)The agent loop stopped; a person must decide (reason in the last comment)

    on Oct 21, 2026
15. Birfy commented on Oct 22, 2026

    

    Birfy

    on Oct 22, 2026

    CollaboratorAuthor

    More actions

    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 calls line 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: the tool/call events core/src/host/turns.js already folds; the count rides the existing work snapshot (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.
16. Birfy

    added

    agent-workingAn agent has claimed this issue (the claim comment names the branch)An agent has claimed this issue (the claim comment names the branch)

    and removed

    agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a templateMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a template

    on Oct 22, 2026
17. Birfy

    self-assigned this

    on Oct 22, 2026
18. Birfy commented on Oct 22, 2026

    

    Birfy

    on Oct 22, 2026

    CollaboratorAuthor

    More actions

    Triage label record (2026-10-22) — #627 scope A.

    agent-working was set at 01:30:05Z (agent-ready removed). The claim comment at 01:30:03Z names feat/471-inbox-board but carries no Written-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
19. Birfy

    added

    needs-humanThe agent loop stopped; a person must decide (reason in the last comment)The agent loop stopped; a person must decide (reason in the last comment)

    and removed

    agent-workingAn agent has claimed this issue (the claim comment names the branch)An agent has claimed this issue (the claim comment names the branch)

    on Oct 22, 2026
20. Birfy commented on Oct 22, 2026

    

    Birfy

    on Oct 22, 2026

    CollaboratorAuthor

    More actions

    Triage label record (2026-10-22): agent-working removed — 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-human and nothing is in flight. agent-pr is not set either: #669 is merged and no follow-up PR is open.
21. Birfy

    added 2 commits that reference this issue on Oct 23, 2026

    Timeline: per-Bot turn outcomes and recent failures (ThinkFlowLab#531)

    ...

    03bfc46

    Show each Agent inbox card's tool-call count (ThinkFlowLab#471) (Thin…

    ...

    217bf15
22. HugoXK

    added a commit that references this issue on Oct 25, 2026

    Let one task lead assign group cards and start the assignee in the gr…

    ...

    604ffa3
23. Birfy commented on Nov 6, 2026

    

    Birfy

    on Nov 6, 2026

    CollaboratorAuthor

    More actions

    Written-by: Chief

    v1 口径 2026-10-21 已定（只做只读计数板，随 #349 交付）；本单剩下的板视图、失败轮次、team 视图各有前置：失败轮次等 #353 的 finish/fail 事件源，team 视图等 #51/#149/#55/#57。现在不开工，等 #353 落地后我挑其中最小一片派出去。