Board view: see all threads in columns by status (Needs you, Working, Waiting, Done)

[romanzdk]

Before submitting

• I searched existing issues and discussions and did not find a duplicate. Related: Sidebar: let a thread report its own status (Needs you, Background, Done) with Stale after N hours #31520 (a thread reports its own status; the author rebuilds a board outside T3), Backlog board next to PRs: see planned work and start threads from issues (Linear, GitHub Issues, Jira…) #30981 (Backlog board for tracker issues), [Proposal] Per-project Kanban board #853 (per-project Kanban, closed in March).
• I am describing a concrete problem or use case.

Area

apps/web (desktop wraps it); mobile later, if wanted

Problem or use case

With many threads running, the sidebar is a long list. To answer "which threads are waiting on me?" I scan every row for the small status label. The answer is already in T3 (Pending Approval, Awaiting Input, Plan Ready, Working, Waiting, Failed, Completed), but it is spread across the list instead of grouped.

#31520 shows the same need: they sort their threads into status groups in a separate board they maintain by hand. #853 asked for a Kanban board a while ago and was closed for lack of interest. This is a much smaller thing than that.

Proposal

An optional Board view next to the thread list. It shows the same threads in columns:

Column	Threads with this status
Needs you	Pending Approval, Awaiting Input, Plan Ready, Failed
Working	Working, Connecting
Waiting	Waiting (blocked on another thread or a background task)
Done	Completed, idle

• Cards show title, project and the same status label the sidebar uses. Clicking a card opens the thread.
• Read only. The column comes from the status T3 already works out. You can't drag a card to change it, so the board can never disagree with the sidebar.
• Uses the existing status logic (resolveThreadStatusPill), so there is no new status model, no new data and no server change.
• Filters follow the sidebar's project filter.
• Off by default. Nothing changes for anyone who doesn't open it.

Not proposed: agents that move cards, a workflow engine, issue tracker sync (that is #30981), or custom columns.

Would a maintainer be OK with this as a small PR (web first)? If a board is not wanted at all, a "Needs you first" sort in the sidebar would cover most of it, and I can propose that instead.

[romanzdk]

To make this concrete I built a small working version in my fork. I have not opened a PR; I'm waiting to hear if a board is wanted at all.

Branch: https://github.com/romanzdk/t3code/tree/feature/thread-status-board (one commit on top of main, 9 files, +366 −3, web only)

What it is

• A read-only Board page at /board, opened from a sidebar button or the command palette ("Open thread board").
• Four columns taken from the status labels the sidebar already shows (resolveThreadStatusPill): Needs you (Pending Approval, Awaiting Input, Guest Request, Plan Ready, Failed), Working (Working, Connecting), Waiting, Done.
• A card shows title, project, the same status label and time. Click opens the thread.
• Settled, snoozed, archived and delegated threads are left out, like the sidebar. Done shows the newest 30.
• No new data, no server change, no new status model.

Before / after (generic demo projects and the free Replay provider, no real data)

Before: status is a label on each row of the list.

After: the same threads grouped by status. One thread asks a question, one is running, three are finished.

Checks

Check	Result
vp run check:changed (format, lint, knip, typecheck, tests)	pass
Test: each status label lands in the right column (8 cases)	pass
Web, by hand on a throwaway server: question thread, running thread, finished threads	each in its own column
Mobile	not done

Not in this version

• It shows all projects. It does not yet follow the sidebar's project filter, which is tied into a large part of Sidebar.tsx.
• Web and desktop only. No mobile, no user docs section.
• The Waiting column is empty in the screenshot because no demo thread was blocked on another thread.

Would a maintainer be OK with this as a small web-first PR?

Built with Claude Opus 5.5 in Claude Code.

[makhnatkin]

Proposal: threads as a board, a second view of the thread list

I'd like to add a new way to see threads: a board with columns by status (Needs you, Working, Waiting, Failed, Done). Today the status is a small label on each row, so to find the threads that wait for me I have to read the whole list. On a board, I just look at the column. You don't move cards by hand: each card's column comes from the status T3 Code already shows, so the board always matches the list. It is not a new page. It is the same sidebar, only wider: drag it past 560 px and the list turns into the board, drag it back and the list returns. Cards are the normal sidebar rows, and the open thread stays next to the board. An optional button next to New thread makes the sidebar 70% of the window wide. The board is off by default. The setting has three options: Off, On, and On with button.

How it looks

board-v2.mp4

How it differs from the existing versions

• feat(web): task board with threads grouped by status #34779: a separate /board page with its own cards and movable panels, +1797 lines. Here the board reuses the sidebar rows, +285 lines with a test and docs.
• The branch in this discussion: also a separate page, without the project filter, with Failed inside Needs you.
• In both, the board replaces the thread. Here the thread stays open next to it.

Ask

Would you consider this direction? The code passes vp run check:changed: main...makhnatkin:t3code:feat/board. If it fits, I can open a PR for review.

Built with Claude Code (Claude Opus 5.5).