[4 of 4] tui: route startup and onboarding config writes through app server#22916
Open
etraut-openai wants to merge 8 commits into
Conversation
etraut-openai
force-pushed
the
etraut/tui-config-app-server-4-startup-bookkeeping
branch
from
fb52e01 to
8cac60f
Compare
etraut-openai
force-pushed
the
etraut/tui-config-app-server-3-feature-toggles
branch
2 times, most recently
from
d8375c8 to
d5f9063
Compare
etraut-openai
force-pushed
the
etraut/tui-config-app-server-4-startup-bookkeeping
branch
from
8cac60f to
6ea4edd
Compare
…raut/tui-config-app-server-4-startup-bookkeeping # Conflicts: # codex-rs/tui/src/config_rpc.rs
…raut/tui-config-app-server-4-startup-bookkeeping # Conflicts: # codex-rs/tui/src/app/config_persistence.rs # codex-rs/tui/src/app/event_dispatch.rs
…raut/tui-config-app-server-4-startup-bookkeeping
…raut/tui-config-app-server-4-startup-bookkeeping
etraut-openai
added a commit
that referenced
this pull request
May 16, 2026
## Why The TUI can run against a remote app server, but several high-traffic settings still persisted by editing the local config file. That sends remote sessions' preference writes to the wrong machine and lets local disk state drift from the app-server-owned config. This is **[1 of 4]** in a stacked series that moves TUI-owned config mutations onto app-server APIs. ## What changed - Added a small TUI helper for typed app-server config writes. - Routed primary interactive preference writes through `config/batchWrite`. - Preserved existing profile scoping for settings that already support `profiles.<profile>.*` overrides. ## Config keys affected - `model` - `model_reasoning_effort` - `personality` - `service_tier` - `plan_mode_reasoning_effort` - `approvals_reviewer` - `notice.fast_default_opt_out` - Profile-scoped equivalents under `profiles.<profile>.*` ## Suggested manual validation - Connect the TUI to a remote app server, change `model` and `model_reasoning_effort`, reconnect, and confirm the remote config retained both values while the local `config.toml` did not change. - Change `personality`, `plan_mode_reasoning_effort`, and the explicit auto-review selection, then reconnect and confirm those choices persist through the app server. - Clear the service tier back to default and confirm `service_tier` is cleared while `notice.fast_default_opt_out = true` is persisted remotely. - Repeat one setting change with an active profile and confirm the write lands under `profiles.<profile>.*`. ## Stack 1. [#22913](#22913) `[1 of 4]` primary settings writes 2. [#22914](#22914) `[2 of 4]` app and skill enablement 3. [#22915](#22915) `[3 of 4]` feature and memory toggles 4. [#22916](#22916) `[4 of 4]` startup and onboarding bookkeeping
…raut/tui-config-app-server-4-startup-bookkeeping
…raut/tui-config-app-server-4-startup-bookkeeping
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
1 participant
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.
Why
The remaining local writes happen during startup, onboarding, and prompt bookkeeping. They are less common than interactive settings changes, but they are still real config mutations and should follow the same app-server ownership model instead of reaching around it.
This is [4 of 4] in a stacked series that moves TUI-owned config mutations onto app-server APIs.
What changed
config/batchWrite.Config keys affected
oss_providerprojects.<project_key>.trust_leveltui.model_availability_nux.<model_slug>notice.hide_full_access_warningnotice.hide_world_writable_warningnotice.hide_rate_limit_model_nudgenotice.model_migrations.<from_model>notice.external_config_migration_prompts.homenotice.external_config_migration_prompts.home_last_prompted_atnotice.external_config_migration_prompts.projects.<project_key>notice.external_config_migration_prompts.project_last_prompted_at.<project_key>Suggested manual validation
--osswhen no OSS provider is configured, pick a provider manually, and confirmoss_provideris persisted through the app-server path.projects.<project_key>.trust_level.Stack
[1 of 4]primary settings writes[2 of 4]app and skill enablement[3 of 4]feature and memory toggles[4 of 4]startup and onboarding bookkeeping