Project kanban board: what each agent is doing, grouped by state #161

This was generated by AI during triage.

Summary

A kanban board per project that shows what each agent in it is doing. A project is a session group, or every session sharing a repo, worktrees included. Columns are states, cards are agents, and each card says what that agent is working on now. The question it answers is "where does each part of this project stand?", which a terminal grid can't answer once a project has four or more agents.

How this differs from the related issues

This view could be built on #57's card component, or replace #57 outright (#57 would become this board with grouping turned off). That's for the maintainer to decide.

Proposed behaviour

v1: columns are agent states, cards are agents

Each card shows:

• accent stripe, name, branch and dirty marker (all existing);
• doing now: one line, taking the best source available:
  1. a status the agent pushed itself (Team Bus Team Bus: let an agent add/edit its own session's run commands, not just title/color/status #138 / OSC 9001 title);
  2. for Claude sessions, the in_progress item of the agent's current todo list, read from the session transcript under ~/.claude/projects/ (ClaudeSessionService already locates it to find the --resume id);
  3. otherwise the last non-blank output line;
• time in the current column ("waiting 12 min"). Combined with the Needs columns, this is the thing that makes the board useful: it shows who has been blocked on you the longest.

Interactions:

• clicking a card focuses that session;
• right-clicking a card opens the same menu as the sidebar row;
• no dragging between columns: the column is observed state, not something the user sets.

Scope selector: a group (reusing SessionGroup), a repo (RepoRoot, which merges worktrees of one repo), or All.

v2: columns are tasks

Gather every agent's todo list into To do / In progress / Done, with each card tagged by the agent that owns it. This is the board people usually mean by "kanban", but it depends entirely on reading todo lists (Claude only, unless other harnesses publish theirs via #132), so it comes second.

Constraints

• It can't be drawn over the terminal grid. WebView2 is an HwndHost (CLAUDE.md, "Session Spinners"). The board must either collapse TerminalGrid while it's shown, as ShutdownOverlay and Add Workspace Overview view: status cards with activity + output preview #57 do, or open as its own window. A separate window has a real advantage here: it can sit on a second monitor and stay live.
• The UI thread is a hot path (see the issue perf: coalesce per-session PTY output dispatcher posts to prevent UI starvation #70 history and PR fix(perf): take three blocking paths off the UI thread and the thread pool #160). State changes must update cards in place, never rebuild the board, and transcript reads must be throttled and run off the UI thread.
• Transcript parsing reads an undocumented Claude Code file format. Treat it as best-effort: a parse failure falls back to source 3, never to an error.

Open decisions

1. Separate window or a grid-replacing view? This also decides Add Workspace Overview view: status cards with activity + output preview #57's fate.
2. Is the transcript todo list an acceptable dependency, or should v1 rely only on what agents push themselves (Team Bus: let an agent add/edit its own session's run commands, not just title/color/status #138) plus output?
3. Which default scope: the active session's group, or its repo?

Depends on #154 (Working state). Related: #57, #132, #125, #138, #151.