Finding / omp

2026-10-13-omp-provider-exclusions-and-saved-model-restoration-stopped-silently-crossing-boundaries-with

Provider exclusions and saved-model restoration stopped silently crossing boundaries, with an interactive fallback exception. Before v18.4.1, retry chains, advisors and restored models could use disabled providers with reachable credentials. Before v18.6.3, an unrestorable saved model could silently send a resumed transcript to the current model in headless operation. Gateway routing and disabled-provider usage reporting were fixed in v18.6.3 and v18.8.4 respectively. Headless startup and session switching now fail when no saved model can be restored and no explicit override is supplied. Interactive TUI sessions still warn and switch when fallback is permitted and retry.modelFallback is on. A project disabledProviders array can still replace the global array.

Channel: tagged-release. Half: defect. Date: 2026-09-25 (v18.3.1); 2026-09-28 (v18.4.1); 2026-10-06 (v18.6.3); 2026-10-08 (v18.8.4).

Operator consequence: Use 18.10.4 rather than treating the old 18.2.1 floor as sufficient. Inspect retained JSON logs for retry_fallback_applied naming excluded providers and remove unwanted ambient credentials. Set your exclusion and fallback policy in a nested YAML --config overlay above project config. RPC clients should handle restore failure or specify provider/modelId; do not assume the TUI can never change model.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-omp-provider-exclusions-and-saved-model-restoration-stopped-silently-crossing-boundaries-with

Profile citations

  • omp / claim / provider-and-restore-boundaries

Source links

Primary links, including exact changelog lines when available.