@paigy/mcp 0.16.0 → 0.17.1
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 +25 -1
- package/dist/{chunk-U3WODCOE.js → chunk-IMIXCPTN.js} +1 -1
- package/dist/chunk-MH6AHNUI.js +633 -0
- package/dist/{chunk-R3YGSGPX.js → chunk-RMTTO6BI.js} +108 -3
- package/dist/index.js +42 -4
- package/dist/listen.js +112 -544
- package/dist/onboard.js +2 -2
- package/dist/statusline.js +1 -1
- package/package.json +12 -11
package/README.md
CHANGED
|
@@ -112,6 +112,30 @@ Then pair: `npx -p @paigy/mcp@latest paigy-mcp-onboard`.
|
|
|
112
112
|
ignored), and `paigy-listen`'s realtime wake channel is a websocket that doesn't
|
|
113
113
|
proxy — its REST sweeps do.
|
|
114
114
|
|
|
115
|
+
## Wake any harness (`paigy-listen`)
|
|
116
|
+
|
|
117
|
+
`paigy-listen` is the self-hosted push daemon: it subscribes to this connection's
|
|
118
|
+
wake channel and sweeps on every nudge. Keep it alive past the terminal with
|
|
119
|
+
`paigy-listen --install` (launchd on macOS, systemd user unit on Linux; `--uninstall`
|
|
120
|
+
removes it).
|
|
121
|
+
|
|
122
|
+
To launch an agent — any agent, not just Claude — when work arrives, set
|
|
123
|
+
`PAIGY_ON_WAKE` to a command before `--install`. The daemon runs it with the swept
|
|
124
|
+
work in `$PAIGY_WORK` (JSON: `replies`, `requests`, `owedCallbacks`); the sweep has
|
|
125
|
+
already claimed the work, so read `$PAIGY_WORK` rather than calling `check_replies`
|
|
126
|
+
again. A request carrying a `contextThreadId` (or an unfamiliar `threadId`) means
|
|
127
|
+
the user is resuming/seeding a past conversation — rehydrate with `get_thread` first.
|
|
128
|
+
|
|
129
|
+
```sh
|
|
130
|
+
# Claude Code:
|
|
131
|
+
PAIGY_ON_WAKE='claude -p "Handle the Paigy work in $PAIGY_WORK — rehydrate threads you do not recognize via get_thread first."' \
|
|
132
|
+
npx -y -p @paigy/mcp paigy-listen --install
|
|
133
|
+
|
|
134
|
+
# Codex (or any CLI harness) works the same way:
|
|
135
|
+
PAIGY_ON_WAKE='codex exec "Handle the Paigy work in $PAIGY_WORK ..."' \
|
|
136
|
+
npx -y -p @paigy/mcp paigy-listen --install
|
|
137
|
+
```
|
|
138
|
+
|
|
115
139
|
## Statusline (Claude Code)
|
|
116
140
|
|
|
117
141
|
`paigy-statusline` prints a one-line connection status — the account's session
|
|
@@ -124,7 +148,7 @@ paigy: all calls · phone ✓
|
|
|
124
148
|
Enable it in `~/.claude/settings.json`:
|
|
125
149
|
|
|
126
150
|
```json
|
|
127
|
-
"statusLine": { "type": "command", "command": "npx -y @paigy/mcp@latest paigy-statusline" }
|
|
151
|
+
"statusLine": { "type": "command", "command": "npx -y -p @paigy/mcp@latest paigy-statusline" }
|
|
128
152
|
```
|
|
129
153
|
|
|
130
154
|
It reads `GET /api/status` with the pairing token and caches the result in
|