Chat: the board and mentions
Every message runs as a plan on the board: the agent draws its steps as cards, runs independent steps together and reports in the thread. Read this to follow a run, steer it with @, add requests while it works, or stop it.
Steps
- Send a message. The Plan tab is open by default; cards replace the hint "Your plan will appear here as the agent works." and the board follows the running card.
- Click a card to open its inspector. When a card asks for your decision, act on the card (Files, previews and approvals).
- Type @ to instruct a step, an agent, a file or a teammate, and keep sending while the run works.
- Click Stop in the composer to cancel the run.
The right pane
Four tabs: Plan, Files, Preview and AMPG (Augmented Multi Resolution Property Graph, the knowledge graph). Plan, Files and AMPG carry a count badge. The open tab, file, scope and step are written into the address (#pane=plan), so a refresh or a pasted link restores them.
Read the board
Cards sit in columns in dependency order, left to right; steps that can run together stack in one column. Solid lines are flow, dashed lines are invariants, and a conditional step's lines carry their branch label. The toolbar has Zoom to fit and Follow running (on by default; it re-centres on the running card after four seconds of quiet and switches off when you pan or zoom). Drag cards to rearrange them; positions are saved with the conversation. Right-click a card for Open thread and Copy @slug.
Each card carries a status pill: Pending (waiting for the steps it depends on), Running (with a live timer), Done, Needs re-run (its inputs changed after it ran), Blocked (the reason is under the title), Awaiting review, Awaiting go-ahead or Wants to run a command (waiting for you: work held for review, a step that will not start until approved, or a flagged command), Failed (the error is under the title), Cancelled, Skipped (faded; an untaken branch reads "branch 'name' not taken") and Unknown (a state this Studio version does not recognise). When an upstream change leaves cards stale, a banner reads "N node(s) need re-running." with Re-run stale. Several cards can be Running or Awaiting you at once.
Look inside a step
Click a card (or press Enter or Space on it). The inspector shows the handle, status, title and objective, then Thread (the step's reasoning and narration), Tool Calls (one card per web search, connector query, grounding lookup or code run, with Inputs and Outputs), Governor and Evidence (citations, web sources, datasets, deliverables and AMPG retrievals; click one to open it in Preview). Code runs are the work of the coder, the part of the agent that writes and runs code; approval asks and Send back notes address it. A decided step lists "Decisions on this step". The address is #pane=plan&node= plus the handle. A card the Governor commented on carries a badge; click it for a popover, "Governor on" plus the handle, with lines labelled ACTIVATED, VERDICT, NOTE, STEER, GROUNDING REQUESTED, BUDGET EXHAUSTED and PROCEEDING.
Mention with @
Type @ at the start of a word. The picker opens above the composer, prefix matches first, grouped as Nodes, Agents, Files and Team; each row shows the handle, its kind and a detail such as the step's status. Up and Down move, Enter or Tab inserts, Escape closes; eight rows show at a time.
| Handle | At the start of a message | Mid-sentence |
|---|---|---|
A step, for example @extract | Instructs it: Pending gets a new objective, Running is steered, Done re-runs in a sub-thread (its dependants read Needs re-run), Failed or Cancelled re-runs from where it stopped, Blocked explains itself. | Attaches the step's output as context; nothing re-runs. |
| An active agent (supervisors are not offered) | Brings it in: the coordinator adds a step for it. | A reference. |
A file by its path from the conversation's folder (@outputs/memo.pdf) or its full project path; a folder ends with / | Attaches its content for the turn. | Attaches the file, or a short folder listing. |
@coder or @governor | Sends your message to that teammate. | A reference. |
In replies a step's handle renders as a chip; click it to select the card and open its inspector.
Keep asking while it works
While a run is active the composer shows "A run is in progress": anything you send is read at the coordinator's next update, the run continues if you close the tab, and Stop cancels it. Send as many follow-ups as you like, or several requests in one; the notice grows a pill, "N waiting to be read". At its next update the coordinator reads everything waiting, adjusts the plan and answers in an Update turn; your messages then read "Read" with the time (the timeline). A conversation runs one turn at a time: messages still waiting when a turn ends are re-submitted one by one, in order, including after Stop; click Stop again if you do not want them.
Stop, leave and reconnect
Stop has no confirmation. Studio asks the runtime to cancel and keeps asking for up to two minutes; the thread gains "Plan stopped by user." and unfinished cards read Cancelled. Files already written stay. Runs execute on the server: leaving, closing the tab or losing your connection does not stop one, and Studio shows no prompt when you leave; on return the board and each step's tabs are rebuilt from the run's record. If the live stream drops, a "Reconnecting…" pill appears after two seconds; Studio retries with waits growing to 15 seconds and gives up after five minutes. While cards await a decision the board re-reads about every ten seconds, so an Inbox decision shows here.
Notes
- Every message is a board run; there is no mode to choose. A request too large for one chat run does not start ("This request needs a larger plan than a chat run can take on at once"): narrow it, split it across chats, or build a workflow.
- The board draws the current run; earlier turns are summarised in the thread. Stop cancels the whole run, not one step.
- Only the first handle instructs, and only when the message starts with it; to refer to a Done step without re-running it, mention it mid-sentence. The Team group offers no rows in this release; type
@coderor@governor. - "The action did not go through.": try again, then reload. "The run accepted the message but did not say how it was queued.": resend when the turn ends. "Reconnecting…" for minutes: reload when your connection is back; the run continued.