@devries-cameron20 / composio Mirror · read-only
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, 06:00 UTC

next
md 1,275 lines 73.1 KB
Rendered Raw
1 # @composio/cli
2
3 ## Unreleased
4
5 ## 0.6.3
6
7 ### Patch Changes
8
9 - Update @composio/client to 2.1.36 to include the latest API changes.
10
11 - Release archives now include a `release-manifest.json` that lists the support files they ship. `composio upgrade` installs exactly what the manifest lists, so later releases can drop a support file without breaking upgrades. Files a release no longer lists stay in place. A release can name the oldest CLI version that may upgrade to it; an older CLI refuses it before changing anything and prints the install command to run instead.
12
13 - Agents calling `composio proxy` or `composio execute` without `-d` no longer hang for minutes with no output. Agent harnesses often run commands with a stdin pipe they never write to or close, and both commands waited for that pipe to end before sending anything.
14 - `composio proxy` reads a request body from stdin only with `-d -` (or `-d @-`). Without `-d` it sends the request without touching stdin, so a proxied GET returns at once. Any method but `GET` without `-d` from a non-terminal stdin warns on stderr that it is sent without a body, since piped input is no longer used as one.
15 - `composio execute` still reads piped JSON arguments without `-d`. A pipe that sends nothing within 1 second now fails with `No input arrived on stdin within 1 second` and exit code 1, without running the tool, rather than running it with `{}` while the arguments may still be on their way. Pass the arguments with `-d '{...}'`, or `-d -` to wait for stdin as long as it takes.
16
17 - Update @composio/client to 2.1.35 to include the latest API changes.
18
19 - `composio listen --stream` shows control characters, including embedded tabs and line breaks,
20 as visible escapes in each output record. Read the saved event JSON for the original value.
21 `composio dev listen`, `composio execute`, `composio proxy` and error messages also show
22 control characters from events, responses and API errors as escapes on the terminal. Printed
23 JSON decodes to the same values, and redirected `proxy` output stays unchanged.
24
25 - `composio upgrade` on Windows now retries a busy executable rename for up to two seconds, allowing a brief file lock after a previous upgrade to clear before replacing the binary.
26
27 - `composio login --poll` accepts `--timeout <seconds>` to bound how long it waits. If the login is still pending when the wait ends, the CLI prints the authorization URL and the command to resume polling. [#5431](https://github.com/ComposioHQ/composio/pull/5431)
28
29 - Update @composio/client to 2.1.33 to include the latest API changes.
30
31 [Compare with 0.6.2](https://github.com/ComposioHQ/composio/compare/%40composio%2Fcli%400.6.2...%40composio%2Fcli%400.6.3)
32
33 ## 0.6.2
34
35 ### Patch Changes
36
37 - A failed request that is safe to send again now exits 75 (`EX_TEMPFAIL`) instead of 1 and says so on stderr: one the API refused with a 429, or a read that timed out, lost its connection, or got a 408 or 5xx. Scripts and agents can retry on 75 without guessing. A failed `composio execute` adds `"retry": "safe"`, or `"retry": "check-first"` when the tool may have run before the request failed, to its `{ "successful": false }` result, and the `composio-cli` skill tells agents what both mean. Every other failed request still exits 1.
38
39 - `composio dev toolkits list` and `info` now read a user's connection status in the resolved developer project. When no directory project applies, `--user-id` or the global test user can use the default developer project. A failed project lookup leaves the catalog available and warns when `--connected` cannot be applied.
40
41 - A directory developer project must belong to the stored login's org, checked before any request. With no stored org, the CLI checks every page of the active key's org list. Resource commands refuse a project outside that boundary and name why they use the default developer project instead.
42
43 - `composio dev` resource commands now act on the directory's developer project or `--project-name`, rather than leaving the backend to choose. Without a directory project they keep working by resolving the default developer project once from session info and naming it on stderr, including in scripts. Project lookup failures preserve their cause and recovery advice.
44
45 - A command whose stdout reader stops reading early, as in
46 `composio search "send a slack message" | head -1`, now drops the rest of
47 its output and exits as it would have. It printed an `EPIPE: broken pipe`
48 stack trace on stderr and exited 1, so a pipeline that only wanted the first
49 lines looked like a failure. `composio listen` and `composio dev listen`
50 stop listening at their next write once that reader is gone and exit 0,
51 where they would keep running with nobody reading. Other stdout write
52 failures still fail the command.
53
54 - `composio search` now fails with "The API response for
55 'toolRouter.session.search' is not in the shape this version of the CLI
56 expects" and `composio upgrade` as the way out when the API answers 200 with
57 JSON it cannot read or with an empty body. It crashed with a raw `TypeError`
58 naming a minified variable, which told an agent nothing it could act on.
59
60 - `composio whoami` now exits 1 when it cannot read the account (the backend
61 rejects the stored key, cannot be reached, or fails), with nothing on stdout
62 and the reason on stderr; a rejected key also names `composio login`. It
63 exited 0 and printed a JSON object of nulls, so checking a login with
64 `composio whoami` passed on a key that no longer worked. A session it reads
65 only in part still prints, with the missing fields as `null`.
66
67 - A command the Composio API answers with 401 now prints the API's message
68 and how to recover: `composio logout && composio login` when the stored
69 login's key may have expired, `composio agent login <composio_agent_key>`
70 with the key from `~/.composio/agent.json` when that login is the saved
71 Composio agent identity's, or replacing `COMPOSIO_USER_API_KEY` when the key
72 came from there. Agent recovery reuses the identity without signing up a
73 replacement or printing its key. `composio search` and other commands printed only the
74 API's `Invalid API key` (inside a defect report), so an agent had no command
75 to get unstuck. The hint was shown only when the API said the user API key
76 itself was rejected; any other 401 now names the login as the likely cause.
77
78 - The `composio-cli` skill now says how to run a tool inside a developer
79 project: `composio dev playground-execute`, with
80 `composio dev connected-accounts link <toolkit>` for a missing connection.
81 Agents on developer tasks used to fall back to `composio execute`, which acts
82 on the consumer project; in live runs with `claude-haiku-5-5` that happened
83 on every developer run, and no longer does.
84
85 - `composio dev playground-execute` without a connection now names
86 `composio dev connected-accounts link <toolkit>` as the fix. It used to name
87 `composio link <toolkit>`, which connects the consumer user and leaves the
88 developer project's test user unconnected, so the retry failed the same way.
89 The `composio-cli` skill's developer reference now lists `composio orgs list`
90 in place of `composio dev orgs list`, which does not exist.
91
92 ### Minor Changes
93
94 - `composio dev logs tools` now searches and retrieves logs through the public
95 tool execution logs API. Pages are capped at 100. Piped JSON uses the public
96 `logs` / `next_cursor` envelope and unified log detail fields. The public API
97 does not support `--case-sensitive` or the legacy `--session-id` filter;
98 these now fail with an explanation. `--tool-router-session-id` remains supported.
99 Each filter flag takes one value; a comma-separated list now fails instead of
100 matching nothing.
101
102 [Compare with 0.6.1](https://github.com/ComposioHQ/composio/compare/%40composio%2Fcli%400.6.1...%40composio%2Fcli%400.6.2)
103
104 ## 0.6.1
105
106 ### Patch Changes
107
108 - Update @composio/client to 2.1.32 to include the latest API changes.
109
110 - `composio dev connected-accounts link --help` now shows
111 `composio dev connected-accounts link …` examples. It showed root
112 `composio link …` examples, which link the consumer user, not a user of the
113 developer project. The description of both pages now says which user each
114 command acts as.
115
116 - `composio link` and `composio dev connected-accounts link` now print the
117 authorization URL when stderr is not a terminal, as under a script, CI or a
118 coding agent, before they wait for the authorization. The URL used to go
119 through terminal decoration that is dropped off a terminal, so a run with
120 `--no-browser` printed nothing until it timed out and an agent had no URL to
121 show the person. The instructions name `--no-wait`, which returns the URL as
122 JSON at once, and the `composio-cli` skill now teaches it.
123
124 - `composio login` and `composio link` stop waiting for an authorization after
125 10 minutes, checking every 5 seconds once a short ramp is over. The wait used
126 to double after every check, so it took about 2 hours 44 minutes to give up,
127 although `composio login`'s hint promised 10 minutes.
128
129 - Update @composio/client to 2.1.17 to include the latest API changes.
130
131 - Update @composio/client to 2.1.16 to include the latest API changes.
132
133 - Update @composio/client to 2.1.13 to include the latest API changes.
134
135 - Update @composio/client to 2.1.6 to include the latest API changes.
136
137 - Update @composio/client to 2.1.0 to include the latest API changes.
138
139 - Update Effect and its Bun and Vitest integrations to `^4.1.0`.
140
141 ### Minor Changes
142
143 - Add experimental native Windows x64 CLI binaries, installed from PowerShell
144 with a checksum-verified one-liner. Installation, `composio run`, and
145 `composio upgrade` are checked on Windows in the beta and stable release
146 workflows; other commands may not work yet. Windows requires Windows 10 1809
147 or newer and an SSE4.2-capable x64 CPU.
148
149 ### Patch Changes
150
151 - `composio connections list` now prints every connection. The server serves
152 at most 50 connected accounts per request and the CLI read only the first
153 page, so a user with more than 50 saw a partial list with no sign it was cut
154 off, and a connected toolkit (such as an active Slack account) looked
155 disconnected. `composio connections remove` could not find an account past
156 the first 50, and `composio execute` sessions left out toolkits whose
157 accounts were past the first 50 active ones. All three now follow
158 `next_cursor` through every page.
159 `composio link --list` and alias-conflict checks when linking also read
160 every page, including accounts filtered by an auth config.
161
162 [Compare with 0.6.0](https://github.com/ComposioHQ/composio/compare/%40composio%2Fcli%400.6.0...%40composio%2Fcli%400.6.1)
163
164 ## 0.6.0
165
166 ### Minor Changes
167
168 - A signal now ends each command the way its work ends. A one-shot command,
169 `composio login` and `composio upgrade` stopped with Ctrl-C (SIGINT), SIGTERM
170 or a closed terminal (SIGHUP) exit 130, 143 or 129. They used to exit 0, so a
171 wrapper or `set -e` script read a cancelled command as a successful one.
172 `composio listen` and `composio dev triggers listen` (`composio dev listen`)
173 treat Ctrl-C and SIGTERM as the way to stop them once subscribed: they
174 disable the temporary trigger, print their summary, and exit 0. A signal
175 before the subscription is confirmed, or SIGHUP, exits 130, 143 or 129 instead.
176 `composio run` forwards SIGINT, SIGTERM and SIGHUP to its script and ends the
177 way the script did: with its exit code, or killed by the same signal. A
178 script still running 2 seconds later gets SIGTERM, then SIGKILL; a script the
179 CLI had to kill this way ends the CLI by the signal it received. A second
180 signal, or a stop that takes longer than 10 seconds, ends the CLI at once:
181 128 plus the signal's number, or, for `composio run`, the script's process
182 group is killed and the CLI is killed by that signal.
183
184 - `composio dev connected-accounts link <toolkit>` (with or without `--list`)
185 now acts on your developer project, like the other `composio dev` commands:
186 the directory's project, or the one `--project-name` names. It links or lists
187 accounts for `--user-id` when given, else the directory's test user id (for
188 the directory's own project), else the global test user id. Without
189 `--project-name` it used to act as your consumer user on your consumer
190 project and silently ignore `--user-id`; outside a directory set up with
191 `composio dev init` it now fails asking for one. With `--project-name`,
192 linking a toolkit now also uses the directory's test user when the name is
193 the directory's own project. `composio link` is unchanged. With
194 `--auth-config`, a missing developer project is now reported before a
195 missing user id. On the dev tree, the alias hints point at
196 `composio dev playground-execute` and `composio dev connected-accounts list`.
197
198 - `composio listen`, `composio dev listen` and `composio dev triggers listen`
199 gain `--fail-fast`: the listener stops at the first event it fails to save,
200 forward, or append to `--out`, prints how many events failed on stderr, and
201 exits 1. Without it, a failed event is still reported and skipped, and the
202 exit code stays 0.
203
204 - `composio execute`, `composio proxy` and `composio listen` (for a trigger
205 slug) now fail with an error listing the candidate accounts, instead of
206 silently using the newest one, when a toolkit has several connected accounts,
207 none is aliased `default`, and no `--account` is passed. Scripts that relied
208 on the implicit newest-account pick now fail. To migrate, pass
209 `--account <id|alias>`, or alias one account `default`.
210
211 ### Patch Changes
212
213 - Command telemetry now derives option types and effective defaults from each
214 command's parser. Commands explicitly select safe properties to measure, and
215 shared root and `dev` definitions reuse that selection. Help and parse failures
216 omit command input properties instead of reporting synthetic defaults, false
217 booleans, or zero counts for input that was never parsed.
218
219 - `composio dev triggers listen --toolkits` now matches toolkits whose slug
220 contains an underscore, such as `one_drive`, `launch_darkly` and
221 `agent_mail`. Events carry no toolkit slug, so the listener took the first
222 `_` segment of the trigger slug (`ONE` for `ONE_DRIVE_FILE_CREATED_TRIGGER`)
223 and dropped every event of those toolkits. A `--toolkits` entry now also
224 matches when the trigger slug starts with `<toolkit>_`.
225
226 - `composio connections list`, `composio connections remove`, and
227 `composio listen` without a consumer user now print the message on stderr
228 and exit 1, like other expected errors. They used to print it under a `💥`
229 banner with the error tag and a stack location. Telemetry: every missing-user
230 failure now reports `error_name` `commands/MissingActingUserError` in
231 `cli.command.failed` and the command-family failure events, replacing
232 `ToolExecutionError` (execute), `commands/CommandInputError` (search),
233 `commands/MissingLinkUserIdError` (link),
234 `commands/MissingConnectionsConsumerUserIdError` (connections list),
235 `commands/MissingConnectionRemovalConsumerUserIdError` (connections remove),
236 `commands/ListenCommandError` (listen), and `commands/ProxyCommandError`
237 (proxy). Other failures of those commands keep their names.
238
239 - Every `composio dev` command that acts as a user now names the test user it
240 falls back to on stderr (`Using test user id "…"` for the directory's,
241 `Using global test user id "…"` for the global one) when you pass no
242 `--user-id`. `composio dev playground-execute` printed nothing before; with
243 `--parallel` it names the user once.
244
245 - A missing user id now gets the same message on every command of a tree.
246 Root commands (`composio execute`, `search`, `link`, `listen`, `proxy`,
247 `connections`) report a missing consumer user id and point at
248 `composio login`; root `execute`, `search`, and `link` no longer tell you to
249 pass `--user-id`, which the root tree does not take, and `listen` and `proxy`
250 no longer describe a missing "project context". `composio dev` commands point
251 at `--user-id` or `composio dev init`, or at `--user-id` or `composio login`
252 with `--project-name`.
253
254 - An empty consumer user id now counts as no user on every command.
255 `composio execute`, `composio search`, and `composio link` fail with the
256 missing-user error and exit 1, as `composio connections`, `composio listen`,
257 and `composio proxy` already did; they used to send requests for the user
258 `""`. `composio run` starts the script without the consumer user's context,
259 as it does when there is no consumer user.
260
261 - The update notice, the Composio plugin tip, the backend mismatch warning,
262 and the daily background check for a newer release now run only for a
263 command that runs. `--help`, `--version`, `composio help …`, a bare
264 `composio` or command group that only prints its help (`composio tools`,
265 `composio orgs`), and a mistyped command or flag no longer print them or
266 start the check; a group with an action of its own (`composio dev`,
267 `composio setup`, `composio generate`) still does. `composio upgrade` still
268 skips the notice and the check, `composio version --check` the check, and
269 `composio setup` the plugin tip.
270 The `CLI_PLUGIN_HINT_SHOWN` event now records the full command path
271 (`dev triggers list`) instead of the first word.
272
273 - CLI telemetry now records the command `effect/cli` parsed instead of guessing
274 it from argv. `composio signup`, `agent …`, `connections …`, `config …`,
275 `debug …` and `help …` were recorded as `composio`, `composio dev init` as
276 `dev`, and `composio setup skill` as `setup` with the `CLI_SETUP_*` events;
277 each is now recorded under its own command path with the generic
278 `CLI_COMMAND_*` events. A rejected invocation (unknown command or flag,
279 missing argument) is recorded with the command path the parser reached and
280 `failure_reason_code: "parse_error"`. Every other command path and event
281 family is unchanged.
282
283 - Hints no longer name commands that do not exist. `composio orgs list` and
284 the "No current org configured" error pointed at `composio dev orgs list` and
285 `composio dev orgs switch`; they now name `composio orgs list` and
286 `composio orgs switch`. `composio triggers list` with an unknown toolkit
287 pointed at `composio toolkits list`; it now suggests
288 `composio search "<what you want to do>"` to find the toolkit.
289 `composio dev triggers list` still names `composio dev toolkits list`.
290
291 - A `composio dev` command that cannot honor `--user-id` or `--project-name`
292 now rejects it before checking that you are logged in, and the message names
293 the exact subcommand you ran instead of the group that declared the
294 restriction: `composio dev logs tools --project-name x` now names
295 `composio dev logs tools`, where it named `composio dev logs`. Telemetry
296 records the failure against that subcommand too. A group run on its own
297 rejects the flag the same way instead of printing its help:
298 `composio dev projects --user-id x` fails with that error, while
299 `composio dev projects --help` still prints the help.
300
301 - CLI telemetry now records a command that prints its own
302 failure and exits 1 (a failed API request, an alias conflict on
303 `composio link`, a `--fail-fast` listener stop) as failed instead of
304 succeeded, and a `composio run` whose script exits non-zero as
305 `CLI_RUN_FAILED` with `failure_reason_code: "child_exit"`.
306
307 - `composio execute` now exits 1 when an argument names a file on your machine
308 but the tool does not accept file uploads for that input, such as `file` in
309 `TRELLO_ADD_CARDS_ATTACHMENTS_BY_ID_CARD`. It used to send the path text to
310 the tool and report success, and the tool stored that text instead of the
311 file. The error names the input and the path. Nothing is sent. `--dry-run`
312 reports the same error. Paths that do not exist on your machine are still
313 sent as before.
314
315 - Local file uploads now use the filename's MIME type instead of always declaring
316 `application/octet-stream`. `execute --file` preserves arrays and injects into
317 the single matching upload field in an existing array item; ambiguous targets
318 require explicit JSON. This fixes Word and PowerPoint image editing through the CLI.
319
320 - `composio listen` now picks the connected account for a trigger slug the way
321 `composio execute` and `composio proxy` do, through the same resolver, so the
322 three commands choose the same account for the same `--account` (or its
323 absence). An `--account` that matches no active account, or a failed account
324 lookup, now fails with the message those commands print, as a plain message
325 on stderr with exit 1.
326
327 - In `composio run`, a `File` or `Blob` passed to `execute()` now uploads with
328 its own `type`, even when its name has no extension, and a `File` keeps its
329 name. It used to upload as `application/octet-stream` under a name with a
330 random prefix, such as `1bfa14f5-deck.pptx`. A nameless `Blob` whose type has
331 no short extension, such as PPTX, is named `file-<id>.bin`.
332
333 - `composio upgrade` no longer starts with a stale "Update available" line.
334 The line came from the cached daily update check, so right after a release
335 it could name an older version than the one `composio upgrade` then
336 installed. Upgrading also refreshes that cache with the latest stable release
337 it found, so later commands stop suggesting an older version. Installing a
338 specific version, a beta, or a pinned release tag leaves the cache unchanged.
339
340 - `composio proxy` now enforces the consumer permission policy that
341 `composio execute` enforces, checked against the connected account the
342 request uses. A denied request fails with the same permission error, and a
343 request that needs approval opens the same approval page, before anything is
344 sent.
345
346 - A tool call or proxied request that a session hook blocks is now reported as
347 a failure carrying the hook's message. `composio execute` prints it as a
348 failed call (`successful: false`) with the message in `error`; on consumer
349 projects, whose calls go through the Dashboard, it used to fail as a response
350 the CLI could not read. `composio proxy` fails naming the hook instead of
351 printing a response with no status.
352
353 - `composio connections list` now prints each account's `id`, its `alias`
354 whenever it has one (previously only when a toolkit had several accounts),
355 and `display_name` — the provider identity from `state.val.displayName`,
356 trimmed and capped at 200 characters — when Composio has filled one in.
357 Nothing else is read from `state`.
358
359 - `composio connections list`, `composio connections remove`, and
360 `composio dev connected-accounts list` exit 1 when the connected-accounts
361 response does not match the shape this CLI expects, naming the mismatched
362 fields. They used to warn and continue with the unchecked response.
363
364 - The CLI now uses `@composio/client@2.0.0-rc.23` (up from `2.0.0-rc.20`). No
365 command changes.
366
367 - `composio dev triggers create` now accepts `--user-id` and sends it with the
368 request, so it works on projects with 2FA enabled, which require the user who
369 owns the connected account. It used to reject `--user-id` and send no user,
370 so creating a trigger on those projects always failed. Without `--user-id`
371 it sends the project's test user id, else the global test user id, and names
372 the one it used on stderr; with neither configured it sends no user, as
373 before. Given a user and no `--connected-account-id`, the API picks that
374 user's first active connection for the trigger's toolkit.
375
376 - More expected errors now print as a plain message on stderr and exit 1, like
377 other usage errors. They used to print under a `💥` banner with the error tag
378 and a stack location, as if the CLI had crashed. The message itself is
379 unchanged, and nothing is printed on stdout. This covers:
380 - `composio execute` without a user id, or with a `--file` the tool has no
381 file input for (or whose field `-d` already sets)
382 - `composio proxy` when the project has no consumer user
383 - `composio link` without a user id, or when the authorization is not
384 finished before the CLI stops waiting
385 - `composio login` with an `--org` that does not exist, a session key that
386 expired or is not linked yet, a login that is not finished in time, or
387 `--poll` without a pending (or with an expired) login
388 - `composio generate` outside a recognizable JavaScript or Python project, or
389 without `@composio/core` or `composio-core` installed
390 - a `COMPOSIO_TOOLKIT_VERSION_<TOOLKIT>` override naming a toolkit or version
391 that does not exist
392
393 - `composio execute` and `composio proxy` no longer print a `💥` banner after
394 reporting that the toolkit is not connected (when the connected-account cache
395 is on). The message, tips, and `{"successful": false, ...}` JSON on stdout
396 are unchanged, and the exit code is still 1.
397
398 - `composio link` and `composio dev connected-accounts link` now exit 1 with
399 the usage message on stderr when their flags can't run: a toolkit together
400 with `--auth-config`, neither a toolkit nor `--auth-config`, `--auth-config`
401 without a developer project, and `--list` without a toolkit or with
402 `--auth-config`. They used to exit 0, and printed the message only when
403 stderr was a terminal, so scripts, CI and agents saw no output and a
404 successful exit. The messages are unchanged.
405
406 - These commands now exit 1 and print their message on stderr. They used to
407 exit 0, and printed the message only when stderr was a terminal, so scripts,
408 CI and agents saw no output and a successful exit. The messages are
409 unchanged.
410 - Missing input, before any request: `composio whoami` without a login,
411 `composio dev projects list` without `--org-id` or a current org,
412 `composio triggers info` and `composio dev triggers info` without a
413 `<slug>`, `composio dev toolkits info` without a `<slug>`,
414 `composio dev triggers disable` without an `<id>`, and
415 `composio dev connected-accounts info` and
416 `composio dev connected-accounts whoami` without an `<id>`.
417 - Missing input that needs one lookup first: `composio dev init` without a
418 stored API key or org (it checks your saved login), and
419 `composio connections remove` with a selector that matches no connection
420 or more than one (it fetches your connections). Both fail before they
421 change anything.
422 - Failures after a request: `composio dev toolkits info` for a toolkit it
423 cannot fetch or find, `composio dev toolkits version` for a toolkit it
424 cannot fetch, `composio dev init` in an org without projects, and
425 `composio link` and `composio dev connected-accounts link` when the link
426 request fails, the link response is incomplete, the `--alias` is already
427 taken, or an account already exists and no `--alias` was passed.
428
429 - These commands already exited 1 but printed their message only when stderr
430 was a terminal; they now print it on stderr either way:
431 `composio dev toolkits list` and `composio dev toolkits search` when the
432 request fails, `composio listen`, `composio dev listen` and
433 `composio dev triggers listen` when the realtime subscription fails, and
434 the `composio agent` commands, `composio signup` and `composio login` when
435 the stored agent identity can't be used.
436
437 - `composio connections remove` gains `--yes` (`-y`) to remove without the
438 confirmation prompt, and `composio logout` accepts `--yes` (`-y`) next to
439 `--force` (`-f`). When not running interactively, both used to answer their
440 own prompt with "no", remove nothing and exit 0; without `--yes` they now
441 exit 1 with "needs --yes when not running interactively" on stderr, before
442 any request (for `logout`, only when logged in as an agent, the case that
443 asks). Declining the prompt on a terminal still removes nothing and exits 0.
444
445 - `composio listen`, `composio dev listen` and `composio dev triggers listen`
446 now print how many events they failed to save, forward, or append to `--out`
447 on stderr when they stop, including on Ctrl+C. The per-event warnings were
448 shown only when stderr was a terminal. One failed event still does not stop
449 the listener, and the exit code is unchanged.
450
451 - `composio listen --max-events N` now stops after N matching events even when
452 saving one of them fails. It used to keep listening until interrupted.
453
454 [Compare with 0.5.0](https://github.com/ComposioHQ/composio/compare/%40composio%2Fcli%400.5.0...%40composio%2Fcli%400.6.0)
455
456 ## 0.5.0
457
458 ### Minor Changes
459
460 - Breaking: some commands now exit 1 where they used to exit 0. Scripts and
461 agents that read the exit code to decide whether a call worked now get the
462 right answer; a script that relied on exit 0 after a failed execution must
463 handle exit 1. Output on stdout and stderr is unchanged.
464
465 - `composio execute` now exits 1 when a tool execution fails: the tool
466 reported a failure, the Composio Dashboard or backend could not run it, or,
467 with `--parallel`, any one of the calls failed. It used to exit 0. Meta tools
468 behave the same. The `{"successful": false, ...}` JSON on stdout and the
469 messages on stderr are unchanged. In `composio run`, `execute()` still
470 rejects with the tool's error message and the failed result.
471
472 - These commands now exit 1 instead of 0 when their input is missing or
473 invalid, printing the same message and example on stderr and nothing on
474 stdout. No request is sent.
475 - `composio dev auth-configs info` without an `<id>`
476 - `composio dev auth-configs create` with `--custom-credentials` that is not
477 a JSON object
478 - `composio tools info` without a `<slug>`
479 - `composio dev triggers create` without a `<trigger-name>`, or with
480 `--trigger-config` that is not a JSON object
481 - `composio dev triggers enable` without an `<id>`
482
483 - `composio orgs switch` now exits 1 and asks you to run `composio login`
484 when the stored `api_key` is empty. It used to warn and exit 0. Nothing is
485 written in either case.
486
487 ### Patch Changes
488
489 - `composio dev connected-accounts list` now reports a response whose `items`
490 is not a list as a request error and exits 1. It used to crash.
491
492 - `composio execute` and `composio proxy` now report an `--account` that
493 matches no connected account (`No connected account matched "…"`) as one
494 line on stderr and exit 1, like other usage errors. They used to print it
495 under a `💥` banner with the error tag and a stack location, as if the CLI had
496 crashed. A failure to load the toolkit's connected accounts is reported the
497 same way. Nothing is printed on stdout.
498
499 - `composio execute` now sends the execution itself (single, `--parallel`, and
500 meta tools) through the Composio Dashboard instead of calling the backend
501 directly. Output, exit codes, error details, connection tips, and `--json`
502 shapes are unchanged for tool results and for the request errors the backend
503 reports; a backend outage is reported with the Dashboard's own message. No
504 new login or configuration is needed.
505 `composio dev playground-execute` and every other command still call the
506 backend. A `COMPOSIO_BASE_URL` override without `COMPOSIO_WEB_URL` keeps
507 `composio execute` on that backend; set both to use that deployment's
508 Dashboard. The request is sent once, with no retry and no redirect following,
509 and gives up after 15 minutes with a message that the tool may still have run.
510 `COMPOSIO_WEB_URL` must be an `https://` URL with no credentials, query
511 string, or fragment (`http://` is accepted only for localhost); otherwise
512 `composio execute` fails before sending anything.
513
514 - When telemetry is enabled, `composio execute` sends the CLI's anonymous
515 analytics install ID (the random UUID in `~/.composio/analytics.json`) to the
516 Composio Dashboard in an `x-cli-install-id` header, so Dashboard-side product
517 analytics can be joined with the CLI's own events. It follows the existing
518 telemetry opt-outs (`COMPOSIO_CLI_TELEMETRY_DISABLED`, `TELEMETRY_DISABLED`,
519 `COMPOSIO_DISABLE_TELEMETRY`, or `CI`): when telemetry is off, or no install
520 ID is stored, the header is not sent. It is never sent to the backend API.
521
522 - The CLI now calls the backend you logged in to. `composio login` already
523 recorded it as `base_url` in `user_data.json`, but every command replaced it
524 with the production default unless `COMPOSIO_BASE_URL` or
525 `COMPOSIO_ENVIRONMENT` was set, so a staging login sent its key to production
526 and failed with `Invalid or revoked user API key`. Those variables still win
527 when set, and the CLI warns on stderr when one sends the stored key to a
528 different backend than the one that issued it. A key from
529 `COMPOSIO_USER_API_KEY` keeps using the backend the environment selects.
530 `composio execute` follows the same rule for the Dashboard it calls, using
531 the recorded `web_url`. `composio orgs switch` no longer rewrites the
532 recorded backend, and a key from `COMPOSIO_USER_API_KEY` is no longer written
533 to `user_data.json`. `composio login --agent` records the backend the
534 environment selects, since agents.composio.dev issued its key. A rejected
535 user API key now prints how to log in again, naming the backend and
536 Dashboard when they are not production's.
537
538 - `composio link` and `composio dev connected-accounts link` reword their usage
539 and status messages on stderr: the rejected `--auth-config` on the root
540 command, a toolkit passed together with `--auth-config`, a missing toolkit,
541 `--list` without a toolkit, a missing user id, `--auth-config` without a
542 developer project, an incomplete link response, a toolkit whose auth
543 Composio does not manage, and the waiting and timeout lines shown while a
544 link is pending. Exit codes and the JSON printed on stdout are unchanged.
545
546 - The CLI now uses `@composio/client@2.0.0-rc.20` (up from `2.0.0-rc.17`),
547 which drops the Stainless resource structure: resource classes, class
548 statics, namespace-member types and the `.js`/`.mjs` subpath spellings are
549 gone. The CLI's type imports move to the one `@composio/client/resources/*`
550 spelling; no command changes.
551
552 - API requests now authenticate through the API client's `auth` option (the
553 logged-in user's API key, or no credential before login) and name the org and
554 project through its `scope`, instead of the CLI placing `x-user-api-key`,
555 `x-org-id` and `x-project-id` in default headers. The headers sent are
556 unchanged. The CLI no longer keeps a client per API key and project for the
557 life of the process, so the user API key is held only by the client making
558 the request.
559
560 - The API client's deprecation notices are dropped by the CLI's logger instead
561 of being turned off in the client. Nothing new is printed.
562
563 ## 0.4.5
564
565 ### Patch Changes
566
567 - Retry only API reads that are safe to repeat. Mutating calls are sent once,
568 including when a request times out after the server may have acted.
569 - Commands that require login now fail consistently with a usage error.
570 Project-resolution failures retain their specific error type.
571 - Tolerate API response fields the command does not consume while continuing
572 to validate fields used for output, credentials, and cached data.
573 - The CLI now uses `@composio/client@2.0.0-rc.17` (up from `2.0.0-rc.14`). No
574 command changes.
575 - API requests now carry the CLI's product, version and runtime headers through
576 the API client's `identity` option instead of default headers. The headers
577 sent are unchanged.
578 - `--user-id` and `--project-name` are now flags of the `composio dev` group,
579 accepted before or after the subcommand name (`composio dev --user-id alice
580 toolkits info gmail` and `composio dev toolkits info gmail --user-id alice`
581 both work) and documented once, with one description each, on every `dev`
582 page. `dev playground-execute` (including `--parallel`),
583 `dev connected-accounts link`, `dev connected-accounts list`,
584 `dev toolkits info`, `dev toolkits list`, `dev listen` and
585 `dev triggers listen` read them from the group instead of declaring their
586 own; `dev logs tools` and `dev logs triggers` read the group's `--user-id` as
587 their comma-separated filter. The other `dev` commands still fail with exit 1
588 on a flag they cannot honor, now with a usage error naming it instead of an
589 unrecognized-flag error: `--project-name` on all of them, `--user-id` on all
590 but `dev logs`. `composio dev --mode` rejects both.
591 Without `--user-id`, a `dev` command given `--project-name` for another
592 project falls back to the global test user instead of the directory's
593 `test_user_id`, which belongs to the directory's project:
594 `dev playground-execute`, `dev connected-accounts link`,
595 `dev toolkits info` and `dev toolkits list`. With neither test user set,
596 the missing-user error now points at `--user-id` or `composio login`.
597 - `composio link --help` now lists `--auth-config`. The root command still
598 rejects it, now with the message ``Top-level `composio link` is
599 consumer-only and does not accept `--auth-config`.`` (exit 1) after the login
600 check, where it used to fail as an unrecognized flag.
601
602 - `composio execute` no longer rejects tool input for string parameters with
603 `format: "binary"` or a non-base64 `contentEncoding`, such as plain text in a
604 binary field or hex in a `base16` field. Only `contentEncoding: "base64"` is
605 checked as base64.
606
607 ## 0.4.4
608
609 ### Patch Changes
610
611 - `composio execute` and the `execute()` helper in `composio run` scripts now
612 report the Instant charge when a call ran on a Composio instant account
613 instead of a linked connection: the result carries an `instantCharge` object
614 (`amount`, `currency`, `chargedBy`) and the success line shows
615 `instant charge: <amount> USD`. The CLI used to create Tool Router sessions
616 without asking for the charge and dropped it from the response, so a billed
617 call looked free.
618 - The CLI now runs on the stable Effect 4 line (`effect@4.0.3`, up from
619 `4.0.0-rc.117`). No command changes on purpose. One parsing difference comes
620 with the framework: an argument that is a negative number, such as `-5`, is
621 now read as a value instead of as a flag.
622
623 ## 0.4.3
624
625 ### Patch Changes
626
627 - `composio execute` (including meta tools), `composio proxy`, the `proxy()`
628 helper in `composio run` scripts, and the custom tool schema lookup in
629 `composio search` now fail with a clear error when the call needs user input,
630 such as an approval, before it can run. The CLI cannot answer input requests
631 yet, and it no longer treats such an answer as a result. The `proxy()` helper
632 used to return an empty `200` response for a call that never ran.
633 - `composio execute` now reads whether a tool succeeded from the `result_type`
634 the API returns with every execution, so a tool that ran and failed is
635 reported as failed even when the API returns no error text. It used to read a
636 failed execution with a `null` error as successful.
637 - `composio execute` now validates the arguments before it sends the tool
638 call, so a call that fails local validation is never run. Validation used to
639 race the request, and the tool could execute while the CLI reported a
640 validation failure. The cached schema named in the validation error is now
641 kept on disk instead of being deleted. A schema the CLI cannot compile no
642 longer blocks the call; the server still validates it.
643 - Generate help from the command definitions, including every supported flag and
644 nested command. Remove help levels and the nonexistent `files` help topic.
645 Install agent skills with `composio setup skill <claude|codex|openclaw>`
646 (optionally `--name <skill-name>`) instead of `--install-skill`.
647 Internal diagnostics are hidden framework commands. `--dangerously-allow`
648 applies only to `dev triggers disable`; refused developer commands exit nonzero.
649 Debug flags after the `run` script boundary now reach the script unchanged.
650 `composio execute <slug> --help` now shows command options. Use
651 `composio execute <slug> --get-schema` to print that tool's input schema as JSON.
652 - `composio execute` (including meta tools) and `composio proxy` are never
653 retried, so a request that timed out or failed after the backend already
654 acted cannot repeat a side effect such as sending the same email twice.
655 - API requests and command analytics now report CLI product/version, language,
656 runtime/version, and the installed API client version separately.
657 - Remove the experimental local-tools stack: the `local-tools` command group,
658 the `local_tools` experimental flag, `LOCAL_*` tool execution, `dev native-ui`,
659 and the bundled macOS sidecars (peekaboo, imessage-cli, composio-native-ui).
660 Release archives no longer ship `local-tools-binaries/`; `composio upgrade`
661 and the installer delete one left by an older install. CI no longer installs
662 Swift. Permission prompts always use the browser approval page. A
663 stored `local_tools` setting is now listed as an unknown feature and has no
664 effect.
665 - Remove `experimental_subAgent()` (alias `invokeAgent`) from `composio run`.
666 Its ACP transport approved every tool call the spawned agent requested, so
667 both transports (ACP and the older `claude -p` / `codex exec` one), the output
668 MCP server, and the bundled ACP adapters are gone. `execute`, `search`,
669 `proxy`, `result.prompt()`, and the `z` / `zod` globals are unchanged. A
670 script that still calls the helper fails at that call with a message naming
671 the removal; tool calls it made earlier have already taken effect. To keep
672 the helper, install an older CLI with the installer:
673 `curl -fsSL https://composio.dev/install | COMPOSIO_INSTALL_VERSION=<version> sh`.
674 `composio upgrade <older version>` from this CLI is not a way back. A stored
675 `experimental_subagent` config key is now ignored and preserved; an invalid
676 target used to reset the whole config to defaults. `COMPOSIO_RUN_ACP_ONLY` is
677 no longer read and the hidden `--acp-only` flag is gone. Remove `--logs-off`,
678 which only canceled `--debug` after sub-agent streaming was removed. Helper
679 logs are written to disk; use `--debug` to also print them to stderr. An
680 unknown flag placed before inline `run` code is now rejected by name
681 (`Unrecognized flag: --x in command composio run`) instead of being executed
682 as source; inline source that is exactly one flag-shaped token needs an
683 explicit `--`. Release archives keep ten legacy paths (the four root
684 `run-subagent-*.mjs` files and six `acp-adapters/*` paths) as intentionally
685 empty placeholders so that a CLI installed before this change still passes
686 its upgrade verification. No adapter binaries are downloaded or shipped.
687
688 ## 0.4.2
689
690 ### Patch Changes
691
692 - Every Composio API call now goes through the `@composio/client` 2.0 runtime,
693 the same client `@composio/core` uses. Org, project, session-info, and
694 consumer lookups gain the client's retries and redirect handling, and API
695 error messages now keep a server message even when it carries no suggested
696 fix. Creating a project API key during `composio dev init` is never retried,
697 so a timed-out request cannot mint a second key.
698 - Ambient `COMPOSIO_CUSTOM_HEADERS` and `COMPOSIO_LOG_LEVEL` values no longer
699 leak into CLI requests or output. Custom HTTP base URLs remain supported
700 without an additional environment flag.
701 - `composio run` now validates binary download URLs returned by the proxy API
702 before fetching them. Private, loopback, link-local, and redirect-based SSRF
703 targets are blocked, DNS resolutions are pinned to prevent rebinding, and the
704 download fails closed when a configured proxy prevents address pinning.
705 - The plugin hint shown under Claude Code or Codex now reads
706 `'composio setup --yes' installs it`, and setup error messages that suggest
707 a rerun now include `--yes` too, so an agent following the printed text no
708 longer fails on the non-interactive `--yes` requirement. CLI telemetry gains
709 `agent_host_env` on every event, a `CLI_PLUGIN_HINT_SHOWN` event, host
710 presence signals on `CLI_SETUP_HOST_DETECTED` when a host is not detected,
711 and a `failure_reason_code` on `CLI_SETUP_FAILED`.
712 - The CLI now runs on Effect 4 (`effect@4.0.0-rc.112`). Unrecognized commands and
713 flags now print a "Did you mean?" suggestion next to the help text for the command
714 that failed to parse, and parse errors for a nested command show that command's
715 help instead of the root help. `composio --version`, `composio -v`, and
716 `composio version` keep printing the same bare version string.
717 - `composio generate` now keeps tool and trigger metadata as inert data in
718 generated Python and TypeScript sources. Crafted slugs and descriptions can
719 no longer inject code into generated modules.
720 - `composio orgs --help`, `composio signup --help`, the `agent` family pages (signup,
721 login, whoami, inbox, claim), and the group help pages for `connections`, `triggers`,
722 `artifacts`, and `install` now render the same curated, styled help page as every
723 other command family, instead of falling back to the framework's raw flag dump.
724 `composio help <command>` is now a supported spelling of command help (`composio help
725 orgs` shows the same page as `composio orgs --help`, with the same longest-prefix
726 fallback for deeper paths); an unknown target fails through the framework parser like
727 any other unknown command. The `orgs` description in contextual error help now matches
728 the command's actual description.
729 - `composio listen <slug> --stream` without a path is accepted again and streams
730 the whole event payload. It previously failed with
731 `Received unknown argument: '--stream='`.
732 - `composio listen` reports an unknown trigger slug as such. A mistyped slug
733 used to fail with a missing-connection error for the toolkit inferred from its
734 prefix, or with a generic trigger-creation error when that toolkit already had
735 an active account.
736 - `composio tools info`, and the other `info`, `create`, `enable`, `disable`,
737 and `status` commands that share its API error handling, now exit non-zero on
738 an API error and print the error when stderr is not a terminal. `composio tools
739 info <unknown-slug>` used to print nothing and exit 0 when piped.
740 - Help examples use `SLACK_SEND_MESSAGE` and `SLACK_CHANNEL_MESSAGE_RECEIVED`
741 instead of a removed Slack tool slug and a trigger without configuration.
742
743 ## 0.4.1
744
745 ### Patch Changes
746
747 - `composio upgrade` (and any other command with a long spinner message) no
748 longer scrolls endlessly in terminals narrower than that message. The spinner
749 printed its line hundreds of times instead of animating in place; live spinner
750 text is now clamped to a single terminal row.
751
752 ## 0.4.0
753
754 ### Patch Changes
755
756 - `composio upgrade` shows download progress. The archive is a few hundred
757 megabytes, and the command previously printed `Downloading...` once and then
758 said nothing for minutes, which was indistinguishable from a hang. It now
759 reports percent and transferred size as the download runs.
760 - `composio upgrade` downloads roughly half as much. Release archives carried
761 all four platforms' `codex-acp` binaries, about 651 MB that the machine
762 unpacking them can never execute. Only the binary for the archive's own
763 platform is shipped now; the other three remain as empty placeholders so that
764 a CLI installed before this change still passes its upgrade verification.
765 - `composio upgrade` works again from any previously released CLI. Release
766 archives had been narrowed to drop the `codex-acp` binaries a machine cannot
767 execute, but a CLI installed before that change verifies a downloaded package
768 against all four platforms' binaries and rejects one that is missing any of
769 them, failing with `Downloaded binary package is incomplete`. Every archive
770 names all four paths again.
771 - Archives are no longer extracted with symbolic links in them. `extract-zip`
772 creates a symlink entry without validating its target (CVE-2026-56876), which
773 has no fixed release, and anything that later reads the extracted tree can be
774 walked out of it. No archive this CLI extracts legitimately contains a
775 symlink, so such an entry is now refused before it is written.
776 - `composio search` now uses schemas returned by Tool Router for dashboard-registered custom MCP tools instead of querying the legacy managed-tool endpoint, which returned 404 for `CUSTOM_*` tool slugs.
777 - `COMPOSIO_ENVIRONMENT=staging` now opens the staging dashboard at
778 `https://staging-dashboard.composio.dev/`.
779 - `composio dev auth-configs create` now sends custom OAuth credentials and scopes
780 in the API's expected shape instead of failing validation.
781
782 ## 0.3.3
783
784 ### Patch Changes
785
786 - Free-form object arguments now pass CLI tool-input validation and keep their content instead of failing with an unknown-key error. Run `composio upgrade` to install the fixed CLI binary.
787 - A tool schema the validator cannot interpret is now reported as a schema compile failure naming the cached schema path, instead of as an input error blaming your arguments. This covers a `patternProperties` key that is not a valid regular expression, and a reference inside a `patternProperties` or schema-valued `additionalProperties` subschema that does not resolve.
788 - Tools belonging to multi-word toolkits now resolve to the right toolkit.
789 `composio tools execute GOOGLE_ANALYTICS_RUN_REPORT --account <alias>`
790 previously looked for a `google` account instead of a `google_analytics` one,
791 because the toolkit was guessed from the text before the first underscore.
792 The toolkit is now matched against the known toolkit list, longest prefix
793 first. This also corrects the toolkit shown in errors, file uploads, trigger
794 listening, and telemetry.
795 - Session meta tools such as `COMPOSIO_SEARCH_TOOLS` are no longer attributed
796 to the `composio_search` toolkit, whose slug their names happen to start
797 with. A failed meta call used to suggest linking an app that had nothing to
798 do with the call.
799 - Commands that consult the toolkit catalog more than once now fetch it once.
800 `composio tools execute` was downloading the full ~800 KB list up to four
801 times per run.
802 - A cached API request that fails is no longer sent a second time. The caching
803 layer treated the request's own failure as a cache failure and retried it,
804 so every failed toolkit, tool, or trigger listing cost two round trips and
805 twice the wait before reporting the same error.
806 - Resolving a tool's toolkit no longer downloads the toolkit catalog. The CLI
807 ships with the toolkit slugs it knew at build time and remembers any it
808 learns since in `known-toolkit-slugs.json`, so `composio tools execute` only
809 reaches for the catalog when a slug matches nothing it knows — a toolkit
810 released after your CLI version. `FORCE_USE_CACHE` is unaffected.
811 - Resolving a tool's toolkit now reads what the CLI knows locally once per run
812 rather than once per lookup. A single `composio tools execute` resolves the
813 same toolkit up to four times — and once per tool with `--parallel` — and
814 each of those re-read `known-toolkit-slugs.json`, re-parsed it, and rebuilt
815 the lookup table over it. The weekly background refresh now also runs once per
816 run instead of rewriting the file after every lookup.
817 - The background catalog refresh is abandoned after ten seconds. A finished
818 command ends when the event loop drains, so a slow network could otherwise
819 hold an exiting `composio` process open until the refresh completed.
820 - Cache files are now written atomically, so an interrupted run can no longer
821 leave a truncated `toolkits.json` or `tools.json` behind.
822
823 ## 0.3.2
824
825 ### Minor Changes
826
827 - The installer (`curl -fsSL https://composio.dev/install | sh`) now configures your shell automatically: `COMPOSIO_INSTALL_SHELL` defaults to `auto`, which infers the login shell from `$SHELL` (zsh, bash, or fish) and always runs idempotent PATH setup for it; `COMPOSIO_INSTALL_SHELL=none` keeps the old install-only behavior for CI, Docker, and dotfile managers. Startup-file setup failures no longer fail the install — the installer keeps the binary, warns, and prints a runnable absolute-path command. `composio install` now reconciles an existing managed PATH block whose bin directory changed (one block per physical file, symlink-aware) and suppresses its boxed restart hint when invoked by the installer, which owns the final message.
828 - `composio install` gains a `--shell <zsh|bash|fish>` flag that overrides `$SHELL` detection, in preparation for the mise-style installer rewrite. The bin-dir PATH target now resolves through `COMPOSIO_BIN_DIR`, an existing `~/.local/bin/composio`, or the real binary's own directory, in that order, instead of hardcoding `~/.composio`; rc blocks write only a PATH line (the `export COMPOSIO_INSTALL_DIR=...` line is gone, since that variable identifies the install bundle, not the PATH entry point). Bash now always writes the PATH line to a login-mode startup file as well as `~/.bashrc`, so `bash -ilc` (and macOS Terminal.app, which starts a login shell) picks it up: the first existing of `~/.bash_profile` or `~/.bash_login`, or a newly created `~/.bash_profile` when neither exists. A `~/.bash_profile` created this way shadows `~/.profile`, so it is seeded to source it first; `~/.profile` itself is never modified. The restart hint bug is fixed: bash now prints `source ~/.bashrc` instead of the literal string `exec $SHELL`.
829 - `COMPOSIO_BIN_DIR` is a documented public override: set it to the absolute directory `composio install` should add to `PATH` when the entry point users reach is a shim or symlink rather than the binary itself. See the CLI README for the full resolution order.
830 - `composio install` now exits non-zero, having written nothing, when it cannot produce a safe PATH line. There are two abort conditions: the resolved bin directory is not absolute, or it contains a character that cannot be embedded in a quoted rc line. A non-zero exit is what makes `install.sh` run its inline PATH fallback, so an aborted run still leaves the user with a working `PATH` — previously the command exited 0 and the fallback never ran.
831 - The unsafe-character set is narrower than the one first shipped in this entry. The bin dir is only ever written inside double quotes, where `;`, `|`, `&`, `(`, `)`, and `'` are literal — only `` ` ``, `$`, `"`, `\`, newline, carriage return, and the `:` PATH separator abort now. Paths like `/Users/o'brien/.composio` are accepted instead of rejected.
832 - An rc file that carries the older three-line Composio block (`export COMPOSIO_INSTALL_DIR=...` plus a PATH line derived from it), written by a previous CLI or by `install.sh`'s fallback, is migrated to the current single-line block instead of being treated as configured forever. The stale managed lines are removed where they stood and one refreshed block is appended after the remaining content, so your own lines keep their order and the last-sourced PATH line wins. Re-running the command is still idempotent, and a completions block elsewhere in the file is untouched.
833 - `composio install` no longer skips the rc write when the bin directory happens to be on the invoking process's `$PATH`. That said nothing about future shells — an ad-hoc `export` or a version-manager shim made the command persist nothing and still report success.
834 - Note for custom install directories: the rc block no longer records `COMPOSIO_INSTALL_DIR`. If you installed to a custom directory with `COMPOSIO_INSTALL_DIR=... curl ... | bash` and later re-run the install script without re-specifying it, the script installs a second copy under `~/.composio` while your rc `PATH` still points at the old one. Re-specify `COMPOSIO_INSTALL_DIR` when reinstalling, or use `composio upgrade`, which replaces the running binary in place.
835
836 ### Patch Changes
837
838 - Fix Linux `composio upgrade` failures with `ETXTBSY` by staging CLI files in
839 the install directory and renaming the executable last. The installer and
840 companion repair use the same replacement strategy, and the running binary
841 now reports its compiled version when `release-tag.txt` disagrees. Users on
842 an affected build must re-run `install.sh` once to install the first fixed
843 version.
844 - Connected-account statuses added by the server no longer break
845 `connected-accounts`, `link`, or `listen`. Piped output still strips
846 credential fields, and schema warnings no longer print raw response values.
847 - `composio login --poll` now reports unreadable cache files as I/O errors
848 instead of treating them as invalid session data.
849
850 ## 0.3.1
851
852 ### Minor Changes
853
854 - The CLI now points Claude Code and Codex users to `composio setup` when the
855 Composio agent plugin is missing. The hint goes to stderr, appears at most
856 once every 24 hours, remains visible in non-TTY agent sessions, and stays
857 suppressed inside `composio run` children.
858 - Telemetry now goes directly to PostHog. This captures `install` and `setup`
859 events before login without changing existing opt-outs.
860 - Telemetry events now include `journey_stage` (`install`, `setup`, `login`,
861 `connect`, `execute`, or `other`) and `cli_channel` (`stable` or `beta`).
862 `install.sh` also labels `composio install` with
863 `invocation_origin: installer`, so script installs can be separated from
864 manual runs. npm and Homebrew installs do not pass through `install.sh` and
865 therefore have no installer origin.
866
867 ## 0.3.0
868
869 ### Patch Changes
870
871 - The GitHub release tag is now the only version source for standalone CLI
872 binaries. Release builds embed the exact tag version, manual skill
873 installation uses that tag, and stable releases can only promote a tested
874 beta.
875
876 ## 0.2.33
877
878 ### Security
879
880 - fc17c37: Security: the CLI's tool file-upload path now enforces the sensitive-file denylist (issue #3746 / GHSA-hp3h-89pf-5q58). Previously `composio execute`/`composio run` read and uploaded any local path a tool argument pointed at — including `~/.ssh/id_rsa`, `~/.aws/credentials`, and `.env` files — enabling credential exfiltration in agentic workflows via prompt injection. The CLI now calls the shared `assertSafeFileUploadPath` guard from `@composio/core` at the lowest-level file read. URLs and `File` objects are unaffected.
881
882 Unlike the core and Python SDKs (which expose a `sensitiveFileUploadProtection` / `sensitive_file_upload_protection` opt-out), the CLI enforces the denylist **unconditionally by design** — the primary attack vector is an agent prompt-injected into supplying its own tool arguments, so a CLI override flag would hand that attacker a trivial bypass. The block error carries CLI-appropriate remediation guidance instead of pointing at the SDK-only flag.
883
884 ### Minor Changes
885
886 - Make headless `composio login` agent-friendly (PRDE-1138): the non-interactive instructions now offer the unattended `composio login --agent` path, and a machine with a stored READY agent identity (`~/.composio/agent.json`) completes plain headless `composio login` unattended by reusing it. Reuse only — a human piping `composio login` still gets the URL + poll instructions and never has an account auto-created.
887 - a0bef5d: Bump `@composio/client` to `0.1.0-alpha.74`.
888 - 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.
889
890 ### Patch Changes
891
892 - Fix `composio listen` crashing with `TypeError: Object is not a constructor` in compiled release binaries (issue #3918). pusher-js 8.5.0 exports a namespace object (`module.exports = { Pusher }`) instead of the constructor (an undocumented upstream packaging regression, pusher/pusher-js#935, fixed in pusher-js 8.6.0), so the dynamic import's `.default` is not callable under Node or Bun; the realtime service now probes every observed interop shape (including the named `Pusher` export), constructs the client inside `Effect.try`, and fails with a typed error instead of crashing.
893 - Preserve the original CLI diagnostic when an adjacent source map is malformed or unusable instead of letting optional source-map enrichment abort error capture. Source-map enrichment is now best-effort end to end: a malformed, invalid, or unreadable `.map`, and a valid map pointing at an original source that was never shipped, all degrade to the raw stack location. `captureErrors` can no longer fail.
894 - Fix source-map resolution on Windows: original source paths are now resolved with the platform path separator instead of a hardcoded `/`, and the `node_modules` filter no longer mistakes directories such as `node_modules_local` for real dependency paths.
895 - Make `composio version --check` report `checkStatus: "unknown"` when GitHub cannot confirm the latest stable release, preserve the last successful cache on failed refreshes, and avoid racing the command with the startup update check.
896 - Keep `composio install` guidance visible when its output is captured. The command reports which rc file it changed and how to reload the shell, but suppressed all of it when stderr was not a terminal — so installers, containers, and CI logs saw nothing and users were left with `command not found`. Those lines now fall back to plain, undecorated output.
897 - Make multi-account selection a stable CLI feature: `execute`, `listen`, and `link --alias` no longer honor the old experimental toggle; `proxy` now accepts `--account <alias|word_id|connected-account-id>`; and duplicate-alias link errors explain how to select the existing account.
898 - 8467efd: Fix `composio whoami` reporting the API key's home organization after `composio orgs switch`. Session info requests now forward the selected global organization.
899 - 5f004ff: Drop `COMPOSIO_UPSERT_RECIPE` and `COMPOSIO_GET_RECIPE` from the CLI meta-tool list. These slugs were removed from `@composio/client` (alpha.74), so listing them broke the type-checked CLI build.
900 - 23f9053: Remove the unused `ansis` dependency from the CLI. Colored output is already handled by `picocolors`, so `ansis` was a dead production dependency that shipped with the package.
901 - 446c6f6: Fix virtual TypeScript file resolution used by CLI type generation so in-memory imports resolve consistently during transpilation and validation.
902 - Updated dependencies [552859a]
903 - Updated dependencies [a0bef5d]
904 - Updated dependencies [23f9053]
905 - Updated dependencies [dfd7a08]
906 - Updated dependencies [507318d]
907 - Updated dependencies [025a657]
908 - Updated dependencies [6a4cb54]
909 - Updated dependencies [4b76dbf]
910 - Updated dependencies [cbbad15]
911 - @composio/core@0.12.0
912 - @composio/json-schema-to-zod@0.2.0
913 - @composio/ts-builders@0.2.0
914 - @composio/cli-keyring@0.2.0
915 - @composio/cli-local-tools@0.1.0
916
917 ## 0.2.32
918
919 ### Patch Changes
920
921 - Updated dependencies [22a9171]
922 - Updated dependencies [93b67e8]
923 - Updated dependencies [b69cef1]
924 - Updated dependencies [1ba66ca]
925 - Updated dependencies [a94715f]
926 - Updated dependencies [ce4b213]
927 - Updated dependencies [44e5458]
928 - @composio/core@0.11.0
929 - @composio/cli-local-tools@0.0.5
930
931 ## 0.2.31
932
933 ### Patch Changes
934
935 - `composio upgrade` now accepts an optional `<version>` argument so you can install a specific stable release or beta (e.g. `composio upgrade 0.13.1`, `composio upgrade 0.13.1-beta.42`, or the full tag `@composio/cli@0.13.1`). When omitted, the command continues to install the latest release on the chosen channel (`--beta` for prereleases).
936 - CLI now sends its per-cwd session id as the `x-cli-session-id` header on every request. The backend uses this to tag tool execution logs with `session_info.cli_session_id`, so all tool executions from a single CLI session (one cwd, one user) can be grouped together in the logs UI.
937 - Refresh the browser fallback approval prompt with the Composio CLI landing page visual style and serve it from the local loopback callback server while continuing to prefer the native macOS sidecar when available.
938 - Make CLI output more LLM-friendly by gating human-only notices/prompts on interactive TTYs and keeping logs on stderr.
939 - Route fish shell completions to `~/.config/fish/completions/composio.fish` (instead of the rc file) and sanitize completion lines that could break parsing.
940 - Permission "allow" decisions now expire after 1 hour — the prompt action is relabeled "Allow for 1 hr" and cached decisions are pruned on expiry.
941
942 ## 0.2.30
943
944 ### Patch Changes
945
946 - Updated dependencies [42ebff3]
947 - @composio/core@0.10.0
948 - @composio/cli-local-tools@0.0.4
949
950 ## 0.2.29
951
952 ### Patch Changes
953
954 - Updated dependencies [84a3a07]
955 - Updated dependencies [c358ffa]
956 - @composio/core@0.9.1
957 - @composio/cli-local-tools@0.0.3
958
959 ## 0.2.28
960
961 ### Patch Changes
962
963 - 79ac220: Scaffold the CLI local-tools foundation package, wire it into Tool Router search/execute sessions, and expose `composio local-tools list|doctor|configure|meta` for discovery, readiness checks, setup hints, and local metadata state. Concrete app integrations are added in follow-up stack PRs.
964 - Updated dependencies [79ac220]
965 - Updated dependencies [79ac220]
966 - Updated dependencies [79ac220]
967 - Updated dependencies [c9b6525]
968 - Updated dependencies [cc673b6]
969 - Updated dependencies [79ac220]
970 - Updated dependencies [9f14971]
971 - Updated dependencies [81f8027]
972 - Updated dependencies [711a703]
973 - Updated dependencies [bccd32b]
974 - Updated dependencies [bccd32b]
975 - Updated dependencies [07c9bab]
976 - Updated dependencies [3ece424]
977 - @composio/cli-local-tools@0.0.2
978 - @composio/core@0.9.0
979
980 ## 0.2.27
981
982 ### Patch Changes
983
984 - Updated dependencies [6b986cd]
985 - Updated dependencies [1c3276b]
986 - @composio/core@0.8.1
987
988 ## 0.2.26
989
990 ### Patch Changes
991
992 - Updated dependencies [ebc9778]
993 - Updated dependencies
994 - @composio/core@0.8.0
995
996 ## 0.2.25
997
998 ### Patch Changes
999
1000 - Updated dependencies [27ed0c9]
1001 - @composio/core@0.6.11
1002
1003 ## 0.2.24
1004
1005 Manual version bump to realign with the GitHub release tag. The 0.2.23 release workflow misclassified the version-bump merge as a beta due to a shallow-checkout bug in `.github/workflows/build-cli-binaries.yml`, so binaries built from that commit landed on `@composio/cli@0.2.24-beta.209` and, after `promote-stable`, on the GitHub tag `@composio/cli@0.2.24`. npm was left at 0.2.23. This release bumps npm to 0.2.24 so the published package and the GitHub release match. Fix for the underlying workflow bug: #3212.
1006
1007 ## 0.2.23
1008
1009 ### Patch Changes
1010
1011 - 4df06d2: feat: add `simple`, `default`, and `verbose` help verbosity modes to root and subcommand help (`--help simple|verbose`); compact simple mode and richer verbose mode with additional commands (#3205)
1012 feat: add `composio connections list` command that groups connected accounts by toolkit and displays aliases (#3206)
1013 feat: migrate API key storage from plaintext `~/.composio/user_data.json` to OS keyring (macOS Keychain / Linux Secret Service); env var > keyring > legacy plaintext precedence with one-shot migration and `dangerouslySaveApiKeyInUserConfig` opt-out for headless environments (#3202)
1014 feat: turn `composio dev` into a real developer-mode toggle backed by CLI user config; gate the `init`, `tools execute`, `triggers listen`, `logs`, `toolkits`, `auth-configs`, `connected-accounts`, `triggers`, and `projects` subcommand tree behind the toggle, and remove deprecated destructive `delete`/`info` commands now covered by the dev-mode gate (#3181)
1015 feat: enable `multi_account` experimental feature by default for stable CLI builds and centralize default experimental-feature behavior so runtime config and skill reference schema stay in sync (#3163)
1016
1017 ## 0.2.22
1018
1019 ### Patch Changes
1020
1021 - Updated dependencies [670ecc9]
1022 - @composio/core@0.6.10
1023
1024 ## 0.2.21
1025
1026 ### Patch Changes
1027
1028 - Updated dependencies [5b5723a]
1029 - @composio/core@0.6.9
1030
1031 ## 0.2.20
1032
1033 ### Patch Changes
1034
1035 - 4e36db8: feat: add `composio listen` command for real-time trigger event monitoring
1036 feat: add top-level `composio triggers` command (list, info subcommands)
1037 fix: pre-existing CI failures across CLI and e2e suites
1038 docs: document `--file` support for CLI skill uploads
1039
1040 ## 0.2.19
1041
1042 ### Patch Changes
1043
1044 - Updated dependencies [2b19ae9]
1045 - @composio/core@0.6.8
1046
1047 ## 0.2.18
1048
1049 ### Patch Changes
1050
1051 - f49e0af: feat: add `--beta` flag to `composio upgrade` for prerelease channel support
1052 feat: preload custom auth connections into tool router sessions for seamless custom-auth toolkit execution
1053 improve: beta-channel CLI release promotion flow in CI workflow
1054 improve: expanded test coverage for upgrade binary and custom auth session creation
1055
1056 ## 0.2.17
1057
1058 ### Patch Changes
1059
1060 - e3322e6: fix: hydrate file_uploadable tool inputs and add temp-file handling for execute payloads
1061 fix: surface in-band tool errors as warnings without overriding successful execution results
1062 fix: resolve 8 TypeScript strict-mode errors blocking CLI build in run-helpers-runtime
1063 refactor: extract run helper runtime (~650 lines) from run.cmd.ts into run-helpers-runtime.ts
1064
1065 ## 0.2.16
1066
1067 ### Patch Changes
1068
1069 - b763753: fix: bundle bun support files into CLI binary so standalone builds work without external bun dependencies
1070
1071 ## 0.2.15
1072
1073 ### Patch Changes
1074
1075 - 51c4e09: fix: bundle MCP server into subagent helper via static imports so it works with standalone CLI binaries without repo-local node_modules; fix codact failures not being reported by dispatching them through a dedicated background worker and wiring up the `tools execute` command to capture wrong-slug and wrong-param failures
1076
1077 ## 0.2.14
1078
1079 ### Patch Changes
1080
1081 - 5a3c661: Change `composio install` to skip shell completions by default and require `--completions` to install them explicitly. Also keep the skipped-completions logging consistent.
1082
1083 ## 0.2.13
1084
1085 ### Patch Changes
1086
1087 - cb02575: fix(cli): harden run subagent structured output and logfile path propagation
1088
1089 ## 0.2.12
1090
1091 ### Patch Changes
1092
1093 - 2eee65d: patch
1094
1095 ## 0.2.11
1096
1097 ### Patch Changes
1098
1099 - 77904b0: Fix link behavior, disable caching, improve search steps
1100
1101 ## 0.2.10
1102
1103 ### Patch Changes
1104
1105 - b301069: ### Bug fixes & hardening
1106 - Fix no-browser link flow to print raw redirect URLs
1107 - Harden session artifacts, analytics dir creation, and consumer cache for sandboxed environments (wrap filesystem ops in try/catch, respect `COMPOSIO_SESSION_DIR` / `COMPOSIO_CACHE_DIR` env vars)
1108 - Fix stale/broken symlink handling in skill installer (use `lstatSync` instead of `existsSync`)
1109 - Fix `detectMaster` parameter type to avoid type conflict from bun env augmentation
1110
1111 ### New features
1112 - Add parallel execute support and help examples
1113 - Add batched multi-query tool search
1114 - Allow `execute --get-schema` without user context
1115 - Cache no-auth toolkits as connected
1116 - Report execute failure origin and tool log IDs
1117 - Add skill installer during `composio login` (with `--no-skill-install` opt-out)
1118 - Add contextual help on CLI errors and unknown arguments
1119 - Add `composio files` subcommand help and richer examples in root help output
1120
1121 ## 0.2.9
1122
1123 ### Patch Changes
1124
1125 - 315238c: - Add telemetry worker and improve tool execution UX
1126 - Fix `composio link` hanging after auth completes
1127 - Add parallel tool execution support
1128 - Add ACP-backed subagent execution to `composio run`
1129 - Move CLI manage commands under `dev` namespace
1130 - Update CLI copy
1131
1132 ## 0.2.8
1133
1134 ### Patch Changes
1135
1136 - ae08b37: - Make top-level `composio search`, `composio link`, and `composio execute` consumer-only
1137 - Keep developer-scoped usage under `composio manage ...`
1138 - Remove developer-only flags from root help and add short related-command hints
1139 - Use `consumer_user_id` from consumer project resolve for consumer flows
1140 - Execute: Default to empty object `{}` when no -d/--data or piped stdin provided
1141 - Search CTA: Use `-d "{}"` for tools with no schema properties (shell-safe)
1142 - Updated dependencies [8dc5568]
1143 - @composio/core@0.6.7
1144
1145 ## 0.2.7
1146
1147 ### Patch Changes
1148
1149 - 106618b: - Make top-level `composio search`, `composio link`, and `composio execute` consumer-only
1150 - Keep developer-scoped usage under `composio manage ...`
1151 - Remove developer-only flags from root help and add short related-command hints
1152 - Use `consumer_user_id` from consumer project resolve for consumer flows
1153 - Execute: Default to empty object `{}` when no -d/--data or piped stdin provided
1154 - Search CTA: Use `-d "{}"` for tools with no schema properties (shell-safe)
1155
1156 ## 0.2.6
1157
1158 ### Patch Changes
1159
1160 - Updated dependencies [e1f6516]
1161 - @composio/core@0.6.6
1162
1163 ## 0.2.5
1164
1165 ### Patch Changes
1166
1167 - a5be528: Cli release with changes in command scopes
1168
1169 ## 0.2.4
1170
1171 ### Patch Changes
1172
1173 - 67867ae: Add login flags for agent/auth flows: `--no-wait` (print URL/session info and exit), `--key` (complete login with session key; polls until linked unless `--no-wait` is also passed)
1174
1175 ## 0.2.3
1176
1177 ### Patch Changes
1178
1179 - Updated dependencies [476d451]
1180 - Updated dependencies
1181 - @composio/core@0.6.5
1182
1183 ## 0.2.2
1184
1185 ### Patch Changes
1186
1187 - 25c3246: CLI v0.2.2: interactive login picker, --no-wait for link, whoami security
1188
1189 ### What's New
1190 - **Interactive org/project picker** after `composio login` (use `-y` to skip)
1191 - **`--no-wait`** flag for `composio link` — print URL/JSON and exit without waiting
1192 - **Whoami** no longer exposes API keys (security improvement)
1193
1194 ### Breaking Changes
1195 - Removed `--api-key`, `--org-id`, `--project-id` from `composio login` and `composio init`
1196 - Non-interactive login/init via flags is no longer supported; use browser flow with `-y` for login
1197
1198 ## 0.2.1
1199
1200 ### Patch Changes
1201
1202 - ecb455c: Fix CTAs and Link commands
1203
1204 ## 0.2.0
1205
1206 ### Minor Changes
1207
1208 - c35b38b: Add top-level command aliases, restructure root help with BASIC/ADVANCED sections, and show full usage/options for basic commands
1209
1210 ## 0.1.35
1211
1212 ### Patch Changes
1213
1214 - Updated dependencies [e3f1f6c]
1215 - @composio/core@0.6.4
1216
1217 ## 0.1.34
1218
1219 ### Patch Changes
1220
1221 - 3d74f52: Added compact gh-style root help for composio --help and fixed the project environment detector empty-directory test on macOS. Updated root help copy (tagline, login/logout, generate) and resolved the CI typecheck failure in bin.ts.
1222
1223 ## 0.1.33
1224
1225 ### Patch Changes
1226
1227 - 5890693: Add a new commands for CLI org switching and project switching
1228
1229 ## 0.1.32
1230
1231 ### Patch Changes
1232
1233 - 9ebaac5: Fallback to gloabl user_id if project user_id is not present
1234
1235 ## 0.1.31
1236
1237 ### Patch Changes
1238
1239 - 6db8463: Skip user api key from env
1240
1241 ## 0.1.30
1242
1243 ### Patch Changes
1244
1245 - 5015210: Fallback to global context if project apikeys not found
1246
1247 ## 0.1.29
1248
1249 ### Patch Changes
1250
1251 - 7b47f35: Fix cli login command
1252
1253 ## 0.1.28
1254
1255 ### Patch Changes
1256
1257 - 2bd2db4: Update tool search and API key inference
1258
1259 ## 0.1.27
1260
1261 ### Patch Changes
1262
1263 - 25a3898: Fix test installation
1264
1265 ## 0.1.26
1266
1267 ### Patch Changes
1268
1269 - dfb07f2: BUmp cli version to enable new release flow
1270
1271 ## 0.1.25
1272
1273 ### Patch Changes
1274
1275 - d7dfa62: Upgrade the new CLI with composio flows