Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 08:30 UTC
docs: rename approval mode to Approvals and mark it experimental
Moves the page to /docs/approvals, adds the experimental sidebar badge, and updates the links to it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Mukund committed
Oct 15, 2026 at 18:04 UTC
fc328266f266e2d28d1725a6e54bc93c6a77ed27
7 files changed
+13
-12
docs/content/docs/approvals.mdx
renamed
+3
-2
@@ -1,5 +1,6 @@
1
---
2
-title: Approval mode
2
+title: Approvals
3
+experimental: true
4
description: Ask the user before your agent runs tools that send, post or delete things on their behalf
5
keywords: [approval, human in the loop, elicitation, require_approval, input_required, confirmation]
6
---
@@ -9,7 +10,7 @@ By default, your agent can run any tool in a session as soon as it decides to. F
10
When your agent calls a tool that requires approval, Composio doesn't run it. It returns an elicitation that asks the user to approve the call, and runs the tool once it receives their answer.
11
12
<Callout type="warn" title="Experimental">
12
-Approval mode is experimental. It needs `composio` newer than 0.27.0 or `@composio/core` newer than 0.24.0.
13
+Approvals are experimental. They need `composio` newer than 0.27.0 or `@composio/core` newer than 0.24.0.
14
</Callout>
15
16
## Requiring approval
docs/content/docs/configuring-sessions.mdx
+1
-1
@@ -407,7 +407,7 @@ Every tool has a [tag](/docs/tool-tags) for the type of action it takes: `readOn
407
408
- **Allow:** leave the tag out. This is the default.
409
- **Block:** add the tag to `tags.disable`. The agent can't see or call these tools.
410
-- **Require approval:** add the tag to `tags.require_approval`. These tools wait for the user's approval before they run. See [Approval mode](/docs/approval-mode).
410
+- **Require approval:** add the tag to `tags.require_approval`. These tools wait for the user's approval before they run. See [Approvals](/docs/approvals).
411
412
For example, to block every tool that can delete something:
413
docs/content/docs/meta.json
+1
-1
@@ -13,7 +13,7 @@
13
"how-composio-works",
14
"configuring-sessions",
15
"session-configs",
16
- "approval-mode",
16
+ "approvals",
17
"instant-tools",
18
"toolkits",
19
"tool-tags",
docs/content/docs/production-readiness.mdx
+1
-1
@@ -62,7 +62,7 @@ Configure sessions with only the toolkits and tools required by the feature. Nar
62
63
Require explicit user confirmation before destructive or externally visible actions, such as sending a message, creating a purchase, or deleting data. Enforce product authorization before creating or restoring the session, especially for workspace-owned connections.
64
65
-See [Configuring sessions](/docs/configuring-sessions) for toolkit and tool filters, and [Approval mode](/docs/approval-mode) to have a session ask the user before it runs the tools you choose.
65
+See [Configuring sessions](/docs/configuring-sessions) for toolkit and tool filters, and [Approvals](/docs/approvals) to have a session ask the user before it runs the tools you choose.
66
67
## 5. Persist the right state
68
docs/content/docs/sessions-vs-direct-execution.mdx
+2
-2
@@ -13,7 +13,7 @@ A **session** is the runtime context Composio creates for one of your users with
13
Direct execution is a legacy interface that remains supported for existing integrations. We recommend sessions for new integrations and encourage existing users to [migrate to sessions](/docs/migration-guide/direct-to-sessions). Sessions handle runtime tool discovery, authentication, and execution.
14
</Callout>
15
16
-If your application needs a fixed tool set, consider the [direct tools preset](/docs/configuring-sessions#direct-tools-preset) within a session. If you need approval before execution, use [approval mode](/docs/approval-mode): the session asks the user before it runs the tools you choose, including calls inside meta tools that execute multiple app tools. The comparison below describes the tradeoffs when maintaining a direct-execution integration.
16
+If your application needs a fixed tool set, consider the [direct tools preset](/docs/configuring-sessions#direct-tools-preset) within a session. If you need approval before execution, use [approvals](/docs/approvals): the session asks the user before it runs the tools you choose, including calls inside meta tools that execute multiple app tools. The comparison below describes the tradeoffs when maintaining a direct-execution integration.
17
18
| | Sessions | Direct execution |
19
|---|---|---|
@@ -23,7 +23,7 @@ If your application needs a fixed tool set, consider the [direct tools preset](/
23
| **Memory** | Meta tools share context across calls, storing discovered IDs and relationships | You manage state between calls |
24
| **Auth** | [In-chat](/docs/authentication#in-chat-authentication): agent prompts the user to connect when needed. Also supports [manual](/docs/authentication/manually-authenticating) | You build the auth flow with [connect links](/docs/tools-direct/authenticating-tools) |
25
| **[Sandbox](/docs/sandbox/remote)** | Built in, large responses offloaded automatically | Not available |
26
-| **Human approval** | [Approval mode](/docs/approval-mode) asks the user before the tools you choose run, including inside meta tools | You intercept before each call in your code |
26
+| **Human approval** | [Approvals](/docs/approvals) ask the user before the tools you choose run, including inside meta tools | You intercept before each call in your code |
27
| **Latency** | Multiple LLM turns (search, then execute) | Single call |
28
29
Sessions are configurable. [Restrict toolkits](/docs/configuring-sessions), set [auth configs](/docs/auth-configuration/custom-auth-configs) for white-labeled OAuth, and pin [connected accounts](/docs/configuring-sessions#account-selection). See [Configuring Sessions](/docs/configuring-sessions) for the full list.
docs/content/docs/tool-tags.mdx
+3
-3
@@ -44,13 +44,13 @@ console.log(tool.tags);
44
A session can allow, block or require approval for tools by their tag, and override this for specific toolkits:
45
46
- To block tools, see [Filtering tools by tags](/docs/configuring-sessions#filtering-tools-by-tags).
47
-- To require approval, see [Approval mode](/docs/approval-mode).
47
+- To require approval, see [Approvals](/docs/approvals).
48
49
## Next
50
51
<Card
52
icon={<Wrench />}
53
- title="Approval mode"
54
- href="/docs/approval-mode"
53
+ title="Approvals"
54
+ href="/docs/approvals"
55
description="Require the user's approval before tools run."
56
/>
docs/lib/home-navigation.ts
+2
-2
@@ -130,7 +130,7 @@ export const DOCS_PRODUCTS = {
130
'/docs/how-composio-works',
131
'/docs/configuring-sessions',
132
'/docs/session-configs',
133
- '/docs/approval-mode',
133
+ '/docs/approvals',
134
'/docs/instant-tools',
135
'/docs/toolkits',
136
'/docs/tool-tags',
@@ -168,7 +168,7 @@ export const DOCS_PRODUCTS = {
168
{ url: '/docs/how-composio-works', label: 'What is a Session?' },
169
{ url: '/docs/configuring-sessions' },
170
{ url: '/docs/session-configs' },
171
- { url: '/docs/approval-mode' },
171
+ { url: '/docs/approvals' },
172
{ url: '/docs/sessions-via-mcp' },
173
],
174
},