@devries-cameron20 / composio Mirror · read-only / commits / 47fc24c71
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, 08:30 UTC

chore(cli): release CLI 0.5.0 (#5001)

This PR: - releases the CLI's Unreleased changes as **0.5.0**, a minor release: `composio execute` exits 1 on a failed execution (#5002), five commands exit 1 on invalid input (#4998), and `orgs switch` exits 1 on an empty stored key (#5029), where they used to exit 0 - splits `ts/packages/cli/CHANGELOG.md` into Minor Changes (the three exit-code changes, with a breaking note) and Patch Changes (#4754's Dashboard execution, #5000's stored-login backend, #5003's `--account` usage error, #5029's `connected-accounts list` shape check, the `composio link` wording, the rc.19 client) - adds `docs/content/changelog/10-21-26-cli-release.mdx` with a Breaking changes section - no Changeset, and the CLI `package.json` is unchanged: the version comes from the beta that gets promoted ## Context ### Releasing 0.5.0 Automatic betas from `next` are numbered `0.4.6-beta.N`, so they can't become 0.5.0. Per `.agents/skills/cli-release/references/release-workflow.md`, an intentional minor needs an explicitly versioned beta: 1. Merge this PR. It only touches the changelogs, so the beta can also be built before it merges; the binary is the same. 2. Dispatch `gh workflow run build-cli-binaries.yml --repo ComposioHQ/composio --ref next --raw-field action=build-beta --raw-field version=0.5.0`, and watch it through the installation tests. 3. Optionally re-run the upgrade check below against the new `@composio/cli@0.5.0-beta.N`. 4. Confirm that exact tag and dispatch `promote-stable` at it. The latest stable is 0.4.5, so `@composio/cli@0.5.0` is free. Merging this PR runs the docs changelog notification workflows for the new `.mdx`. ### Upgrade check Beta: `@composio/cli@0.4.6-beta.475`, target commit `09e2fb7faa41c51fcd364ee01e0aaf6719a62896` (#4754), published 2026-10-20T15:39:35Z. All six assets are `uploaded`, and [Build CLI Binaries run 39449485448](https://github.com/ComposioHQ/composio/actions/runs/39449485448) passed, including the installation tests. Each old version ran from its released `composio-darwin-aarch64.zip` (checksum matched the release's `checksums.txt`), unpacked into `$HOME/.composio` of a fresh temporary `HOME`, with telemetry off. | Old version | Upgrade command | Upgrade | `composio --version` | `composio run 'console.log(1)'` | Script that calls `experimental_subAgent()` | Files after upgrade | | --- | --- | --- | --- | --- | --- | --- | | 0.4.2 | `composio upgrade 0.4.6-beta.475` | exit 0, checksum verified | `0.4.6-beta.475` | `1`, exit 0 | try/catch script: removal message caught, exit 0. Uncaught call: same message, exit 1 | 10 legacy paths are 0 bytes, `release-tag.txt` = beta tag | | 0.3.3 | `composio upgrade 0.4.6-beta.475` | exit 0, checksum verified | `0.4.6-beta.475` | `1`, exit 0 | same | same; `generation-runtime.mjs` restored on first `run` | | 0.2.14 | `COMPOSIO_GITHUB_TAG='@composio/cli@0.4.6-beta.475' composio upgrade` | exit 0, checksum verified | `0.4.6-beta.475` | `1`, exit 0 | same | 4 `run-subagent-*.mjs` are 0 bytes; runtime modules restored on first `run` | The removal message, as printed: `experimental_subAgent() was removed from composio run because its agent transport automatically approved permission requests. Print the tool results and let the calling agent summarize them instead.` Notes: - #4732 is already in stable releases since 0.4.3. This check confirms that its placeholder files still let 0.2.14 through 0.4.2 upgrade to the current beta. - Old upgraders never delete files. After upgrading from 0.4.2 or 0.3.3, the old `services/run-subagent-*.mjs` bundles (2.4–6.3 MB) stay on disk. They are unused. - Old binaries read their GitHub settings with a `COMPOSIO_` prefix (`COMPOSIO_GITHUB_TAG`, `COMPOSIO_GITHUB_API_BASE_URL`). With a bare `GITHUB_TAG=<tag>`, 0.2.14 ignores the pin and installs the latest stable, 0.4.5. To pin a release on an old binary, set `COMPOSIO_GITHUB_TAG`, not `GITHUB_TAG`. - This machine's IP had used up GitHub's unauthenticated API quota. The old upgraders can't send a token, so their release lookups (`COMPOSIO_GITHUB_API_BASE_URL`) went through a local GET-only proxy that added a token. The asset downloads, checksum checks and file replacement ran as they do for users. ### Checks run - `bun run lint:links` (docs): 0 errors. - `bun test tests/static/` (docs): 727 pass, 5 fail. All 5 are in `content-freshness.test.ts` and fail the same way on `next`. - `prettier --check` on both changed files: clean. - `pnpm validate:changesets`: passed.

Alberto Schiabel committed Oct 21, 2026 at 19:34 UTC 47fc24c71be55fb758e51e1c53bcc091e3a6dfb6
2 files changed +68 -12
docs/content/changelog/10-21-26-cli-release.mdx new
+37
@@ -0,0 +1,37 @@
1 +---
2 +title: 'CLI 0.5.0 exits 1 on failed executions and runs `composio execute` through the Composio Dashboard'
3 +description: 'Failed tool executions and invalid input now exit 1, the CLI calls the backend you logged in to, and `composio execute` goes through the Composio Dashboard.'
4 +date: '2026-10-21'
5 +---
6 +
7 +CLI 0.5.0 is a minor release because of one breaking change: commands that failed but exited 0 now exit 1. It also fixes staging and custom-backend logins, and sends `composio execute` through the Composio Dashboard. You don't need to log in again or change any configuration.
8 +
9 +### Release versions
10 +
11 +| SDK | Version |
12 +| -------------- | ------- |
13 +| CLI `composio` | `0.5.0` |
14 +
15 +### Breaking changes
16 +
17 +- **Failed executions exit 1.** `composio execute` now exits 1 when a tool execution fails: the tool reported a failure, the Dashboard or backend couldn't run it, or, with `--parallel`, any one of the calls failed. Meta tools behave the same. It used to exit 0. The `{"successful": false, ...}` JSON on stdout and the messages on stderr are unchanged. In `composio run`, `execute()` still rejects with the tool's error message and the failed result.
18 +- **Invalid input exits 1.** These commands now exit 1 instead of 0 when their input is missing or invalid. They print the same message on stderr, nothing on stdout, and send no request:
19 + - `composio dev auth-configs info` without an `<id>`
20 + - `composio dev auth-configs create` with `--custom-credentials` that isn't a JSON object
21 + - `composio tools info` without a `<slug>`
22 + - `composio dev triggers create` without a `<trigger-name>`, or with `--trigger-config` that isn't a JSON object
23 + - `composio dev triggers enable` without an `<id>`
24 +- **`composio orgs switch` without a usable key exits 1.** When the stored API key is empty, `composio orgs switch` now exits 1 and asks you to run `composio login`, instead of warning and exiting 0. It changes nothing either way.
25 +
26 +If a script or agent checks the exit code, it now sees these failures. If it relied on exit 0 after a failed execution, handle exit 1 instead.
27 +
28 +### Improvements
29 +
30 +- **The CLI calls the backend you logged in to.** `composio login` records the backend that issued your key, but commands used to call production unless `COMPOSIO_BASE_URL` or `COMPOSIO_ENVIRONMENT` was set, so a staging login failed with `Invalid or revoked user API key`. Those variables still win when set, and the CLI warns on stderr when one sends your stored key to a different backend. `composio execute` uses the Dashboard recorded with the same login. A rejected key now prints the command to log in again.
31 +- **Unmatched `--account` is a usage error.** When `--account` matches no connected account, `composio execute` and `composio proxy` print one line on stderr and exit 1, instead of a crash report.
32 +- **`composio execute` goes through the Dashboard.** Single executions, `--parallel` executions, and meta tools all use the Dashboard at `https://dashboard.composio.dev`. Output, error details, connection tips, and `--json` shapes stay the same. If the backend is unavailable, the CLI shows the Dashboard's error message. If your network restricts outbound hosts, allow `dashboard.composio.dev` as well as `backend.composio.dev`. Every other command, including `composio dev playground-execute`, still calls the backend API.
33 +- **Executions are sent once.** The CLI sends each execution request once, without retrying or following redirects. After 15 minutes it stops waiting and reports that the tool may still have run.
34 +- **Custom deployments.** If you set `COMPOSIO_BASE_URL` without `COMPOSIO_WEB_URL`, `composio execute` keeps calling that backend. To use a deployment's Dashboard, set both. `COMPOSIO_WEB_URL` must be an `https://` URL without credentials, a query string, or a fragment (`http://` is accepted only for `localhost`). Otherwise `composio execute` fails before sending anything.
35 +- **Telemetry install ID.** When telemetry is enabled, `composio execute` sends the CLI's anonymous install ID, the random UUID stored in `~/.composio/analytics.json`, to the Dashboard in an `x-cli-install-id` header. The header is never sent to the backend API. It isn't sent when you set `COMPOSIO_CLI_TELEMETRY_DISABLED`, `TELEMETRY_DISABLED`, `COMPOSIO_DISABLE_TELEMETRY`, or `CI`.
36 +- **Clearer `composio link` messages.** `composio link` and `composio dev connected-accounts link` reword their usage errors and their waiting and timeout lines on stderr. Exit codes and the JSON on stdout are unchanged.
37 +- **API client.** The CLI uses `@composio/client` `2.0.0-rc.19`. Commands are unchanged.
ts/packages/cli/CHANGELOG.md
+31 -12
@@ -1,8 +1,13 @@
1 # @composio/cli
2
3 -## Unreleased
3 +## 0.5.0
4
5 -### Patch Changes
5 +### Minor Changes
6 +
7 +- Breaking: some commands now exit 1 where they used to exit 0. Scripts and
8 + agents that read the exit code to decide whether a call worked now get the
9 + right answer; a script that relied on exit 0 after a failed execution must
10 + handle exit 1. Output on stdout and stderr is unchanged.
11
12 - `composio execute` now exits 1 when a tool execution fails: the tool
13 reported a failure, the Composio Dashboard or backend could not run it, or,
@@ -11,6 +16,26 @@
16 messages on stderr are unchanged. In `composio run`, `execute()` still
17 rejects with the tool's error message and the failed result.
18
19 +- These commands now exit 1 instead of 0 when their input is missing or
20 + invalid, printing the same message and example on stderr and nothing on
21 + stdout. No request is sent.
22 + - `composio dev auth-configs info` without an `<id>`
23 + - `composio dev auth-configs create` with `--custom-credentials` that is not
24 + a JSON object
25 + - `composio tools info` without a `<slug>`
26 + - `composio dev triggers create` without a `<trigger-name>`, or with
27 + `--trigger-config` that is not a JSON object
28 + - `composio dev triggers enable` without an `<id>`
29 +
30 +- `composio orgs switch` now exits 1 and asks you to run `composio login`
31 + when the stored `api_key` is empty. It used to warn and exit 0. Nothing is
32 + written in either case.
33 +
34 +### Patch Changes
35 +
36 +- `composio dev connected-accounts list` now reports a response whose `items`
37 + is not a list as a request error and exits 1. It used to crash.
38 +
39 - `composio execute` and `composio proxy` now report an `--account` that
40 matches no connected account (`No connected account matched "…"`) as one
41 line on stderr and exit 1, like other usage errors. They used to print it
@@ -41,16 +66,6 @@
66 `COMPOSIO_DISABLE_TELEMETRY`, or `CI`): when telemetry is off, or no install
67 ID is stored, the header is not sent. It is never sent to the backend API.
68
44 -- These commands now exit 1 instead of 0 when their input is missing or
45 - invalid, printing the same message and example on stderr and nothing on
46 - stdout. No request is sent.
47 - - `composio dev auth-configs info` without an `<id>`
48 - - `composio dev auth-configs create` with `--custom-credentials` that is not
49 - a JSON object
50 - - `composio tools info` without a `<slug>`
51 - - `composio dev triggers create` without a `<trigger-name>`, or with
52 - `--trigger-config` that is not a JSON object
53 - - `composio dev triggers enable` without an `<id>`
69 - The CLI now calls the backend you logged in to. `composio login` already
70 recorded it as `base_url` in `user_data.json`, but every command replaced it
71 with the production default unless `COMPOSIO_BASE_URL` or
@@ -66,6 +81,7 @@
81 environment selects, since agents.composio.dev issued its key. A rejected
82 user API key now prints how to log in again, naming the backend and
83 Dashboard when they are not production's.
84 +
85 - `composio link` and `composio dev connected-accounts link` reword their usage
86 and status messages on stderr: the rejected `--auth-config` on the root
87 command, a toolkit passed together with `--auth-config`, a missing toolkit,
@@ -73,8 +89,10 @@
89 developer project, an incomplete link response, a toolkit whose auth
90 Composio does not manage, and the waiting and timeout lines shown while a
91 link is pending. Exit codes and the JSON printed on stdout are unchanged.
92 +
93 - The CLI now uses `@composio/client@2.0.0-rc.19` (up from `2.0.0-rc.17`). No
94 command changes.
95 +
96 - API requests now authenticate through the API client's `auth` option (the
97 logged-in user's API key, or no credential before login) and name the org and
98 project through its `scope`, instead of the CLI placing `x-user-api-key`,
@@ -82,6 +100,7 @@
100 unchanged. The CLI no longer keeps a client per API key and project for the
101 life of the process, so the user API key is held only by the client making
102 the request.
103 +
104 - The API client's deprecation notices are dropped by the CLI's logger instead
105 of being turned off in the client. Nothing new is printed.
106