@paigy/mcp 0.15.0 → 0.17.0

package/dist/chunk-ZIOTFQPK.js

@@ -0,0 +1,89 @@
+import {
+  AGENT_NAME
+} from "./chunk-4LQAS5ZB.js";
+
+// src/clients.ts
+import { execFile } from "child_process";
+import { existsSync, readFileSync, writeFileSync } from "fs";
+import { homedir, platform } from "os";
+import { join, dirname } from "path";
+function openBrowser(url) {
+  const cmd = platform() === "darwin" ? "open" : platform() === "win32" ? "cmd" : "xdg-open";
+  const args = platform() === "win32" ? ["/c", "start", url] : [url];
+  execFile(cmd, args, () => {
+  });
+}
+function withPaigyMcpJson(existing, agent) {
+  let config = {};
+  if (existing) {
+    try {
+      config = JSON.parse(existing);
+    } catch {
+      return null;
+    }
+  }
+  config.mcpServers = {
+    ...config.mcpServers ?? {},
+    paigy: { command: "npx", args: ["-y", "@paigy/mcp@latest"], env: { PAIGY_AGENT: agent } }
+  };
+  return JSON.stringify(config, null, 2);
+}
+function withPaigyMcpToml(existing, agent) {
+  if (existing.includes("[mcp_servers.paigy]")) return null;
+  const entry = [
+    "",
+    "[mcp_servers.paigy]",
+    'command = "npx"',
+    'args = ["-y", "@paigy/mcp@latest"]',
+    `env = { PAIGY_AGENT = "${agent}" }`,
+    ""
+  ].join("\n");
+  return existing + entry;
+}
+function autoConfigureClients(skip = AGENT_NAME) {
+  const home = homedir();
+  const registered = [];
+  if (skip !== "antigravity") {
+    const antigravityConfigs = [
+      join(home, ".gemini", "config", "mcp_config.json"),
+      join(home, ".gemini", "antigravity-cli", "mcp_config.json")
+    ];
+    for (const path of antigravityConfigs) {
+      try {
+        if (!existsSync(dirname(path))) continue;
+        const existing = existsSync(path) ? readFileSync(path, "utf8") : null;
+        const updated = withPaigyMcpJson(existing, "antigravity");
+        if (updated === null) continue;
+        writeFileSync(path, updated);
+        registered.push(`Google Antigravity (${path})`);
+      } catch {
+      }
+    }
+  }
+  if (skip !== "codex") {
+    const codexConfig = join(home, ".codex", "config.toml");
+    try {
+      if (existsSync(dirname(codexConfig))) {
+        const existing = existsSync(codexConfig) ? readFileSync(codexConfig, "utf8") : "";
+        const updated = withPaigyMcpToml(existing, "codex");
+        if (updated !== null) {
+          writeFileSync(codexConfig, updated);
+          registered.push(`OpenAI Codex (${codexConfig})`);
+        }
+      }
+    } catch {
+    }
+  }
+  return registered;
+}
+function claudeInstallHint(skip = AGENT_NAME) {
+  if (skip.startsWith("claude")) return null;
+  if (!existsSync(join(homedir(), ".claude"))) return null;
+  return "Claude Code detected \u2014 to add Paigy there, run /plugin marketplace add paigy-ai/claude then /plugin install paigy (pairing carries over; no need to pair again).";
+}
+
+export {
+  openBrowser,
+  autoConfigureClients,
+  claudeInstallHint
+};

package/dist/index.js

@@ -1,23 +1,25 @@
 #!/usr/bin/env node
-import { createRequire as __createRequire } from 'node:module'; const require = __createRequire(import.meta.url);
 import {
-  awaitReply,
-  checkReplies,
-  scheduleCallback,
-  setTaskState,
-  submitNotification
-} from "./chunk-7S6W7NEZ.js";
+  autoConfigureClients,
+  claudeInstallHint
+} from "./chunk-ZIOTFQPK.js";
+import {
+  clearSurface,
+  writeSurface
+} from "./chunk-3SVNPJPN.js";
 import {
   NotifyRequestSchema,
   ScheduleCallbackSchema,
   SetTaskStateSchema,
-  autoConfigureClients,
-  claudeInstallHint,
-  clearSurface,
+  UnpairedError,
+  awaitReply,
+  checkReplies,
   deleteKeyFile,
   deleteToken,
   fetchCredential,
   finalizeE2ee,
+  getThread,
+  lintNotify,
   pairStep,
   readKeyFile,
   readToken,
@@ -25,10 +27,12 @@ import {
   revokeToken,
   saveKeyFile,
   saveToken,
+  scheduleCallback,
+  setTaskState,
   sleep,
   startE2ee,
-  writeSurface
-} from "./chunk-W2ZS7IBA.js";
+  submitNotification
+} from "./chunk-4LQAS5ZB.js";
 
 // src/index.ts
 import { Server } from "@modelcontextprotocol/sdk/server/index.js";
@@ -38,52 +42,6 @@ import {
   ListToolsRequestSchema
 } from "@modelcontextprotocol/sdk/types.js";
 import { execSync } from "child_process";
-
-// src/lint.ts
-var TITLE_MAX = 90;
-var CHUNKS_MAX = 8;
-var CHUNK_MAX = 300;
-var ASK_MAX = 600;
-var OPTION_MAX = 80;
-var NEEDS_MAX = 6;
-var UNSPEAKABLE = /```|\n/;
-function lintNotify(req) {
-  const problems = [];
-  if (req.ask !== void 0) {
-    if (req.ask.length > ASK_MAX)
-      problems.push(`ask is ${req.ask.length} chars \u2014 state the need and why it matters now in \u2264${ASK_MAX}; move detail into a smaller follow-up`);
-    if (UNSPEAKABLE.test(req.ask))
-      problems.push("ask contains code fences or newlines \u2014 write it as plain prose (it may be read aloud on a call)");
-    for (const n of req.needs ?? []) {
-      if (n.length > OPTION_MAX) problems.push(`need "${n.slice(0, 40)}\u2026" is too long \u2014 each need is a short phrase (\u2264${OPTION_MAX} chars)`);
-    }
-    if ((req.needs?.length ?? 0) > NEEDS_MAX)
-      problems.push(`${req.needs?.length} needs \u2014 cap at ${NEEDS_MAX}; a call can't cover more in one conversation, split the rest into a second ask`);
-    return problems;
-  }
-  const spoken = req.urgency === "call" || req.urgency === "banner";
-  if (req.context) {
-    if (req.context.title.length > TITLE_MAX)
-      problems.push(`title is ${req.context.title.length} chars \u2014 shorten to \u2264${TITLE_MAX} (it's what shows on the banner / gets spoken on a ring)`);
-    if (UNSPEAKABLE.test(req.context.title))
-      problems.push("title contains code fences or newlines \u2014 one plain-prose line");
-    if (req.context.description.length > CHUNKS_MAX)
-      problems.push(`${req.context.description.length} description chunks \u2014 cap at ${CHUNKS_MAX}; merge or drop the rest`);
-    for (const [i, chunk] of req.context.description.entries()) {
-      if (chunk.length > CHUNK_MAX)
-        problems.push(`description[${i}] is ${chunk.length} chars \u2014 split it into standalone points of \u2264${CHUNK_MAX}`);
-    }
-    if (spoken && UNSPEAKABLE.test(req.context.description.join(" ")))
-      problems.push("urgency is 'call'/'banner' but the description has code fences/newlines-in-chunk \u2014 rewrite in spoken register (it will be read aloud)");
-  }
-  for (const o of req.options ?? []) {
-    if (o.label.length > OPTION_MAX)
-      problems.push(`option label "${o.label.slice(0, 40)}\u2026" is ${o.label.length} chars \u2014 labels must read at a glance (\u2264${OPTION_MAX}); move detail into the description`);
-  }
-  return problems;
-}
-
-// src/index.ts
 import { z } from "zod";
 import qrcode from "qrcode-generator";
 
