feat(webui): expand and organize settings with autosave - #5704
Draft
chengyongru wants to merge 24 commits into
Draft
feat(webui): expand and organize settings with autosave#5704chengyongru wants to merge 24 commits into
chengyongru wants to merge 24 commits into
Conversation
chengyongru
force-pushed
the
codex/webui-config-coverage
branch
from
September 9, 2026 02:39
f88b9b9 to
86e4e33
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.
Settings currently leave many non-channel options editable only in config.json. This exposes 41 configuration fields through validated settings endpoints and organizes common controls on their feature pages, with low-frequency settings in Advanced.
Backend scope is limited to settings payloads, validation, persistence, and route registration. This PR does not change AgentLoop, cron scheduling, session management, workspace switching, or listener lifecycle. Saving does not introduce live reload or automatic service restarts.
Validation:
Draft follow-up: