Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

next
md 92 lines 5.83 KB
Rendered Raw
1 # @composio/experimental
2
3 ## 0.2.9
4
5 ### Patch Changes
6
7 - d5c1861: Update runtime dependencies, require patched Zod 4 releases where used directly, support Anthropic SDK 1.6, and update the AutoGen provider's FLAML dependency. Preserve Zod 3 compatibility fixtures and existing framework version boundaries.
8
9 ## 0.2.8
10
11 ### Patch Changes
12
13 - fd59eba: Update SDK and provider dependencies to compatible releases. Accept Anthropic SDK 0.132 and OpenAI Agents 0.20 in provider peer ranges, and add Pi coding-agent 1.x to the experimental provider's supported peer range.
14
15 ## 0.2.7
16
17 ### Patch Changes
18
19 - 1afd8be: Stop re-sending a workbench tool execution after a network failure. The Python `run_composio_tool` helper retried a timed-out or dropped request up to three more times, so a tool the backend had already run could repeat its side effect, such as sending the same email twice. It now returns the error after the first attempt; rate-limited (429) requests still retry.
20 - 31e8b3f: Report a failed tool execution and a call that needs user input as errors from the Python workbench helpers. `run_composio_tool` returned an empty error, which reads as success, for a `failed` execution without error text and for an `input_required` answer, and `proxy_execute` returned `(None, "")` for a proxied call that needs user input. Both now return a non-empty error. For `input_required` the error says that the call needs user input and was not executed, and `run_composio_tool` returns the questions as `input_requests` without the opaque `request_state`.
21
22 ## 0.2.6
23
24 ### Patch Changes
25
26 - 485c09d: Refresh runtime dependencies and support Anthropic SDK 0.127 in the Anthropic provider.
27
28 ## 0.2.5
29
30 ### Patch Changes
31
32 - 7055914: Move published dependency ranges to their current upstream releases: zod 4.5, openai 7.10, typebox 1.3.27, @mastra/schema-compat 1.3.8, and @cloudflare/workers-types 5.20260905. `@composio/anthropic` also accepts `@anthropic-ai/sdk` 0.124 as a peer, the line it is now tested against.
33 - 100d568: Stamp eve's durable callback descriptors on the tools `EveProvider` wraps. eve only stamps descriptors on `defineTool` calls it finds in an agent's own source, so tools built inside `node_modules` were rejected at resolve time and every Composio tool was dropped from the step. Each wrapped tool now persists only its slug and an id for the resolve that produced it, and re-attaches to that resolve's Composio executor when eve replays or resumes a parked call.
34
35 ## 0.2.4
36
37 ### Patch Changes
38
39 - 4e633d1: Update TypeBox to 1.3.18.
40
41 ## 0.2.3
42
43 ### Patch Changes
44
45 - db7b576: Declare Node.js 22.22.3 as the minimum supported runtime for every published TypeScript package so package managers surface incompatible runtimes before users encounter ESM loading failures.
46
47 ## 0.2.2
48
49 ### Patch Changes
50
51 - 4ceaede: Refresh the TypeBox runtime dependency.
52
53 ## 0.2.1
54
55 ### Patch Changes
56
57 - 503b50a: Refresh runtime dependencies across the TypeScript SDK packages.
58
59 ## 0.2.0
60
61 ### Minor Changes
62
63 - b07fcad: Add an eve provider: `EveProvider` makes `session.tools()` return eve-native `defineTool`s, `defineComposioTools` is the replay-safe `step.started` resolver, and `(ctx, next)` hooks can rewrite, deny, or transform Tool Router meta-tool calls.
64
65 Preserve successful local-tool results when the remote half of a mixed `COMPOSIO_MULTI_EXECUTE_TOOL` batch fails at the transport layer, so callers can see which side effects already completed before retrying.
66
67 ### Patch Changes
68
69 - 58bc93b: Refresh dependency ranges and lockfiles across the workspace.
70 - fa933a6: Fix the `homepage` links in these packages' `package.json`. They pointed at `github.com/ComposioHQ/composio/tree/main/...`, but the default branch is `next` and no `main` branch exists, so every link 404'd on npm and in editor tooltips. They now point at `tree/next/...`.
71
72 ## 0.1.0
73
74 ### Minor Changes
75
76 - d17a268: Add the experimental BYO local workbench helpers on the new `@composio/experimental/workbench` subpath.
77
78 These let you run a Composio Tool Router session in a sandbox you own instead of Composio's hosted remote sandbox:
79
80 - `experimental_createLocalWorkbenchSession(composio, session)` takes a caller-created session and returns `{ helperSource, env }`. It throws unless the session was created with `workbench: { enable: false }` (a local sandbox and the remote workbench cannot both run for one session).
81 - `experimental_createWorkbenchEnv(options)` builds the environment variables the in-sandbox helper needs to reach Composio.
82 - `experimental_createPythonWorkbenchHelperSource(options)` returns the Python helper source.
83
84 The local workbench assumes code runs in the developer's sandbox and exposes Apollo-parity Python helpers for `run_composio_tool`, `invoke_llm`, `web_search`, and `proxy_execute`.
85
86 > **Security caveat:** the helper authenticates with the developer's full _project_ API key, injected into the sandbox env as `COMPOSIO_API_KEY`. Any code or tool output running in the sandbox can read and exfiltrate it — treat the sandbox as your security boundary and rotate the key. A session-scoped `x-session-access-key` (so the long-lived project key never enters the sandbox) is the planned follow-up.
87
88 - d17a268: Add an experimental package with a Pi coding-agent provider, static Composio tool wrapping, and dynamic Tool Router session helpers.
89
90 ### Patch Changes
91
92 - d17a268: Add `proxy_execute` to the experimental local workbench helper. The in-sandbox helper from `experimental_createLocalWorkbenchSession` (`@composio/experimental/workbench`) now exposes `proxy_execute(method, endpoint, toolkit, query_params=None, body=None, headers=None)` alongside `run_composio_tool`, `invoke_llm`, and `web_search`, so a local sandbox can make authenticated direct API calls to a connected toolkit when no pre-built tool exists. It posts to the public `…/session/{id}/proxy_execute` route with the session's project API key, and always returns a `(data, error)` tuple.