Composio's agent CLI makes account choice and cancellation explicit
Version 0.6.0 separates developer-project linking from consumer behavior, returns interruption exit codes and lets listeners fail fast.
Composio CLI 0.6.0 changes what happens when an agent workflow chooses an account, loses its listener or gets cancelled. The November 1 release introduces consistent developer-project and acting-user resolution, explicit interruption exit codes and a fail-fast option for event listeners.
Composio CLI is standalone command-line tooling for the Composio platform, usable alongside coding agents such as Claude Code and Codex. It is not a new model or a model provider. Its commands search and execute tools, link service accounts and run local workflows; developer commands manage projects, accounts and triggers.
More deliberate account selection
According to the release notes, dev connected-accounts link now uses the selected developer project, while root link retains consumer-project behavior. Commands reject shared flags they cannot honor. Developer account linking requires a resolvable project and acting user, so users may need to initialize the working directory or select a project explicitly.
When a toolkit has several accounts without a default alias, scripts must pass --account <id|alias> or establish a default instead of relying on an implicit newest-account choice. Connection listings now expose account IDs, aliases, word IDs and available provider display names. Proxy calls enforce consumer permissions, and local file uploads retain their MIME type.
Cancellation becomes a script-visible outcome
Normal commands interrupted by SIGINT, SIGTERM or SIGHUP now exit with codes 130, 143 or 129 respectively. The run command forwards signals to its child process group and preserves the child’s outcome. Subscribed listeners can stop on Ctrl+C or SIGTERM, while listen and dev triggers listen gain --fail-fast for sink failures. Existing automation must handle those cancellation codes rather than treating interruption as success.
Telemetry is also narrowed to canonical command identity and typed, parsed inputs. The release says lifecycle properties exclude credentials, request bodies, header values, rejected flags and script-tail options. That does not mean telemetry is disabled; the pinned README documents COMPOSIO_CLI_TELEMETRY_DISABLED=1 for opting out.
New installations use Composio’s official installer; existing installations can run composio upgrade. The installation guide supports Linux and macOS directly and Windows through WSL. Authentication uses browser login or a user API key, with local state under ~/.composio. Connected-service permissions and any platform, service or model-provider charges remain separate considerations. The update’s concrete value is clearer operational behavior when tool-connected agents move between projects or run inside scripts.