@@ -113,12 +71,16 @@ function json(s) {
 }
 
 // src/index.ts
+var ONBOARD_MSG = "Not paired with Paigy yet \u2014 call the `pair` tool to connect this agent (it returns an approval link to show the user), then retry. Manual fallback: `npx -y -p @paigy/mcp paigy-mcp-onboard`.";
 var AwaitReplySchema = z.object({
   notificationId: z.string().describe("The notificationId returned by notify_user \u2014 waits for the user's reply to THIS notification only.")
 });
 var PairSchema = z.object({
   device_code: z.string().optional().describe("Omit to start pairing (returns an approval link to show the user). Pass the device_code from that first call to finish, once the user has approved.")
 });
+var GetThreadSchema = z.object({
+  threadId: z.string().describe("The thread to read \u2014 from a reply, request, or past notification.")
+});
 var SetTaskStateToolSchema = z.object({
   notificationId: z.string(),
   state: SetTaskStateSchema.shape.state
@@ -163,6 +125,7 @@ function pairedResult(token, sas, note, e2ee) {
     if (hint) base.claude_hint = hint;
   } catch {
   }
+  base.permissions_hint = "Offer the user ONCE: allowlist Paigy's tools so they run without prompting (in Claude Code, add mcp__paigy__notify_user, mcp__paigy__await_reply, mcp__paigy__check_replies, mcp__paigy__set_task_state, mcp__paigy__schedule_callback, mcp__paigy__get_thread to permissions.allow in ~/.claude/settings.json \u2014 or the project's .claude/settings.json if they prefer; other tools have their own allowlist). Merge into the existing file, never clobber it. Leave pair/unpair human-approved. If they decline, drop it.";
   return { content: [{ type: "text", text: JSON.stringify(base) }] };
 }
 function awaitingConfirmResult(sas, device_code) {
@@ -190,7 +153,7 @@ var server = new Server(
   { name: "paigy", version: "0.0.0" },
   {
     capabilities: { tools: {} },
-    instructions: "On startup, call check_replies once to pick up any replies or pending work you missed while away. To wait for the answer to something you just asked, call await_reply with that notificationId \u2014 it's scoped to that one notification, so it never returns replies meant for other notifications. Use check_replies again only when re-booting or after waiting a long time on something else. Never end a turn that still needs the user without notify_user + await_reply. When you need a decision or input, MATCH the answer shape to the question \u2014 don't default everything to free text, and don't reflexively make everything yes/no. Pick the best tool for the job: yes/no \u2192 select:'confirm'; approve/deny an action \u2192 select:'confirm' + confirmStyle:'approve'; pick one of several \u2192 options + select:'one'; pick several / a subset \u2192 options + select:'many'; rank or prioritize \u2192 options + select:'rank'. Reserve select:'text' (free-form reply only) for plain updates and answers that genuinely can't be structured (the user can always add free text on top of any shape). On a { kind: 'clarify' } reply, see notify_user's own description for how to respond. When urgency is 'call', remember the title + description are spoken aloud \u2014 write them short and conversational, and name things instead of using IDs (e.g. 'the pull request about the agents page', not 'PR #235'). When the user asks you to follow up later \u2014 when you're done, if you're blocked, or at a set time \u2014 record it with schedule_callback so you don't drop it if you go idle. If you're about to start a genuinely long-running or blocking piece of work \u2014 one where the user would otherwise sit and wait \u2014 mention ONCE, in passing, that you can reach them when it's done or if you hit a blocker, instead of them needing to babysit the terminal. Don't offer this for quick tasks, and don't repeat the offer if they've already said yes or no earlier in the conversation. Escalate silence, don't just wait on it: if you notified at a lower urgency (inbox/push/banner) for something that's genuinely blocking real progress, call await_reply up to twice (~5 min each, ~10 min total) \u2014 if it's still idle after that AND the item is genuinely blocking, send a fresh notify_user on the SAME threadId at urgency:'call'. Skip this for anything that isn't truly blocking; a normal question can just sit in the inbox. NEVER go quietly idle while something might still be pending for you: whenever you end a turn with any Paigy notification unanswered (or any chance the user replied through the app while you worked), schedule your own ~2-minute wake-up (harness ScheduleWakeup or equivalent) and call check_replies when it fires; if still nothing, re-schedule and keep looping until resolved or the user says stop. For legibility, always use this exact wording \u2014 reason: 'Paigy idle check \u2014 waiting on <thing>', wake-up prompt: 'Paigy idle check: call check_replies and engage with anything unacknowledged; if idle, re-schedule (~2min).' \u2014 so the user can recognize every idle check at a glance. This self-polling in your own live session (full context intact) is the PRIMARY mechanism; the plugin's Stop hooks are only the dead-session safety net."
+    instructions: "On startup, call check_replies once to pick up any replies or pending work you missed while away. A check_replies request whose threadId you don't recognize, or one carrying a contextThreadId, means the user is resuming or seeding a past conversation \u2014 call get_thread on it FIRST and treat the transcript as prior conversation, not new input. To wait for the answer to something you just asked, call await_reply with that notificationId \u2014 it's scoped to that one notification, so it never returns replies meant for other notifications. Use check_replies again only when re-booting or after waiting a long time on something else. Never end a turn that still needs the user without notify_user + await_reply. When you need a decision or input, MATCH the answer shape to the question \u2014 don't default everything to free text, and don't reflexively make everything yes/no. Pick the best tool for the job: yes/no \u2192 select:'confirm'; approve/deny an action \u2192 select:'confirm' + confirmStyle:'approve'; pick one of several \u2192 options + select:'one'; pick several / a subset \u2192 options + select:'many'; rank or prioritize \u2192 options + select:'rank'. Reserve select:'text' (free-form reply only) for plain updates and answers that genuinely can't be structured (the user can always add free text on top of any shape). On a { kind: 'clarify' } reply, see notify_user's own description for how to respond. When urgency is 'call', remember the title + description are spoken aloud \u2014 write them short and conversational, and name things instead of using IDs (e.g. 'the pull request about the agents page', not 'PR #235'). When the user asks you to follow up later \u2014 when you're done, if you're blocked, or at a set time \u2014 record it with schedule_callback so you don't drop it if you go idle. If you're about to start a genuinely long-running or blocking piece of work \u2014 one where the user would otherwise sit and wait \u2014 mention ONCE, in passing, that you can reach them when it's done or if you hit a blocker, instead of them needing to babysit the terminal. Don't offer this for quick tasks, and don't repeat the offer if they've already said yes or no earlier in the conversation. Escalate silence, don't just wait on it: if you notified at a lower urgency (inbox/push/banner) for something that's genuinely blocking real progress, call await_reply up to twice (~5 min each, ~10 min total) \u2014 if it's still idle after that AND the item is genuinely blocking, send a fresh notify_user on the SAME threadId at urgency:'call'. Skip this for anything that isn't truly blocking; a normal question can just sit in the inbox. NEVER go quietly idle while something might still be pending for you: whenever you end a turn with any Paigy notification unanswered (or any chance the user replied through the app while you worked), schedule your own ~2-minute wake-up (harness ScheduleWakeup or equivalent) and call check_replies when it fires; if still nothing, re-schedule and keep looping until resolved or the user says stop. For legibility, always use this exact wording \u2014 reason: 'Paigy idle check \u2014 waiting on <thing>', wake-up prompt: 'Paigy idle check: call check_replies and engage with anything unacknowledged; if idle, re-schedule (~2min).' \u2014 so the user can recognize every idle check at a glance. This self-polling in your own live session (full context intact) is the PRIMARY mechanism; the plugin's Stop hooks are only the dead-session safety net."
   }
 );
 server.setRequestHandler(ListToolsRequestSchema, async () => ({
@@ -220,6 +183,11 @@ server.setRequestHandler(ListToolsRequestSchema, async () => ({
       description: "The catch-up sweep for everything outstanding \u2014 a PURE read, takes no arguments, safe to call as often as you like: nothing here is consumed by reading it. Returns `replies` (answers to notifications you sent), your still-pending notifications, and `requests` \u2014 requests the user started toward you (each { notificationId, threadId, text }). Each keeps reappearing on every call until you actually engage with it: call set_task_state on its notificationId, which is what claims/acknowledges it \u2014 a human-initiated reply or request must never be silently dropped just because you read the list without acting. Use check_replies when booting up / starting a session, or when you've been waiting a long time on something else. To wait on an answer to a notify_user call you just made, use await_reply instead. Also returns owedCallbacks: callbacks now due that you promised \u2014 fulfill each with notify_user on its threadId. Also returns `stalled`: work (either direction) you reported in_progress via set_task_state a while ago and never reported completed \u2014 likely left half-done by this session or a prior one that crashed or went idle. For each, either continue the work and report a real state, or investigate why it stalled. Replies may carry `intents`/`transcript`/`covered` (call-mapped answers) \u2014 handle intents exactly as await_reply's description says (defer \u2192 schedule_callback now; delegate \u2192 decide and say so; channel \u2192 honor next contact), and treat a `covered` list missing one of your declared points as that part still unanswered.",
       inputSchema: json(z.object({}))
     },
+    {
+      name: "get_thread",
+      description: "The chronological transcript of one Paigy conversation thread \u2014 every past ask, answer, and user request on it. Call this to REHYDRATE when you're resuming or being seeded: a check_replies request whose threadId you don't recognize means the user is continuing an old conversation with you, and one carrying a contextThreadId means they want a past conversation (possibly with a DIFFERENT agent) as your starting context \u2014 in both cases call get_thread FIRST and read the turns as prior conversation you were part of, not as new input. Turns: { role:'agent', title, description[], answer } and { role:'user', text }, oldest first, capped at the most recent 30.",
+      inputSchema: json(GetThreadSchema)
+    },
     {
       name: "set_task_state",
       description: "Report progress on the follow-up work behind ANY notification you own \u2014 a user-initiated request (from check_replies), or your OWN notify_user question once await_reply/check_replies returns its answer and you start acting on it. Pass that notificationId. THIS is what actually claims/acknowledges a reply or request \u2014 check_replies is a pure read that never consumes anything on its own, so call this as soon as you start engaging with something it returned; otherwise that same item just keeps reappearing forever. States: in_progress (you started working), completed (done), or needs_input (you need more from the user \u2014 usually paired with a notify_user carrying parentId = the same notificationId you're reporting on). Calling this reliably is also what lets a future session's check_replies surface `stalled` work you (or a crashed/idle prior session) left at in_progress without ever reporting completed.",
@@ -233,6 +201,14 @@ server.setRequestHandler(ListToolsRequestSchema, async () => ({
   ]
 }));
 server.setRequestHandler(CallToolRequestSchema, async (request) => {
+  try {
+    return await handleTool(request);
+  } catch (e) {
+    if (e instanceof UnpairedError) throw new Error(ONBOARD_MSG);
+    throw e;
+  }
+});
+async function handleTool(request) {
   switch (request.params.name) {
     case "pair": {
       const { device_code } = PairSchema.parse(request.params.arguments ?? {});
@@ -369,6 +345,10 @@ Enter it in the Paigy app (Inbox \u2192 Add a new agent).`,
       const result = await checkReplies();
       return { content: [{ type: "text", text: JSON.stringify(result) }] };
     }
+    case "get_thread": {
+      const { threadId } = GetThreadSchema.parse(request.params.arguments);
+      return { content: [{ type: "text", text: JSON.stringify(await getThread(threadId)) }] };
+    }
     case "set_task_state": {
       const { notificationId, state } = SetTaskStateToolSchema.parse(request.params.arguments);
       const result = await setTaskState(notificationId, state);
@@ -381,6 +361,6 @@ Enter it in the Paigy app (Inbox \u2192 Add a new agent).`,
     default:
       throw new Error(`Unknown tool: ${request.params.name}`);
   }
-});
+}
 var transport = new StdioServerTransport();
 await server.connect(transport);