Add service tier overrides to spawned agents#22139
Open
aibrahim-oai wants to merge 2 commits into
Open
Conversation
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.
Why
Spawned agents can already override
modelandreasoning_effort, but they have no equivalent way to opt into a model-supported service tier. That makes it impossible to preserve or intentionally select tiered execution behavior when delegating work to a sub-agent, even though the model catalog already advertises supportedservice_tiers.What changed
service_tierto both legacy andMultiAgentV2spawn_agenttool inputs.spawn_agenttool guidance.service_tierusable on full-history forks, while still honoring the existing model/reasoning fork restrictions.service_tieralongside other spawn metadata whenhide_spawn_agent_metadatais enabled.Verification
Added focused coverage for:
spawn_agentschema exposure forservice_tierLocal Rust tests were not run in this workspace per repo guidance; the new coverage is included for CI.