docs: add tool approval (human-in-the-loop) feature documentation#1095
docs: add tool approval (human-in-the-loop) feature documentation#1095MaderHatt3r wants to merge 1 commit into
Conversation
ℹ️ Documentation PR Guidelines👋 Welcome! This is an automated message posted on all new documentation PRs to help guide our contributors. Just because this comment appeared doesn't mean you have done anything wrong! Please ensure you're using the correct branches: Target branch (where you're merging TO):
Source branch (where you're merging FROM):
If your docs PR depends on a pending PR in open-webui/open-webui:
Please adjust your PR target branch, source branch, and/or draft status accordingly if needed. |
| @@ -0,0 +1,98 @@ | |||
| --- | |||
There was a problem hiding this comment.
new folders for tool related features not wanted. move to tools folder
| Approvals are **granular**: you can approve at the level of an individual function (e.g. `read_file`) or an entire parent tool (e.g. `mcp:desktop_commander`). This is especially useful for tools like MCP servers that expose many child functions with varying risk levels. | ||
|
|
||
| :::info | ||
| Requires **Open WebUI v0.9.0+** (or whichever release includes this feature). |
There was a problem hiding this comment.
what is this here
also specific version requirements are usually not a pattern you see in the other feature pages in the docs.
|
Related PR was closed - Closing. |
3 participants
Related PR: open-webui/open-webui#21678