@devries-cameron20 / composio-1 / commits / 58fa50e49
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.

docs(cli): split the changelog into the 0.4.0 to 0.4.4 releases (#4889)

This PR: - moves the 29 entries of the CLI changelog's `Unreleased` section, which had collected everything since 0.3.3, under `## 0.4.4`, `0.4.3`, `0.4.2`, `0.4.1` and `0.4.0` - assigns each entry to the first stable release whose source commit contains the commit that added it, using each release's `targetCommitish` - keeps an empty `## Unreleased` heading on top, as when 0.3.3 was recorded - changes only headings and order: the sorted text lines match `next` exactly - keeps every section under `### Patch Changes`, as the source listed them, including 0.4.0

Alberto Schiabel committed Oct 15, 2026 at 17:08 UTC 58fa50e49e6dfbf0c7247f76b2db1c3940f5ac5a
1 file changed +47 -32
ts/packages/cli/CHANGELOG.md
+47 -32
@@ -2,6 +2,8 @@
2
3 ## Unreleased
4
5 +## 0.4.4
6 +
7 ### Patch Changes
8
9 - `composio execute` and the `execute()` helper in `composio run` scripts now
@@ -11,6 +13,14 @@
13 `instant charge: <amount> USD`. The CLI used to create Tool Router sessions
14 without asking for the charge and dropped it from the response, so a billed
15 call looked free.
16 +- The CLI now runs on the stable Effect 4 line (`effect@4.0.3`, up from
17 + `4.0.0-rc.117`). No command changes on purpose. One parsing difference comes
18 + with the framework: an argument that is a negative number, such as `-5`, is
19 + now read as a value instead of as a flag.
20 +
21 +## 0.4.3
22 +
23 +### Patch Changes
24
25 - `composio execute` (including meta tools), `composio proxy`, the `proxy()`
26 helper in `composio run` scripts, and the custom tool schema lookup in
@@ -18,19 +28,16 @@
28 such as an approval, before it can run. The CLI cannot answer input requests
29 yet, and it no longer treats such an answer as a result. The `proxy()` helper
30 used to return an empty `200` response for a call that never ran.
21 -
31 - `composio execute` now reads whether a tool succeeded from the `result_type`
32 the API returns with every execution, so a tool that ran and failed is
33 reported as failed even when the API returns no error text. It used to read a
34 failed execution with a `null` error as successful.
26 -
35 - `composio execute` now validates the arguments before it sends the tool
36 call, so a call that fails local validation is never run. Validation used to
37 race the request, and the tool could execute while the CLI reported a
38 validation failure. The cached schema named in the validation error is now
39 kept on disk instead of being deleted. A schema the CLI cannot compile no
40 longer blocks the call; the server still validates it.
33 -
41 - Generate help from the command definitions, including every supported flag and
42 nested command. Remove help levels and the nonexistent `files` help topic.
43 Install agent skills with `composio setup skill <claude|codex|openclaw>`
@@ -40,14 +47,11 @@
47 Debug flags after the `run` script boundary now reach the script unchanged.
48 `composio execute <slug> --help` now shows command options. Use
49 `composio execute <slug> --get-schema` to print that tool's input schema as JSON.
43 -
50 - `composio execute` (including meta tools) and `composio proxy` are never
51 retried, so a request that timed out or failed after the backend already
52 acted cannot repeat a side effect such as sending the same email twice.
47 -
53 - API requests and command analytics now report CLI product/version, language,
54 runtime/version, and the installed API client version separately.
50 -
55 - Remove the experimental local-tools stack: the `local-tools` command group,
56 the `local_tools` experimental flag, `LOCAL_*` tool execution, `dev native-ui`,
57 and the bundled macOS sidecars (peekaboo, imessage-cli, composio-native-ui).
@@ -78,6 +82,11 @@
82 `run-subagent-*.mjs` files and six `acp-adapters/*` paths) as intentionally
83 empty placeholders so that a CLI installed before this change still passes
84 its upgrade verification. No adapter binaries are downloaded or shipped.
85 +
86 +## 0.4.2
87 +
88 +### Patch Changes
89 +
90 - Every Composio API call now goes through the `@composio/client` 2.0 runtime,
91 the same client `@composio/core` uses. Org, project, session-info, and
92 consumer lookups gain the client's retries and redirect handling, and API
@@ -106,10 +115,42 @@
115 - `composio generate` now keeps tool and trigger metadata as inert data in
116 generated Python and TypeScript sources. Crafted slugs and descriptions can
117 no longer inject code into generated modules.
118 +- `composio orgs --help`, `composio signup --help`, the `agent` family pages (signup,
119 + login, whoami, inbox, claim), and the group help pages for `connections`, `triggers`,
120 + `artifacts`, and `install` now render the same curated, styled help page as every
121 + other command family, instead of falling back to the framework's raw flag dump.
122 + `composio help <command>` is now a supported spelling of command help (`composio help
123 +orgs` shows the same page as `composio orgs --help`, with the same longest-prefix
124 + fallback for deeper paths); an unknown target fails through the framework parser like
125 + any other unknown command. The `orgs` description in contextual error help now matches
126 + the command's actual description.
127 +- `composio listen <slug> --stream` without a path is accepted again and streams
128 + the whole event payload. It previously failed with
129 + `Received unknown argument: '--stream='`.
130 +- `composio listen` reports an unknown trigger slug as such. A mistyped slug
131 + used to fail with a missing-connection error for the toolkit inferred from its
132 + prefix, or with a generic trigger-creation error when that toolkit already had
133 + an active account.
134 +- `composio tools info`, and the other `info`, `create`, `enable`, `disable`,
135 + and `status` commands that share its API error handling, now exit non-zero on
136 + an API error and print the error when stderr is not a terminal. `composio tools
137 +info <unknown-slug>` used to print nothing and exit 0 when piped.
138 +- Help examples use `SLACK_SEND_MESSAGE` and `SLACK_CHANNEL_MESSAGE_RECEIVED`
139 + instead of a removed Slack tool slug and a trigger without configuration.
140 +
141 +## 0.4.1
142 +
143 +### Patch Changes
144 +
145 - `composio upgrade` (and any other command with a long spinner message) no
146 longer scrolls endlessly in terminals narrower than that message. The spinner
147 printed its line hundreds of times instead of animating in place; live spinner
148 text is now clamped to a single terminal row.
149 +
150 +## 0.4.0
151 +
152 +### Patch Changes
153 +
154 - `composio upgrade` shows download progress. The archive is a few hundred
155 megabytes, and the command previously printed `Downloading...` once and then
156 said nothing for minutes, which was indistinguishable from a hang. It now
@@ -135,32 +176,6 @@
176 `https://staging-dashboard.composio.dev/`.
177 - `composio dev auth-configs create` now sends custom OAuth credentials and scopes
178 in the API's expected shape instead of failing validation.
138 -- `composio orgs --help`, `composio signup --help`, the `agent` family pages (signup,
139 - login, whoami, inbox, claim), and the group help pages for `connections`, `triggers`,
140 - `artifacts`, and `install` now render the same curated, styled help page as every
141 - other command family, instead of falling back to the framework's raw flag dump.
142 - `composio help <command>` is now a supported spelling of command help (`composio help
143 -orgs` shows the same page as `composio orgs --help`, with the same longest-prefix
144 - fallback for deeper paths); an unknown target fails through the framework parser like
145 - any other unknown command. The `orgs` description in contextual error help now matches
146 - the command's actual description.
147 -- `composio listen <slug> --stream` without a path is accepted again and streams
148 - the whole event payload. It previously failed with
149 - `Received unknown argument: '--stream='`.
150 -- `composio listen` reports an unknown trigger slug as such. A mistyped slug
151 - used to fail with a missing-connection error for the toolkit inferred from its
152 - prefix, or with a generic trigger-creation error when that toolkit already had
153 - an active account.
154 -- `composio tools info`, and the other `info`, `create`, `enable`, `disable`,
155 - and `status` commands that share its API error handling, now exit non-zero on
156 - an API error and print the error when stderr is not a terminal. `composio tools
157 -info <unknown-slug>` used to print nothing and exit 0 when piped.
158 -- Help examples use `SLACK_SEND_MESSAGE` and `SLACK_CHANNEL_MESSAGE_RECEIVED`
159 - instead of a removed Slack tool slug and a trigger without configuration.
160 -- The CLI now runs on the stable Effect 4 line (`effect@4.0.3`, up from
161 - `4.0.0-rc.117`). No command changes on purpose. One parsing difference comes
162 - with the framework: an argument that is a negative number, such as `-5`, is
163 - now read as a value instead of as a flag.
179
180 ## 0.3.3
181