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

Closed
opened 2026-11-04 13:09:12 -05:00 by cmoriarty · 1 comment
Owner

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 says STATUS ● Running and SERVICES ●●● 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

  1. The project's name, in full.
  2. The run's settings (pipeline, mode, context window) — readable, not an ellipsis.
  3. The backend this run uses and its state in one place: 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.
  4. The ticket's full title.
  5. The run's total elapsed time: only the time it was actually running. A run that stopped and was started again does not count the time in between.

Functionality

  1. Stop run vs Stop. They are different things today: the bar's Stop run calls POST /runs/{id}/stop (stops what is running, cancels the rest, keeps the work; #9, #51); the composer's Stop calls POST /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.
  2. The phase stepper (Setup → Explore → … → Merge & archive) becomes a setting, off by default.
  3. Subagents as tabs on the coding pane, not a popup. The 1 subagent button'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.
  4. The Services box shows three unnamed dots. Replace it with a box titled Braid that shows Braid's version and one light for the connection to the Braid server. (No version is shown anywhere in the UI today.)

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).

**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 says `STATUS ● Running` and `SERVICES ●●●` 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** 1. The project's name, in full. 2. The run's settings (pipeline, mode, context window) — readable, not an ellipsis. 3. The backend this run uses and its state in one place: `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. 4. The ticket's full title. 5. The run's total elapsed time: only the time it was actually running. A run that stopped and was started again does not count the time in between. **Functionality** 1. **Stop run vs Stop.** They are different things today: the bar's *Stop run* calls `POST /runs/{id}/stop` (stops what is running, cancels the rest, keeps the work; #9, #51); the composer's *Stop* calls `POST /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. 2. **The phase stepper** (Setup → Explore → … → Merge & archive) becomes a setting, off by default. 3. **Subagents as tabs on the coding pane, not a popup.** The `1 subagent` button'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. 4. **The Services box** shows three unnamed dots. Replace it with a box titled *Braid* that shows Braid's version and one light for the connection to the Braid server. (No version is shown anywhere in the UI today.) **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)._
Author
Owner

Shipped in #380 and deployed to production.

  • Run bar: one strip of captioned cells: Project, Pipeline, Mode, Context used, Backend, Model, Phase, Steps, Time, Status. As the window narrows, whole cells give way to the Project cell's hover. Status holds the only running light, and Time counts only the time the run was running.
  • Top bar: a Braid box with the version and one connection light.
  • Stops: the bar's stop is End run, and the composer's button stays Stop.
  • Stepper: a setting, off by default.
  • Subagents: a persistent tab that shares the composer.

Evidence: ./tools/test.sh passes 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.

Shipped in #380 and deployed to production. - **Run bar:** one strip of captioned cells: Project, Pipeline, Mode, Context used, Backend, Model, Phase, Steps, Time, Status. As the window narrows, whole cells give way to the Project cell's hover. Status holds the only running light, and Time counts only the time the run was running. - **Top bar:** a Braid box with the version and one connection light. - **Stops:** the bar's stop is End run, and the composer's button stays Stop. - **Stepper:** a setting, off by default. - **Subagents:** a persistent tab that shares the composer. **Evidence:** `./tools/test.sh` passes 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.
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#377
No description provided.