Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 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. |