palmier 0.9.2 → 0.9.3

package/palmier-server/pwa/src/constants.ts

@@ -1,2 +1,2 @@
 /** Bump when a breaking host change is made. */
-export const MIN_HOST_VERSION = "0.8.11";
+export const MIN_HOST_VERSION = "0.9.2";

package/palmier-server/pwa/src/contexts/HostConnectionContext.tsx

@@ -173,6 +173,14 @@ export function HostConnectionProvider({ children, activeHost }: { children: Rea
               config.natsJwt,
               new TextEncoder().encode(config.natsNkeySeed),
             ),
+            // Default is 2 min — too slow to notice a silently-dead WebSocket
+            // when the user has the page foregrounded but the network drops.
+            // The resume-probe useEffect below catches dead conns within 2s
+            // when the user returns to the app, so this background heartbeat
+            // can stay conservative (maxPingOut: 2 → ~60s) and avoid false
+            // positives from transient network jitter.
+            pingInterval: 30_000,
+            maxPingOut: 2,
           });
           if (cancelled) { conn.close().catch(() => {}); return; }
           console.log("[NATS] Connected");
@@ -211,17 +219,24 @@ export function HostConnectionProvider({ children, activeHost }: { children: Rea
     };
   }, [isDirectHost, activeHost]);
 
-  // Mobile WebViews suspend WebSockets when the app backgrounds; nats.ws often
-  // doesn't notice the dead socket on resume, leaving RPCs to hang/throw "Not
-  // connected." Force-close on resume so the connectLoop reconnects with a
-  // fresh socket.
+  // WebSockets can die silently — mobile WebViews suspend them on background,
+  // laptops on sleep, networks on switch. On any resume (visibility change on
+  // web, foreground on native), probe the connection with a short-timeout
+  // flush (PING/PONG round-trip); close only if it doesn't respond. nats.ws's
+  // own pingInterval catches it eventually, but probing on resume gets us
+  // back faster when the user immediately fires an RPC.
   useEffect(() => {
     if (isDirectHost) return;
     const handle = CapacitorApp.addListener("appStateChange", (state: { isActive: boolean }) => {
-      if (state.isActive && ncRef.current) {
-        console.log("[NATS] App resumed; cycling NATS conn to recover from possible dead socket");
-        ncRef.current.close().catch(() => {});
-      }
+      if (!state.isActive || !ncRef.current) return;
+      const conn = ncRef.current;
+      Promise.race([
+        conn.flush(),
+        new Promise<void>((_, reject) => setTimeout(() => reject(new Error("ping timeout")), 2_000)),
+      ]).catch(() => {
+        console.log("[NATS] Resume probe failed — cycling conn");
+        conn.close().catch(() => {});
+      });
     });
     return () => { handle.then((h) => h.remove()); };
   }, [isDirectHost]);

package/palmier-server/pwa/src/pages/PairHost.tsx

@@ -141,8 +141,11 @@ export default function PairHost() {
               <h3 className="pair-instruction-heading">Setting up a new host?</h3>
               <ol className="pair-steps">
                 <li>Install at least one agent CLI (e.g., <a href="https://www.palmier.me/agents" target="_blank" rel="noopener noreferrer">Claude Code, Gemini CLI, Codex CLI</a>)</li>
-                <li>Install Palmier on your host machine:
-                  <code className="pair-command">npm install -g palmier</code>
+                <li>Install Palmier on your host machine.
+                  <span className="pair-platform-label">Linux / macOS:</span>
+                  <code className="pair-command">curl -fsSL https://palmier.me/install.sh | bash</code>
+                  <span className="pair-platform-label">Windows (PowerShell):</span>
+                  <code className="pair-command">irm https://palmier.me/install.ps1 | iex</code>
                 </li>
                 <li>Run the setup wizard:
                   <code className="pair-command">palmier init</code>
@@ -189,8 +192,12 @@ export default function PairHost() {
                 disabled={pairing}
               />
               <span className="pair-checkbox-text">
-                <span className="pair-checkbox-title">Link this device</span>
-                <span className="pair-checkbox-hint">The host will use this device for SMS, contacts, calendar, location, and alarms. Only one device can be linked at a time.</span>
+                <span className="pair-checkbox-title">Link the host to this device</span>
+                <span className="pair-checkbox-hint">
+                  {makeLinked
+                    ? "The host will use this device for SMS, contacts, calendar, location, and alarms. Only one device can be linked to the host."
+                    : "This device won't provide SMS, contacts, calendar, location, or alarms to the host. You can link it later from the menu."}
+                </span>
               </span>
             </label>
           )}

package/palmier-server/pwa/src/pages/PairSetup.tsx

