@paigy/mcp 0.40.33 → 0.40.36

package/README.md

@@ -117,7 +117,7 @@ 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, manage_goals, get_goal, search, check_activity,
+`packages/schema/src/tools.ts` — contact, manage_goals, get_goals, search, check_activity,
 send_feedback — 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 `configure`, the one identity tool, which pairs, reports who you are,
@@ -135,7 +135,9 @@ acknowledged with `ackEventIds`, and a Goal is postponed with manage_goals `defe
 when its time comes). Durable Entries and accepted answers can
 repeat on reads; contact with nothing to send receives what is addressed to you (a request the
 user started toward you, an answer relayed to something you asked, a handoff, a question you owe) without
-consuming any of it until you acknowledge it (`ackEventIds`), and get_goal reads a Goal.
+consuming any of it until you acknowledge it (`ackEventIds`).
+`get_goals({ goalIds: [id1, id2] })` reads one to ten Goals, returning `{ goals: [...] }`
+in the requested order; `history` applies to every ID. It replaces `get_goal`.
 `claim_goal` is gone (2026-10-07): you are on a Goal from your first write to it (a contact
 naming it, or a manage_goals change), never from a read, so there is nothing to claim or join;
 `who_is_working` is now `check_activity`. manage_goals creates, edits, assigns, organizes and closes work, a change at a
@@ -181,8 +183,8 @@ To launch an agent — any agent, not just Claude — when work arrives, set
 | `PAIGY_WORK` | everything the wake found, as JSON (`deliveries`, `goal`) |
 | `PAIGY_EVENT` | the wake that caused this run — `boot`, `wake:reply`, `wake:request`… |
 | `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 (`get_goal` on `PAIGY_GOAL_ID` reads its conversation) |
-| `PAIGY_GOAL_ID` | the Goal it belongs to — read it with `get_goal` **first** |
+| `PAIGY_DELIVERY_ID` | the Delivery being acted on (`get_goals` on `PAIGY_GOAL_ID` reads its conversation) |
+| `PAIGY_GOAL_ID` | the Goal it belongs to — read it with `get_goals` **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
@@ -193,7 +195,7 @@ 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 — read each Goal it names with get_goal first."' \
+PAIGY_ON_WAKE='claude -p "Handle the Paigy work in $PAIGY_WORK — read each Goal it names with get_goals first."' \
   npx -y -p @paigy/mcp paigy-listen --install
 
 # Codex terminal session: no custom script and no new conversation.
@@ -237,7 +239,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
-codex exec "Paigy goal $PAIGY_GOAL_ID. Read it with get_goal first. The user said: $PAIGY_TEXT. Reply with contact when done."
+codex exec "Paigy goal $PAIGY_GOAL_ID. Read it with get_goals first. The user said: $PAIGY_TEXT. Reply with contact when done."
 ```
 
 ## Stalled work (turn-end hook — Claude Code, Codex, Gemini CLI, Antigravity)