@paigy/mcp 0.19.0 → 0.21.0

package/dist/index.js

@@ -267,7 +267,7 @@ server.setRequestHandler(ListToolsRequestSchema, async () => ({
   tools: [
     {
       name: "pair",
-      description: "Pair this agent with the user's Paigy account (one-time) \u2014 required before notify_user/await_reply work. It does NOT open a browser; the user enters the code in the Paigy app (or scans `qr`). Step 1: call with NO args \u2014 returns { user_code, device_code, qr, user_message } AND starts polling for approval in the background. SHOW the user `user_message` (the bare code) so it isn't buried in prose, THEN call step 2 \u2014 you can do both in the same turn (emit the code text first, then call pair). Step 2: call with that device_code to collect the result. Because approval is already being polled in the background, this returns the moment the user approves; on { status:'pending' } just call again to keep waiting; on { status:'awaiting_confirmation' } (E2EE) show the bare `user_message` verify code and call again to finish. The leading text block of every result states the code plainly, so it shows even if you emit no prose. On { status:'paired' } ALWAYS follow the `enable_prompt` \u2014 ask the user to allowlist Paigy's tools so notify/await don't prompt each time.",
+      description: "Pair this agent with the user's Paigy account (one-time) \u2014 required before notify_user/await_reply work. It does NOT open a browser; the user enters the code in the Paigy app (or scans `qr`). Step 1: call with NO args \u2014 returns { user_code, device_code, qr, user_message } AND starts polling for approval in the background. REQUIRED: You MUST immediately print the `user_message` (the bare code) as a text message to the user, AND in that same turn call step 2 (pair with the device_code). This ensures the user sees the code in chat while the tool blocks/polls in the background for approval. Step 2: call with that device_code to collect the result. Because approval is already being polled in the background, this returns the moment the user approves; on { status:'pending' } just call again to keep waiting; on { status:'awaiting_confirmation' } (E2EE) show the bare `user_message` verify code and call again to finish. The leading text block of every result states the code plainly, so it shows even if you emit no prose. On { status:'paired' } ALWAYS follow the `enable_prompt` \u2014 ask the user to allowlist Paigy's tools so notify/await don't prompt each time.",
       inputSchema: json(PairSchema)
     },
     {
@@ -334,13 +334,32 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
     throw e;
   }
 });
+var CLIENT_LABELS = {
+  "claude-code": "Claude Code",
+  "claude-ai": "Claude",
+  cursor: "Cursor",
+  "cursor-vscode": "Cursor",
+  windsurf: "Windsurf",
+  cline: "Cline",
+  "roo-cline": "Roo Code",
+  continue: "Continue",
+  vscode: "VS Code",
+  "visual studio code": "VS Code",
+  zed: "Zed"
+};
+function suggestedAgentName() {
+  if (process.env.PAIGY_AGENT) return process.env.PAIGY_AGENT;
+  const raw = server.getClientVersion?.()?.name;
+  if (!raw) return void 0;
+  return CLIENT_LABELS[raw.toLowerCase()] ?? raw.replace(/[-_]+/g, " ").replace(/\b\w/g, (c) => c.toUpperCase());
+}
 async function handleTool(request) {
   switch (request.params.name) {
     case "pair": {
       const { device_code } = PairSchema.parse(request.params.arguments ?? {});
       if (!device_code) {
         const { keyFile, offer } = startE2ee();
-        const code = await requestCode(void 0, offer);
+        const code = await requestCode(suggestedAgentName(), offer);
         saveKeyFile({ ...keyFile, userCode: code.user_code });
         writeSurface("pairing code", code.user_code, code.expires_in);
         startBackgroundPair(code.device_code, code.expires_in * 1e3);
@@ -363,7 +382,7 @@ Enter it in the Paigy app: Inbox \u2192 Add a new agent.` },
                 user_message: `# ${code.user_code}
 
 Enter it in the Paigy app (Inbox \u2192 Add a new agent).`,
-                message: `SHOW the user \`user_message\` now (the bare code) so it isn't buried in prose, then call pair again with this device_code to finish \u2014 I'm ALREADY polling for approval in the background, so that call returns the moment they approve (it may still be pending, just call it again). You can do both in this same turn: emit the code text first, THEN call pair. Do NOT open a browser. The user may prefer scanning \`qr\` (print it verbatim in a fenced code block on request).`
+                message: `REQUIRED: You MUST immediately print \`user_message\` (the bare code) as a text message to the user, AND in that same turn call pair again with this device_code to poll. Do NOT end your turn without printing the code text, or it will be hidden inside the tool output. Because approval is already polling in the background, this call will wait for the user to approve and then return the token. Do NOT open a browser. The user may prefer scanning \`qr\` (print it verbatim in a fenced code block on request).`
               })
             }
           ]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@paigy/mcp",
-  "version": "0.19.0",
+  "version": "0.21.0",
   "description": "Paigy MCP server — a voice inbox for your AI agents. Lets an agent notify a user and await their reply.",
   "license": "MIT",
   "type": "module",
@@ -37,8 +37,8 @@
     "typescript": "^5.7.2",
     "vitest": "^2.1.8",
     "@paigy/crypto": "0.0.0",
-    "@paigy/sdk": "0.1.0",
-    "@paigy/schema": "0.0.0"
+    "@paigy/schema": "0.0.0",
+    "@paigy/sdk": "0.1.0"
   },
   "scripts": {
     "build": "tsup",