clawmoney 0.12.2 → 0.12.3

package/dist/relay/daemon.js

@@ -5,6 +5,16 @@
  * It runs the relay provider main loop (WS + Executor).
  */
 import { runRelayProvider } from "./provider.js";
+import { relayLogger as logger } from "./logger.js";
+// Process-level safety net: an unhandled promise rejection anywhere in the
+// async reconnect / request path must NOT silently kill the daemon. Log it
+// loudly and keep running — the reconnect loop will self-heal any broken WS.
+process.on("unhandledRejection", (reason) => {
+    logger.error("Unhandled promise rejection (daemon continues running):", reason instanceof Error ? reason.stack ?? reason.message : reason);
+});
+process.on("uncaughtException", (err) => {
+    logger.error("Uncaught exception (daemon continues running):", err.stack ?? err.message);
+});
 // Parse CLI args passed from the parent
 let cliType;
 const args = process.argv.slice(2);

package/dist/relay/ws-client.js

@@ -94,7 +94,12 @@ export class RelayWsClient {
             this.reconnectTimer = null;
             this.connect();
         }, delay * 1000);
-        this.reconnectTimer.unref();
+        // CRITICAL: do NOT .unref() this timer. When the WS handle closes we lose
+        // our only refed I/O source — if the reconnect timer is unref'd Node sees
+        // an empty event loop and the process silently exits with code 0 before
+        // the timer fires. This was the "daemon dies after every Hub deploy" bug
+        // observed in 0.12.0–0.12.2. Leaving the timer refed is what keeps the
+        // daemon alive across WS disconnects.
         const { max, multiplier } = this.config.relay.reconnect;
         this.reconnectDelay = Math.min(delay * multiplier, max);
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "clawmoney",
-  "version": "0.12.2",
+  "version": "0.12.3",
   "description": "ClawMoney CLI -- Earn rewards with your AI agent",
   "type": "module",
   "bin": {