CLI 0.5.0 exits 1 on failed executions and runs composio execute through the Composio Dashboard
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.
Release versions
Breaking changes
- Failed executions exit 1.
composio executenow 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. Incomposio run,execute()still rejects with the tool’s error message and the failed result. - 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:
composio dev auth-configs infowithout an<id>composio dev auth-configs createwith--custom-credentialsthat isn’t a JSON objectcomposio tools infowithout a<slug>composio dev triggers createwithout a<trigger-name>, or with--trigger-configthat isn’t a JSON objectcomposio dev triggers enablewithout an<id>
composio orgs switchwithout a usable key exits 1. When the stored API key is empty,composio orgs switchnow exits 1 and asks you to runcomposio login, instead of warning and exiting 0. It changes nothing either way.
Improvements
- The CLI calls the backend you logged in to.
composio loginrecords the backend that issued your key, but commands used to call production unlessCOMPOSIO_BASE_URLorCOMPOSIO_ENVIRONMENTwas set, so a staging login failed withInvalid 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 executeuses the Dashboard recorded with the same login. A rejected key now prints the command to log in again. - Unmatched
--accountis a usage error. When--accountmatches no connected account,composio executeandcomposio proxyprint one line on stderr and exit 1, instead of a crash report. composio executegoes through the Dashboard. Single executions,--parallelexecutions, and meta tools all use the Dashboard athttps://dashboard.composio.dev. Output, error details, connection tips, and--jsonshapes stay the same. If the backend is unavailable, the CLI shows the Dashboard’s error message. If your network restricts outbound hosts, allowdashboard.composio.devas well asbackend.composio.dev. Every other command, includingcomposio dev playground-execute, still calls the backend API.- 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.
- Custom deployments. If you set
COMPOSIO_BASE_URLwithoutCOMPOSIO_WEB_URL,composio executekeeps calling that backend. To use a deployment’s Dashboard, set both.COMPOSIO_WEB_URLmust be anhttps://URL without credentials, a query string, or a fragment (http://is accepted only forlocalhost). Otherwisecomposio executefails before sending anything. - Telemetry install ID. When telemetry is enabled,
composio executesends the CLI’s anonymous install ID, the random UUID stored in~/.composio/analytics.json, to the Dashboard in anx-cli-install-idheader. The header is never sent to the backend API. It isn’t sent when you setCOMPOSIO_CLI_TELEMETRY_DISABLED,TELEMETRY_DISABLED,COMPOSIO_DISABLE_TELEMETRY, orCI. - Clearer
composio linkmessages.composio linkandcomposio dev connected-accounts linkreword their usage errors and their waiting and timeout lines on stderr. Exit codes and the JSON on stdout are unchanged. - API client. The CLI uses
@composio/client2.0.0-rc.19. Commands are unchanged.