Repository navigation
[Bug] ocx sync overwrites hand-edited config.json from stale server memory (GLM-5.3 tune lost); 2.21.0 save path fixed it but sync path question remains #1802
Description
Activity
🔗 Related PRs
#518 - fix(codex): warn or restart stale app-server after sync [open]
#576 - fix(codex): warn about stale Codex app-servers after a catalog write [merged]
#889 - fix(providers): Copilot mixed-wire routing, DeepSeek service_tier + reasoning replay, Claude 4.6/4.7 1M windows [open]
#892 - fix: bound the six remaining retained-state leaks (#820wave 2) [merged]
#1331 - fix(catalog): keep failover combos when live discovery omits members [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.- Create Plan
🧪 Issue enrichment is currently in open beta.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:issue_enrichment: auto_enrich: enabled: false
💬 Have feedback or questions? Drop into our discord!
Maintainer decision respected
A maintainer has reopened this issue. The automated closure has been deactivated.
Fixed on
devby #1848 (merged as73440d4bb) — though the code path was already correct; what was missing was proof.POST /api/synccallsloadConfig()at its own route boundary (src/server/management/config-routes.ts:383), andsyncModelsToCodexwrites Codex artifacts rather than OpenCodexconfig.json. Combined with the 2.21.0 save-path fix, the reported clobber is no longer reachable.The regression added here starts a server, hand-edits
config.jsonout of band so disk is strictly newer than the server's snapshot, then calls/api/syncand asserts against the FILE — because the failure being prevented is the route persisting a caller-held snapshot back over it. It was driven red first by making the route save its held config: the hand-edited provider disappears and the test fails.Closing as completed. The change is on
devand ships with the next release; it is not in a published version yet.- added a commit that references this issue
on Aug 16, 2026 - added a commit that references this issue
on Sep 17, 2026
Summary
A hand-edited config.json (adding glm-5.3 to the zai provider) was silently reverted by an ocx sync while the long-lived proxy server was running. The running server held the pre-edit config in memory; the sync-triggered service-time save serialized the stale copy over the disk file. This is the bug class from #488 (closed). In 2.21.0 the normal save path was fixed to re-read disk first (verified: a later service-time write preserved the hand-edit), but we have not confirmed whether the ocx sync write path was part of that fix or still uses the stale in-memory config.
Environment
Timeline (2026-08-15, America/New_York, EDT)
Evidence
Ask
Impact / prevention on our side
Documented runbook guard: hand-edit -> restart proxy before any ocx sync/GUI toggle; snapshot -> validate -> diff after every upgrade/sync; config.json now git-tracked locally for one-command rollback.