@lumi.ai/runner 0.5.7 → 0.5.9

package/README.md

@@ -69,7 +69,8 @@ lumi-runner login --key <shipKey> --api-key <firebaseWebApiKey> --project <proje
 | `start` | Run the daemon in the foreground |
 | `status` | Ships, approval state, current job, queue depth, today's tokens |
 | `logs [-f]` | The daemon's own rotating log file |
-| `config list` / `set <key> <on\|off>` | `notifications`, `keepAwake` |
+| `update [--check]` | Install the latest published version and restart (see **Staying current**) |
+| `config list` / `set <key> <value>` | `notifications`, `keepAwake`, `autoUpdate`, `channel`, `checkEvery`, `parallel` |
 
 Global flags: `--json` (machine-readable stdout, and never prompts), `-y/--yes`, `--no-color`.
 
@@ -116,6 +117,41 @@ Each job is a separate `claude` process with its own empty working directory, so
 state — but they do share your CPU, your RAM and your Claude usage window. Start at 2 and watch a
 real job before going higher. Restart the daemon (`lumi-runner service restart`) to pick up a change.
 
+## Staying current
+
+**This machine updates itself.** Every half hour the daemon asks npm whether there is a newer
+version on the channel it was installed from. When there is, it stops claiming new work, lets the
+jobs it is already running **finish**, installs the new version, and exits — launchd and systemd
+restart it, which is what picks up the new code. A captain sees all of it on the Daemons page.
+
+It only ever does this when the background service is installed and running, because "exit and be
+restarted" is the whole mechanism: a daemon you started by hand in a terminal tells you about the
+update and leaves it to you. Windows is the same — the running file is locked there and the
+scheduled task does not restart on exit — so `lumi-runner update` prints the command instead.
+
+```bash
+lumi-runner update --check     # is there a newer version?
+lumi-runner update             # install it now and restart the service
+```
+
+To pin a machine to a version:
+
+```bash
+npm i -g @lumi.ai/runner@0.5.7
+lumi-runner config set autoUpdate off
+```
+
+Other settings, all machine-wide:
+
+```bash
+lumi-runner config set channel dev        # follow prereleases (default: whichever you installed)
+lumi-runner config set checkEvery 360     # ask less often (minutes, 5–1440)
+```
+
+A version is never installed twice: three failed attempts at the same one and the machine stops
+trying until a different version is published. `lumi-runner doctor` reports whether you are behind,
+always as a warning — being out of date never fails the preflight.
+
 ## While a job runs
 
 - **Idle sleep is inhibited** (`caffeinate` / `systemd-inhibit`, best-effort on Windows), so a
@@ -190,6 +226,8 @@ claiming from one queue.
 | `CREW_CLAUDE_BIN` | Path to the Claude binary (default: `claude` from `PATH`) |
 | `CREW_NO_NOTIFY` | Disable desktop notifications |
 | `CREW_NO_POWER` | Disable sleep inhibition |
+| `LUMI_RUNNER_REGISTRY` | npm registry to check for updates (default `https://registry.npmjs.org`) |
+| `LUMI_RUNNER_CHANNEL` | Force the update channel: `latest` or `dev` |
 
 `CREW_RUNNER_HOME` is still honoured as a fallback for machines configured before the rename.