fix: filter extra fields from tool_use blocks to prevent Anthropic API rejection #247
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
tool_useblocks to only include fields that Anthropic accepts in requests:type,id,name, andinputcallerfield being rejectedProblem
Anthropic's API returns a
callerfield intool_useresponse blocks (introduced with programmatic tool calling), but rejects this field when sent back in subsequent requests. The currentmodel_dump()preserves all fields, causing validation errors.Test plan
🤖 Generated with Claude Code
Summary by cubic
Strip unsupported fields from tool_use blocks before sending to Anthropic to prevent validation errors and multi-step agent failures. Only type, id, name, and input are kept; caller is removed.
Written for commit 69ef3f5. Summary will update automatically on new commits.