Repository navigation
Enforce current provider requirements for the model catalog - #46917
Merged
copyberry[bot] merged 1 commit intoSep 21, 2026
Conversation
## Why The app server retains its startup model provider, but managed provider requirements can change while it is running. Catalog reads and background refreshes must check those requirements even when models are cached. ## What changed - Gate `model/list` and background refreshes through a shared catalog that validates the startup provider against current requirements. - Return JSON-RPC error `-32600` with restart guidance when the provider no longer complies, and skip background requests to that endpoint. Requirement load failures also block catalog access. - Log only the error kind for blocked refreshes to avoid exposing credentials in parser diagnostics. ## Testing Add coverage for cached catalog access after provider selection or definition changes, invalid requirements, cloud configuration load failures, and recovery when requirements allow the retained provider again. Extend refresh tests to cover startup provider overrides, blocked endpoint requests, and credential-safe logging. GitOrigin-RevId: 03127bba46f1f59f2a8b1dc37391eab75f9be23c
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/03127bba46f1f59f2a8b1dc37391eab75f9be23c
branch
from
September 21, 2026 01:19
13d7757 to
75db67b
Compare
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/03127bba46f1f59f2a8b1dc37391eab75f9be23c
branch
September 21, 2026 01:19
This branch was successfully deployed
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
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.
Enforce current provider requirements for the model catalog
Why
The app server retains its startup model provider, but managed provider requirements can change while it is running. Catalog reads and background refreshes must check those requirements even when models are cached.
What changed
model/listand background refreshes through a shared catalog that validates the startup provider against current requirements.-32600with restart guidance when the provider no longer complies, and skip background requests to that endpoint. Requirement load failures also block catalog access.Testing
Add coverage for cached catalog access after provider selection or definition changes, invalid requirements, cloud configuration load failures, and recovery when requirements allow the retained provider again. Extend refresh tests to cover startup provider overrides, blocked endpoint requests, and credential-safe logging.