fix: handle BinaryImage and UserContent types as attachments in cast() #1257
+132
−1
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
BinaryImagetomarvin.cast()Problem
When passing a
BinaryImagetomarvin.cast(), the binary data was being serialized into the task context as a string (base64), causing token explosion (207K+ tokens for a ~200KB image).Solution
Added detection for pydantic-ai's
UserContenttypes and pass them as task attachments instead of putting them in the context dictionary.Test Plan
_is_user_content()helper functionFixes #1246