skydive-cli 0.2.0-beta.615 → 0.2.0-beta.624

package/README.md

@@ -6,6 +6,53 @@ The Skydive CLI — manage agents and chat with them from the terminal.
 npx skydive-cli --help
 ```
 
+## Installing
+
+Two ways to install, depending on whether you have a Node toolchain:
+
+**npm (needs Node ≥ 20):**
+
+```sh
+npm install -g skydive-cli   # then: skydive --help
+# or run without installing:
+npx skydive-cli --help
+```
+
+**Standalone binary (no Node required):**
+
+```sh
+curl -fsSL https://skydive.com/api/v1/cli/install.sh | sh
+```
+
+Installs a self-contained `skydive` to `~/.local/bin`. The installer detects
+your OS/arch, downloads the matching binary from the release CDN, verifies its
+sha256, and installs it. Options via env vars: `SKYDIVE_CHANNEL=canary` for the
+canary line, `SKYDIVE_VERSION=X.Y.Z` to pin a version, `SKYDIVE_INSTALL_DIR` to
+choose the directory.
+
+## Updating
+
+```sh
+skydive update            # update to the latest release
+skydive update --check    # just report whether an update is available
+```
+
+A **binary** install self-updates in place (download → verify sha256 → atomic
+replace). An **npm/yarn/pnpm/bun** install is owned by your package manager, so
+`skydive update` offers to run the right upgrade command for it and relaunches
+the CLI on the new version.
+
+The CLI also checks for updates in the background (at most once a day, never
+blocking a command) and prints a one-line notice when a newer version exists.
+Control this in `config.json` or via env vars:
+
+- `autoupdate`: `"patch"` (default — silently self-apply a stable **patch**
+  release of a binary install; notify for minor/major, canary, and
+  package-manager installs), `"notify"` (only ever print the notice), or
+  `false` (no auto-update and no notice). Env override: `SKYDIVE_AUTOUPDATE`.
+- `updateCheck: false` (or `SKYDIVE_NO_UPDATE_CHECK` / `NO_UPDATE_NOTIFIER`)
+  turns the background check off entirely.
+
 ## Authentication
 
 Sign in once via the browser — the same shape as `doppler login`: the CLI