@whalent/agent 0.3.434 → 0.3.436

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 CHANGED
@@ -68,6 +68,25 @@ whalent --token <YOUR_TOKEN>
68
68
 
69
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.
70
70
 
71
+ Startup is quiet by default: connection/instance summaries and actionable errors
72
+ remain visible; routine startup and worker lifecycle records stay in the daily
73
+ log collected by the diagnostics tools. Use `whalent --verbose` for startup
74
+ details, or `WHALENT_DEBUG=1 whalent` for protocol diagnostics.
75
+
76
+ In an interactive terminal, the daemon offers a small menu:
77
+
78
+ - `1` / `status`: show connection and managed-process counts.
79
+ - `2` / `logs`: show the latest 20 diagnostic lines.
80
+ - `3` / `help`: show available actions.
81
+ - `q`: stop the daemon and managed instances after confirmation (default: no).
82
+
83
+ Ctrl+C still stops the daemon; EOF only closes the menu. Pipes and background
84
+ services do not open it. `--no-interactive` explicitly disables prompts and the
85
+ menu. Existing `whalent status --json`, MCP stdio and provider-local sessions
86
+ keep their original output contracts. Startup diagnostics and the menu require
87
+ the updated core; quieter npm supervision requires updating the wrapper package
88
+ as well (`npm install -g @whalent/agent`).
89
+
71
90
  Codex workers reserve their agent-scoped `CODEX_HOME` with a process-generation
72
91
  lease before starting app-server. Worker restart and shutdown wait for the whole
73
92
  native process tree to exit; daemon startup and periodic maintenance reclaim