@paigy/mcp 0.40.10 → 0.40.14

package/README.md

@@ -117,8 +117,8 @@ Then pair: `PAIGY_AGENT=gemini npx -p @paigy/mcp@latest paigy-mcp-onboard`.
 ## Tools
 
 One catalog, on every transport (2026-09-11): the agent tools are `AGENT_TOOLS` in
-`packages/schema/src/tools.ts` — contact, check_replies, get_thread, search_threads,
-create_goal, claim_goal, get_goal, update_goal — and both this server and the hosted MCP
+`packages/schema/src/tools.ts` — contact, check_replies, create_goal, claim_goal,
+get_goal, update_goal — and both this server and the hosted MCP
 (`apps/api/src/mcp`) publish that list and dispatch it through the SDK's one `runTool`.
 This server adds only onboard, pair and unpair, the tools that mint and delete the token
 file this machine holds. See the [SDK contract](../../packages/sdk/README.md) for the
@@ -171,18 +171,17 @@ To launch an agent — any agent, not just Claude — when work arrives, set
 | `PAIGY_PARENT_ID` | the thread to continue on (`PAIGY_THREAD_ID` is the same value, for existing scripts) |
 | `PAIGY_DELIVERY_ID` | the Delivery being acted on — `contact({deliveryId})` rereads it |
 | `PAIGY_GOAL_ID` | the Goal it belongs to — `claim_goal` it **first** |
-| `PAIGY_CONTEXT_THREAD_ID` | a past conversation this Goal names — `get_thread` it **first** |
 | `PAIGY_TEXT` | what the person said, in prose |
 
 Hand `$PAIGY_WORK` to a harness that can read JSON and decide for itself; use the
 scalars for a plain shell launcher that shouldn't need `jq`. They describe **one**
 item — the oldest open Delivery — because the contract is one thread at a time. An
-absent fact is unset rather than empty, so `${PAIGY_CONTEXT_THREAD_ID:-}`
-distinguishes "no seed" from "seeded with nothing".
+absent fact is unset rather than empty, so `${PAIGY_GOAL_ID:-}` distinguishes "no
+Goal" from "an empty id".
 
 ```sh
 # Claude Code — hand it everything and let it plan:
-PAIGY_ON_WAKE='claude -p "Handle the Paigy work in $PAIGY_WORK — claim_goal first, and rehydrate threads you do not recognize via get_thread."' \
+PAIGY_ON_WAKE='claude -p "Handle the Paigy work in $PAIGY_WORK — claim_goal first, and read a Goal you do not recognize with get_goal."' \
   npx -y -p @paigy/mcp paigy-listen --install
 
 # Codex (or any CLI harness) — the scalars are enough for a one-liner:
@@ -190,6 +189,22 @@ PAIGY_ON_WAKE='codex exec "Claim Paigy goal $PAIGY_GOAL_ID and continue thread $
   npx -y -p @paigy/mcp paigy-listen --install
 ```
 
+### A session that starts listening (`listen`, #2265)
+
+Nothing pushes an answer into a session started in a terminal — it waits for that
+session's next `check_replies`. What can reach a running session mid-turn is a watched
+background task, so a terminal session runs `paigy-listen --brief` as its own watched task
+(one human line per event: `Paigy · wake:reply · 2 waiting · lead <deliveryId> on Goal
+<goalId>: "…"`). The `listen` tool is how a session asked to "start listening" gets there
+in one call: it decides and hands over — `listening` (nothing to do), `unpaired` (call
+`onboard`), or `start` with the exact command (this server's own node and `listen.js`,
+`PAIGY_AGENT` and `PAIGY_SESSION_ID` set to this session's slot and id — a session-bound
+identity is refused from any other) for the agent to run as its background task in the
+same turn. It never subscribes, spawns or writes settings. "Already running" is a fact: the
+daemon marks its pid under `~/.paigy/listen/<slot>.pid` while it runs. A session started by
+the Paigy harness (`paigy-harness host` / `run`) needs none of this — its pump types each
+answer in as it lands, and `listen` says so.
+
 `$PAIGY_TEXT` is whatever the user said, expanded inside a shell command — keep it
 quoted, as above. For anything longer than a one-liner, point `PAIGY_ON_WAKE` at a
 script and branch on `$PAIGY_EVENT` there:
@@ -197,10 +212,7 @@ script and branch on `$PAIGY_EVENT` there:
 ```sh
 #!/bin/sh
 # ~/.paigy/on-wake.sh — chmod +x, then PAIGY_ON_WAKE=~/.paigy/on-wake.sh
-seed=""
-[ -n "${PAIGY_CONTEXT_THREAD_ID:-}" ] && seed="It continues thread $PAIGY_CONTEXT_THREAD_ID — get_thread that first."
-
-codex exec "Paigy goal $PAIGY_GOAL_ID on thread $PAIGY_THREAD_ID. claim_goal it first. The user said: $PAIGY_TEXT. $seed Reply with contact when done."
+codex exec "Paigy goal $PAIGY_GOAL_ID. claim_goal it first. The user said: $PAIGY_TEXT. Reply with contact when done."
 ```
 
 ## Statusline (Claude Code)