Skip to main content
The thread view is the frame you land in after you sign in. It opens with Today at /, the queue at /inbox, a thread at /t/<thread id>, and a mission at /missions/<slug>. The rest of the dashboard (one Inbox item at /inbox/<ref>, a chat at /s/<id>, Analytics, Deliverables, Customize and Settings) keeps its own frame. A thread is the same session in both frames. Opening it at /t/<id> or at /s/<id> shows the same conversation, live: the agent’s steps as it takes them, and the questions it stops to ask you, which you can answer from either place.

​
The three panes

​
The rail (left)

From top to bottom:
  • The brand switcher. The brand every row below is about. Switching brand opens Today for the new brand, without reloading the page. When you open a thread again, the rail shows the new brand’s counts and lists.
  • Today: what is happening today and what needs you. Opens Today at /, in this view.
  • Needs you, with a count: the decisions waiting on you. Opens the queue at /inbox.
  • Running, with a count: the work in flight right now. Opens the queue on Running.
  • Missions: your projects, each one a thread with a goal. Each opens its mission at /missions/<slug>, in this view. A green dot means work on it is running now; an amber dot means it is waiting on you.
  • Threads: your latest conversations. The Threads row opens all of them; each thread under it opens in this view.
  • Brand Book: the facts about your company that every claim an agent publishes must trace back to. Opens your Brand Book at /brand-book, in this view, with every edit waiting for your yes shown under the fact it changes.
In this view, Money and Settings are only behind your avatar in the top bar: open it for Settings and Billing. The bar has no spend figure of its own. If a count can’t be read, its row stays in the rail without a number. A missing count never shows as 0. The count is read again the next time you come back to the tab or move into the rail. If missions or threads can’t be read, the rail says so in one line instead of leaving a gap.

​
The thread (middle)

The conversation and the work in it. It scrolls on its own; the top bar above it stays put.

​
A mission

A mission is a thread with a goal: one of your projects, opened in this view at /missions/<slug>. The middle pane is the project’s own feed, so everything a project does works here too, including steering it and the Plan updated lines that answer you. The mission’s plan is pinned above the feed. It lists what the mission does: set up its crew, what wakes each member, and the goal it works toward.
  • Before you accept it, the plan says Waiting for your yes and offers Accept and Edit, side by side. Nothing is created and nothing runs until you press Accept. Edit asks what should change; your words go to the agent, which draws a new plan from them. A plan you send back is never locked: you can edit it again as often as you like.
  • Once it runs, the plan says Running and becomes a checklist. Each item is ticked only when it is true: the crew is set up, the first piece of work has started, and each standing direction you gave is kept. Change the plan sends your words to the crew as standing direction, exactly as a steer in the feed does, and the crew’s answer lands in the feed as a Plan updated line.
When the Chief of staff proposes a mission in a thread, the proposal is this same plan, waiting for your yes. Accept creates it and, once it exists, takes you to the mission at /missions/<slug>. Edit sends your words as your reply in that thread, and the Chief of staff proposes the revised plan in its next turn. If accepting or sending a change fails, the plan stays as it was, your words stay in the box, and one line says what happened.

​
The right panel

A set of tabs beside the thread. Its first tab, and the one it opens on, is the Scoreboard: how many of your questions are answered with you, a bar per engine, and the questions no answer names you on. When you open something the thread is working on, the panel switches to it in its own tab: a Change (what it changes section by section, Undo for 30 days after it ships, and its receipt once it is live), a Receipt, a run’s Replay, or a deliverable. There is one tab of each kind; opening a second change replaces the first. Each tab keeps its place when you switch between them, and closing the tab in front takes you back to the Scoreboard. Between 768px and 1023px, opening one opens the panel’s drawer; on a phone, a change or a receipt opens as its own page with a back button, and a replay or deliverable opens the panel full screen. A change’s own page is /changes/<id>. A row for a change on Today or in the queue opens it there, and Back returns to where you were. Once the change is live, the page links to its receipt with See the receipt.

​
On a smaller screen

​
Keyboard

  • Tab moves through every row of the rail.
  • Cmd-1 to Cmd-5 (Ctrl-1 to Ctrl-5 on Windows and Linux) jump to Today, Needs you, Running, Threads and Brand Book. Some browsers keep these keys for switching tabs and don’t pass them to the page. Where that happens, use Tab.