Docs / Threads

Threads

A thread is a conversation with your team about one thing. You say what you need, the Lead answers, and the work it starts appears right there in the thread until it ships. Each project can have as many threads as you like.

Starting a thread

Press ⌘N or choose New thread in the sidebar. An empty thread puts the composer in the middle of the window with three suggestions taken from your project, such as a pending idea, a failing check or something from the README.

After the first exchange, the Lead names the thread in a few words. You can rename it any time from the thread's menu.

The sidebar groups threads into Pinned, Live and Earlier. The dot beside each thread tells you its state at a glance:

DotMeaning
Indigo, breathingWork is running
SaffronSomething needs you
GreenShipped
RedSomething failed
GreyIdle

The composer

Write the way you'd brief a colleague. Enter sends and Shift+Enter adds a new line.

  • @mention a teammate to send the ask to them directly.
  • Attach files or screenshots by dropping or pasting them in.
  • Dictate with the microphone button.

Three small pills sit under the field and apply to the message you're about to send:

PillWhat it does
Plan firstThe team writes a plan and waits for your approval before building, even for small asks.
Ship when readySkips the ship approval for this ask, so it goes out as soon as the checks pass.
Fast / Balanced / ThoroughThe model profile for this ask. Fast is cheapest; Thorough uses the strongest models and more review.

How the Lead answers

The Lead reads your message with the rest of the thread and a short summary of the project's work. Then it does one of three things:

  • answers you directly, when the ask is a question;
  • asks a quick question back, when something important is unclear;
  • starts work, sizing it and writing acceptance criteria as it goes.

Because the Lead triages in the conversation, there's no separate triage run for asks it starts from chat. Up to two threads in a project can get replies at the same time.

Work blocks

Work the Lead starts shows up as a work block right after your message. Collapsed, it shows:

  • the task key and title, such as PAIR-16 Streak freeze for missed days;
  • a status phrase: "Working for 34m", "Waiting for PAIR-14", "Usage limit, resumes 3:40 PM";
  • the stitch: a five-stage line for triage, plan, build, verify and ship. Finished stages are solid, the current one moves, and the rest are dashed.

Click the block to expand it. Each step gets a row with the teammate, what they did, how long it took and the tokens it used, plus links to the full task page, the diff and the transcript.

If a work block isn't moving, its status phrase says why. Troubleshooting lists every reason and what to do about it.

Decisions in the thread

When a task needs your approval or an answer, a decision card with a saffron edge appears in the thread. Its main action (Ship it, Approve plan or Answer) is on ⌘↵; you can also Send back with a note or View changes first. See Approvals and decisions.

Results

When a task ships, the Lead posts a result: a one-line outcome, chips for the pull request, the release tag and the deploy's health, and an "Edited N files" card that opens the diff.

All work and the task page

All work in the sidebar lists every task in the project, as a list or as a kanban board. Filter it by status, thread or teammate. Tasks from before 3.0 that weren't linked to a conversation show here, under "Earlier work".

Click any task to open its page: the full stitch, the plan, every step, the diff, the transcripts, verification, the ship record, and the tokens and cost. If it's waiting, the page shows why with a button to fix it: Retry, Unblock or Raise limit.

The inspector

Press ⌘I to show the inspector on the right. In a thread it shows the project card (changes today, shipped this week, tokens today with a 14-day trend), who's working right now and what they're doing, and the sources for the thread: the repo, pull requests and the deploy URL. On a task page it shows that task's details. The inspector hides itself on narrow windows.

Something unclear or out of date? Email [email protected].