palmier 0.8.8 → 0.8.9

package/README.md

@@ -15,6 +15,18 @@ It runs on your machine as a background daemon and connects to a mobile-friendly
 
 1. Install a supported agent CLI — [Claude Code](https://docs.anthropic.com/en/docs/claude-code), [Gemini CLI](https://github.com/google-gemini/gemini-cli), [Codex CLI](https://github.com/openai/codex), [GitHub Copilot](https://github.com/github/gh-copilot), [OpenClaw](https://openclaw.ai/), or [others](https://www.palmier.me/agents).
 2. Install Palmier:
+
+   **Linux / macOS:**
+   ```bash
+   curl -fsSL https://palmier.me/install.sh | bash
+   ```
+
+   **Windows (PowerShell):**
+   ```powershell
+   irm https://palmier.me/install.ps1 | iex
+   ```
+
+   The one-liner installs Node.js 24+ if needed (via [fnm](https://github.com/Schniz/fnm) on Linux/macOS, winget on Windows), then `palmier` globally. If you already have Node.js 24+ and npm:
    ```bash
    npm install -g palmier
    ```
@@ -61,7 +73,7 @@ Palmier exposes an [MCP](https://modelcontextprotocol.io) server at `http://loca
 **Available resources:**
 | Resource | URI | Permission | Description |
 |----------|-----|------------|-------------|
-| Device Notifications | `notifications://device` | Read Notifications | Recent notifications from the user's Android device |
+| Device Notifications | `notifications://device` | Notifications from Other Apps | Recent notifications from the user's Android device |
 | Device SMS | `sms-messages://device` | Read SMS | Recent SMS messages from the user's Android device |
 
 Resources support MCP subscriptions — clients can subscribe via `resources/subscribe` and receive real-time `notifications/resources/updated` events via the streamable HTTP transport when the resource changes.
@@ -92,32 +104,29 @@ All device tools work while the Palmier Android app is in the background — the
                                        │   SMS, contacts, │
                                        │   calendar, GPS) │
                                        └──────────────────┘
-        Local / LAN: direct HTTP
-        Server mode: via relay server + FCM
+        Local mode (loopback): direct HTTP on the host machine
+        Server mode: via relay (events) + auto-LAN direct HTTP for RPC when reachable (native app)
 ```
 
 ## Access Modes
 
-Local always works. Enable LAN and/or Server mode during `palmier init`.
+Two modes — Local always works on the host machine; Server pairs other devices through the cloud relay.
 
-| Mode | Transport | URL | Pairing | Features |
-|------|-----------|-----|---------|----------|
-| **Local** | HTTP (localhost) | `http://localhost:<port>` | Not required | Full access from the host machine, no internet needed |
-| **LAN** | HTTP (direct) | `http://<host-ip>:<port>` | Required | Access from other devices on the local network |
-| **Server** | Cloud relay (NATS) | [https://app.palmier.me](https://app.palmier.me) | Required | Push notifications, remote access from anywhere |
+| Mode | URL | Pairing | Notes |
+|------|-----|---------|-------|
+| **Local** | `http://localhost:<port>` | Not required | Loopback only — open in a browser on the host machine. No internet needed. |
+| **Server** | [https://app.palmier.me](https://app.palmier.me) | Required | Pair the device with a one-time code. Push notifications, remote access from anywhere. |
 
-**LAN mode** binds the daemon to `0.0.0.0` so the PWA is accessible from other devices on your network. Devices must pair with a pairing code.
-
-**Server mode** relays communication through the Palmier cloud server (via [NATS](https://nats.io)). All features including push notifications are available. Server mode and LAN mode can be active at the same time.
+**Auto-LAN (native app only).** When the Capacitor Android app is on the same network as the host, it transparently routes RPC over direct LAN HTTP (`http://<host-ip>:<port>/rpc/...`) instead of through the relay — lower latency, no protocol change. Events still flow over the relay. Browser PWAs can't do this and stay on the relay.
 
 ## Security & Privacy
 
-**Local mode** — all traffic stays on `127.0.0.1`. No data leaves your machine.
-
-**LAN mode** — traffic stays on your local network. Devices must pair with a one-time pairing code before they can access the host. Unpaired requests are rejected.
+**Local mode** — all traffic stays on `127.0.0.1`. No data leaves your machine. The web UI, `/pair`, and `/events` reject any non-loopback caller; only `/rpc/<method>` (bearer-auth) and `/health` are reachable from the LAN.
 
 **Server mode** — communication between your device and host is relayed through the Palmier cloud server over TLS-encrypted NATS connections. The server acts as a passthrough relay only — it does not store, log, or inspect any user data, task content, or agent output. The only data the server persists is a host registration ID used for message routing and Web Push subscription info for delivering notifications. See the [Privacy Policy](https://www.palmier.me/privacy) for full details.
 
+**Auto-LAN** — direct LAN HTTP requests use the same client token (Bearer auth) generated during pairing. The host validates every `/rpc/*` call regardless of source.
+
 In all modes, client tokens are generated and validated entirely on your host. The Palmier server never sees or stores them.
 
 ## Setup Details
@@ -126,7 +135,7 @@ In all modes, client tokens are generated and validated entirely on your host. T
 
 Local access (`http://localhost:<port>`) works immediately — no pairing needed.
 
-For LAN or server mode, run `palmier pair` on the host to generate a pairing code. Enter it in the PWA — either at `http://<host-ip>:<port>` (LAN mode) or [https://app.palmier.me](https://app.palmier.me) (server mode).
+For other devices, run `palmier pair` on the host to generate a code, then enter it at [https://app.palmier.me](https://app.palmier.me). Pairing always goes through the relay; auto-LAN kicks in transparently afterward when the device is on the same network.
 
 ### Managing Clients
 
@@ -145,7 +154,7 @@ palmier clients revoke-all
 
 The wizard:
 - Detects installed agent CLIs and caches the result
-- Configures access modes (HTTP port, LAN access)
+- Asks for the HTTP port
 - Shows a summary (including any existing scheduled tasks to recover) and asks for confirmation
 - Registers with the Palmier server, saves configuration to `~/.config/palmier/host.json`
 - Installs a background daemon (systemd user service on Linux, LaunchAgent on macOS, Task Scheduler on Windows)

package/dist/commands/init.js

@@ -27,24 +27,20 @@ export async function initCommand() {
             process.exit(1);
         }
         console.log(`  Found: ${green(agents.map((a) => a.label).join(", "))}\n`);
-        const lanAnswer = await ask("Enable LAN access (direct HTTP from local network)? (y/N): ");
-        const lanEnabled = lanAnswer.trim().toLowerCase() === "y";
         let httpPort = 7256;
-        const portLabel = lanEnabled ? "HTTP port for local and LAN access" : "HTTP port for local access";
-        const portAnswer = await ask(`${portLabel} (default ${httpPort}): `);
+        const portAnswer = await ask(`HTTP port (default ${httpPort}): `);
         const parsed = parseInt(portAnswer.trim(), 10);
         if (parsed > 0 && parsed < 65536)
             httpPort = parsed;
+        const lanIp = detectLanIp();
         console.log(`\n${bold("Setup summary:")}\n`);
         console.log(`  ${dim("Task storage:")}   ${bold(process.cwd())}`);
         console.log(`                  All tasks and execution data will be stored here.\n`);
         console.log(`  ${dim("Local access:")}   ${cyan(`http://localhost:${httpPort}`)}`);
-        console.log(`                  Always available — no internet required.\n`);
-        if (lanEnabled) {
-            const ip = detectLanIp();
-            console.log(`  ${dim("LAN access:")}     ${cyan(`http://${ip}:${httpPort}`)}`);
-            console.log(`                  Accessible from other devices on your local network. Pairing required.\n`);
-        }
+        console.log(`                  Open in a browser on this machine — no internet required.\n`);
+        console.log(`  ${dim("Remote access:")}  ${cyan("https://app.palmier.me")}`);
+        console.log(`                  Pair the app to your host. The app uses ${cyan(`http://${lanIp}:${httpPort}`)}`);
+        console.log(`                  for direct RPC when on the same network, otherwise the relay.\n`);
         console.log(`  ${dim("Agents:")}         ${agents.map((a) => a.label).join(", ")}\n`);
         const existingTasks = listTasks(process.cwd());
         if (existingTasks.length > 0) {
@@ -93,7 +89,6 @@ export async function initCommand() {
             natsNkeySeed: registerResponse.natsNkeySeed,
             agents,
             httpPort,
-            lanEnabled,
         };
         saveConfig(config);
         console.log(`Config saved to ${dim("~/.config/palmier/host.json")}`);

package/dist/commands/pair.js

@@ -4,6 +4,7 @@ import { StringCodec } from "nats";
 import { loadConfig } from "../config.js";
 import { connectNats } from "../nats-client.js";
 import { addClient } from "../client-store.js";
+import { detectLanIp } from "../transports/http-transport.js";
 const CODE_CHARS = "ABCDEFGHJKMNPQRSTUVWXYZ23456789"; // no O/0/I/1/L
 const CODE_LENGTH = 6;
 export const PAIRING_EXPIRY_MS = 60 * 1000; // 1 minute
@@ -14,9 +15,11 @@ export function generatePairingCode() {
 }
 function buildPairResponse(config, label) {
     const client = addClient(label);
+    const port = config.httpPort ?? 7256;
     return {
         hostId: config.hostId,
         clientToken: client.token,
+        directUrl: `http://${detectLanIp()}:${port}`,
         hostName: os.hostname(),
     };
 }