Add documentation warnings for AgentTool/TeamTool parallel tool calls limitation #6883
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.
When using
AgentToolorTeamToolwith parallel tool calls enabled (the default), the second tool execution fails with "The team is already running, it cannot run again until it is stopped." This occurs because teams and agents maintain internal state that conflicts with concurrent execution.The issue manifests when an LLM makes multiple tool calls simultaneously:
Solution: Users must disable parallel tool calls when using these tools:
This PR adds comprehensive documentation warnings:
agents.ipynb): Added prominent warning in the Parallel Tool Calls section explaining the limitation and solution.. important::directive with clear explanation and updated example showing proper usageparallel_tool_calls=FalseAll examples now show the correct pattern of creating separate model clients with parallel tool calls disabled for the main agent while allowing the wrapped agents/teams to use their own model clients normally.
Fixes #6882.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.