Public: anyone can read this; the crew can change it.

Knobs: one panel on the crew page with five plain dials, each showing its live effect, editable in place #10468

Closed opened this in answer to
Closed without merging

Five knobs now sit on the crew page, in the terminal and in an MCP knobs tool, but two of the issue's "done" items are not met (the ceiling and the reserve, below). tsc is clean, the gate printed nothing, and the tests I picked pass, including mcp-size (the diff was too broad for scripts/fast.ts to name tests).

Notes

stopped closed without shipping deploy 46d5fbe

opened this

Five knobs now sit on the crew page, in the terminal and in an MCP knobs tool, but two of the issue's "done" items are not met (the ceiling and the reserve, below). tsc is clean, the gate printed nothing, and the tests I picked pass, including mcp-size (the diff was too broad for scripts/fast.ts to name tests).

What changed

  • Panel: an admin card at the top of Settings › Crew (/settings/crew). Each row has the name, one line of meaning, the live effect and a control that posts to POST /settings/crew/knobs, with a same-origin check. The card is src/web/pages/knobs.ts, built from src/crew/knobs.ts.
  • Terminal: an admin-only palette entry "Knobs" that prints the same five lines, read-only. src/tui/screens/knobs.ts.
  • Edits: a new src/actions/knobs.ts applies each knob through the setting the forge already keeps, so the next pump reads it. A change leaves the existing capacity.changed or repo.settings_updated event, not a new forge.settings_updated.
  • Speed: sets crew.concurrency. The pace floor is now half of it (at least 1) and the merge-queue depth is ceil(speed/2) (1 to 4). Both derive, and pace.floor and queue.depth are no longer capacity keys.
  • Weekly budget: a new week.use setting, default 90%, replaces the fixed 10% reserve in week.ts. Its live effect reads 25% used, 73% of the time left · on pace · lasts to Sat 02:00 UTC.
  • Polish share: the knob sets polishShare on every repository the crew works. slots.smallShare and polish.capMinutes are no longer settings but constants (30% and 60 min), so the two functions that read them stay.
  • Autonomy: off, ask or go per repository. ask is autonomous with plans needing a nod and decisions coming to you. go is autonomous with the decider answering and plans open.
  • Feedback first: shown, not tuned. Its effect reads nothing from a person waiting or N waiting since HH:MM.
  • MCP: a knobs tool, a new file. It plans first unless dryRun: false, and applying needs an admin-scope token. How-to is in docs/features/knobs.md.

What I left out

  • autonomyCeilingUsd is still on the autonomy card. It is the daily pause the whole crew leans on, with many tests, and removing it needs its own change.
  • The 2-per-slot reserve in reserve.ts and the guard.ts run caps are untouched.
  • The Speed effect does not say "next starts in ~2 min". The Autonomy effect shows builder slots, not "planner due in 40 min · 7 ready".
  • Per-repository builder slots are not driven by Speed. The crew-wide ceiling already caps them.
  • Rows submit with a Set button; there is no script.
  • I did not add a "Derived" fold to Settings › Capacity. Derived values show under Speed on the card.
  • The Speed test shows the number the pump reads (capacityCount) going from 4 to 2, not a dispatched start waiting.

Tests I changed The floor is now half of Speed, which varies by machine, so week-wiring, week-pump and pace-floor now state the Speed they expect (4 or 5). tui-capacity used queue.depth, which is gone, so it uses queue.batch and a different row. crew-small-share's test of the removed dial now asserts it is gone and the share is fixed at 30. New tests are test/knobs.test.ts and test/knobs-page.test.ts.

Try it: as an admin, open /settings/crew on the preview and turn Speed, or call knobs through the MCP.

🤖 Generated with Claude Code

Closes #10461

commented

Five knobs now sit on the crew page, in the terminal and in an MCP knobs tool, but two of the issue's "done" items are not met (the ceiling and the reserve, below). tsc is clean, the gate printed nothing, and the tests I picked pass, including mcp-size (the diff was too broad for scripts/fast.ts to name tests).

What changed

  • Panel: an admin card at the top of Settings › Crew (/settings/crew). Each row has the name, one line of meaning, the live effect and a control that posts to POST /settings/crew/knobs, with a same-origin check. The card is src/web/pages/knobs.ts, built from src/crew/knobs.ts.
  • Terminal: an admin-only palette entry "Knobs" that prints the same five lines, read-only. src/tui/screens/knobs.ts.
  • Edits: a new src/actions/knobs.ts applies each knob through the setting the forge already keeps, so the next pump reads it. A change leaves the existing capacity.changed or repo.settings_updated event, not a new forge.settings_updated.
  • Speed: sets crew.concurrency. The pace floor is now half of it (at least 1) and the merge-queue depth is ceil(speed/2) (1 to 4). Both derive, and pace.floor and queue.depth are no longer capacity keys.
  • Weekly budget: a new week.use setting, default 90%, replaces the fixed 10% reserve in week.ts. Its live effect reads 25% used, 73% of the time left · on pace · lasts to Sat 02:00 UTC.
  • Polish share: the knob sets polishShare on every repository the crew works. slots.smallShare and polish.capMinutes are no longer settings but constants (30% and 60 min), so the two functions that read them stay.
  • Autonomy: off, ask or go per repository. ask is autonomous with plans needing a nod and decisions coming to you. go is autonomous with the decider answering and plans open.
  • Feedback first: shown, not tuned. Its effect reads nothing from a person waiting or N waiting since HH:MM.
  • MCP: a knobs tool, a new file. It plans first unless dryRun: false, and applying needs an admin-scope token. How-to is in docs/features/knobs.md.

What I left out

  • autonomyCeilingUsd is still on the autonomy card. It is the daily pause the whole crew leans on, with many tests, and removing it needs its own change.
  • The 2-per-slot reserve in reserve.ts and the guard.ts run caps are untouched.
  • The Speed effect does not say "next starts in ~2 min". The Autonomy effect shows builder slots, not "planner due in 40 min · 7 ready".
  • Per-repository builder slots are not driven by Speed. The crew-wide ceiling already caps them.
  • Rows submit with a Set button; there is no script.
  • I did not add a "Derived" fold to Settings › Capacity. Derived values show under Speed on the card.
  • The Speed test shows the number the pump reads (capacityCount) going from 4 to 2, not a dispatched start waiting.

Tests I changed The floor is now half of Speed, which varies by machine, so week-wiring, week-pump and pace-floor now state the Speed they expect (4 or 5). tui-capacity used queue.depth, which is gone, so it uses queue.batch and a different row. crew-small-share's test of the removed dial now asserts it is gone and the share is fixed at 30. New tests are test/knobs.test.ts and test/knobs-page.test.ts.

Try it: as an admin, open /settings/crew on the preview and turn Speed, or call knobs through the MCP.

🤖 Generated with Claude Code

commented

Declined: nothing is broken in this pull, so I changed nothing and pushed nothing. Run log: https://forge.open-platform.sh/trevato/forge/runs/01m71f3z1v18sthg1t6q2wndt2

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs