You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current implementation, only one tool can be called per interaction, which can lead to more conversational turns in certain scenarios (such as reading multiple files or editing multiple files). I believe it would be beneficial to increase the limit on the number of tools that can be called per interaction to make tool usage more efficient.
Describe the proposed solution in detail
In fact, handling multiple tool calls in a single interaction is already technically feasible in the current implementation—it's just restricted by an enforced limit of one tool call at a time. Special handling would be required for task creation and completion.
Technical considerations or implementation details (optional)
No response
Describe alternatives considered (if any)
No response
Additional Context & Mockups
Proposal Checklist
I have searched existing Issues and Discussions to ensure this proposal is not a duplicate.
This proposal is for a specific, actionable change intended for implementation (not a general idea).
I understand that this proposal requires review and approval before any development work begins.
Are you interested in implementing this feature if approved?
Yes, I would like to contribute to implementing this feature.
The text was updated successfully, but these errors were encountered:
What problem does this proposed feature solve?
In the current implementation, only one tool can be called per interaction, which can lead to more conversational turns in certain scenarios (such as reading multiple files or editing multiple files). I believe it would be beneficial to increase the limit on the number of tools that can be called per interaction to make tool usage more efficient.
Describe the proposed solution in detail
In fact, handling multiple tool calls in a single interaction is already technically feasible in the current implementation—it's just restricted by an enforced limit of one tool call at a time. Special handling would be required for task creation and completion.
Technical considerations or implementation details (optional)
No response
Describe alternatives considered (if any)
No response
Additional Context & Mockups
Proposal Checklist
Are you interested in implementing this feature if approved?
The text was updated successfully, but these errors were encountered: