Run bar redesign: one running light, full names, Stop run vs Stop, stepper as a setting, subagents as a tab, a Braid box in place of Services #377
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happens
The run bar (
RunBar.tsx) and the top bar (BackendPanel.tsx) together are too noisy, and the things a person looks for are hard to find. On run 172 the row reads:scratch-vllm-m… / thorough · auto: one step (226k conte… / #172 # Build "Scratch" — a multiplay… ● Running ● vLLM · qwen3.8-27b 1/6 5h 22m [1 subagent] [Step details] [Stop run], under a top bar that saysSTATUS ● RunningandSERVICES ●●●with no names.Two "Running" lights are on screen at once (the top bar's, for Braid, and the run bar's, for the run), and the project name, the run's settings and the ticket's title are all truncated.
Redesign: what the bar must show, in this order
vLLM · qwen3.8-27b · running · 70 t/s. One "running" light, on the run bar, not on the top tab bar: since braid#305 backends belong to runs, and the bar should look like it.Functionality
POST /runs/{id}/stop(stops what is running, cancels the rest, keeps the work; #9, #51); the composer's Stop callsPOST /steps/{id}/interrupt(aborts the agent's current turn, the session stays usable, Esc). Keep both, but name them so the difference is plain: e.g. Stop this turn in the composer and End run on the bar, with the bar's one confirming since it cancels the rest.1 subagentbutton's panel (SubagentsPanel.tsx) works but has no composer: a person cannot talk to a subagent from it. Proposal: one persistent Subagents tab beside the step's main agent on the coding pane. It expands to a list of that step's subagents, each marked active or ended and labelled as a subagent; picking one shows its transcript with the shared composer; the main agent's tab is always one click back. One persistent tab (not a tab per subagent) so many subagents do not crowd the strip, and closing it or switching back never loses them.Done when
The run bar shows the five items above in full with a single running light; Stop run and Stop have names that say what they do; the stepper is a setting, off by default; subagents are reached through a persistent tab on the coding pane with the composer; the top-bar box says
Braid <version>with one connection light.Observed on run 172, 2026-11-04 (screenshot attached in the session); related: braid#305 (backends per run), braid#324 (services box), braid#375 (coding pane ordering).
Shipped in #380 and deployed to production.
Evidence:
./tools/test.shpasses locally, including journeys for the strip narrowing, Context used, the elapsed time and the offline light. I also checked the bar in a browser with seeded data, at widths from 390 to 1920.Not verified: messaging a subagent has only run against the fake client, not a real opencode, so the first real use is its first real test.