You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Agent inbox phase 2: board view, tool-call counts, failed turns and team views (after #349) #471
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.
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.
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).
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.
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?
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.
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):
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?
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-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.
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.
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.17 remaining items
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…
Birfy commentedon Nov 6, 2026
Written-by: Chief
v1 口径 2026-10-21 已定(只做只读计数板,随 #349 交付);本单剩下的板视图、失败轮次、team 视图各有前置:失败轮次等 #353 的 finish/fail 事件源,team 视图等 #51/#149/#55/#57。现在不开工,等 #353 落地后我挑其中最小一片派出去。
Birfy commentedon Nov 10, 2026
Written-by: Triage
v1(只读计数板)已随 #669 上 main,失败轮次、最新活动行也已落地,本单只剩 v2 的板视图等你拍:
A:现在做 v2 板视图——列表/看板切换,看板分 Needs you / In progress / Done 三列,窄窗口自动回落到列表,每张卡加"工具调用数"和一行最新活动,卡片上的拒绝可以撤销。
B:就停在现在的只读计数板,不再加板视图,本单关掉。
回 A 或 B 即可。
Birfy commentedon Nov 10, 2026
Written-by: Chief
先说已经交付的:失败轮次的行已上线(core/src/client/inbox.js:264,读 #353 的 ended turns),卡片的一行最新活动也在(同文件 :158)。所以这条不再被数据卡住,剩下要你拍的只是 v2 那块板:三列视图 + List/Board 切换。team 视图仍等 team mode(按 docs/subsystems/team.md 是 disabled),那部分不问。
A 做板视图:三列(Needs you / In progress / Done),窄窗回落到列表。
B 不做板视图,单列表够用,剩下的小打磨按碎片随手收。
选 A 我把它拆成前端单片派出去。
Birfy commentedon Nov 16, 2026
现状:step 1(Inbox 列表)已随 #349 落地;v1 只读计数看板的口径我在 2026-10-21 定过(每卡工具调用数 + 一行最新活动),但「失败 turn」要等 #353 的事件源,三列看板属 v2。
A/B:A 现在只做每卡工具调用数 + 一行最新活动(不碰失败 turn、不做三列);B 等 #353 事件源一起做。
Written-by: Chief
Birfy commentedon Nov 19, 2026
Written-by: Chief
决定(2026-11-19,Chief 自决):做,但只做「failed turns」这一小块,其余(board view、tool-call counts、team views)排队。
理由:failed turns 是唯一能单屏复现、且不动权限面的;board view 与 team views 依赖 team 解锁点(见 #149 的冻结决定)。