@maintainer-pro/ai-bridge 0.1.32 → 0.1.33

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -26,7 +26,7 @@ Credentials and per-sandbox project data (host-app cache, screenshots, logs) liv
26
26
  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.
27
27
  4. In admin → Bridges: pick a reported folder + client sandbox → **Setup sandbox in folder**.
28
28
 
29
- 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).
29
+ For **empty / new** folders the bridge reserves a free site port, serves a business intake form on the share link, then asks the coding-agent CLI to generate a Next.js site. The generated app starts on that **same port**, so the share URL does not change. Chat requests on intake-built sites are queued on the bridge workspace, then after **4 hours** (or when the bridge stops) the coding-agent CLI merges them into the existing **platform-wide** memory in Maintainer Pro (`platform_settings.website_memory`) so the next new site can improve. Only product improvements are stored (more photos, calmer motion, etc.) — never personal information. This is not part of the chat prompt. 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).
30
30
 
31
31
  One bridge process can run many sandboxes (different folders / ports) for different clients.
32
32
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@maintainer-pro/ai-bridge",
3
- "version": "0.1.32",
3
+ "version": "0.1.33",
4
4
  "description": "Local bridge daemon that pairs a machine to Maintainer Pro and configures multiple client sandboxes.",
5
5
  "keywords": [
6
6
  "maintainer-pro",
@@ -28,8 +28,8 @@
28
28
  "node": ">=22"
29
29
  },
30
30
  "dependencies": {
31
- "@maintainer-pro/ai-cli": "^0.1.17",
32
- "@maintainer-pro/ai-server": "^0.1.9",
31
+ "@maintainer-pro/ai-cli": "^0.1.18",
32
+ "@maintainer-pro/ai-server": "^0.1.10",
33
33
  "ws": "^8.21.3"
34
34
  }
35
35
  }