Repository navigation
feat(web): Fork settings page rows for automatic updates, handoff and playtest - #544
Merged
Merged
Conversation
scuttletoby
added a commit
that referenced
this pull request
Nov 19, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scuttletoby
added a commit
that referenced
this pull request
Nov 19, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scuttletoby
force-pushed
the
fork-settings-page-b
branch
from
November 19, 2026 16:34
080639f to
51dd533
Compare
scuttletoby
added a commit
that referenced
this pull request
Nov 19, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scuttletoby
added a commit
that referenced
this pull request
Nov 19, 2026
…ws lock and reset per row Fix round for the review of #544: - On a project screen a save of handoff or playtest merged the shown value into the project's current one, so a removed playtest step or an emptied handoff command came back. Both now replace the project's value whole, as waitChecks and reviewRules do (the server reads them so). A test saves through the real writer and settings patch. - A thread's title and id are in their own elements, so the title reads (and is found) on its own. - A managed lock or a missing write permission makes every handoff and playtest control inert: the thread list, Add thread, the command and instructions too. A refused Add thread keeps the typed id. - On a project screen each Handoff and Playtest sub-row resets only its own fields to the environment's value; the section's first row still clears the whole override. - "Reset playtest to default" restores the real default (steps included), and a clamped number shows the saved value. - The playtest test switches the adapter on and then off. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scuttletoby
force-pushed
the
fork-settings-page
branch
from
November 19, 2026 17:09
460e13c to
321cc16
Compare
scuttletoby
force-pushed
the
fork-settings-page-b
branch
from
November 19, 2026 17:09
51dd533 to
d320352
Compare
scuttletoby
added a commit
that referenced
this pull request
Nov 19, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scuttletoby
added a commit
that referenced
this pull request
Nov 19, 2026
…ws lock and reset per row Fix round for the review of #544: - On a project screen a save of handoff or playtest merged the shown value into the project's current one, so a removed playtest step or an emptied handoff command came back. Both now replace the project's value whole, as waitChecks and reviewRules do (the server reads them so). A test saves through the real writer and settings patch. - A thread's title and id are in their own elements, so the title reads (and is found) on its own. - A managed lock or a missing write permission makes every handoff and playtest control inert: the thread list, Add thread, the command and instructions too. A refused Add thread keeps the typed id. - On a project screen each Handoff and Playtest sub-row resets only its own fields to the environment's value; the section's first row still clears the whole override. - "Reset playtest to default" restores the real default (steps included), and a clamped number shows the saved value. - The playtest test switches the adapter on and then off. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scuttletoby
force-pushed
the
fork-settings-page
branch
from
November 19, 2026 17:10
321cc16 to
531a93a
Compare
scuttletoby
force-pushed
the
fork-settings-page-b
branch
from
November 19, 2026 17:10
d320352 to
42220e8
Compare
scuttletoby
force-pushed
the
fork-settings-page
branch
from
November 19, 2026 17:27
531a93a to
0bf753b
Compare
scuttletoby
added a commit
that referenced
this pull request
Nov 19, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scuttletoby
force-pushed
the
fork-settings-page-b
branch
from
November 19, 2026 17:27
42220e8 to
dbc6732
Compare
scuttletoby
added a commit
that referenced
this pull request
Nov 19, 2026
…ws lock and reset per row Fix round for the review of #544: - On a project screen a save of handoff or playtest merged the shown value into the project's current one, so a removed playtest step or an emptied handoff command came back. Both now replace the project's value whole, as waitChecks and reviewRules do (the server reads them so). A test saves through the real writer and settings patch. - A thread's title and id are in their own elements, so the title reads (and is found) on its own. - A managed lock or a missing write permission makes every handoff and playtest control inert: the thread list, Add thread, the command and instructions too. A refused Add thread keeps the typed id. - On a project screen each Handoff and Playtest sub-row resets only its own fields to the environment's value; the section's first row still clears the whole override. - "Reset playtest to default" restores the real default (steps included), and a clamped number shows the saved value. - The playtest test switches the adapter on and then off. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scuttletoby
added a commit
that referenced
this pull request
Nov 19, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scuttletoby
added a commit
that referenced
this pull request
Nov 19, 2026
…ws lock and reset per row Fix round for the review of #544: - On a project screen a save of handoff or playtest merged the shown value into the project's current one, so a removed playtest step or an emptied handoff command came back. Both now replace the project's value whole, as waitChecks and reviewRules do (the server reads them so). A test saves through the real writer and settings patch. - A thread's title and id are in their own elements, so the title reads (and is found) on its own. - A managed lock or a missing write permission makes every handoff and playtest control inert: the thread list, Add thread, the command and instructions too. A refused Add thread keeps the typed id. - On a project screen each Handoff and Playtest sub-row resets only its own fields to the environment's value; the section's first row still clears the whole override. - "Reset playtest to default" restores the real default (steps included), and a clamped number shows the saved value. - The playtest test switches the adapter on and then off. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scuttletoby
force-pushed
the
fork-settings-page-b
branch
from
November 19, 2026 18:39
dbc6732 to
44db49b
Compare
scuttletoby
force-pushed
the
fork-settings-page
branch
from
November 19, 2026 18:39
0bf753b to
b184d4f
Compare
scuttletoby
force-pushed
the
fork-settings-page
branch
from
November 19, 2026 20:31
b184d4f to
6b5148d
Compare
scuttletoby
added a commit
that referenced
this pull request
Nov 19, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scuttletoby
added a commit
that referenced
this pull request
Nov 19, 2026
…ws lock and reset per row Fix round for the review of #544: - On a project screen a save of handoff or playtest merged the shown value into the project's current one, so a removed playtest step or an emptied handoff command came back. Both now replace the project's value whole, as waitChecks and reviewRules do (the server reads them so). A test saves through the real writer and settings patch. - A thread's title and id are in their own elements, so the title reads (and is found) on its own. - A managed lock or a missing write permission makes every handoff and playtest control inert: the thread list, Add thread, the command and instructions too. A refused Add thread keeps the typed id. - On a project screen each Handoff and Playtest sub-row resets only its own fields to the environment's value; the section's first row still clears the whole override. - "Reset playtest to default" restores the real default (steps included), and a clamped number shows the saved value. - The playtest test switches the adapter on and then off. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scuttletoby
force-pushed
the
fork-settings-page-b
branch
from
November 19, 2026 20:31
44db49b to
77ce421
Compare
… playtest These fork settings had no screen. Settings > Fork gets three sections: - Updates (server only): "Update automatically" and the quiet check program asked before an automatic update. - Handoff: the mode (Off, Handoff, Compact), each thread's own mode (added by thread id, shown with its title where this client knows the thread, removable), and under Advanced the size and idle sizes, who writes the handoff with its command (one argument per line) and the instructions. - Playtest: the switch, which stays off until claim, renew, push and release are set; the steps as JSON in a dialog, checked as the server's save checks them; the renew, idle and session limits under Advanced. Handoff and playtest are project-scoped and replace the environment's value whole, so a change on a project screen saves the whole value it shows as the project's own, and the row's override control clears it. The page leaves a marked place for MCP profiles. Every new row is in the settings search. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ws lock and reset per row Fix round for the review of #544: - On a project screen a save of handoff or playtest merged the shown value into the project's current one, so a removed playtest step or an emptied handoff command came back. Both now replace the project's value whole, as waitChecks and reviewRules do (the server reads them so). A test saves through the real writer and settings patch. - A thread's title and id are in their own elements, so the title reads (and is found) on its own. - A managed lock or a missing write permission makes every handoff and playtest control inert: the thread list, Add thread, the command and instructions too. A refused Add thread keeps the typed id. - On a project screen each Handoff and Playtest sub-row resets only its own fields to the environment's value; the section's first row still clears the whole override. - "Reset playtest to default" restores the real default (steps included), and a clamped number shows the saved value. - The playtest test switches the adapter on and then off. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…reset never builds a refused value - Handoff size and idle size are bounded above by the server's limit (HANDOFF_MAX_TOKENS, now exported), so the field never offers a value the save refuses. - A project sub-row reset is offered only when its result passes the server's strict check: a project whose own playtest is on no longer gets a step reset missing a step it needs. - The reset helper's test covers an object field (threads) and a list field (push) by value. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scuttletoby
force-pushed
the
fork-settings-page-b
branch
from
November 19, 2026 20:42
77ce421 to
567e401
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #543, which is stacked on #542. Merge in that order. Like #543, this PR's "Fork lines in upstream files" check is red until #542 is on main. This PR adds no upstream line of its own.
Problem
automaticUpdates,automaticUpdatesQuietCommand,handoffandplaytesthad no screen: changing them meant editingsettings.jsonby hand.Fix
Three more sections on Settings → Fork (#543), each in a fork file under
apps/web/src/components/settings/fork/:modelSelectionhas no row: a model picker is its own piece of work. Every save keeps the stored value. The docs say so.The page ends with a marked place for the later MCP profiles section. Every new row has a search item (13 more), so the settings search finds them.
Upstream fit
No upstream file changes. All changes are in fork files: the panels, the logic files and their tests, the fork search items and the fork docs. The seam check against #542's list passes. Labels are English only, as the fork's other panels.
General vs project
automaticUpdates,automaticUpdatesQuietCommandhandoffplaytestScreenshot
Not captured: the browser tests and dev server could not run on the machine that wrote this, which is missing Chromium's system libraries and has no root. CI runs the browser tests. What the page shows below Reviews:
/usr/local/bin/quiet-check).Tests
fork/handoffSettings.logic.test.ts:fork/playtestSettings.logic.test.ts:fork/ForkPanels.browser.test.tsx(CI only): the exact patch each control sends, with settings decoded from a settings file as the server loads it (empty and stored):vp run check:changed: format, lint, knip, typecheck, the react compiler check and all 62 unit tests pass. Only the three browser test files fail, at browser launch on this machine.State question
🤖 Generated with Claude Code