Skip to content

See every step: streaming and the Trajectory tab

Why this page exists

Two things became true at once: replies can appear while they are still being written, and every step Maggie took to produce a reply is now recorded and readable back. Together they answer the question "what actually happened in that conversation?" — as it happened, and afterwards. This page explains both, what the record shows, and who can see which part of it.

Answers arrive as they are written

When you send a message, the reply does not wait to be finished before it appears. The first words show up almost immediately and the rest arrive as Maggie produces them, so you are reading rather than watching a spinner.

There is one honest exception. Some answers depend on work Maggie has to do first — looking something up, running a tool, checking a file. When a turn needs that work, the visible reply cannot begin until the work returns its result, because the answer is built from it. In those turns you will see the step being taken, then the reply that follows from it. A turn that only needs what Maggie already knows streams immediately.

The Trajectory tab

Open any conversation and you will find two ways to look at it: Chat, the back-and-forth you already know, and Trajectory, a read-only record of the work behind it. The Trajectory view is where you go to see how an answer was reached rather than only what was said.

At the top of the Trajectory view are three summary figures for the whole conversation:

  • Duration — how long the recorded work took, end to end.
  • Turns — how many exchanges are in the conversation.
  • Calls — how many model calls the work used, with an estimated cost and the number of tokens read and written across them.

Below the summary is a timeline with a lane for each turn, so you can see where the time and the calls went. You can switch the timeline between three lenses — Duration, Turns, or Calls — to ask a different question of the same record. Selecting a turn opens an inspector panel beside the timeline.

What a single step shows

When you select a step, the inspector offers four readings of it:

  • Summary — the plain description of what the step did.
  • Preview — the content of the step, shortened for reading.
  • Raw — the step exactly as it was recorded.
  • Source — where the step's content came from, when that is known.

The record is a faithful copy of what happened; it is never rewritten or tidied after the fact. That is the point of it.

Who sees what

The Trajectory view honours your organisation's roles. Administrators can open every reading of a step, including Raw and Source. Members see the summary view. When a reading is not available to you, the panel says so plainly rather than showing an empty or invented one — the view never fills a gap it cannot see.

Where it lives, and when it is on

The Trajectory tab appears in every conversation. Its content depends on turn recording being switched on for your environment: where it is on, each conversation shows its recorded steps, and where it is not yet on, the view says so honestly instead of pretending the conversation had no steps. Recording is rolled out environment by environment.

What it is not

The Trajectory view is a record, not a control. It does not change anything, it does not re-run work, and it is not where you approve or decline an action — those live on the surfaces where the action is proposed. Read it to understand a result, then act where you normally would.