Feature proposal: add a Board view for simultaneous live chats

[beejsbj]

Add a Board view for simultaneous live chats

Feature

Add a Board view to the web and desktop clients where users can keep several agent conversations visible and usable at the same time.

The defining unit is an existing T3 Code thread rendered as a compact live chat card. Each card shows the conversation timeline and its composer, so the user can read progress and send a follow-up without leaving the board. Opening the card full-screen returns to the same canonical thread; the board does not create a parallel task or conversation model.

First version

• A Board item in the sidebar and a /board route.
• Compact live chat cards for active threads across connected environments.
• The existing conversation timeline in each visible card, including loading older turns.
• A usable composer that sends to that card's existing thread.
• In-card approval responses; structured input questionnaires can open in the full thread.
• Project, environment, branch, model, and runtime-status context.
• Viewport-aware mounting. Unseen chats stay cheap; focused, drafted, sending, or manually scrolled chats remain mounted until their state is safe to release.
• Responsive behavior for the web client and desktop wrapper.
• A way to open any card as its canonical full thread.

This is a new spatial view over T3 Code's existing threads. Thread history, turns, provider sessions, and lifecycle remain owned by the current server and client-runtime contracts.

Scope

The first PR does not include custom lanes, drag-and-drop organization, persistent placement, manual card resizing, board draft cards, agent/CLI control, or a native mobile screen. Those are separately reviewable follow-ups.

The timeline and composer are not follow-ups: without them, this becomes a session dashboard rather than a board of chats.

Why

T3 Code users often supervise and steer several agents at once. The sidebar makes switching possible, but switching still hides every other conversation. Board view lets the user scan several live threads, notice which one changed, and reply in place while preserving each thread as the durable unit of work.

The implementation uses an explicit embedded-conversation surface built from the existing timeline and composer primitives. Mounting several full ChatView workspace controllers would duplicate global shortcut, panel, preview, terminal, and worker ownership, so the board shares the thread-level UI without cloning the page controller.

Current first PR

Desktop web view:

Responsive narrow web view:

Full direction

The fork demonstrates the larger direction through linked follow-up PRs: flexible card sizing, client-local lanes and placement, draft cards, spatial keyboard navigation, and optional agent control.

Full-fork overview:

Flexible sizing direction:

Questions

1. Does a Board of simultaneous live chats fit T3 Code's direction?
2. Is a dedicated embedded timeline/composer surface the right seam for the first implementation?
3. Is web/desktop an acceptable initial surface before a native mobile version?

[t3dotgg]

Note

🤖 GPT-6.1 Terra [1m] responding on behalf of Theo

Closing in line with the decision on the linked implementation. This live-chat Board design is not proceeding in its submitted form. #9046 #9046 comment