Settings: another design pass, with one row style, less text and tabs considered (research first) #475
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 last pass (#463, item 7) fit every setting on one page, and it reads as messy and unprofessional:
What we want
A style that is compact by design, not by shrinking. One screen is no longer the goal; a clean, consistent, professional page is.
Done when
Where to look:
ui/src/components/Settings.tsx,openspec/specs/settings/spec.md,ui/e2e/console.spec.ts.From the owner's review of the one-page settings, 2026-11-10.
Research: how well-made apps lay out dense settings
Read first-hand: Apple, Microsoft, JetBrains, IBM Carbon, GitHub Primer and NN/g (links below). They agree on more than they differ.
Also: JetBrains tab rules (1–3 word labels, no "General" or "Advanced", most used first, never hide a tab, say why in its body); Apple: fewer settings, reopen on the last pane; Microsoft: keep rarely used settings behind an expander, and say in the row why a control is disabled.
What this means here. Panes of about ten rows that each fit a laptop window; the backend named once, not on four cards; the per-step thinking levels behind a disclosure; and Save stays, since Braid validates a save as a whole. Settings that move each other stay together: the model window, output reservation and context per agent (the ceiling), and parallel sessions with the run and subagent limits.
Next: three options with the real settings, as screenshots of the real console.
Sources: Apple · Microsoft · JetBrains groups, tabs, layout, help text, checkbox · Carbon forms, form · Primer forms · NN/g tabs, toggles
Three layouts to pick from
Screenshots of the real console on fixture data, at 1280×800. All three use the same new row, so only the way the panes are held differs. Click an image for full size.
Now
A. Tabs (my pick). Backend · Model · Runs · Display, one row of tabs, each pane fits the window with room to spare. Model and Runs belong to the backend chosen in the selector at their top, which replaces "Kept with …" on four cards. Display is the console's, so it has none. A tab with an unsaved change or an error will get a dot (not drawn yet), and each pane has its own address,
#/settings/runs.B. Side list. The same four panes as a list on the left (Runs shown). It costs 9 rem of width for four items, and earns its place past about eight sections.
C. One column. Everything in a single scrolling column under a bar of jump links. It is more than two screens long, which is the opposite of compact.
What changed in every option
Which one? Reply here, or tell me in the session.
Decision (owner): the one column, with a search.
Option C is the layout: one scrolling column, which also reads well on a phone. The bar of jump links goes, and a search box takes its place: it shows the settings that match what is typed, as it is typed, and the sections that have none drop out.
Building it now, in a worktree, with the proposal first:
/jumps to itShipped in #478, archived in #479.
The settings page is one column of one-shape rows, the owner's choice of the three layouts mocked above.
Kept with …is gone.Evidence, from the laptop
./tools/test.shpassed in 47 s, 52 browser journeys among them. The new search journey cannot pass on the old page, which has no search box, and it also asks for every setting by its own name. A phone journey replaces the one that held every setting in a laptop window, whose rule ("Every setting is on one page") the settings spec no longer has.The research is the first comment above, and the owner's pick of the layout the third.