Console: eight UI updates (runs page, spine labels, Visual check pane, run bar, settings, composer) #463
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?
Eight changes to the console, asked for by the owner on 2026-11-09. Mock the options for 2, 3, 4 and 7 before building.
1. Runs page: archive as well as delete
Now. "Select" on the Runs page lets you delete the runs you tick.
Fix. The same selection also offers Archive.
2. Spine: one label in line with the step, not a row under it
Now. A review or fix step gets a line under its name ("1 fixed", "round 1 green", "fail · 1 way of opening failed", "pass · 8 of 8"), in a green that is not the app's mint green, and they are ugly.
Fix. One element in line with the step's name:
agent.code-review): "fix requested >" in the yellow/orange Braid already uses. It is a button: it opens the agent pane with the review pane expanded.script.run-teststhat passed: its normal mint-green check and nothing else.script.run-teststhat failed: "test failed >" in red, looking like "fix requested >". There is no test pane to open.Every label under a step goes (owner, 2026-11-09): "1 fixed", "1 note", "round 1 green", "pass · 8 of 8", "fail · 1 way of opening failed". A step with a problem gets the one in-line label; a step with none shows its mint-green check and nothing more. A Visual check that failed is read here as "fix requested >", opening its report pane; confirm that in the mock.
3. Visual check pane: readable at a glance
Now. The pane works, but opens with a dense block of summary text, and each check's title is long. It uses the wrong green.
Fix. The pane is for people only: a short summary, each check's title shortened for a person, and the result of everything visible without reading paragraphs. Mint green.
4. Run bar: two rows, and one "Run Details" page
Now. The bar between the tab row and the graph/agent panes has the project and its cells on one line. Backend and Step details are two pages.
Fix. Row one: the project and the issue title, on the same line. Row two: every cell that is on that line today. The cells together are one link to a new page, "Run Details", which combines the backend page and the step details page.
A step's details live on Run Details (decided by the owner, 2026-11-09). The page knows which step is active and shows that step's details by default, following the run as it moves on, and lets the user choose another step to show.
5. Run bar: two cells go
Remove the Steps cell and the Context used cell. The context ring on a running step's row in the graph pane is the reading of context, and is enough (owner, 2026-11-09).
6. Run bar: two buttons go
Remove the "End Run" and "Step Details" buttons.
Stopping the whole run moves to the Run Details page (4), as "Stop run" (decided by the owner, 2026-11-09). It does what End run does today: it stops the current step, cancels the steps left, loses nothing finished, and the run can be resumed. The keyboard command stays. The composer's Stop (8) still interrupts only the agent's current turn.
7. Settings: all on one page
Now. Settings take far more room than they need.
Fix. A denser style for the controls so every setting fits on one page, laid out by good UX practice: intuitive, and visually balanced.
8. Composer: Stop is a square icon, at the far right
Now. The composer's buttons read "■ Stop" then "Send", with Send at the far right.
Fix. Stop is a square icon with no word, and swaps places with Send: Stop is all the way to the right. It keeps its hover text and its name for a screen reader.
Done when
Each of the eight is in the console and checked in a real browser, with a browser test for 1, 2, 4, 5, 6 and 8, and all settings visible on one page at a laptop's window size.
Console: seven UI updates (runs page, spine labels, Visual check pane, run bar, settings)to Console: eight UI updates (runs page, spine labels, Visual check pane, run bar, settings, composer)Shipped in PR 464, archived in PR 465; production runs
1c4dd26.Sstill asksEvidence from the laptop. Browser tests for each item (48 in all pass), console unit tests (114) and the Python suite (645). Looked at in a real browser on fixture runs; the owner reviewed screenshots and asked for Status first and Stop run under Redo, both in.
Decided while building, for the record: bulk Archive keeps files; a Visual check that failed reads "fix requested ›";
dopens Run details on the selected step; about fifteen other components still use the older green for "succeeded".