CLI @composio/cli@0.6.0
Composio CLI 0.6.0 introduces explicit signal interruption exit codes, standardized project/user resolution for developer commands, listener failure controls, and sanitized telemetry.
Why this signal matters
Composio CLI release 0.6.0 updates developer-project and acting-user resolution rules, ensuring dev connected-accounts link uses the developer project while the root link uses consumer-project behavior. Process signal handling is standardized: SIGINT, SIGTERM, and SIGHUP result in exit codes 130, 143, and 129 respectively, with signal forwarding to child process groups in run . The listen and dev triggers listen commands add a --fail-fast flag for sink failures. Additionally, proxy calls enforce consumer permissions, file uploads retain MIME types, and telemetry strips sensitive lifecycle data like headers, request bodies, and unparsed input.
Actionable summary
Composio CLI 0.6.0 changes exit codes on SIGINT (130), SIGTERM (143), and SIGHUP (129), and forwards signals in run . Developer project resolution is now strictly enforced for dev commands, requiring explicit project selection or account flags when defaults are absent.
- Agent usefulness
- 72/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Update automation scripts to handle standard exit codes (130, 143, 129) instead of expecting 0 on signal cancellations.
- Initialize working directories or explicitly pass a project to developer commands if implicit developer-project resolution fails.
- Specify --account or configure a default alias when interacting with toolkits that contain multiple accounts.
- Run composio upgrade or reinstall via curl script to adopt version 0.6.0.