Settings: one backend row with a selector and Delete, explanations in the hovers, and auto-approve per run #187

Closed
opened 2026-10-17 11:31:35 -04:00 by cmoriarty · 1 comment
Owner

The operator's review of the Settings page on 2026-10-17.

  1. Backends. Every backend added is pinned as a row of its own, which will not scale. Show one row, the backend runs use, as a selector that lists the others and switches between them. Deleting a backend must be easy: the selected backend gets a Delete that works, and one that cannot be deleted (the one runs use, the Free profile) says why instead of being greyed out.
  2. Reasoning effort. The per-step list under the field (high: openspec.explore, … low: agent.summarize, medium: every other step) moves into the field's ⓘ hover.
  3. Context per agent. "Hands off at 67,500, stops at 90,000 · ceiling 492,288" moves into the hover, and says "Compacts at …" now that every step compacts in place (#186).
  4. Fix rounds per run. The field shows "Unlimited" as its placeholder and "default: null" under it. Drop the "default: null" line; the hover says "default: unlimited".
  5. Apply the change. Too much small text: each choice's explanation goes into a hover, with a short phrase of when it is good: one step "Good when context is abundant", group by group "Good when context is scarce", side by side "Good when trying to speed up development". This field is being rewritten for the Auto mode (one step at 200k of context or more, else group by group; #172 follow-up), so it lands with that.
  6. Auto-approve, per run. Today it is one global switch, and the run page's button flips that same switch, so turning it on from one run's page answers open gates in every run. Decided: auto-approve is a run setting like the others. Settings sets the default for new runs ("Approve gates automatically in new runs"), the New Run form shows it pre-filled, and the run page's switch changes that run only. Runs already going keep what they started with. Its hover says it in one line: "When on, a run merges and archives without waiting for you."

Done when

  • Each of the six is in, with vitest and Playwright checks (the selector switching and deleting a backend; the hovers holding the moved text; a run's switch leaving another run's gates alone; the New Run form's default).
  • Checked in a real browser on production after the deploy.
The operator's review of the Settings page on 2026-10-17. 1. **Backends.** Every backend added is pinned as a row of its own, which will not scale. Show one row, the backend runs use, as a selector that lists the others and switches between them. Deleting a backend must be easy: the selected backend gets a Delete that works, and one that cannot be deleted (the one runs use, the Free profile) says why instead of being greyed out. 2. **Reasoning effort.** The per-step list under the field (high: openspec.explore, … low: agent.summarize, medium: every other step) moves into the field's ⓘ hover. 3. **Context per agent.** "Hands off at 67,500, stops at 90,000 · ceiling 492,288" moves into the hover, and says "Compacts at …" now that every step compacts in place (#186). 4. **Fix rounds per run.** The field shows "Unlimited" as its placeholder and "default: null" under it. Drop the "default: null" line; the hover says "default: unlimited". 5. **Apply the change.** Too much small text: each choice's explanation goes into a hover, with a short phrase of when it is good: one step "Good when context is abundant", group by group "Good when context is scarce", side by side "Good when trying to speed up development". This field is being rewritten for the Auto mode (one step at 200k of context or more, else group by group; #172 follow-up), so it lands with that. 6. **Auto-approve, per run.** Today it is one global switch, and the run page's button flips that same switch, so turning it on from one run's page answers open gates in every run. Decided: auto-approve is a run setting like the others. Settings sets the default for new runs ("Approve gates automatically in new runs"), the New Run form shows it pre-filled, and the run page's switch changes that run only. Runs already going keep what they started with. Its hover says it in one line: "When on, a run merges and archives without waiting for you." ## Done when - Each of the six is in, with vitest and Playwright checks (the selector switching and deleting a backend; the hovers holding the moved text; a run's switch leaving another run's gates alone; the New Run form's default). - Checked in a real browser on production after the deploy.
Author
Owner

Shipped in fdd6c70, live since 23:28Z on 2026-10-17 with migration 17 (backed up first), and archived in OpenSpec as settings-page-tidy in 874eb27.

What shipped

  1. One Backend row (39d5f63). "Backend runs use" is a selector with Add a backend and Duplicate. Delete removes the chosen backend after Save. Where it can't, a sentence in its place says why: "Runs use this backend. Choose another for runs and save, then delete it."

  2. Hovers (39d5f63). Each of these moved into its field's ⓘ: reasoning effort's per-step map, "Compacts at …, stops at … · ceiling …", "default: unlimited", and each apply choice's text.

  3. Auto-approve per run:

    • each run keeps its own auto-approve (d9f2ad4);
    • POST /api/runs takes it, and POST /api/runs/{id}/auto-approve switches one run (a0edab2);
    • the engine answers that run's gates only, and an answered gate is not emailed (86c0b7d);
    • the spine's switch, the labels and New Run follow the run (53b3a13).

    Settings' checkbox reads "Approve gates automatically in new runs" and sets the default for new runs.

  4. After review:

    • Settings follows runs as they start and end, so Delete comes back once a backend's runs end (8d6a25f);
    • a run detail read that began before a switch keeps the switch (c44fffc);
    • opening Settings shares a read already in flight (e7028de).

Runs from before the deploy. Migration 17 turns a run's own auto-approve on only when the run was created under the switch and the switch was still on at the upgrade. On production, runs 55 to 65 read on and runs 66 to 74 read off. Run 75 was created after the deploy.

Checked on production (fdd6c70, in a real browser):

  • Settings has one "Backend runs use" selector with Add a backend and Duplicate, and the in-use sentence where Delete would be. "default: null" and "Hands off" are gone. The Approvals checkbox reads "Approve gates automatically in new runs".
  • Run 75 was created with its own auto-approve off while Settings' default is on. On 2026-10-18:
    • its merge gate (human.merge-pr) opened at 01:45:11Z and was still open 20 s later;
    • at 01:45:33Z, POST /api/runs/{id}/auto-approve {on: true} answered {"auto_approve": true}, and auto_approve answered the merge gate the same second;
    • the archive gate opened at 01:45:38Z and was answered at once;
    • the run succeeded at 01:45:45Z.

Not checked on production:

  • the four hovers: reasoning effort's per-step map, "Compacts at …, stops at … · ceiling …", "default: unlimited", and each apply choice's text;
  • a run's switch leaving another run's open gate alone;
  • the New Run form's default.

The last two were checked on the local stack (task 8.4).

Not done: one cosmetic issue, filed as #191. The selector reads "vLLM · qwen3.8-27b — vLLM · qwen3.8-27b" when a backend's name is the same as its kind and model.

Closing.

Shipped in fdd6c70, live since 23:28Z on 2026-10-17 with migration 17 (backed up first), and archived in OpenSpec as `settings-page-tidy` in 874eb27. **What shipped** 1. **One Backend row** (39d5f63). "Backend runs use" is a selector with Add a backend and Duplicate. Delete removes the chosen backend after Save. Where it can't, a sentence in its place says why: "Runs use this backend. Choose another for runs and save, then delete it." 2. **Hovers** (39d5f63). Each of these moved into its field's ⓘ: reasoning effort's per-step map, "Compacts at …, stops at … · ceiling …", "default: unlimited", and each apply choice's text. 3. **Auto-approve per run:** - each run keeps its own auto-approve (d9f2ad4); - `POST /api/runs` takes it, and `POST /api/runs/{id}/auto-approve` switches one run (a0edab2); - the engine answers that run's gates only, and an answered gate is not emailed (86c0b7d); - the spine's switch, the labels and New Run follow the run (53b3a13). Settings' checkbox reads "Approve gates automatically in new runs" and sets the default for new runs. 4. **After review:** - Settings follows runs as they start and end, so Delete comes back once a backend's runs end (8d6a25f); - a run detail read that began before a switch keeps the switch (c44fffc); - opening Settings shares a read already in flight (e7028de). **Runs from before the deploy.** Migration 17 turns a run's own auto-approve on only when the run was created under the switch and the switch was still on at the upgrade. On production, runs 55 to 65 read on and runs 66 to 74 read off. Run 75 was created after the deploy. **Checked on production** (fdd6c70, in a real browser): - Settings has one "Backend runs use" selector with Add a backend and Duplicate, and the in-use sentence where Delete would be. "default: null" and "Hands off" are gone. The Approvals checkbox reads "Approve gates automatically in new runs". - Run 75 was created with its own auto-approve off while Settings' default is on. On 2026-10-18: - its merge gate (`human.merge-pr`) opened at 01:45:11Z and was still open 20 s later; - at 01:45:33Z, `POST /api/runs/{id}/auto-approve {on: true}` answered `{"auto_approve": true}`, and `auto_approve` answered the merge gate the same second; - the archive gate opened at 01:45:38Z and was answered at once; - the run succeeded at 01:45:45Z. **Not checked on production:** - the four hovers: reasoning effort's per-step map, "Compacts at …, stops at … · ceiling …", "default: unlimited", and each apply choice's text; - a run's switch leaving another run's open gate alone; - the New Run form's default. The last two were checked on the local stack (task 8.4). **Not done:** one cosmetic issue, filed as #191. The selector reads "vLLM · qwen3.8-27b — vLLM · qwen3.8-27b" when a backend's name is the same as its kind and model. Closing.
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#187
No description provided.