Goal & plan
What Optimus is holding onto
A strip inside the top of the composer frame: the durable goal with its elapsed timer and pause/clear controls, and the plan as a step ticker. Both rows expand — the goal to full text, the plan to the whole ordered list.
status: active — emerald pulse, pause + clearstatus: paused — resume replaces pauseNo goal set — the plan ticker stands aloneQueued direction — pause flushes rather than pausesAsk user
When Optimus stops to ask
A question set is answered one step at a time, so a five-question interview reads as a sequence instead of a wall of form. Once answered it collapses into a one-line record so the reply that follows still has a visible cause.
Which shaping approach should the promoted variant use?
single → multi → text, steppedCollapsed by default; click for the full exchangeDirection & errors
Steering and failure
Mid-run direction shows its own lifecycle under the transcript — steering, steered, queued, delivered, failed. A missing provider or a billing stop is a setup step rather than a failure, so it reads amber and ships with the action that resolves it.
Last three only; steer is amber, follow-up is neutralOptimus needs a model provider before it can answer. Connect one and send your message again.
Connect a providerchatRecoveryKind → providerAnything else — red, verbatim