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, 18:30 UTC
feat(cli): install plugins from the CLI installer (#3840)
## Summary - run plugin setup automatically from the canonical `install.sh` flow after shell integration - configure every detected Claude Code and Codex host through the setup engine from #3835 - add `composio setup --if-present` so installer automation succeeds when no supported host is installed - support `--no-plugins` and `COMPOSIO_INSTALL_PLUGINS=0` as explicit opt-outs - fail visibly with an exact retry command when a detected host cannot be configured ## Stack This is a deliberately small follow-up to #3835 and targets `jk/cli-plugin-setup-review`. It should be rebased onto `next` after #3835 merges. ## Behavior The installer invokes the newly installed binary directly, so it does not depend on the current shell reloading `PATH`: ```bash "$exe" setup --target auto --yes --if-present ``` No detected host is a successful no-op. A detected host setup failure leaves the CLI installed but fails the installer with `composio setup --target auto --yes` as the retry path. ## Validation - install.sh release-resolution, automatic setup, opt-out, and setup-failure harness passed - focused setup suite: 25 tests passed - full CLI suite: 83 files passed; 761 tests passed; 1 skipped - direct CLI source and test typechecks passed - stable and beta skill validation passed - focused ESLint, shell syntax checks, and `git diff --check` passed - packaged setup E2E updated for the no-host installer path; local launch is blocked by missing `mise`, so scratch-container CI is the authoritative packaged check ## Recording No VHS recording: this is installer orchestration plus a non-interactive automation flag, covered at the shell-installer and packaged CLI boundaries.
No changes.