fix: correctly set disable_parallel_tool_use
#78
Merged
+171
−5
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.
Relates to #2.
Currently we're indiscriminately setting
disable_parallel_tool_usein theanytype: this is a correctness bug.We should only set this field for the type which is set.
https://platform.claude.com/docs/en/agents-and-tools/tool-use/implement-tool-use#parallel-tool-use
There are 4 types:
auto,any,tool,none.noneis irrelevant (can't parallelize tool calls which don't occur).We should check which type is used (or set
autoif none is provided) and set the field on that.I noticed this today when using Claude Code v2.0.69.
The request did not contain a
tool_choicefield (behavioural change), so I got this error:{ "error": { "message": "Thinking may not be enabled when tool_choice forces tool use.", "type": "invalid_request_error" }, "request_id": "", "type": "error" }