Pass metadata into toolPart to allow multi step tool calls for @effect/ai-google #5955
+4
−2
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.
…
Type
Description
Prompt.fromResponseParts doesn't copy metadata to options when converting Response.ToolCallPart and Response.ToolResultPart to prompt parts.
This breaks multi-turn tool calls with Google's Gemini API, which requires thoughtSignature (stored in metadata.google.thoughtSignature) to be present in follow-up requests. Without this fix, Gemini returns a 400 error: "Function call is missing a thought_signature in functionCall parts."
The fix adds options: part.metadata when creating tool-call and tool-result parts in fromResponseParts.
Related
fromResponsePartsdropsmetadatawhen converting tool-call/tool-result parts #5954