@mrrlin-dev/mcp 0.3.2 → 0.3.4
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 +5 -5
- package/dist/bin.cjs +1047 -477
- package/package.json +7 -5
package/README.md
CHANGED
|
@@ -1,16 +1,16 @@
|
|
|
1
1
|
# `@mrrlin-dev/mcp` — Mrrlin Director Bridge
|
|
2
2
|
|
|
3
|
-
CLI that runs the local Director bridge under PM2 and forwards chat turns to a locally-spawned Codex `app-server`. Installed globally on operator boxes via `
|
|
3
|
+
CLI that runs the local Director bridge under PM2 and forwards chat turns to a locally-spawned Codex `app-server`. Installed globally on operator boxes via `npm install -g @mrrlin-dev/mcp` (the official install path; `pnpm install -g` also works if the operator has `pnpm setup` configured).
|
|
4
4
|
|
|
5
5
|
## Self-update & process hygiene
|
|
6
6
|
|
|
7
|
-
The bridge auto-picks up new `@mrrlin-dev/mcp` versions after `
|
|
7
|
+
The bridge auto-picks up new `@mrrlin-dev/mcp` versions after `npm install -g`. No manual `pm2 restart` is required.
|
|
8
8
|
|
|
9
9
|
### How it works
|
|
10
10
|
|
|
11
11
|
- **L1 (self-update loop):** every 15 minutes (env-tunable) the bridge hashes its own `bin.cjs` and, on change, drains the current Codex turn cleanly and exits via `bridgeShutdown`. PM2 restarts. New code loads.
|
|
12
|
-
- **L2 (postinstall nudge):** `
|
|
13
|
-
- **L3 (in-chat update offer):** every 6 hours the bridge checks `https://registry.npmjs.org/@mrrlin-dev/mcp/latest`. When a newer version is published, on your next chat turn the Director asks: *"Бачу що bridge на X, на npm уже Y — оновити зараз?"*. Say "yes" → Director runs `
|
|
12
|
+
- **L2 (postinstall nudge):** `npm install -g @mrrlin-dev/mcp@latest` triggers a `SIGUSR2` to every running PM2 bridge, collapsing the L1 wait to seconds.
|
|
13
|
+
- **L3 (in-chat update offer):** every 6 hours the bridge checks `https://registry.npmjs.org/@mrrlin-dev/mcp/latest`. When a newer version is published, on your next chat turn the Director asks: *"Бачу що bridge на X, на npm уже Y — оновити зараз?"*. Say "yes" → Director runs `npm install -g @mrrlin-dev/mcp@latest` itself. 48h cooldown if you decline.
|
|
14
14
|
- **L4 (process hygiene):** the bridge refuses to start a second instance on the same port and warns about orphan `mrrlin-mcp director-bridge` processes at startup.
|
|
15
15
|
|
|
16
16
|
### Env tuning
|
|
@@ -72,7 +72,7 @@ This is only needed for the legacy population (bridges started before this self-
|
|
|
72
72
|
|
|
73
73
|
When a newer `@mrrlin-dev/mcp` is published and your bridge polls (within 6h):
|
|
74
74
|
|
|
75
|
-
1. On your next chat turn, the Director weaves a yes/no question in: *"Бачу що bridge на X, на npm уже Y — оновити зараз? (запущу `
|
|
75
|
+
1. On your next chat turn, the Director weaves a yes/no question in: *"Бачу що bridge на X, на npm уже Y — оновити зараз? (запущу `npm install -g @mrrlin-dev/mcp@latest`)"*
|
|
76
76
|
2. You reply "yes" / "так" / "ага" → Director runs the install via its shell tool, reports stdout + exit code in chat.
|
|
77
77
|
3. L1 picks up the new `bin.cjs` (or L2 SIGUSR2 nudges it sooner) → drain-on-quiet → PM2 restart → web reconnects.
|
|
78
78
|
4. You reply "later" → Director acknowledges and drops it for 48h.
|