Repository navigation
feat: model aliases - #21
Merged
Merged
Conversation
Panaetius
approved these changes
Oct 22, 2026
Panaetius
left a comment
Member
There was a problem hiding this comment.
Thanks looks fine to me. I would have probably put the alias as a property on the model, but I like this solution much more where it's a top level config, that makes it easier to see 👍
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
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.
Context
We want to support stable model ids like
sdsc-largeto let users keep their client config as we update the underlying models.Summary
Adds
modelAliasesin values, a map of stable model names to entries inmodels, routed using envoy AI gateway'smodelNameOverride. Aliases also work for external (apiUrl) models.Notes
🤖 Generated with Claude Code