chore(adk): remove id_token monkey patch following upstream ADK fix#602
Merged
anubhav756 merged 3 commits intomainfrom Mar 24, 2026
Merged
chore(adk): remove id_token monkey patch following upstream ADK fix#602anubhav756 merged 3 commits intomainfrom
anubhav756 merged 3 commits intomainfrom
Conversation
dishaprakash
approved these changes
Mar 24, 2026
### Description Removes the `id_token` monkey-patching in `toolbox_adk/tool.py` since the upstream fix in ADK has been successfully merged ([google/adk-python#4402](google/adk-python#4402)). With the ADK natively retaining the `id_token`, the workaround is no longer necessary.
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
2 participants
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.
Removes the
id_tokenmonkey-patching intoolbox_adk/tool.pysince the upstream fix in ADK has been successfully merged (google/adk-python#4402).With the ADK natively retaining the
id_token, the workaround is no longer necessary.