What carries over
Keep your agent integration, application user IDs, and unaffected toolkits and connections. If you already use Sessions, you don’t need to migrate to a different execution model.Choose a replacement
Instant support is per tool. Check each tool’s support, rate, and input schema before replacing it.
Update your application
First, enable Instant and check your organization’s balance. Then replace affected toolkit references, tool names, arguments, and response handling in your application. For example, replacecomposio_search with exa in your Session’s toolkit filter, choose the replacement search action, and update any tool restrictions. Keep the other toolkits your agent needs. Use the existing Session and agent examples for your framework.
If your Session already permits eligible Instant tools, keep that policy. If it disables Instant, restricts it to other tools, or selects a provider account explicitly, follow Control Instant usage and Know which account runs the tool.
Update or recreate existing Sessions that reference retired toolkits, and update saved configurations for future Sessions. Enabling Instant doesn’t rewrite these references.
Keeping retired toolkit references in your Session configuration doesn’t block Session creation, but retired tools remain unavailable. Remove any retired tools listed in preload.tools.
If you call tools directly
composio.tools.execute() is a different execution path from Sessions. A Session’s instant policy doesn’t configure direct-tool calls.
To keep direct execution, replace retired tool references. To choose Instant explicitly, pass connected_account_id="instant_account" to composio.tools.execute() in Python or connectedAccountId: "instant_account" in TypeScript. Instant runs the latest toolkit version, so a call pinned to an older version fails. To run latest, the SDKs also need dangerously_skip_version_check=True in Python or dangerouslySkipVersionCheck: true in TypeScript; see Use the latest version. An older toolkit version isn’t a way to preserve retired shared access.
Alternatively, follow Migrate from Direct Tools to Sessions. This is a separate migration; agents already using Sessions don’t need it.
Verify before the cutoff
- Check the published rate for each replacement tool.
- Replace affected toolkit and tool references, including saved configurations. Check request and response differences for each replacement.
- Test your agent or direct execution path, then check the execution logs for the credential source and charge.
- Check existing Sessions and pinned direct-tool versions. A successful replacement call doesn’t prove every old workflow has migrated.