@devries-cameron20 / composio-1 / commits / 4b39a6dac
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

docs(skills): separate toolkit scoping from direct tools

jkomyno committed Oct 30, 2026 at 17:59 UTC 4b39a6dac74de4d43e9eba7169a91223e3393f7a
1 file changed +1 -1
skills/composio/references/platform.md
+1 -1
@@ -130,7 +130,7 @@ Sessions expose a small set of meta tools by default so the agent can discover i
130
131 Keep connection management enabled for interactive agents. It returns a Connect Link when a user needs to authorize an app; do not build a provider OAuth flow.
132
133 -Classify the request before restricting the session. A generic capability request such as “send an email” does not select Gmail, Outlook, or a provider-specific action. Keep the default meta tools so Composio and the agent can choose the integration and tool from user intent. Narrow the session only when the user, existing application configuration, or inspected code explicitly fixes the provider or exact action.
133 +Before you restrict a session, check whether the request names a toolkit. A capability request such as "send an email" doesn't name Gmail, Outlook, or any other toolkit. Keep the default meta tools so the agent can find the toolkit and tool with `COMPOSIO_SEARCH_TOOLS`. Restrict the session only when the user, the application's configuration, or the inspected code names the toolkit. Then enable only that toolkit and keep the meta tools.
134
135 Use the direct-tools preset only for a narrow, deterministic agent with a fixed allowlist. It removes meta tools by default. Re-enable connection management when users must authenticate in the agent, and keep or disable the sandbox deliberately. Fetch `configuring-sessions.md` for the current preset and option syntax before implementing it.
136