@devries-cameron20 / composio-1 / commits / 5941fbace
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.

docs(cli): announce the shell-setup default in its own dated entry

The 07-31 changelog entry is already published on next and describes the install-only default that composio.dev/install serves today. Rewriting it in place would replace a live, accurate description with its opposite under a date on which that behavior never shipped, and readers who already saw it would get no notice of the flip. Restore that entry verbatim and add a dated 08-05 entry carrying the behavior-change callout, the auto/none bullets, and the created ~/.bash_profile disclosure. The download-verification section moves to the new entry rather than staying on 07-31: the strict abort is new here. The live installer warns and continues when checksums.txt is missing -- the official_release_source gate that turns that into an abort does not exist there. Also scope the HTTPS claim, which is_allowed_http_authority contradicts for loopback and COMPOSIO_INSTALL_ALLOW_HTTP_HOST; document the second shape of the installer-created ~/.bash_profile, which survives the documented uninstall when ~/.profile existed; and record the checksum abort in INSTALL.md, where someone hitting 'Refusing to install' will look for it.

jkomyno committed Aug 5, 2026 at 19:33 UTC 5941fbace11b1c7f5d075b619dd663a077044a19
4 files changed +50 -32
INSTALL.md
+3 -1
@@ -10,6 +10,8 @@ The installer also configures your shell. It infers your login shell from `$SHEL
10
11 If your shell is not recognized, or shell setup fails, the binary install still succeeds and the installer prints a runnable command instead. The installer does not install agent plugins or log you in unless you ask it to.
12
13 +Official releases must pass SHA-256 verification against the release's `checksums.txt`: a missing manifest, a manifest with no entry for your platform's archive, a malformed entry, or a mismatch aborts the install with `Refusing to install`. On systems with no `sha256sum` or `shasum`, the installer warns that verification was skipped and continues.
14 +
15 ## Choose or skip shell setup
16
17 Set `COMPOSIO_INSTALL_SHELL` to force a specific shell, or to skip shell configuration entirely:
@@ -106,7 +108,7 @@ rm -rf \
108 "$install_dir/local-tools-binaries"
109 ```
110
109 -Remove the managed `# Composio CLI` PATH block from `~/.zshrc`, `~/.bashrc`, `~/.bash_profile`, `~/.bash_login`, or `~/.config/fish/config.fish`. Blocks written by older installers contain an extra `export COMPOSIO_INSTALL_DIR=...` (or `set --export COMPOSIO_INSTALL_DIR ...`) line after the marker; remove that line too. If removing the block leaves `~/.bash_profile` with nothing but blank lines, delete the file: the installer creates it on bash systems that had no login startup file, and even an empty `~/.bash_profile` keeps bash from reading `~/.profile`.
111 +Remove the managed `# Composio CLI` PATH block from `~/.zshrc`, `~/.bashrc`, `~/.bash_profile`, `~/.bash_login`, or `~/.config/fish/config.fish`. Blocks written by older installers contain an extra `export COMPOSIO_INSTALL_DIR=...` (or `set --export COMPOSIO_INSTALL_DIR ...`) line after the marker; remove that line too. If removing the block leaves `~/.bash_profile` with nothing but blank lines, delete the file: the installer creates it on bash systems that had no login startup file, and even an empty `~/.bash_profile` keeps bash from reading `~/.profile`. If you had a `~/.profile` at install time, that created file instead holds a passthrough sourcing it, starts with `# Created by the Composio CLI installer.`, and is left in place; delete it as well to restore bash's default startup-file selection.
112
113 To purge credentials, configuration, caches, and every other CLI file, run `rm -rf "${COMPOSIO_INSTALL_DIR:-$HOME/.composio}"`. This is a complete reset and cannot be undone.
114
docs/content/changelog/07-31-26-installer.mdx
+6 -30
@@ -1,41 +1,17 @@
1 ---
2 title: "Install the Composio CLI with a POSIX shell"
3 -description: "The CLI installer now runs on POSIX sh, verifies official release checksums, and configures your shell's PATH by default."
3 +description: "The CLI installer now runs on POSIX sh, keeps the release bundle separate from the entry point, and makes shell configuration opt-in."
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>
7 +The Composio CLI installer now separates the release bundle from the command you run, works with POSIX `sh`, and leaves shell configuration opt-in.
8
9 ### What's new
10
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`.
11 +- `curl -fsSL https://composio.dev/install | sh` installs the verified release bundle in `~/.composio` and creates `~/.local/bin/composio`.
12 +- The default flow does not edit shell files, install agent plugins, or log you in.
13 +- `COMPOSIO_INSTALL_SHELL=zsh|bash|fish` configures the requested shell explicitly, for example `curl -fsSL https://composio.dev/install | COMPOSIO_INSTALL_SHELL=zsh sh`.
14 - `COMPOSIO_INSTALL_VERSION`, `COMPOSIO_BIN_DIR`, `COMPOSIO_QUIET`, and `COMPOSIO_DEBUG` give you control over version, layout, and output.
15 - Existing `COMPOSIO_INSTALL_DIR` configurations keep their bundle-directory meaning.
16
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.
17 +The opt-in default described here was later replaced: see [the installer now configures your shell by default](/docs/changelog/2026/08/05).
docs/content/changelog/08-05-26-installer-shell-default.mdx new
+40
@@ -0,0 +1,40 @@
1 +---
2 +title: "The CLI installer configures your shell by default"
3 +description: "curl | sh now infers your login shell and writes a managed PATH block, with COMPOSIO_INSTALL_SHELL=none as the install-only opt-out."
4 +date: "2026-08-05"
5 +---
6 +
7 +The Composio CLI installer now puts `composio` on `PATH` for future terminals automatically. This replaces the install-only default announced in [Install the Composio CLI with a POSIX shell](/docs/changelog/2026/07/31).
8 +
9 +<Callout type="warn">
10 +**Behavior change: `curl | sh` now edits shell startup files by default**
11 +
12 +The previous installer copied files into place and left `PATH` alone. It now infers your login shell from `$SHELL` and writes a managed `PATH` block to that 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 +
29 +- 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.
30 +- `COMPOSIO_INSTALL_SHELL=zsh|bash|fish` still forces a specific shell, for example `curl -fsSL https://composio.dev/install | COMPOSIO_INSTALL_SHELL=zsh sh`.
31 +- If your `$SHELL` is not zsh, bash, or fish, the installer degrades to an install-only run and prints the command to configure `PATH` yourself.
32 +- Agent plugin installation and login remain opt-in.
33 +- Re-running the installer reconciles the managed block instead of appending a second one, so repeated installs leave exactly one block per startup file.
34 +
35 +### Download verification
36 +
37 +- 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.
38 +- Official releases — the default `github.com/ComposioHQ/composio` source — must now 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. Previously a missing manifest warned and continued.
39 +- On systems with no SHA-256 utility (`sha256sum` or `shasum`), rare outside minimal containers, the installer warns that checksum verification was skipped and continues.
40 +- 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.
docs/content/docs/cli.mdx
+1 -1
@@ -186,7 +186,7 @@ done
186
187 The loop stages every rewrite in a `mktemp` scratch file — created with an unpredictable name and `0600` permissions, so startup-file contents never pass through a world-readable path — and writes the result back only when `awk` succeeds. A failed or missing `awk` leaves the startup file untouched, and the scratch file is always removed. Writing back with `cat` keeps a symlinked startup file intact: the symlink, its target's inode, owner, and mode all survive. The filter removes the current managed block and the three-line block written by older installers (marker plus `export COMPOSIO_INSTALL_DIR=...` or `set --export COMPOSIO_INSTALL_DIR ...`).
188
189 -`~/.bash_profile` gets one extra step: when removing the block leaves only blank lines, the file is deleted. The installer creates `~/.bash_profile` on bash systems that had no login startup file, and bash prefers even an empty `~/.bash_profile` over `~/.profile`, so leaving the empty file behind would silently override bash's normal startup-file selection forever. Note the edge case: a `~/.bash_profile` you created yourself but left empty is also removed.
189 +`~/.bash_profile` gets one extra step: when removing the block leaves only blank lines, the file is deleted. The installer creates `~/.bash_profile` on bash systems that had no login startup file, and bash prefers even an empty `~/.bash_profile` over `~/.profile`, so leaving the empty file behind would silently override bash's normal startup-file selection forever. Note the edge case: a `~/.bash_profile` you created yourself but left empty is also removed. If you had a `~/.profile` when you installed, the created `~/.bash_profile` instead keeps a passthrough that sources it, so the file is not blank and survives the loop with only the block removed. It begins with `# Created by the Composio CLI installer.`; delete it too if you want bash to read `~/.profile` directly again.
190
191 <Callout type="warn">
192 **Purge all CLI state**