@cabane/companion 0.6.159 → 0.6.160

package/README.md

@@ -52,7 +52,7 @@ cabane start
 
 Either puts `cabane` on your PATH, with `cabane-companion` kept as an alias. If `cabane` isn't found right after an npm install, npm's global bin isn't on your PATH: run `"$(npm prefix -g)/bin/cabane" start`, and the Companion prints full paths from then on. If npm reports `EEXIST … cabane`, an older self-host CLI owns the name: `npm i -g @cabane/cli@latest` (its command is `cabane-server` now), then install again.
 
-To **update**, stop first, because a stop ends any turn in progress: `cabane stop`, then re-run the install script (it starts the new version), or `npm i -g @cabane/companion@latest` and `cabane start`. The install script changes nothing while a Companion is running.
+To **update**, run `cabane update`, whichever way you installed: it installs the version Cabane names. Under the service (below) the Companion restarts into it once its turns finish; without the service, the next `cabane start` runs it, and `cabane stop` before that ends any turn in progress. Re-running the install script changes nothing while a Companion is running.
 
 ## First run
 
@@ -310,7 +310,7 @@ What "exposed" means differs per harness, because each is discoverable in a diff
 | **Codex**       | A `codex` block in `~/.cabane/config.json`, **and** the Codex SDK's vendored binary installed.     |
 | **opencode**    | An `opencode.serverUrl` in `~/.cabane/config.json` pointing at a reachable `opencode serve`.       |
 
-Claude Code and Codex each run a native binary their SDK ships, installed alongside the Companion as an optional npm dependency. Those are what a turn launches — not the `claude` / `codex` CLIs on your PATH, which are for setup and login. If one didn't install, the Companion says so on startup and on the device's page in Cabane, with the command that repairs it: `npm i -g @cabane/companion --include=optional`.
+Claude Code and Codex each run a native binary their SDK ships, installed alongside the Companion as an optional npm dependency. Those are what a turn launches — not the `claude` / `codex` CLIs on your PATH, which are for setup and login. If one didn't install, the Companion says so on startup and on the device's page in Cabane, with the commands that repair it: `npm i -g @cabane/companion --include=optional` for an npm install, `cabane stop` then the install script for a script install, and `cabane stop` then `cabane update` for a copy Cabane installed itself when it updated or became a service. Stopping ends any turn in progress.
 
 **You usually don't hand-edit the config.** Interactive `cabane start` offers each signed-in agent, and `cabane connect codex` (or `claude-code` / `opencode`) can connect one later. Editing `~/.cabane/config.json` yourself is the fallback and what a headless device wants: