Skip to content

Conversation

@dannykopping
Copy link
Collaborator

Relates to #2.

Currently we're indiscriminately setting disable_parallel_tool_use in the any type: 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. none is irrelevant (can't parallelize tool calls which don't occur).

We should check which type is used (or set auto if 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_choice field (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"
}

Signed-off-by: Danny Kopping <danny@coder.com>
@dannykopping dannykopping changed the title fix: correctly set disable_parallel_tool_use fix: correctly set disable_parallel_tool_use Dec 15, 2025
Copy link

@ssncferreira ssncferreira left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just a small nit 👍

@dannykopping dannykopping merged commit 9aec90b into main Dec 15, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants