kylon-cli 0.6.0-next.835 → 0.6.0-next.838

package/README.md

@@ -380,6 +380,13 @@ Nothing installs a provider CLI in the background. A daemon that finds its
 provider missing reports it and waits — installing software on someone's
 machine is something they ask for, not something a health check decides.
 
+Codex normally uses the desktop app's current executable when installed. To
+select a specific installation, set `KYLON_CODEX_BINARY_PATH` to its absolute
+executable path before connecting or repairing the gateway service. The service
+captures this selection for health checks and agent turns. A missing or invalid
+path fails instead of switching installations. Use the same path with
+`kylon provider update codex --binary-path <path>` when updating that installation.
+
 The drain waits up to five minutes for in-flight agent work, and a drain that
 exhausts its window rolls the upgrade back — so a persistently busy host would
 never upgrade without an operator interrupt. Two are available:
@@ -533,13 +540,19 @@ kylon gateway run
 It takes no connection flags: link an agent first with `kylon agent link`.
 Without a saved runtime connection it exits with guidance pointing there.
 
-### Sleep, wake, and keep-awake (macOS)
+### Sleep, wake, and keep-awake (macOS and Windows)
+
+By default the daemon requests idle sleep prevention whenever it runs: macOS
+uses `caffeinate`; Windows uses a hidden helper tied to the daemon's lifetime.
+The display can turn off while agents remain available. Sleep prevention is
+only requested on AC power; Windows checks for battery transitions every second.
+Battery, lid-close, and manual sleep policy still take precedence. No effect on Linux.
 
-By default the daemon holds a macOS sleep assertion (the same mechanism as
-`caffeinate`) whenever it runs: on AC power the machine can turn its display
-off without ever going to sleep, so its agents stay online and dispatchable
-from the web at any time. Sleep is only prevented on AC power — on battery,
-and when the lid closes, normal sleep policy always wins. No effect on Linux.
+On Windows, the hidden scheduled-task launcher retries a failed supervisor three times at one-minute
+intervals. A normal exit with no saved registration stays stopped. This does not
+run while the user is signed out, wake a sleeping computer, or recover every
+explicit Task Scheduler stop. Updated task definitions take effect on the next
+task start; an already running supervisor keeps its original code until restarted.
 
 ```bash
 kylon keep-awake            # show the current mode
@@ -565,7 +578,7 @@ instead of waiting out inactivity timeouts and heartbeat intervals.
 | `kylon agent link --url <link> [-- <launch command>]` | **Recommended.** Connect one agent and start its local runtime. ACP launch commands are saved in the same operation. |
 | `kylon disconnect` | Forget this environment's saved runtime connection. Local only: workspace-side agent configuration is unchanged. |
 | `kylon gateway run` | Run the local runtime service from the saved connection (service entrypoint). |
-| `kylon keep-awake [mode]` | Show or set macOS sleep prevention (`always` (default) / `while-busy` / `off`). |
+| `kylon keep-awake [mode]` | Show or set macOS/Windows sleep prevention (`always` (default) / `while-busy` / `off`). |
 
 ### Supported Providers
 

package/dist/kylon-bundle.manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.6.0-next.835",
-  "fingerprint": "42fd90c58c61011f7cfecf5a687b8c530580a30de054a059988c8cf1f7e581cd",
-  "source_commit": "4fb600ddfaa67e280638460fd78f540bb644242f"
+  "version": "0.6.0-next.838",
+  "fingerprint": "45ad32f5d5309f69a97c0cae6ea3daef0c0dfd7ba1414f8094d9ca1a5b3650b2",
+  "source_commit": "5c1506644e36adffd1f2de865ef24fc0cd4b9cad"
 }