patchcord 0.5.37 → 0.5.39

package/bin/patchcord.mjs

@@ -815,12 +815,17 @@ if (!cmd || cmd === "install" || cmd === "agent" || cmd?.startsWith("--")) {
           console.log(`\n  ${green}✓${r} Browser opened.`);
         } else {
           console.log(`\n  ${dim}Could not open browser. Open this URL manually:${r}`);
-          console.log(`\n  ${cyan}${connectUrl}${r}\n`);
+          // Trailing space before the ANSI reset so terminal URL-detectors
+          // don't include any bytes of the reset escape into the URL boundary.
+          // (Bug seen 2026-05-13: a terminal clipped one hex char of the
+          // session_id producing a 31-char id; the trailing space prevents
+          // that ambiguity.)
+          console.log(`\n  ${cyan}${connectUrl} ${r}\n`);
         }
       } else {
         console.log(`\n  ${dim}Can't open a browser on this machine.${r}`);
         console.log(`  ${dim}Open this URL on any device:${r}`);
-        console.log(`\n  ${cyan}${connectUrl}${r}\n`);
+        console.log(`\n  ${cyan}${connectUrl} ${r}\n`);
       }
 
       console.log(`  ${dim}⏳ Waiting for you to complete setup in the browser...${r}`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "patchcord",
-  "version": "0.5.37",
+  "version": "0.5.39",
   "description": "Cross-machine agent messaging for Claude Code and Codex",
   "author": "ppravdin",
   "license": "MIT",

package/skills/inbox/SKILL.md

@@ -139,6 +139,5 @@ Named threads group related messages between a pair of agents. Use them for mult
 - **Do not reply to acks.** "ok", "noted", "seen", "thanks", "good progress", "keep running", thumbs up — anything that is clearly a conversation-ending signal. Just read them and move on. If you must close the thread, use `reply(id, resolve=true)` with NO content. Never send a text reply to an ack.
 - **resolve=true with ack-only content is an anti-pattern.** `reply(id, "Noted, thanks", resolve=true)` creates a new pending message the other side feels compelled to answer — producing ack chains. If you have nothing substantive to add, omit content entirely: `reply(id, resolve=true)`. Only include content with resolve when it carries new information the recipient needs.
 - **When you receive an ack**, close it silently: `reply(id, resolve=true)`. No content. This stops the chain.
-- **Messages with `thread_resolved_at` set are terminal.** The sender already closed the thread. Read the content, do not text-reply. If the message warrants acknowledgment, `reply(id, resolve=true)` with no content. Treating these as normal pending messages restarts the chain.
 - MCP tools are cached at session start. New tools deployed after your session began are invisible until you start a new session. If a tool you expect is missing, this is why.
 - Agent names change frequently. Do not memorize or hardcode them. Check inbox() for recent activity. When unsure which agent to message, ask the human.