strip anthropic prefixes from models client-side - #480
Merged
Conversation
andy-xu-db
approved these changes
Sep 3, 2026
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.
we need to add an
anthropic-aigw-(8char hash)-prefix to non-claude model ids so they appear in the anthropic model picker. the problem is that these ids don't get cleaned up properly when they get sent to the smart router so the smart router doesnt recognize say glm-5-3-flash as a legit model.this PR cleans up the prefix client-side. i'm going to add this clean up server-side in the router, but this is until the server-side change lands.
before - routes to sonnet because it can't recognize the oss models
after - routes to glm-5-3-flash because it's a recognized model
