Symptom
Global user settings revert to defaults every time RPCE restarts, and changes made in one window don't appear in other open windows. Affected settings include:
- Oracle / planning model
- Context Builder agent selection
- Sub-agent role overrides (explore / engineer / pair / design)
Setting one of these in window A leaves other open windows showing the old value until the app is restarted (e.g. A shows Oracle = fable while every other window keeps gpt-5.5).
Root cause
- An unsupported schema is indistinguishable from "no settings." A
globalSettings.json whose schemaVersion is newer than the running build supports decodes the same as a missing file, so the store silently falls back to in-memory defaults on every launch. Settings appear to never persist, with no signal to the user that the file is being ignored.
- No live cross-window re-sync. Each window caches global settings locally and the shared
GlobalSettingsStore doesn't publish changes to observing windows, so a change in one window only appears in the others after a restart.
Proposed fix
- Detect an on-disk schema newer than supported and surface it to the user: a banner explaining settings won't save, with one-click recovery that backs up the offending file and restores fresh current-schema defaults. The app must never auto-overwrite a schema it did not write.
- Publish
objectWillChange on the global-defaults setters so windows observing the shared store re-sync live.
Status
Fix implemented with tests (cross-window propagation + JSON-only persistence / schema-block recovery), green locally. PR to follow and will reference this issue.
Symptom
Global user settings revert to defaults every time RPCE restarts, and changes made in one window don't appear in other open windows. Affected settings include:
Setting one of these in window A leaves other open windows showing the old value until the app is restarted (e.g. A shows Oracle =
fablewhile every other window keepsgpt-5.5).Root cause
globalSettings.jsonwhoseschemaVersionis newer than the running build supports decodes the same as a missing file, so the store silently falls back to in-memory defaults on every launch. Settings appear to never persist, with no signal to the user that the file is being ignored.GlobalSettingsStoredoesn't publish changes to observing windows, so a change in one window only appears in the others after a restart.Proposed fix
objectWillChangeon the global-defaults setters so windows observing the shared store re-sync live.Status
Fix implemented with tests (cross-window propagation + JSON-only persistence / schema-block recovery), green locally. PR to follow and will reference this issue.