@devries-cameron20 / composio Mirror · read-only / commits / f00838c95
Fork 0

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, 17:15 UTC

docs(changelog): disclose the auto shell setup default accurately

Call out the breaking default change (curl | sh now edits startup files and can create ~/.bash_profile), document COMPOSIO_INSTALL_SHELL=none as the install-only opt-out, and align the verification claims with the implemented checksum policy.

jkomyno committed Aug 4, 2026 at 00:15 UTC f00838c95f0df57392001e0e99b9ef5247c6cbdd
1 file changed +27 -2
docs/content/changelog/07-31-26-installer.mdx
+27 -2
@@ -1,16 +1,41 @@
1 ---
2 title: "Install the Composio CLI with a POSIX shell"
3 -description: "The CLI installer now runs on POSIX sh, keeps the release bundle separate from the entry point, and configures your shell automatically."
3 +description: "The CLI installer now runs on POSIX sh, verifies official release checksums, and configures your shell's PATH by default."
4 date: "2026-07-31"
5 ---
6
7 The Composio CLI installer now separates the release bundle from the command you run, works with POSIX `sh`, and puts `composio` on `PATH` for future terminals automatically.
8
9 +<Callout type="warn">
10 +**Behavior change: `curl | sh` now edits shell startup files by default**
11 +
12 +Previous installers only copied files into place. The installer now also writes a managed `PATH` block to your shell's startup files so new terminals find `composio` without manual setup:
13 +
14 +- zsh: `~/.zshrc`
15 +- bash: `~/.bashrc` and your login file — `~/.bash_profile`, or `~/.bash_login` when that is the only login file present
16 +- fish: `~/.config/fish/config.fish`
17 +
18 +On bash systems with no login file at all, the installer **creates `~/.bash_profile`**. When `~/.profile` exists, the new file is seeded to keep sourcing it, so your existing login settings still load.
19 +
20 +To keep the previous install-only behavior, opt out with `COMPOSIO_INSTALL_SHELL=none`:
21 +
22 +```sh
23 +curl -fsSL https://composio.dev/install | COMPOSIO_INSTALL_SHELL=none sh
24 +```
25 +</Callout>
26 +
27 ### What's new
28
11 -- `curl -fsSL https://composio.dev/install | sh` installs the verified release bundle in `~/.composio` and creates `~/.local/bin/composio`.
29 +- `curl -fsSL https://composio.dev/install | sh` installs the release bundle in `~/.composio` and creates `~/.local/bin/composio`.
30 - The default flow infers your shell from `$SHELL` and configures `PATH` for future terminals. Set `COMPOSIO_INSTALL_SHELL=none` for an install-only run in CI, Docker images, or when a dotfile manager owns your startup files.
31 - Agent plugin installation and login remain opt-in.
32 - `COMPOSIO_INSTALL_SHELL=zsh|bash|fish` forces a specific shell, for example `curl -fsSL https://composio.dev/install | COMPOSIO_INSTALL_SHELL=zsh sh`.
33 - `COMPOSIO_INSTALL_VERSION`, `COMPOSIO_BIN_DIR`, `COMPOSIO_QUIET`, and `COMPOSIO_DEBUG` give you control over version, layout, and output.
34 - Existing `COMPOSIO_INSTALL_DIR` configurations keep their bundle-directory meaning.
35 +
36 +### Download verification
37 +
38 +- Every download uses HTTPS, and redirects can only lead to HTTPS URLs.
39 +- Official releases — the default `github.com/ComposioHQ/composio` source — must pass checksum verification: a missing `checksums.txt`, a manifest with no entry for your platform's archive, a malformed entry, or a checksum mismatch aborts the install.
40 +- On systems with no SHA-256 utility (`sha256sum` or `shasum`), rare outside minimal containers, the installer warns that checksum verification was skipped and continues.
41 +- Overridden sources (`COMPOSIO_GITHUB_URL`, `COMPOSIO_GITHUB_OWNER`, `COMPOSIO_GITHUB_REPO`, or a custom API base) are lenient: a missing manifest or entry warns and continues, and only a checksum mismatch or malformed entry aborts.