The CLI installer configures your shell by default
The Composio CLI installer now putscomposio on PATH for future terminals automatically. This replaces the install-only default announced in Install the Composio CLI with a POSIX shell.
What’s new
- The default flow infers your shell from
$SHELLand configuresPATHfor future terminals. SetCOMPOSIO_INSTALL_SHELL=nonefor an install-only run in CI, Docker images, or when a dotfile manager owns your startup files. COMPOSIO_INSTALL_SHELL=zsh|bash|fishstill forces a specific shell, for examplecurl -fsSL https://composio.dev/install | COMPOSIO_INSTALL_SHELL=zsh sh.- If your
$SHELLis not zsh, bash, or fish, the installer degrades to an install-only run and prints the command to configurePATHyourself. - Agent plugin installation and login remain opt-in.
- Re-running the installer reconciles the managed block instead of appending a second one, so repeated installs leave exactly one block per startup file.
Download verification
- Every download uses HTTPS — plain HTTP is accepted only for loopback addresses or a host you explicitly allow with
COMPOSIO_INSTALL_ALLOW_HTTP_HOST— and redirects can only ever lead to HTTPS URLs. - Official releases — the default
github.com/ComposioHQ/composiosource — must now pass checksum verification: a missingchecksums.txt, a manifest with no entry for your platform’s archive, a malformed entry, or a checksum mismatch aborts the install. Previously a missing manifest warned and continued. - On systems with no SHA-256 utility (
sha256sumorshasum), rare outside minimal containers, the installer warns that checksum verification was skipped and continues. - Overridden sources (
COMPOSIO_GITHUB_URL,COMPOSIO_GITHUB_OWNER,COMPOSIO_GITHUB_REPO, or a custom API base) stay lenient: a missing manifest or entry warns and continues, and only a checksum mismatch or malformed entry aborts.