@@ -74,9 +74,9 @@ export default function PairSetup() {
   const linkModal = phase === "confirming" && createPortal(
     <div className="confirm-modal-overlay" onClick={cancelLink}>
       <div className="confirm-modal" onClick={(e) => e.stopPropagation()}>
-        <h2 className="confirm-modal-title">Link this device?</h2>
+        <h2 className="confirm-modal-title">Link the host to this device?</h2>
         <p className="confirm-modal-message">
-          Only one device can be linked at a time — switching will disable those capabilities on the currently linked device.
+          Another device is already linked to this host. Only one device can be linked to the host — switching will disable those capabilities on the currently linked device.
         </p>
         <div className="confirm-modal-actions">
           <button className="btn btn-secondary" onClick={cancelLink}>Cancel</button>
@@ -89,19 +89,21 @@ export default function PairSetup() {
 
   if (phase === "loading" || phase === "confirming" || phase === "linking" || phase === "linkError") {
     const isWizardCandidate = isFirstHost;
+    const showSpinner = phase === "loading" || phase === "confirming" || phase === "linking";
     return (
       <div className="pair-setup">
         <div className="pair-setup-inner">
           {isWizardCandidate && <h1 className="pair-setup-title">Device Capabilities</h1>}
           <div className="pair-setup-loading">
-            {phase === "loading" && "Connecting to host…"}
-            {phase === "confirming" && "Awaiting confirmation…"}
-            {phase === "linking" && "Linking device…"}
+            {showSpinner && <span className="spinner spinner-lg" />}
+            {phase === "loading" && <span>Connecting to host…</span>}
+            {phase === "confirming" && <span>Awaiting confirmation…</span>}
+            {phase === "linking" && <span>Linking device…</span>}
             {phase === "linkError" && (
               <>
                 <p className="pair-error">{linkError}</p>
                 <button className="btn btn-primary" onClick={retryLink}>Retry</button>
-                <button className="btn btn-secondary" onClick={goToHost} style={{ marginTop: 8 }}>Skip linking</button>
+                <button className="btn btn-secondary" onClick={goToHost}>Skip linking</button>
               </>
             )}
           </div>

package/palmier-server/pwa/vite.config.ts

@@ -24,7 +24,7 @@ export default defineConfig({
       manifest: {
         name: "Palmier",
         short_name: "Palmier",
-        description: "Control AI agents running on your machine from any device. Schedule tasks, monitor runs, and stay in control.",
+        description: "Bridge your AI agents and your phone. Agents on your machine get your phone as a tool — SMS, calendar, GPS, alarms, approvals — and your phone as the remote to run them from anywhere.",
         start_url: "/",
         display: "standalone",
         background_color: "#ffffff",

package/palmier-server/spec.md

@@ -144,8 +144,8 @@ If no clients exist, the host skips client validation (backward compatibility fo
 
 Each host tracks a single **linked device** — the one paired device responsible for answering device capability requests (SMS, contacts, calendar, location, alarm, ringer, email, battery). The host stores only `{ clientToken, fcmToken }` in `~/.config/palmier/linked-device.json`; it has no knowledge of which capabilities are actually enabled on the device. That set lives in Android SharedPreferences on the linked device itself and is consulted by the FCM handlers as a local kill-switch.
 
-- **Opt-in at pair time.** The PWA shows a "Link this device" checkbox during pairing (native only, default on). If checked, the pair flow continues to a setup step that calls `device.link` with the FCM token. On the very first host pair (when the device has no other paired hosts), that step also shows a one-time "Device Capabilities" screen with all toggles default OFF; the user opts into each one, and Finish writes the set to SharedPreferences. On subsequent host pairs the capability screen is skipped — the device-wide enabled set is host-agnostic and set once.
-- **Reassignment.** Any paired device can take over as the linked device from the drawer's "Link this device" button. This displaces the previous linked device (its drawer toggles go dark).
+- **Opt-in at pair time.** The PWA shows a "Link the host to this device" checkbox during pairing (native only, default on). If checked, the pair flow continues to a setup step that calls `device.link` with the FCM token. On the very first host pair (when the device has no other paired hosts), that step also shows a one-time "Device Capabilities" screen with all toggles default OFF; the user opts into each one, and Finish writes the set to SharedPreferences. On subsequent host pairs the capability screen is skipped — the device-wide enabled set is host-agnostic and set once.
+- **Reassignment.** Any paired device can take over as the linked device from the drawer's "Link the host to this device" button. This displaces the previous linked device (its drawer toggles go dark).
 - **Loss.** If the linked device is unpaired (via `clients.revoke_self` or CLI `palmier clients revoke`), `linked-device.json` is cleared and capability tools return "No linked device configured" until the user picks a new one.
 - **Routing.** MCP capability tools look up the linked device once per invocation and publish FCM to its token (via `host.<host_id>.fcm.<capability>` relayed by the server). Non-linked devices aren't woken and don't receive capability FCMs.
 

package/src/platform/linux.ts

@@ -185,6 +185,15 @@ Environment=PATH=${process.env.PATH || "/usr/local/bin:/usr/bin:/bin"}
 `;
 
     fs.writeFileSync(path.join(UNIT_DIR, serviceName), serviceContent, "utf-8");
+
+    // Tear down any previously installed timer unit so on-demand tasks don't
+    // keep firing on the old schedule. Service unit stays so startTask works.
+    const timerPath = path.join(UNIT_DIR, timerName);
+    if (fs.existsSync(timerPath)) {
+      try { execSync(`systemctl --user stop ${timerName}`, { encoding: "utf-8" }); } catch { /* not running */ }
+      try { execSync(`systemctl --user disable ${timerName}`, { encoding: "utf-8" }); } catch { /* not enabled */ }
+      fs.unlinkSync(timerPath);
+    }
     daemonReload();
 
     if (!task.frontmatter.schedule_enabled) return;