The helper's conversation, Ask or Repair, shows as a tab beside the subagents #424

Closed
opened 2026-11-08 03:10:13 -05:00 by cmoriarty · 1 comment
Owner

What happens. On run 182 the owner asked Ask a question during apply (braid#223). The answer landed in Repair's panel: the Repair button on the run bar lit up and the step's transcript was replaced by the helper's conversation, the way a stopped run's Repair is shown. Confusing: the operator used Ask, not Repair, and the run is live. And Repair's own panel is a mechanic of its own, unlike anything else on the stage.

Fix. One mechanic for every conversation that is not the step's own: the tab strip the subagents use (AgentTabs, beside Main agent and Subagents). The helper's conversation is a tab there, named Ask while the run is live and Repair once it is stopped or failed, shown as soon as the helper has a session or can be written to. Sending in Ask mode, or to Repair, opens that tab. The Repair button and panel on the run bar go; the tab is the way in, and the composer keeps deciding where a message goes by the run's state. The tab carries the same live stream and record the panel carried (repairDeltaKey, the run's repair record), and the spine's Repair entries keep linking to it.

Done when. On a seeded running run, a question sent in Ask mode shows its reply on an Ask tab of the step and no Repair button is shown; once the run is stopped, the same conversation is on a Repair tab, a message to Repair opens it, and the run bar has no Repair button. The journeys that opened Repair through the button are rewritten for the tab.

From run 182 (the owner, 2026-11-08: Ask first, then "perhaps the repair agent should also use the subagent visual ui mechanic as well, for consistency").

**What happens.** On run 182 the owner asked Ask a question during apply (braid#223). The answer landed in Repair's panel: the Repair button on the run bar lit up and the step's transcript was replaced by the helper's conversation, the way a stopped run's Repair is shown. Confusing: the operator used Ask, not Repair, and the run is live. And Repair's own panel is a mechanic of its own, unlike anything else on the stage. **Fix.** One mechanic for every conversation that is not the step's own: the tab strip the subagents use (`AgentTabs`, beside Main agent and Subagents). The helper's conversation is a tab there, named Ask while the run is live and Repair once it is stopped or failed, shown as soon as the helper has a session or can be written to. Sending in Ask mode, or to Repair, opens that tab. The Repair button and panel on the run bar go; the tab is the way in, and the composer keeps deciding where a message goes by the run's state. The tab carries the same live stream and record the panel carried (`repairDeltaKey`, the run's `repair` record), and the spine's Repair entries keep linking to it. **Done when.** On a seeded running run, a question sent in Ask mode shows its reply on an Ask tab of the step and no Repair button is shown; once the run is stopped, the same conversation is on a Repair tab, a message to Repair opens it, and the run bar has no Repair button. The journeys that opened Repair through the button are rewritten for the tab. From run 182 (the owner, 2026-11-08: Ask first, then "perhaps the repair agent should also use the subagent visual ui mechanic as well, for consistency").
cmoriarty changed title from Ask's conversation shows as a tab beside the subagents, not as Repair to The helper's conversation, Ask or Repair, shows as a tab beside the subagents 2026-11-08 03:10:35 -05:00
Author
Owner

Shipped in PR #437 (merged 6a8ee372), archived in PR #438 (helper-conversation-tab). The helper's conversation is a tab on the agent view's strip beside Main agent and Subagents: named Ask while the run is live, Repair once it is stopped or failed; there on every stopped or failed run, and on a live one once a question has been sent or a session exists; sending to the helper opens it, and it stays open while the reply is on its way. The Repair button is gone. On the tab the box is Ask (no switch, Send only) on a live run and Repair on a stopped one.

Evidence from the laptop: vitest ui/src/lib/repair.test.ts (the tab by state, the pending words), and two journeys in ui/e2e/ask.spec.ts: a question in Ask mode lands on a selected Ask tab with no switch and no Repair button, Main agent brings the switch back; a stopped run shows a Repair tab, no button, and a message to Repair selects it. ./tools/test.sh green.

**Shipped in PR #437 (merged 6a8ee372), archived in PR #438 (`helper-conversation-tab`).** The helper's conversation is a tab on the agent view's strip beside Main agent and Subagents: named Ask while the run is live, Repair once it is stopped or failed; there on every stopped or failed run, and on a live one once a question has been sent or a session exists; sending to the helper opens it, and it stays open while the reply is on its way. The Repair button is gone. On the tab the box is Ask (no switch, Send only) on a live run and Repair on a stopped one. Evidence from the laptop: vitest `ui/src/lib/repair.test.ts` (the tab by state, the pending words), and two journeys in `ui/e2e/ask.spec.ts`: a question in Ask mode lands on a selected Ask tab with no switch and no Repair button, Main agent brings the switch back; a stopped run shows a Repair tab, no button, and a message to Repair selects it. `./tools/test.sh` green.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid#424
No description provided.