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, 23:30 UTC
docs: address PR review comments
- Revert changelog addition (don't modify older changelogs) - Remove version management row from sessions-vs-direct-execution table - Remove agentic consumption claim from trigger versioning note Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: rahul.lingala <rahul.lingala@composio.dev>
Zen Agent committed
Apr 14, 2026 at 06:01 UTC
afd22ab78886fe9c0427a7bf0bc372f68f5167b6
3 files changed
+1
-4
docs/content/changelog/04-08-26-v31-api.mdx
-2
@@ -40,8 +40,6 @@ Every non-tool endpoint (`/auth_configs`, `/connected_accounts`, `/triggers`, `/
40
2. If you depend on a specific pinned version, pass it explicitly — `version=00000000_00` for most endpoints, or `toolkit_versions=00000000_00` for `GET /tools` (see table above)
41
3. If you were already passing `version: "latest"` (or `toolkit_versions: "latest"`), you can drop the parameter entirely on v3.1
42
43
-**Which default is right for you?** If your application passes tool outputs to an LLM or AI agent, the v3.1 default (`latest`) is the better fit — agents interpret responses dynamically and benefit from always having the newest tools. If your code parses tool outputs programmatically (e.g., destructuring specific fields or mapping to a database schema), pin to a specific version so schema changes don't silently break your integration. See [Toolkit Versioning](/docs/tools-direct/toolkit-versioning#choosing-between-latest-and-a-pinned-version) for details.
44
-
43
**Before (v3):**
44
```bash
45
curl "https://backend.composio.dev/api/v3/tools/GMAIL_SEND_EMAIL?version=latest" \
docs/content/docs/sessions-vs-direct-execution.mdx
-1
@@ -19,7 +19,6 @@ Use sessions unless you need full control over which tools are available and whe
19
| **Auth** | [In-chat](/docs/authenticating-users/in-chat-authentication): agent prompts the user to connect when needed. Also supports [manual](/docs/authenticating-users/manually-authenticating) | You build the auth flow with [connect links](/docs/tools-direct/authenticating-tools) |
20
| **[Workbench](/docs/workbench)** | Built in, large responses offloaded automatically | Not available |
21
| **Human approval** | You configure approval rules on the session. Harder to intercept individual calls since tools are discovered dynamically | You intercept before each call in your code |
22
-| **Version management** | Always uses `latest` — ideal for agentic workflows where an LLM interprets outputs | You [choose the version](/docs/tools-direct/toolkit-versioning#choosing-between-latest-and-a-pinned-version): `latest` for agent-consumed outputs, pinned for programmatic parsing |
22
| **Latency** | Multiple LLM turns (search, then execute) | Single call |
23
24
Sessions are configurable. You can [enable or disable specific toolkits](/docs/toolkits/enable-and-disable-toolkits), set [auth configs](/docs/auth-configuration/custom-auth-configs) for white-labeled OAuth, and pin specific [connected accounts](/docs/configuring-sessions#account-selection). See [Configuring Sessions](/docs/configuring-sessions) for the full list.
docs/content/docs/setting-up-triggers/creating-triggers.mdx
+1
-1
@@ -73,7 +73,7 @@ console.log(`Trigger created: ${trigger.triggerId}`);
73
</Tabs>
74
75
<Callout>
76
-Trigger instances default to `'latest'` toolkit version. This is the recommended setting for most use cases — trigger payloads are typically consumed by an LLM or agent that adapts to response changes dynamically. If your code parses trigger payloads programmatically against a fixed schema, you can pin a specific version at SDK initialization. See [Toolkit Versioning](/docs/tools-direct/toolkit-versioning#choosing-between-latest-and-a-pinned-version) for details.
76
+Trigger instances default to the `'latest'` toolkit version. If your code parses trigger payloads programmatically against a fixed schema, you can pin a specific version at SDK initialization. See [Toolkit Versioning](/docs/tools-direct/toolkit-versioning#choosing-between-latest-and-a-pinned-version) for details.
77
</Callout>
78
79
## Using the dashboard