Files
hyperframes/packages/studio/src/contexts
Miguel Angel Simon Sierra 18b3caa9dc feat(studio): answer the agent's question from the run tray
A run stopped on a question now shows what it is being asked and the
agent's own options, one button each; clicking one sends that option's id
and the run carries on. The element says so too, in amber and still,
where every working state moves: a run that has stopped must not look
like one getting on with it. Being waited on leads the tray's headline
and outranks working in the canvas badge, because it is the only state
the reader can do something about.

Three files had to come apart first, all of them over the editor's
600-line cap and so uncommittable as they stood:

- the canvas connector moves out of InlineAgentComposer into its own
  file, and the composer's geometry joins the layout module that already
  owned the rest of it (813 -> 551)
- the queue's mutations move out of useAskAgentModal into useAgentQueue,
  which is where answering belongs (653 -> 598)
- useDomEditSession listed all 34 agent fields twice, once to
  destructure and once to return; it spreads them instead (604 -> 540)

Polling also treated a parked run as idle, so an answer took up to eight
seconds to look like it had landed.
2026-08-05 22:39:55 -07:00
..