Do not register models the catalog would not offer - #151
Merged
Conversation
The registry is cheap to append to, which is why it grows without anyone deciding that it should. A daily job proposing every model its providers ship makes that worse, not better: left alone it would register routing for models nothing surfaces, and each one is a name the gateway then has to route, price and test forever for a model no user can select. Point the skill at the curation bar that actually governs this — the one in chat-api's add-catalog-model skill, where a new model earns a picker row only if it offers something no current row does, and a better model replaces the model it supersedes instead of joining it. Registration is downstream of that decision, so apply it here first rather than registering speculatively and sorting it out later. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LCzE1jP1Yvy4fbSj4xtRkv
adambalogh
marked this pull request as ready for review
September 3, 2026 17:34
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Curation policy for the daily model-release watch. One file, no code change — the registry itself is untouched. (Split out of the closed #150, which also carried a CI workflow that may not be needed; this half is needed either way.)
The registry is cheap to append to, which is exactly why it grows without anyone deciding it should. A daily job proposing every model our providers ship makes that worse: left alone it would register routing for models nothing surfaces, and each one is a name the gateway then has to route, price correctly and test forever for a model no user can select.
.claude/skills/add-gateway-model/SKILL.mdnow points at the bar that actually governs this — the one in chat-api'sadd-catalog-modelskill, tightened in OpenGradient/chat-api#282, where a new model earns a picker row only if it offers something no current row does, and a better model replaces the one it supersedes rather than joining it. Registration is downstream of that decision, so it gets applied here first rather than registering speculatively and sorting it out later.Practically, for a run adding a model: apply the catalog's bar before touching the enum, and if the new model supersedes one already registered, expect the catalog change to hide the old one and say which in the PR.
🤖 Generated with Claude Code
https://claude.ai/code/session_01LCzE1jP1Yvy4fbSj4xtRkv
Generated by Claude Code