Scout Threads
Stateful memory rooms for follow-ups from Daily Brief, WhatsApp, email, interests, and dispatches.
A Scout thread is where a brief item becomes a working conversation. It
lives at /dashboard/threads/[id], one per chat thread, and should be
anchored to something concrete — a dispatch, an
interest, a Daily Brief delivery, a source, or the
brief itself.
Daily Brief and WhatsApp are for fast reading. Threads are for depth and memory.
How you get into a Notebook
- Daily Brief item — opens a thread anchored to that brief item or its interest.
- WhatsApp handoff — long answers are written into a thread, with a short link sent back to WhatsApp.
- Ask scout on any dispatch — opens a thread anchored to that dispatch.
- Free-text cmd+k — typing a question into cmd+k (instead of a slash command) opens a fresh thread with that question as turn one.
- Direct navigation — clicking an existing thread in your history.
What's in a Notebook
- A streaming conversation — scout replies arrive token-by-token over SSE. No "thinking…" wait wall.
- A bottom composer for follow-ups.
- A memory rail showing the anchor, room type, next reply verbs, and
cited dispatches:
- ANCHOR — what this thread is about. The dispatch, interest, Daily Brief, source, or brief that scoped the conversation.
- CITED DISPATCHES — every dispatch the scout has referenced inline, listed for quick jumping back to the Wire.
- Inline tool-call action chips — when the scout takes an action mid-conversation (e.g. paused interest "anduril hiring"), a small chip appears in the transcript instead of plain text. Click through to undo or inspect.
What the scout can do in a thread
Beyond just answering, the scout can take actions on your behalf — tool calls that mutate state. Examples:
- Pausing or resuming an interest.
- Creating a new interest or tagging an existing one.
- Pulling fresh signals on a sub-topic.
- Generating a one-off PDF brief.
Every mutation surfaces as an inline tool-call chip; nothing happens silently.
Anchors, in detail
The anchor shapes the scout's context window:
| Anchor | What the scout sees |
|---|---|
| Dispatch | The full dispatch, its sources, and the run that produced it. |
| Interest | The interest's signals, recent runs, and recent dispatches. |
| Daily Brief / Delivery | The brief item, delivery context, and user's reply intent. |
| Source | The source and related dispatches or signals. |
| Brief | The whole brief and the recent Wire. |
A free-text cmd+k question that doesn't reference anything specific opens with the brief as its implicit anchor.
Threads vs Daily Brief vs Wire
| Surface | Use it when… |
|---|---|
| Daily Brief | You want the few things worth attention today. |
| WhatsApp / email | You want to reply in the channel where you work. |
| Scout thread | You want to follow up, correct, save, or dig deeper. |
| Wire | You want to scan the live feed of dispatches. |