[Bug]: manual opencode-go modelContextWindows entries are reset after update

[RanceLee233]

Client or integration

Codex App

Area

Catalog / models

Summary

After upgrading @bitkyc08/opencodex from 2.11.0 to 2.11.1, a manually configured providers.opencode-go.modelContextWindows entry for deepseek-v4-flash was silently removed and replaced by the registry defaults. The Codex App context indicator changed from about 855k to 950k. I expected user-defined model context overrides to survive upgrades, daemon restarts, and subsequent config saves.

Reproduction

1. In ~/.opencodex/config.json, set the relevant provider override:

   {
     "providers": {
       "opencode-go": {
         "modelContextWindows": {
           "deepseek-v4-flash": 900000
         }
       }
     }
   }

   The real file contains other fields; the snippet above is redacted to the relevant shape.

2. Run OpenCodex 2.11.0 and select opencode-go / deepseek-v4-flash.

3. Verify that the Codex App context indicator is about 855k.

4. Upgrade from 2.11.0 to 2.11.1 and restart the daemon/app.

5. Inspect the config after the upgrade and after the first unrelated provider/config write.

6. The custom deepseek-v4-flash entry is gone. opencode-go.modelContextWindows contains only the registry-seeded entry kimi-k3: 262144.

7. The catalog falls back to context_window=1000000 and auto_compact_token_limit=900000, and the UI shows about 950k.

Additional observation: the modelContextWindows setting for the separate deepseek provider was not changed. Only the opencode-go override was reset.

Version

2.11.1

Operating system

macOS (Darwin 25.5.0)

Provider and model

opencode-go / deepseek-v4-flash

Logs or error output

Expected:
- Explicit user values under providers.opencode-go.modelContextWindows remain unchanged after updates, restarts, and unrelated provider config writes.
- Registry defaults can seed missing entries, but must not delete or overwrite explicit user overrides.

Actual:
- providers.opencode-go.modelContextWindows was reset to {"kimi-k3": 262144}, matching the registry default.
- The effective context window changed from 900000 (UI about 855k) to 1000000 (UI about 950k).

The update log records the 2.11.0 -> 2.11.1 daemon restart. A later full config write after an unrelated provider change was when the reset became visible. No API keys, tokens, request IDs, or personal data are included here.

Screenshots and supporting files

No response

Redacted configuration

{
  "providers": {
    "opencode-go": {
      "modelContextWindows": {
        "deepseek-v4-flash": 900000
      }
    }
  }
}

Checks

• I searched existing issues and documentation.
• I removed secrets, tokens, account details, request credentials, and personal data.

[Ingwannu]

I checked current dev. src/providers/derive.ts:405 seeds modelContextWindows only when the entire user map is absent; src/router.ts:273-275 fills registry values beneath user entries; and src/server/management/provider-routes.ts:185-204 merges individual keys. None of those paths should replace the explicit deepseek-v4-flash value with the kimi-k3 registry seed.

The timing in this report, where a later unrelated full-config write makes the reset visible, matches the stale whole-document writer still tracked in #1273. The current sequence does not yet prove that it is the only cause, however. Please provide the exact order and redacted before/after snippets: which OCX or proxy processes were alive, whether the 900000 value was edited while the proxy was already running, which CLI or Dashboard action performed the unrelated write, and whether any restart happened between those steps. Config-file mtime and relevant mutation-generation log lines would also help.

Keeping this open separately until we can determine whether #1273 fully explains the write or whether the update path directly rewrites this field.