@chatpanel/bridge 0.2.9 → 0.2.10

package/README.md

@@ -14,26 +14,30 @@ the ones the bridge reports as available.
 
 ## Run it
 
-### Option A — one-line install (no Node.js needed)
+### macOS / Linux — one line, no Node.js needed
 
-**macOS / Linux:**
 ```bash
 curl -fsSL https://dl.chatpanel.net/bridge/install.sh | bash
 ```
 
-**Windows (PowerShell):**
+Downloads the standalone binary, installs it, and sets it to start at login
+(installing via curl avoids the macOS "damaged" prompt). Re-running is a clean
+in-place upgrade.
+
+### Windows — via Node (recommended)
+
+Windows SmartScreen flags unsigned downloads, so on Windows run the bridge through
+Node — you already have it if you use Claude Code / Codex / Gemini (all npm CLIs),
+and there's no security prompt:
+
 ```powershell
-irm https://dl.chatpanel.net/bridge/install.ps1 | iex
+npm i -g @chatpanel/bridge
+chatpanel-bridge --install      # starts hidden at login
 ```
 
-This downloads the standalone binary for your OS, installs it, and sets it to
-start at login. **Recommended** — installing this way avoids the macOS "damaged"
-and Windows SmartScreen prompts that browser downloads trigger. Re-running it is a
-clean in-place upgrade (no duplicate installs). Then open the ChatPanel side panel
-and your agents appear.
+Just trying it? `npx @chatpanel/bridge` runs it once in the foreground.
 
-Manage it: `chatpanel-bridge --status` · `--uninstall` · run with no flags to start
-once in the foreground.
+Manage it anywhere: `chatpanel-bridge --status` · `--uninstall`.
 
 ### Manual download
 
@@ -50,25 +54,17 @@ chmod +x chatpanel-bridge-macos-arm64
 .\chatpanel-bridge-windows-x64.exe --install
 ```
 
-> These binaries aren't notarized yet, so macOS/Windows may warn on first run.
-> The curl installer above sidesteps the macOS prompt entirely.
->
-> **Intel Mac?** No x64 binary yet — use **Option B** (`npx @chatpanel/bridge`).
-> Apple Silicon (`uname -m` → `arm64`) uses `chatpanel-bridge-macos-arm64`.
-
-### Option B — via npm (needs Node.js 18+)
-
-```bash
-npx @chatpanel/bridge        # → http://127.0.0.1:4319
-```
+> These binaries aren't code-signed yet, so macOS/Windows may warn on first run
+> (the curl/npm routes above sidestep that). **Intel Mac?** No x64 binary yet —
+> use npm (`npx @chatpanel/bridge`). Apple Silicon uses `chatpanel-bridge-macos-arm64`.
 
-…then leave it running and open the ChatPanel side panel. Prefer a persistent
-command? `npm i -g @chatpanel/bridge` then `chatpanel-bridge`.
+### Prerequisites
 
-Prerequisites (the agents you want to use must already be set up):
+The agents you want to use must already be set up:
 
-- **Claude Code**: be signed in (`claude`) or set `ANTHROPIC_API_KEY`.
+- **Claude Code**: installed and signed in (`claude`), or set `ANTHROPIC_API_KEY`.
 - **Codex**: `codex` on your `PATH` and `codex login` done.
+- **Gemini CLI**: `gemini` on your `PATH` and signed in.
 
 The extension polls `/health` and shows each agent as available/unavailable.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chatpanel/bridge",
-  "version": "0.2.9",
+  "version": "0.2.10",
   "type": "module",
   "description": "Local bridge that exposes the AI coding agents installed on your machine — Claude Code (Agent SDK), Codex (CLI), and Gemini CLI — to the ChatPanel Chrome extension over a localhost SSE endpoint. Bring your own agent.",
   "keywords": [

package/src/server.js

@@ -22,7 +22,7 @@ import * as gemini from './engines/gemini.js';
 import { installService, uninstallService, serviceStatus } from './service.js';
 import { enrichPath, findAgentBin } from './env.js';
 
-const VERSION = '0.2.9';
+const VERSION = '0.2.10';
 const HOST = process.env.CHATPANEL_BRIDGE_HOST || '127.0.0.1';
 const PORT = Number(process.env.CHATPANEL_BRIDGE_PORT) || 4319;
 

package/src/service.js

@@ -84,7 +84,9 @@ function macStatus() {
 // the bridge with NO console window.
 const WIN_RUN_KEY = 'HKCU\\Software\\Microsoft\\Windows\\CurrentVersion\\Run';
 const WIN_RUN_NAME = 'ChatPanelBridge';
-const winVbs = () => path.join(path.dirname(resolveLaunch().program), 'launch.vbs');
+// A user-writable location for the launcher. NOT next to the program — under
+// `npm i -g` the program is node.exe, whose dir is protected (EPERM).
+const winVbs = () => path.join(os.homedir(), '.chatpanel', 'launch.vbs');
 
 function winInstall() {
   const { program, args } = resolveLaunch();