@maintainer-pro/ai-bridge 0.1.7 → 0.1.9

package/README.md

@@ -7,21 +7,26 @@ Local bridge daemon that pairs a **developer machine** to a Maintainer Pro **par
 1. In admin → **Bridges**, generate a pair code
 2. On the machine (any folder):
 
+**Published (production admin):**
+
 ```bash
-npx --yes @maintainer-pro/ai-bridge --pair AB12-CD34 --admin-url https://your-admin
+npx --yes --prefer-online @maintainer-pro/ai-bridge@latest --pair AB12-CD34 --admin-url https://your-admin
 ```
 
-Credentials are stored in `~/.maintainer-pro/bridge.json` (not the cwd).
+**Local development** (SDK checkout next to admin). From this repo:
 
-3. Keep the bridge running (`npx @maintainer-pro/ai-bridge`). It advertises the current folder (and any `--offer-folder` paths).
-4. In admin → Bridges: pick a reported folder + client sandbox → **Setup sandbox in folder**.
+```bash
+npm run bridge -- --pair AB12-CD34 --admin-url http://localhost:4100
+```
 
-For **empty / new** folders the bridge:
-- Writes `.env` (server + client keys)
-- Scaffolds `index.html` with the chat widget (served by `ai-server`)
-- Starts `ai-server` and marks the sandbox Online
+Or the absolute `node packages/ai-bridge/bin/cli.js …` command shown in admin → Bridges.
+
+Credentials and per-sandbox project data (host-app cache, screenshots, logs) live under `~/.maintainer-pro/` — `bridge.json` plus `projects/<sandboxId>/`. Host app folders are not modified.
+
+3. Keep the bridge running (`npx --yes --prefer-online @maintainer-pro/ai-bridge@latest`, or `npm run bridge` in local dev). It advertises the current working directory so admin can choose a folder inside it.
+4. In admin → Bridges: pick a reported folder + client sandbox → **Setup sandbox in folder**.
 
-For **existing** apps it injects the widget / Next env when possible. Use **Client setup** on the Bridges form for manual overrides (`empty`, `existing`, or keys-only).
+For **empty / new** folders the bridge scaffolds a starter `index.html` (chat served in-process). For **existing** apps it does not modify host files — env is injected into the process it starts, and chat is injected on the share URL. Use **Client setup** on the Bridges form for manual overrides (`empty`, `existing`, or keys-only).
 
 One bridge process can run many sandboxes (different folders / ports) for different clients.
 
@@ -31,9 +36,8 @@ One bridge process can run many sandboxes (different folders / ports) for differ
 |------|---------|
 | `--pair <code>` | Claim a pair code (first run) |
 | `--admin-url <url>` | Admin base URL (required when pairing) |
-| `--offer-folder <path>` | Advertise an extra folder in admin |
 | `--no-ai-server` | Do not start sidecars |
 
 ## Auth
 
-After pairing, the daemon uses a long-lived `mp_bridge_…` machine token (not a per-sandbox API key). Sandbox server/client keys are written into each workspace `.env` during setup.
+After pairing, the daemon uses a long-lived `mp_bridge_…` machine token (not a per-sandbox API key). Sandbox server/client keys stay in `~/.maintainer-pro/bridge.json` and are injected into processes the bridge starts — they are not written into the host app.

package/bin/cli.js

@@ -1,5 +1,6 @@
 #!/usr/bin/env node
 /**
- *   npx --yes @maintainer-pro/ai-bridge
+ *   npx --yes --prefer-online @maintainer-pro/ai-bridge@latest
+ *   npm run bridge
  */
 import "../src/daemon.mjs";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maintainer-pro/ai-bridge",
-  "version": "0.1.7",
+  "version": "0.1.9",
   "description": "Local bridge daemon that pairs a machine to Maintainer Pro and configures multiple client sandboxes.",
   "keywords": [
     "maintainer-pro",
@@ -28,6 +28,7 @@
     "node": ">=22"
   },
   "dependencies": {
-    "@maintainer-pro/ai-cli": "^0.1.5"
+    "@maintainer-pro/ai-cli": "^0.1.6",
+    "@maintainer-pro/ai-server": "^0.1.5"
   }
 }