Skip to main content

Python SDK 0.14.0 removes the legacy custom-tool registry

Python SDK composio 0.14.0 removes the legacy composio.tools.custom_tool registry. It was an older, separate custom-tool path that duplicated the Tool Router model and made it unclear which execution surface a tool belonged to.

SDK versions

Breaking change

Breaking changecomposio.tools.custom_tool, core.models.custom_tools, and their legacy execution wiring were removed. Use composio.experimental.tool() and composio.experimental.Toolkit with a Tool Router session instead.
The current custom-tool APIs support inline execution and Tool Router preload, attach, and reuse flows. They are the only custom-tool path supported by the SDK.

Migration

  1. Replace @composio.tools.custom_tool with @composio.experimental.tool.
  2. Change the tool signature from a request object plus execution callback to input, ctx.
  3. Attach the tool when creating the session through experimental.custom_tools.
Before:
After:
For a tool that calls a toolkit API, set extends_toolkit on the decorator and use ctx.proxy_execute(...) from the function body.