@maintainer-pro/ai-bridge

Local bridge daemon that pairs a developer machine to a Maintainer Pro partner, then configures many client sandboxes from folders you choose in admin.

Flow

1. In admin → Bridges, generate a pair code
2. On the machine (any folder):

Published (production admin):

npx --yes --prefer-online @maintainer-pro/ai-bridge@latest --pair AB12-CD34 --admin-url https://your-admin

Local development (SDK checkout next to admin). From this repo:

npm run bridge -- --pair AB12-CD34 --admin-url http://localhost:4100

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 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 static HTML/CSS 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).

One bridge process can run many sandboxes (different folders / ports) for different clients.

Flags

| Flag | Purpose | |------|---------| | --pair <code> | Claim a pair code (first run) | | --admin-url <url> | Admin base URL (required when pairing) | | --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 stay in ~/.maintainer-pro/bridge.json and are injected into processes the bridge starts — they are not written into the host app.