social-autoposter 1.6.93 → 1.6.94

package/mcp/dist/index.js

@@ -655,6 +655,7 @@ async function postApproved(batchId, plan) {
     // the post for the browser. Reset is guaranteed by scheduleShellLockRelease()
     // in the finally below, so an early/failed post can't wedge scanning.
     postingActive = true;
+    startPostingFlagHeartbeat(); // cross-instance: a sibling MCP's scan defers too
     // Posting is a priority over scanning: abort any in-flight plugin scan so the
     // approved post takes the browser immediately instead of waiting on the lock.
     // Plugin pipeline only — never affects the plist autopilot.
@@ -2020,6 +2021,64 @@ function sapsStateDir() {
     return (process.env.SAPS_STATE_DIR ||
         path.join(process.env.HOME || os.homedir(), ".social-autoposter-mcp"));
 }
+// ---- Cross-instance "posting active" flag ----------------------------------
+// posting-active.json in the shared state dir is the CROSS-MCP-INSTANCE version
+// of the in-process `postingActive` flag. The autopilot scan and the post
+// sometimes run in the SAME MCP (the in-process flag covers that) and sometimes
+// in TWO SEPARATE MCP instances (different agent sessions each spawn their own).
+// A file every instance's scan_candidates reads makes the mutual exclusion hold
+// regardless of which topology Claude Desktop happens to use. Heartbeat'd with a
+// short TTL so a crashed poster's flag self-clears and never wedges scanning.
+const POSTING_FLAG_TTL_MS = 45_000;
+let postingFlagHeartbeat = null;
+function postingFlagPath() {
+    return path.join(sapsStateDir(), "posting-active.json");
+}
+function writePostingFlag() {
+    try {
+        fs.mkdirSync(sapsStateDir(), { recursive: true });
+        fs.writeFileSync(postingFlagPath(), JSON.stringify({ pid: process.pid, expires_at: Date.now() + POSTING_FLAG_TTL_MS }) + "\n", "utf-8");
+    }
+    catch {
+        /* best effort */
+    }
+}
+function startPostingFlagHeartbeat() {
+    writePostingFlag();
+    if (postingFlagHeartbeat)
+        return;
+    // Refresh well within the TTL so a long batch stays flagged, but a dead poster
+    // expires within POSTING_FLAG_TTL_MS.
+    postingFlagHeartbeat = setInterval(() => {
+        if (postingActive)
+            writePostingFlag();
+    }, Math.floor(POSTING_FLAG_TTL_MS / 2));
+    if (typeof postingFlagHeartbeat.unref === "function")
+        postingFlagHeartbeat.unref();
+}
+function stopPostingFlagHeartbeat() {
+    if (postingFlagHeartbeat) {
+        clearInterval(postingFlagHeartbeat);
+        postingFlagHeartbeat = null;
+    }
+    try {
+        fs.rmSync(postingFlagPath(), { force: true });
+    }
+    catch {
+        /* best effort */
+    }
+}
+// True when ANY MCP instance has a FRESH posting flag on disk. Absent or expired
+// == not posting. This is what makes a sibling instance's scan_candidates defer.
+function isPostingFlagFresh() {
+    try {
+        const j = JSON.parse(fs.readFileSync(postingFlagPath(), "utf-8"));
+        return typeof j?.expires_at === "number" && j.expires_at > Date.now();
+    }
+    catch {
+        return false;
+    }
+}
 // activity.json: a tiny "what's running right now" signal the menu bar reads to
 // show a loading spinner + label (scanning / drafting / posting / …). Written by
 // long-running tools, cleared when they finish. Best-effort; absence == idle.
@@ -2327,6 +2386,7 @@ function scheduleShellLockRelease() {
     shellLockReleaseTimer = setTimeout(() => {
         shellLockReleaseTimer = null;
         postingActive = false; // posting drained -> the autopilot may scan again
+        stopPostingFlagHeartbeat(); // clear the cross-instance flag too
         releaseShellBrowserLock();
     }, SHELL_LOCK_GRACE_MS);
 }
@@ -2573,7 +2633,7 @@ tool("scan_candidates", {
     // post are children of THIS MCP, so this in-process gate is exact — the
     // autopilot never even starts a scan to interrupt a post. Posting always wins;
     // the autopilot just re-calls and runs once the batch drains.
-    if (postingActive)
+    if (postingActive || isPostingFlagFresh())
         return scanDeferredForPost();
     // Long-poll the single in-flight scan job (see the ScanJob registry above).
     // A finished-but-unconsumed job: hand back its result and clear the slot so a

package/mcp/dist/version.json

@@ -1,4 +1,4 @@
 {
-  "version": "1.6.93",
-  "installedAt": "2026-06-23T20:32:39.303Z"
+  "version": "1.6.94",
+  "installedAt": "2026-06-24T00:11:08.740Z"
 }

package/mcp/manifest.json

@@ -2,7 +2,7 @@
   "dxt_version": "0.1",
   "name": "social-autoposter",
   "display_name": "S4L",
-  "version": "1.6.93",
+  "version": "1.6.94",
   "description": "Draft, review, approve, and autopilot X/Twitter posts. Thin desktop client over the S4L pipeline.",
   "long_description": "A guided assistant that drafts, reviews, and autopilots X/Twitter posts.\nTo get started:\n1. Click **Configure** and set every tool permission to **Always Allow**.\n2. Copy this prompt: **Set me up on S4L end to end**.\n3. Quit fully with CMD+Q, restart Claude, and paste the prompt into a new chat.",
   "author": {

package/mcp/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@m13v/social-autoposter-mcp",
-  "version": "1.6.93",
+  "version": "1.6.94",
   "private": true,
   "description": "Desktop MCP client for social-autoposter (X/Twitter rail): manual draft/review/approve loop, autopilot control, and stats. Thin wrapper over the existing pipeline scripts.",
   "license": "MIT",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "social-autoposter",
-  "version": "1.6.93",
+  "version": "1.6.94",
   "description": "Automated social posting pipeline for Reddit, X/Twitter, LinkedIn, and Moltbook. Install as a Claude Code agent skill.",
   "bin": {
     "social-autoposter": "bin/cli.js"