openclaw - 💡(How to fix) Fix [Bug]: Gemini API error (400): missing `thought_signature` [4 comments, 2 participants]

Google Generative AI API error (400): Function call is missing a thought_signature in functionCall parts. This is required for tools to work correctly, and missing thought_signature may lead to degraded model performance. Additional data, function call `def… [code=INVALID_ARGUMENT] Although this sounds like its optional - its not, its a full fledge no response error.

TL;DR

The most likely fix is to store the thought_signature of the output before the tool usage and attach it to the API call after the tool usage.

Guidance

• Review the Vertex AI documentation on Thought Signatures to understand the requirements for thought_signature in API calls.
• Modify the code to store the thought_signature of the output before the tool usage and attach it to the API call after the tool usage, as suggested in the fix suggestion.
• Verify that the thought_signature is being correctly stored and attached to the API call by checking the API request payload.
• Test the modified code with the Gemini API models to ensure that the chain of thought agentic workflows is sustained smoothly.

Example

No code snippet is provided as the issue does not include specific code details.

Notes

The fix may require modifications to the OpenClaw code to store and attach the thought_signature to the API call. The Vertex AI documentation should be consulted to ensure that the thought_signature is being used correctly.

Recommendation

Apply the workaround by modifying the code to store and attach the thought_signature to the API call, as this is the suggested fix and is supported by the Vertex AI documentation.