Repository navigation
fix: accept latest child Agent versions in Managed rosters - #43
Merged
Merged
Conversation
Agent rosters may save a child version as "latest", but the SDK typed roster versions as integers, so strict response parsing rejected valid Agents. Add a roster-specific request type and accept int or string versions in responses; Session and Deployment references stay numeric.
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.
Summary
MultiagentAgentParamsfor Managed Agent multiagent roster entries. A child Agentversionnow accepts a positive integer,"latest", or a positive integer string.MultiagentAgentUnion.version) asint | str, so Agent responses containing"latest"parse with_strict_response_validation=True.Why
The official Agent schema saves and returns
"latest"for child Agent references, and the Managed service has resolved"latest"roster entries since 2026-09-15. The SDK typed roster versions as integers, so strict response parsing rejected valid Agents and the request types could not express"latest".Verification
uv run make lintuv run make typecheckuv run make testuv run make docs-check--helpsmoke checksCommands and results:
Impact
CHANGELOG.mdunderUnreleased, or not applicable (explain below).env.live, logs, or generated test output committedAdditional context:
Optional[int]type it fails withAPIResponseValidationError.NO_PROXYentry of[::1]makes httpx reject client construction during collection."latest".