@devries-cameron20 / composio Mirror · read-only / commits / d102ab03c
Fork 0

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

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 19:45 UTC

Release: update version (#3676)

This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated. # Releases ## @composio/core@0.13.0 ### Minor Changes - d17a268: Add the first-class `composio.sessions.create()` API while keeping `composio.create()` as an alias, expose the experimental shared-connection ACL patch helper as `connectedAccounts.updateAcl()` while keeping `experimental.updateAcl()` as an alias, and include SDK docs/source in the published package. **MCP is now opt-in.** Sessions return native tools by default; the hosted MCP endpoint is only surfaced on the type when you create the session with `{ mcp: true }`. The default `create()` / `use()` now return `SessionWithoutMcp` (the runtime object is unchanged — `session.mcp` still exists at runtime — but it is no longer in the type). Migration: read `session.mcp` only after creating with `{ mcp: true }`. - d17a268: Surface the resolved workbench config on Tool Router sessions. - `Session.workbench` is now populated from the API response (on create/retrieve/attach/update). It exposes the resolved workbench config, e.g. `session.workbench?.enable` (defaults to `true` server-side). This lets callers create a session with the remote workbench disabled (`workbench: { enable: false }`) and detect that state — the foundation for running code in a sandbox you own via the experimental `@composio/experimental/workbench` helpers. ### Patch Changes - d17a268: Prefer `sandbox` for session code-execution configuration while continuing to accept the existing `workbench` alias. - d17a268: Add `triggers.parse()` to parse and optionally verify incoming webhook requests. - d17a268: Add `triggers.setWebhookSubscription()` to create or update the project webhook subscription from the TypeScript SDK. ## @composio/experimental@0.1.0 ### Minor Changes - d17a268: Add the experimental BYO local workbench helpers on the new `@composio/experimental/workbench` subpath. These let you run a Composio Tool Router session in a sandbox you own instead of Composio's hosted remote sandbox: - `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). - `experimental_createWorkbenchEnv(options)` builds the environment variables the in-sandbox helper needs to reach Composio. - `experimental_createPythonWorkbenchHelperSource(options)` returns the Python helper source. 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`. > **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. - d17a268: Add an experimental package with a Pi coding-agent provider, static Composio tool wrapping, and dynamic Tool Router session helpers. ### Patch Changes - 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. ## @composio/slim@0.13.0 ### Minor Changes - d17a268: Add a slim Composio core package that mirrors the built `@composio/core` runtime and types without publishing the packaged `docs/` or `src/` trees. ## @composio/cli@0.3.1 ### Patch Changes - Updated dependencies [d17a268] - Updated dependencies [d17a268] - Updated dependencies [d17a268] - Updated dependencies [d17a268] - Updated dependencies [d17a268] - @composio/core@0.13.0 - @composio/cli-local-tools@0.1.1 ## @composio/cli-local-tools@0.1.1 ### Patch Changes - Updated dependencies [d17a268] - Updated dependencies [d17a268] - Updated dependencies [d17a268] - Updated dependencies [d17a268] - Updated dependencies [d17a268] - @composio/core@0.13.0 Co-authored-by: Rahul Tarak <cryogenicplanet@gmail.com>

sdkrelease[bot] committed Jun 25, 2026 at 18:54 UTC d102ab03ca22b3275b5b6d6768c3831bc1b4042d
16 files changed +56 -67
.changeset/add-slim-package.md deleted
-5
@@ -1,5 +0,0 @@
1 ----
2 -"@composio/slim": minor
3 ----
4 -
5 -Add a slim Composio core package that mirrors the built `@composio/core` runtime and types without publishing the packaged `docs/` or `src/` trees.
.changeset/bright-lions-jam.md deleted
-9
@@ -1,9 +0,0 @@
1 ----
2 -'@composio/core': minor
3 ----
4 -
5 -Add the first-class `composio.sessions.create()` API while keeping `composio.create()` as an alias, expose the experimental shared-connection ACL patch helper as `connectedAccounts.updateAcl()` while keeping `experimental.updateAcl()` as an alias, and include SDK docs/source in the published package.
6 -
7 -**MCP is now opt-in.** Sessions return native tools by default; the hosted MCP endpoint is only surfaced on the type when you create the session with `{ mcp: true }`. The default `create()` / `use()` now return `SessionWithoutMcp` (the runtime object is unchanged — `session.mcp` still exists at runtime — but it is no longer in the type).
8 -
9 -Migration: read `session.mcp` only after creating with `{ mcp: true }`.
.changeset/byos-local-workbench.md deleted
-9
@@ -1,9 +0,0 @@
1 ----
2 -'@composio/core': minor
3 ----
4 -
5 -Surface the resolved workbench config on Tool Router sessions.
6 -
7 -- `Session.workbench` is now populated from the API response (on create/retrieve/attach/update). It exposes the resolved workbench config, e.g. `session.workbench?.enable` (defaults to `true` server-side).
8 -
9 -This lets callers create a session with the remote workbench disabled (`workbench: { enable: false }`) and detect that state — the foundation for running code in a sandbox you own via the experimental `@composio/experimental/workbench` helpers.
.changeset/config.json
+1 -1
@@ -14,5 +14,5 @@
14 "___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {
15 "onlyUpdatePeerDependentsWhenOutOfRange": true
16 },
17 - "ignore": []
17 + "ignore": ["@composio/cli", "@composio/cli-local-tools"]
18 }
.changeset/experimental-local-workbench.md deleted
-15
@@ -1,15 +0,0 @@
1 ----
2 -'@composio/experimental': minor
3 ----
4 -
5 -Add the experimental BYO local workbench helpers on the new `@composio/experimental/workbench` subpath.
6 -
7 -These let you run a Composio Tool Router session in a sandbox you own instead of Composio's hosted remote sandbox:
8 -
9 -- `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).
10 -- `experimental_createWorkbenchEnv(options)` builds the environment variables the in-sandbox helper needs to reach Composio.
11 -- `experimental_createPythonWorkbenchHelperSource(options)` returns the Python helper source.
12 -
13 -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`.
14 -
15 -> **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.
.changeset/experimental-pi-provider.md deleted
-5
@@ -1,5 +0,0 @@
1 ----
2 -"@composio/experimental": minor
3 ----
4 -
5 -Add an experimental package with a Pi coding-agent provider, static Composio tool wrapping, and dynamic Tool Router session helpers.
.changeset/local-workbench-proxy-execute.md deleted
-5
@@ -1,5 +0,0 @@
1 ----
2 -'@composio/experimental': patch
3 ----
4 -
5 -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.
.changeset/sdk-sandbox-alias.md deleted
-5
@@ -1,5 +0,0 @@
1 ----
2 -'@composio/core': patch
3 ----
4 -
5 -Prefer `sandbox` for session code-execution configuration while continuing to accept the existing `workbench` alias.
.changeset/triggers-parse-helper.md deleted
-5
@@ -1,5 +0,0 @@
1 ----
2 -'@composio/core': patch
3 ----
4 -
5 -Add `triggers.parse()` to parse and optionally verify incoming webhook requests.
.changeset/webhook-subscription-sdk.md deleted
-5
@@ -1,5 +0,0 @@
1 ----
2 -'@composio/core': patch
3 ----
4 -
5 -Add `triggers.setWebhookSubscription()` to create or update the project webhook subscription from the TypeScript SDK.
ts/packages/core/CHANGELOG.md
+22
@@ -1,5 +1,27 @@
1 # @composio/core
2
3 +## 0.13.0
4 +
5 +### Minor Changes
6 +
7 +- d17a268: Add the first-class `composio.sessions.create()` API while keeping `composio.create()` as an alias, expose the experimental shared-connection ACL patch helper as `connectedAccounts.updateAcl()` while keeping `experimental.updateAcl()` as an alias, and include SDK docs/source in the published package.
8 +
9 + **MCP is now opt-in.** Sessions return native tools by default; the hosted MCP endpoint is only surfaced on the type when you create the session with `{ mcp: true }`. The default `create()` / `use()` now return `SessionWithoutMcp` (the runtime object is unchanged — `session.mcp` still exists at runtime — but it is no longer in the type).
10 +
11 + Migration: read `session.mcp` only after creating with `{ mcp: true }`.
12 +
13 +- d17a268: Surface the resolved workbench config on Tool Router sessions.
14 +
15 + - `Session.workbench` is now populated from the API response (on create/retrieve/attach/update). It exposes the resolved workbench config, e.g. `session.workbench?.enable` (defaults to `true` server-side).
16 +
17 + This lets callers create a session with the remote workbench disabled (`workbench: { enable: false }`) and detect that state — the foundation for running code in a sandbox you own via the experimental `@composio/experimental/workbench` helpers.
18 +
19 +### Patch Changes
20 +
21 +- d17a268: Prefer `sandbox` for session code-execution configuration while continuing to accept the existing `workbench` alias.
22 +- d17a268: Add `triggers.parse()` to parse and optionally verify incoming webhook requests.
23 +- d17a268: Add `triggers.setWebhookSubscription()` to create or update the project webhook subscription from the TypeScript SDK.
24 +
25 ## 0.12.0
26
27 ### Minor Changes
ts/packages/core/package.json
+1 -1
@@ -1,7 +1,7 @@
1 {
2 "name": "@composio/core",
3 "type": "module",
4 - "version": "0.12.0",
4 + "version": "0.13.0",
5 "description": "",
6 "main": "src/index.ts",
7 "publishConfig": {
ts/packages/experimental/CHANGELOG.md new
+23
@@ -0,0 +1,23 @@
1 +# @composio/experimental
2 +
3 +## 0.1.0
4 +
5 +### Minor Changes
6 +
7 +- d17a268: Add the experimental BYO local workbench helpers on the new `@composio/experimental/workbench` subpath.
8 +
9 + These let you run a Composio Tool Router session in a sandbox you own instead of Composio's hosted remote sandbox:
10 +
11 + - `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).
12 + - `experimental_createWorkbenchEnv(options)` builds the environment variables the in-sandbox helper needs to reach Composio.
13 + - `experimental_createPythonWorkbenchHelperSource(options)` returns the Python helper source.
14 +
15 + 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`.
16 +
17 + > **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.
18 +
19 +- d17a268: Add an experimental package with a Pi coding-agent provider, static Composio tool wrapping, and dynamic Tool Router session helpers.
20 +
21 +### Patch Changes
22 +
23 +- 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.
ts/packages/experimental/package.json
+1 -1
@@ -1,6 +1,6 @@
1 {
2 "name": "@composio/experimental",
3 - "version": "0.0.1",
3 + "version": "0.1.0",
4 "description": "Experimental Composio integrations and helpers",
5 "main": "src/index.ts",
6 "type": "module",
ts/packages/slim/CHANGELOG.md new
+7
@@ -0,0 +1,7 @@
1 +# @composio/slim
2 +
3 +## 0.13.0
4 +
5 +### Minor Changes
6 +
7 +- d17a268: Add a slim Composio core package that mirrors the built `@composio/core` runtime and types without publishing the packaged `docs/` or `src/` trees.
ts/packages/slim/package.json
+1 -1
@@ -1,7 +1,7 @@
1 {
2 "name": "@composio/slim",
3 "type": "module",
4 - "version": "0.0.1",
4 + "version": "0.13.0",
5 "description": "Slim Composio core package without packaged source or docs",
6 "main": "dist/index.mjs",
7 "publishConfig": {