Skip to content

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

jkomyno5941fbace11b
diff --git a/INSTALL.md b/INSTALL.md
index 8cfa0b795..007c15c27 100644
--- a/INSTALL.md
+++ b/INSTALL.md
@@ -10,6 +10,8 @@ The installer also configures your shell. It infers your login shell from `$SHEL
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.
+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.
+
## Choose or skip shell setup
Set `COMPOSIO_INSTALL_SHELL` to force a specific shell, or to skip shell configuration entirely:
@@ -106,7 +108,7 @@ rm -rf \
"$install_dir/local-tools-binaries"
```
-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`.
+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.
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.
diff --git a/docs/content/changelog/07-31-26-installer.mdx b/docs/content/changelog/07-31-26-installer.mdx
index e5e5e1af7..07c84b832 100644
--- a/docs/content/changelog/07-31-26-installer.mdx
+++ b/docs/content/changelog/07-31-26-installer.mdx
@@ -1,41 +1,17 @@
---
title: "Install the Composio CLI with a POSIX shell"
-description: "The CLI installer now runs on POSIX sh, verifies official release checksums, and configures your shell's PATH by default."
+description: "The CLI installer now runs on POSIX sh, keeps the release bundle separate from the entry point, and makes shell configuration opt-in."
date: "2026-07-31"
---
-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.
-
-<Callout type="warn">
-**Behavior change: `curl | sh` now edits shell startup files by default**
-
-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:
-
-- zsh: `~/.zshrc`
-- bash: `~/.bashrc` and your login file — `~/.bash_profile`, or `~/.bash_login` when that is the only login file present
-- fish: `~/.config/fish/config.fish`
-
-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.
-
-To keep the previous install-only behavior, opt out with `COMPOSIO_INSTALL_SHELL=none`:
-
-```sh
-curl -fsSL https://composio.dev/install | COMPOSIO_INSTALL_SHELL=none sh
-```
-</Callout>
+The Composio CLI installer now separates the release bundle from the command you run, works with POSIX `sh`, and leaves shell configuration opt-in.
### What's new
-- `curl -fsSL https://composio.dev/install | sh` installs the release bundle in `~/.composio` and creates `~/.local/bin/composio`.
-- 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.
-- Agent plugin installation and login remain opt-in.
-- `COMPOSIO_INSTALL_SHELL=zsh|bash|fish` forces a specific shell, for example `curl -fsSL https://composio.dev/install | COMPOSIO_INSTALL_SHELL=zsh sh`.
+- `curl -fsSL https://composio.dev/install | sh` installs the verified release bundle in `~/.composio` and creates `~/.local/bin/composio`.
+- The default flow does not edit shell files, install agent plugins, or log you in.
+- `COMPOSIO_INSTALL_SHELL=zsh|bash|fish` configures the requested shell explicitly, for example `curl -fsSL https://composio.dev/install | COMPOSIO_INSTALL_SHELL=zsh sh`.
- `COMPOSIO_INSTALL_VERSION`, `COMPOSIO_BIN_DIR`, `COMPOSIO_QUIET`, and `COMPOSIO_DEBUG` give you control over version, layout, and output.
- Existing `COMPOSIO_INSTALL_DIR` configurations keep their bundle-directory meaning.
-### Download verification
-
-- Every download uses HTTPS, and redirects can only lead to HTTPS URLs.
-- 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.
-- On systems with no SHA-256 utility (`sha256sum` or `shasum`), 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) are lenient: a missing manifest or entry warns and continues, and only a checksum mismatch or malformed entry aborts.
+The opt-in default described here was later replaced: see [the installer now configures your shell by default](/docs/changelog/2026/08/05).
diff --git a/docs/content/changelog/08-05-26-installer-shell-default.mdx b/docs/content/changelog/08-05-26-installer-shell-default.mdx
new file mode 100644
index 000000000..15c7b054a
--- /dev/null
+++ b/docs/content/changelog/08-05-26-installer-shell-default.mdx
@@ -0,0 +1,40 @@
+---
+title: "The CLI installer configures your shell by default"
+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."
+date: "2026-08-05"
+---
+
+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).
+
+<Callout type="warn">
+**Behavior change: `curl | sh` now edits shell startup files by default**
+
+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:
+
+- zsh: `~/.zshrc`
+- bash: `~/.bashrc` and your login file — `~/.bash_profile`, or `~/.bash_login` when that is the only login file present
+- fish: `~/.config/fish/config.fish`
+
+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.
+
+To keep the previous install-only behavior, opt out with `COMPOSIO_INSTALL_SHELL=none`:
+
+```sh
+curl -fsSL https://composio.dev/install | COMPOSIO_INSTALL_SHELL=none sh
+```
+</Callout>
+
+### What's new
+
+- 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.
+- `COMPOSIO_INSTALL_SHELL=zsh|bash|fish` still forces a specific shell, for example `curl -fsSL https://composio.dev/install | COMPOSIO_INSTALL_SHELL=zsh sh`.
+- 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.
+- 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/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.
+- On systems with no SHA-256 utility (`sha256sum` or `shasum`), 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.
diff --git a/docs/content/docs/cli.mdx b/docs/content/docs/cli.mdx
index 54bdd31bd..e73314e21 100644
--- a/docs/content/docs/cli.mdx
+++ b/docs/content/docs/cli.mdx
@@ -186,7 +186,7 @@ done
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 ...`).
-`~/.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.
+`~/.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.
<Callout type="warn">
**Purge all CLI state**