[Fix] Automation model overrides fail only after launch - #1168
Merged
daniel-lxs merged 1 commit intoAug 7, 2026
Conversation
Contributor
daniel-lxs
marked this pull request as ready for review
August 7, 2026 22:44
daniel-lxs
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
August 7, 2026 22:44
daniel-lxs
approved these changes
Aug 7, 2026
daniel-lxs
deleted the
fix/custom-automation-model-options-2kbm04j2tkz4m
branch
August 7, 2026 22:50
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.
What changed
list_modelsaction to custom automation management that returns the deployment's enabled model options and default model ID.openai/...uses the deployment OpenAI route, including connected ChatGPT subscription routing.Why this change was made
Custom automation management accepted any syntactically valid model ID, but agents could not discover the deployment's enabled choices. An unavailable override therefore failed only when the automation launched, after the invalid configuration had already been saved.
Impact
Agents can now choose an exact enabled model and inference route without guessing. Invalid overrides fail immediately with an actionable error, while omitted or cleared overrides continue to use the deployment default.