Thread

Thread shells for empty states, mapped transcripts, and toolbars.

ChatView owns the thread surface while routes decide how to provide toolbars, composers, and custom-part rendering.

Empty state

Title, description, suggestions, and composer can all be provided without any messages.

Start a thread

A route can pair the empty state with its own prompt suggestions.

Start a new conversation

Choose a suggestion or type your own prompt below.

Summarise this brief and leave a handoff note.Render a task card for the current run.Show an embedded custom status card.

Mapped transcript

Text, markdown, attachments, task cards, and custom parts can all coexist in the same thread.

Agent thread

A mapped message array stays small and stable even as the app adds custom UI.

Thinking

Pulling out dependencies first so the summary reads like an operating note, not a transcript.

What matters

The call surfaced three real blockers: access to the data export, unclear owner for QA sign-off, and a missing dry-run date.

Next step Owner Why it matters
Confirm export shape Platform Blocks the rest of the migration prep.
Lock QA sign-off owner Ops Prevents late ambiguity before launch.
Schedule the dry run Delivery Gives the team one rehearsal before cutover.

Wrap that into a task card and call out the highest-risk dependency.

Task board sketch task-board.png
Running
High risk

Status card

Migration tracker

The export contract still needs a committed owner.

This is the dependency most likely to block downstream planning, because every other task assumes a stable data shape.

Started 11 minutes ago

Owner locked, dry run pending

Risk

Export format

ETA

2 days

The card stays inside the thread, so the user can move from chat copy to structured status without switching surfaces.

Embedded card 81%
Extension hook
The route can inject richer status UI without changing the library renderer.

Finalising the owner handoff

Mapped transcript
Rendered task card
Prepared custom summary