@whalent/agent 0.3.367 → 0.3.369
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +28 -0
- package/dist/core.cjs +7 -7
- package/dist/index.cjs +1 -1
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -52,6 +52,10 @@ directly.
|
|
|
52
52
|
By default the daemon checks Platform's release API at startup and every five
|
|
53
53
|
minutes for newer `sqlite-helper`, `terminal-helper`, and enabled desktop
|
|
54
54
|
`tray-helper` releases, then downloads and activates the returned manifests.
|
|
55
|
+
All due helper identities are sent in one authenticated `check-batch` request;
|
|
56
|
+
downloads and installs remain serial. A Platform without the batch route falls
|
|
57
|
+
back to the legacy per-helper checks, while an edge/server failure remains one
|
|
58
|
+
failed request and one warning.
|
|
55
59
|
Helper releases are independent from daemon/npm releases. A guacd installation
|
|
56
60
|
that already uses Whalent's managed component is updated through the same flow;
|
|
57
61
|
system-installed or missing guacd remains an explicit user choice.
|
|
@@ -64,6 +68,30 @@ whalent --token <YOUR_TOKEN>
|
|
|
64
68
|
|
|
65
69
|
The daemon connects to the Whalent Memory platform, fetches agent configurations, and auto-starts workers marked with `auto_restart`. It also accepts remote commands (upgrade, restart) via the gateway.
|
|
66
70
|
|
|
71
|
+
Codex workers reserve their agent-scoped `CODEX_HOME` with a process-generation
|
|
72
|
+
lease before starting app-server. Worker restart and shutdown wait for the whole
|
|
73
|
+
native process tree to exit; daemon startup and periodic maintenance reclaim
|
|
74
|
+
orphaned app-servers, including those whose old Agent directory was already
|
|
75
|
+
deleted. A genuine live-writer conflict parks only that startup attempt and
|
|
76
|
+
does not silently switch off the saved auto-restart setting.
|
|
77
|
+
|
|
78
|
+
To allow a last-known-good startup while Platform is temporarily unreachable:
|
|
79
|
+
|
|
80
|
+
```bash
|
|
81
|
+
whalent daemon --offline
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
`--offline` is a fallback, not a forced disconnected mode: the daemon still
|
|
85
|
+
connects normally when possible. After every successful agent-config inventory
|
|
86
|
+
fetch (and each authenticated config push), it atomically replaces the private
|
|
87
|
+
`agent-config-cache.json` in the active account profile. On a transient network,
|
|
88
|
+
timeout, rate-limit, or 5xx startup failure, the daemon starts runnable workers
|
|
89
|
+
from that same-machine snapshot and keeps reconnecting in the background.
|
|
90
|
+
Explicit 401/403/404 responses never use the cache. A first-ever launch with no
|
|
91
|
+
snapshot remains online-waiting and starts no cached workers. The equivalent
|
|
92
|
+
environment switch is `WHALENT_OFFLINE=1`; `whalent status` reports whether the
|
|
93
|
+
active config source is `platform`, `cache`, or `none`.
|
|
94
|
+
|
|
67
95
|
On Windows, macOS, and graphical Linux sessions, daemon mode installs and starts
|
|
68
96
|
the native `tray-helper` automatically. Its menu shows the current Whalent login,
|
|
69
97
|
Gateway/worker status, opens Whalent Memory or today's daemon log, checks and
|