Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
feat(core): update clients to 2.0.0-rc.12, add `session.executeMeta` (#4842)
## Summary This PR: - updates the owned API clients to `@composio/client@2.0.0-rc.12` and `composio-client==2.0.0rc12` (see https://github.com/ComposioHQ/composio-client/pull/75) - adds `session.executeMeta()` (TypeScript) and `session.execute_meta()` (Python), the one live client endpoint neither SDK wrapped - passes `user_id` to `tools.proxy` as a native client argument in Python, replacing the `extra_body` workaround that was waiting on this release - adds the `ToolRouterSessionMetaToolSlug` type to both SDKs, covering the 9 `COMPOSIO_*` slugs the endpoint accepts `executeMeta` follows each SDK's existing `execute`: same result type (including `resultType` / `result_type`), the input-required error when the tool needs user input, a validation error when the answer has no known result type, and no retries. ```typescript const { data, resultType } = await session.executeMeta('COMPOSIO_SEARCH_TOOLS', { queries: [{ use_case: 'send an email' }], }); ``` ```python result = session.execute_meta( "COMPOSIO_SEARCH_TOOLS", arguments={"queries": [{"use_case": "send an email"}]}, ) ``` Designated PR reviewer: @jkomyno ## Changes - `pnpm-workspace.yaml`, `python/pyproject.toml`, `python/setup.py`: client pins. `pnpm-lock.yaml` and `uv.lock` change only for the client entry. - `ToolRouterSession.executeMeta` / `ToolRouterSession.execute_meta`: forward the slug, arguments and inline custom tool definitions to the meta endpoint. - Python `require_execute_meta_result`: returns the meta answer as the session execute response, with the fields as the client parsed them. - Two changesets: a patch for the client bump and a minor for `executeMeta`, both for `@composio/core` and `@composio/slim`. ## Type of change - [ ] Bug fix - [x] New feature - [x] Refactor/Chore - [ ] Documentation - [ ] Breaking change ## How Has This Been Tested? - `@composio/core`: typecheck, and the full Vitest suite (1804 passed, 2 expected failures). - Typecheck for `@composio/cli` and `@composio/experimental` against rc.12. - Python: full pytest suite (2284 passed, 77 skipped); ruff check and format on the changed files; `uv lock --check`. - New tests cover the request sent to the meta endpoint, the returned result, the input-required error and the unknown `result_type` error in both SDKs. A Python test fails if the local slug list drifts from the client's `execute_meta` signature. - Merged with #4764 locally: no conflicts, core typecheck passes, and the session tests of both SDKs pass on the combined code. ## Checklist - [x] I have read the Code of Conduct and this PR adheres to it - [x] I ran linters/tests locally and they passed - [x] I added tests or explain why not applicable - [x] I added a changeset if this change affects published packages ## Additional context - `session.execute()` already accepts meta tool slugs. `executeMeta` adds a meta-only entry point with a typed slug, not a new capability. - Custom tools named inside a `COMPOSIO_MULTI_EXECUTE_TOOL` call are not run in-process by `executeMeta`, which matches `session.execute()` today. - When arguments are omitted, TypeScript sends `{}` and Python omits the field. Each mirrors its own `execute`. - The other client methods neither SDK wraps are deprecated in the API spec (`tools.retrieveRequiredScopes` and the MCP instance and app methods), so they are left out on purpose. - The Python client's params `TypedDict` for this endpoint lists 7 of the 9 slugs that its method signature accepts.