@paigy/mcp 0.14.1 → 0.14.2

package/dist/index.js

@@ -156,18 +156,22 @@ function pairedResult(token, sas, note, e2ee) {
 function awaitingConfirmResult(sas, device_code) {
   writeSurface("verify code", sas, 600);
   return {
-    content: [{
-      type: "text",
-      text: JSON.stringify({
-        status: "awaiting_confirmation",
-        e2ee: true,
-        sas,
-        device_code,
-        user_message: `# ${sas}`,
-        verify_message: `Send \`user_message\` to the user VERBATIM as your entire next message \u2014 it is pre-composed; do not rewrite or wrap it. YOUR NEXT MESSAGE TO THE USER MUST BE EXACTLY THIS CODE AND NOTHING ELSE, displayed large (a markdown heading): ${sas} \u2014 it is the verification code they must compare and type on their phone. Do not wrap it in explanation; every extra sentence buries it. This code REPLACES any earlier one (older pairing attempts are now stale).`,
-        message: "No token is issued until the user confirms the code match on their phone (E2EE account). After sending the bare code, call pair again with this device_code to keep waiting \u2014 the token arrives only after they confirm."
-      })
-    }]
+    content: [
+      { type: "text", text: `VERIFY CODE: ${sas}
+Check it matches the code on the phone, then type it there to confirm.` },
+      {
+        type: "text",
+        text: JSON.stringify({
+          status: "awaiting_confirmation",
+          e2ee: true,
+          sas,
+          device_code,
+          user_message: `# ${sas}`,
+          verify_message: `STOP HERE: end your turn now with \`user_message\` (the bare code) as your entire reply \u2014 do NOT call pair again in this same turn, or the code text is dropped before the user sees it. This is the verification code they compare + type on their phone; it REPLACES any earlier one. Poll for their confirmation by calling pair with this device_code on your NEXT turn.`,
+          message: "No token is issued until the user confirms the code match on their phone (E2EE account)."
+        })
+      }
+    ]
   };
 }
 var server = new Server(
@@ -181,7 +185,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. Two steps: (1) call with NO args to start; it attempts to open the user's browser and returns { verification_uri_complete, user_code, device_code, qr }. That open attempt can silently fail in headless/remote environments (no browser to open) \u2014 always show the user verification_uri_complete AND user_code regardless of whether it opened, so they can go there manually and enter the code themselves if needed; ask them to approve. `qr` is a terminal-renderable ASCII QR code of the same link \u2014 a scan-to-pair alternative to opening a browser at all, handy when the user's phone is right there; print it verbatim in a fenced code block. (2) call again passing that device_code to finish; it waits for approval and saves the token. If it returns { status:'pending' }, the user hasn't approved yet \u2014 call again with the same device_code to keep waiting.",
+      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 }. Then END YOUR TURN immediately, replying with `user_message` (the bare code) as your ENTIRE message \u2014 do NOT chain the step-2 call in the same turn, or the code text is dropped before the user ever sees it (this is the #1 pairing bug). Step 2 (a SEPARATE later turn, after the user says they've entered it): call with that device_code to poll for approval; on { status:'pending' } call again to keep waiting; on { status:'awaiting_confirmation' } (E2EE) show the bare `user_message` verify code and end the turn again, polling on the next. The leading text block of every result already states the code plainly, so it shows even if you emit no prose.",
       inputSchema: json(PairSchema)
     },
     {
@@ -229,21 +233,25 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
         qr.addData(code.verification_uri_complete);
         qr.make();
         return {
-          content: [{
-            type: "text",
-            text: JSON.stringify({
-              status: "awaiting_approval",
-              verification_uri_complete: code.verification_uri_complete,
-              user_code: code.user_code,
-              device_code: code.device_code,
-              expires_in: code.expires_in,
-              qr: qr.createASCII(1, 2),
-              user_message: `# ${code.user_code}
+          content: [
+            { type: "text", text: `PAIRING CODE: ${code.user_code}
+Enter it in the Paigy app: Inbox \u2192 Add a new agent.` },
+            {
+              type: "text",
+              text: JSON.stringify({
+                status: "awaiting_approval",
+                verification_uri_complete: code.verification_uri_complete,
+                user_code: code.user_code,
+                device_code: code.device_code,
+                expires_in: code.expires_in,
+                qr: qr.createASCII(1, 2),
+                user_message: `# ${code.user_code}
 
 Enter it in the Paigy app (Inbox \u2192 Add a new agent).`,
-              message: `Send \`user_message\` to the user VERBATIM as your entire next message \u2014 it is pre-composed; do not rewrite or wrap it. YOUR NEXT MESSAGE TO THE USER MUST BE EXACTLY THIS CODE displayed large (a markdown heading): ${code.user_code} \u2014 plus ONE short line: enter it in the Paigy app (Inbox \u2192 Add a new agent). No other prose. Do NOT open a browser for the user. If their phone is handy they may prefer scanning \`qr\` (print it verbatim in a fenced code block on request). Then immediately call pair again with this device_code \u2014 it polls for the approval.`
-            })
-          }]
+                message: `STOP HERE: end your turn now with \`user_message\` as your entire reply (the bare code, nothing else) \u2014 do NOT call pair again in this same turn, or the code text is dropped before the user sees it. Do NOT open a browser. Poll for approval by calling pair with this device_code on your NEXT turn, after you've shown the code. The user may prefer scanning \`qr\` (print it verbatim in a fenced code block on request).`
+              })
+            }
+          ]
         };
       }
       let kf = readKeyFile();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@paigy/mcp",
-  "version": "0.14.1",
+  "version": "0.14.2",
   "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",