What changes
Migrating
1
Pass your existing auth configs to the session
You already have auth configs (e.g. Since the session uses the same
ac_github_config, ac_slack_config). Pass them when creating a session so it uses your existing OAuth credentials and your users’ connected accounts carry over.- Python
- TypeScript
- API
user_id and auth configs, it automatically picks up existing connected accounts. No re-authentication needed.2
Replace manual tool fetching with session tools
Instead of fetching specific tools by name, get the session’s meta tools. These let the agent discover, authenticate, and execute any tool at runtime.
- Python
- TypeScript
- API
3
Remove manual auth flows
If you were manually creating connect links and waiting for connections, sessions handle this automatically. When a tool requires authentication, the agent prompts the user with a connect link in-chat.
- Python
- TypeScript
- API
4
Remove toolkit version management
If you were pinning toolkit versions in your code or environment variables, you can remove that. Sessions handle versioning automatically.
- Python
- TypeScript
- API
Restricting toolkits
If you were fetching tools from specific toolkits, you can restrict the session to only those toolkits:- Python
- TypeScript
- API
Multiple connected accounts
If your users have multiple accounts for the same toolkit (e.g., work and personal Gmail), you can specify which one to use per session:- Python
- TypeScript
- API
Triggers
Triggers don’t work with sessions yet. Continue using them the same way you do today withcomposio.triggers.create(), composio.triggers.enable(), and webhook subscriptions.
See Triggers for setup instructions.
White labeling
If you’ve set up white-labeled OAuth screens with custom auth configs, those carry over automatically. Just pass the same auth config IDs to your session viaauth_configs / authConfigs. Your users will continue to see your branding on consent screens.
See White-labeling authentication for more.