Repository navigation
Offer a list of models in the agents example configuration - #52
Merged
Merged
Conversation
GEMINI_MODEL named one model. The chat can offer a choice now, so the example lists them instead, and the first is what a conversation uses until one is picked for it. The id it suggested was gemini-3-flash-preview, which is a preview and was already behind; the list names stable ids, with the one preview marked as such because those are retired on Google's schedule rather than ours.
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
1 participant
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.
Configuration side of the model picker (yeti-platform/yeti-agents#10, and google/osdfir-infrastructure#281 for Helm). Without a list the chat offers one model and hides its selector, so the feature is unreachable from a Compose deployment.
Same for
OLLAMA_MODEL→OLLAMA_MODELS.The id previously suggested,
gemini-3-flash-preview, is a preview and was already behind — Google lists it under Preview and recommends a stable id for production. The replacements are stable, apart fromgemini-3.1-pro-preview, which is marked as a preview because there is nogemini-3.1-pro: that line only ships a preview.GEMINI_MODELstill works if a deployment sets it, and wins over the list, so nothing configured that way changes.docker compose configvalidates against the updated template.