kylon-cli 0.3.8 → 0.3.9-next.686

package/README.md

@@ -67,16 +67,20 @@ hosted install script in `~/.kylon/server-url`, then production.
 `agent link` authenticates only the link operation with its embedded
 credential; it never creates a human CLI session. Linking mints or reuses an
 installation credential stored locally with mode `0600` and starts the local
-agent runtime. In release builds on supported environments a user-level
-`launchd` / `systemd --user` service is installed so the daemon survives
-terminal exit, reboot, and sleep/wake; otherwise the daemon runs in the
-foreground until `Ctrl+C`.
+agent runtime. In release builds a user-level service is installed so the
+daemon survives terminal exit, reboot, and sleep/wake: `launchd` on macOS,
+`systemd --user` on Linux, and on Windows a logon-triggered Scheduled Task
+named `Kylon Gateway` that runs `kylon gateway supervise`, a small loop that
+restarts `gateway run` after a crash and after a drained upgrade. When no
+service can be installed (a source build, or a Windows machine whose policy
+blocks scheduled tasks) the daemon runs in the foreground until `Ctrl+C`, and
+`connect` says so.
 
 The dist-tag tracks the environment: production uses `@latest`, dev uses
 `@next` (newest prerelease). To pin a specific build, use `kylon-cli@X.Y.Z`.
 
-Requirements: Linux / macOS only (Windows operators should use WSL). The
-hosted script needs no preinstalled Node.js; the `npx` spellings need
+Requirements: macOS, Linux, or Windows. The hosted `install.sh` needs no
+preinstalled Node.js; the Windows `install.ps1` and the `npx` spellings need
 Node.js 22.15.0+ (npm ships with Node).
 
 ### One managed `kylon` for humans and agents
@@ -97,6 +101,28 @@ fresh `npx` can still install itself over an older pinned copy; set
 
 ### Upgrading a local runtime
 
+Automatic Kylon CLI updates are enabled by default for each enrolled computer.
+The server checks an online computer for an eligible update at most once every
+four hours. When it rolls an exact published version out to that computer, the
+daemon uses the same drain-restart path as a manual upgrade: it waits for active
+agent work to finish, installs the managed bundle under `~/.kylon/bin`, and
+restarts onto it. The server never requests `--force` automatically.
+
+The owner can change the setting under **Settings → Developer tools → Kylon
+CLI → Authorized devices**, or from that computer:
+
+```bash
+kylon gateway auto-update status
+kylon gateway auto-update on
+kylon gateway auto-update off
+```
+
+The setting controls future automatic requests only. Turning it off does not
+cancel an upgrade whose drain has already started, and manual upgrades remain
+available.
+
+To upgrade manually:
+
 ```bash
 npx --yes kylon-cli@latest gateway service upgrade
 ```
@@ -151,8 +177,13 @@ for the debugger-friendly tsx-based dev loop.
 
 ### Release channels
 
-npm dist-tags are the version pointer — there is no server-side version
-policy. Every merge to `develop` publishes a prerelease to the `next` tag
+npm dist-tags remain the publication pointer. A separate server runtime-config
+policy (`cli_auto_update/latest` and `cli_auto_update/next`) selects an exact
+currently published target plus a 0-100% stable per-computer rollout for
+automatic updates. A missing, disabled, mismatched, or 0% policy sends no
+automatic request; manual upgrades still resolve the dist-tag normally.
+
+Every merge to `develop` publishes a prerelease to the `next` tag
 (`.github/workflows/cli-publish.yml`). A production deployment dispatched from
 `main` automatically invokes the same workflow in stable mode and publishes the
 exact `packages/cli/package.json` version to `latest`; it is idempotent when that
@@ -262,7 +293,8 @@ workspace; sign in again to replace one with the per-installation flow.
 
 `gateway run` starts the local runtime service from this environment's saved
 connection. It is the command the installed `launchd` / `systemd --user`
-service execs; run it manually to keep connected agents available in the foreground.
+service execs, and the child the Windows `gateway supervise` loop keeps
+running; run it manually to keep connected agents available in the foreground.
 
 ```bash
 kylon gateway run

package/dist/kylon-bundle.manifest.json

@@ -0,0 +1,5 @@
+{
+  "version": "0.3.9-next.686",
+  "fingerprint": "000c2bc294c938f997327d49a0dabcdef2c77a7721f833703d85831727d6cb3a",
+  "source_commit": "e686c3b8070a831294238bdc6d76c47893f867dc"
+}