Feature Request: Clearer UI to associate a tool call and its approval in single step with multiple tool calls #2371
Labels
enhancement
New feature or request
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please explain the motivation behind the feature request.
When an extension makes several tool call requests in a single step, they all appear sequentially, followed by the tool call approval for each (also sequentially). Each tool call approval says "Goose would like to call the above tool. Allow?" but when there are several, it can be hard to quickly inspect what step you are approving. If there are enough it can even require scrolling up to find which tool is going to be invoked.
This disrupts the flow of the conversation and can lead to erroneous actions being taken by the user by accident.
Describe the solution you'd like
Even if an extension makes multiple tool call requests in a single "step", it would be better if the tool approval step was more clearly associated with the actual tool invocation. The exact approach to do this is certainly something that doesn't necessarily have one best way, as I can see the benefit of seeing what the follow-up tool calls are, so simply blocking them from showing up until earlier tool calls are handled might be undesirable.
One way to do this "elegantly" could be to integrate the manual tool approval UI into the tool call box itself, such that output actually appears below where the user accepted the tool call.
Describe alternatives you've considered
I haven't really thought too much about this, though I think it's fairly clear that the current UI, when running without auto-accept mode, is problematic.
Additional context
Here are some screenshots of a conversation I had which was making multiple edits to Airtable - 1 update, and multiple creates. If I wasn't diligent, I could have easily missed the fact that I was actually initially approving an update tool call, not a create.
Note that this is from session history, hence why "Tool confirmation is not available".
The text was updated successfully, but these errors were encountered: