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, 07:15 UTC
docs(skills): classify intent before restricting sessions
Brendan O'Leary committed
Oct 29, 2026 at 18:10 UTC
8ac99a30e82383835735520cd5b127b1f3e42368
1 file changed
+2
skills/composio/references/platform.md
+2
@@ -130,6 +130,8 @@ 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.
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
137
If the application has its own connect UI, use session authorization and connection-state methods and suppress in-chat connection prompts. Use managed auth initially. Create a custom auth config only for the application's OAuth branding, additional scopes, dedicated provider quotas, or self-hosted or regional requirements.