@m13v/s4l 1.7.4-rc.32 → 1.7.4-rc.33

package/mcp/dist/version.json

@@ -1,4 +1,4 @@
 {
-  "version": "1.7.4-rc.32",
-  "installedAt": "2026-07-13T22:36:08.709Z"
+  "version": "1.7.4-rc.33",
+  "installedAt": "2026-07-13T22:44:32.415Z"
 }

package/mcp/manifest.json

@@ -2,7 +2,7 @@
   "dxt_version": "0.1",
   "name": "social-autoposter",
   "display_name": "S4L",
-  "version": "1.7.4-rc.32",
+  "version": "1.7.4-rc.33",
   "description": "Draft, review, approve, and autopilot X/Twitter posts.",
   "long_description": "## **⚠️ The disclaimer above is generic Claude boilerplate.** Anthropic shows the same warning on every plugin regardless of what it does; any plugin has the same level of access as any app you download from the internet.\n\nS4L is an open source product developed by Mediar.ai Incorporated, a VC-backed San Francisco-based startup.\n\nTo get started:\n\n1\\. Copy this prompt: **Set me up on S4L plugin end to end**\n\n2\\. Quit with CMD+Q, reopen Claude, paste into a new chat.\n\nWhat happens next:\n\n* About every 5 minutes S4L scans X for posts that match your topics and drafts replies in your voice.\n* Drafts show up as review cards, usually the first within a few minutes. Nothing is posted automatically; you approve each one.\n* Posting autopilot stays off until you explicitly turn it on.",
   "author": {

package/mcp/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@m13v/s4l-mcp",
-  "version": "1.7.4-rc.32",
+  "version": "1.7.4-rc.33",
   "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": "@m13v/s4l",
-  "version": "1.7.4-rc.32",
+  "version": "1.7.4-rc.33",
   "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",

package/skill/lib/linkedin-backend.sh

@@ -333,25 +333,39 @@ ensure_linkedin_browser_for_backend() {
         # The occlusion/backgrounding flags matter: the window sits offscreen,
         # and without them Chrome stops laying out SPA-rendered content, so
         # every element measures 0x0 and clicks become impossible (2026-07-03).
-        # os.setsid: Chrome must escape THIS job's process group — launchd
-        # SIGKILLs a transient job's whole process group when the shell exits,
-        # and `disown` does not change the pgid, so Chrome died with every
-        # completed run and the next lane's relaunch stole the user's focus
-        # (2026-07-12; same fix as twitter-backend.sh).
-        "${S4L_PYTHON:-python3}" -c 'import os,sys
+        # Launch flags shared by both spawn paths below.
+        local _li_launch_args=(
+            --remote-debugging-port=9556
+            --user-data-dir="$HOME/.claude/browser-profiles/browser-harness-linkedin"
+            --no-first-run --no-default-browser-check
+            --disable-features=ChromeWhatsNewUI
+            --disable-backgrounding-occluded-windows
+            --disable-renderer-backgrounding
+            --disable-background-timer-throttling
+            "${_extra[@]}"
+            about:blank
+        )
+        # macOS + .app-bundled Chrome: `open -n -g` launches a NEW instance
+        # WITHOUT stealing the user's focus (a directly-exec'd Chrome always
+        # activates itself), and LaunchServices parents it outside this launchd
+        # job's process group. Same fix + rationale as twitter-backend.sh
+        # (2026-07-13). Fallback: direct exec in a new session — os.setsid so
+        # Chrome escapes the job's process group; launchd SIGKILLs a transient
+        # job's whole pgroup when the shell exits, and `disown` does not change
+        # the pgid (2026-07-12).
+        local _li_app_bundle=""
+        case "$_chrome_bin" in
+            *.app/Contents/MacOS/*) _li_app_bundle="${_chrome_bin%%/Contents/MacOS/*}" ;;
+        esac
+        if [ "$(uname -s)" = "Darwin" ] && [ -n "$_li_app_bundle" ] && [ -d "$_li_app_bundle" ]; then
+            open -n -g -a "$_li_app_bundle" --args "${_li_launch_args[@]}" >/dev/null 2>&1 || true
+        else
+            "${S4L_PYTHON:-python3}" -c 'import os,sys
 os.setsid()
 os.execv(sys.argv[1], sys.argv[1:])' \
-            "$_chrome_bin" \
-            --remote-debugging-port=9556 \
-            --user-data-dir="$HOME/.claude/browser-profiles/browser-harness-linkedin" \
-            --no-first-run --no-default-browser-check \
-            --disable-features=ChromeWhatsNewUI \
-            --disable-backgrounding-occluded-windows \
-            --disable-renderer-backgrounding \
-            --disable-background-timer-throttling \
-            "${_extra[@]}" \
-            about:blank >/dev/null 2>&1 &
-        disown
+                "$_chrome_bin" "${_li_launch_args[@]}" >/dev/null 2>&1 &
+            disown
+        fi
         for _i in 1 2 3 4 5 6 7 8 9 10 11 12; do
             curl -sf --max-time 2 -o /dev/null http://127.0.0.1:9556/json/version 2>/dev/null && break
             sleep 1

package/skill/lib/twitter-backend.sh

@@ -309,27 +309,47 @@ ensure_twitter_browser_for_backend() {
             [ -n "$_stale_pids" ] && { kill -9 $_stale_pids 2>/dev/null || true; sleep 1; }
             rm -f "$_prof_dir/SingletonLock" "$_prof_dir/SingletonSocket" "$_prof_dir/SingletonCookie" 2>/dev/null || true
         fi
-        # os.setsid: Chrome must escape THIS job's process group. The kicker is a
-        # transient launchd job, and launchd SIGKILLs the job's whole process
-        # group the moment the shell exits (no AbandonProcessGroup) — `disown`
-        # does not change the pgid, so a plainly-backgrounded Chrome died on
-        # every cycle completion and the NEXT cycle's relaunch stole the user's
-        # focus (2026-07-12 root cause; the foreground-telemetry `cause:launched`
-        # loop). A new session makes Chrome survive its launcher regardless of
-        # which lane spawned it.
-        "${S4L_PYTHON:-python3}" -c 'import os,sys
+        # Launch flags shared by both spawn paths below.
+        local _launch_args=(
+            --remote-debugging-port=9555
+            --user-data-dir="$HOME/.claude/browser-profiles/browser-harness"
+            --no-first-run --no-default-browser-check
+            --password-store=basic --use-mock-keychain
+            --disable-features=ChromeWhatsNewUI,CalculateNativeWinOcclusion
+            --disable-backgrounding-occluded-windows
+            "${_extra[@]}"
+            "${BH_LAUNCH_URL:-https://x.com}"
+        )
+        # macOS + .app-bundled Chrome: launch via `open -n -g` so the window
+        # NEVER steals the user's focus. A directly-exec'd Chrome always
+        # activates itself on launch — every legitimate relaunch (wedge heal,
+        # user quit, crash) popped a window over the user's work (the
+        # foreground-telemetry `cause:launched` events, 2026-07-13). -n forces
+        # a NEW instance (the user's personal Chrome may already be running;
+        # without -n LaunchServices would just poke it and drop our --args),
+        # -g launches WITHOUT activation. LaunchServices also parents the
+        # process outside this launchd job's process group, which independently
+        # covers the 2026-07-12 pgroup-reaping bug the setsid fallback fixes.
+        local _app_bundle=""
+        case "$_chrome_bin" in
+            *.app/Contents/MacOS/*) _app_bundle="${_chrome_bin%%/Contents/MacOS/*}" ;;
+        esac
+        if [ "$(uname -s)" = "Darwin" ] && [ -n "$_app_bundle" ] && [ -d "$_app_bundle" ]; then
+            open -n -g -a "$_app_bundle" --args "${_launch_args[@]}" >/dev/null 2>&1 || true
+        else
+            # Fallback (Linux, bare chromium binaries): direct exec in a NEW
+            # SESSION. os.setsid: Chrome must escape THIS job's process group —
+            # launchd SIGKILLs a transient job's whole process group the moment
+            # the shell exits (no AbandonProcessGroup), and `disown` does not
+            # change the pgid, so a plainly-backgrounded Chrome died on every
+            # cycle completion and the NEXT cycle's relaunch stole the user's
+            # focus (2026-07-12 root cause).
+            "${S4L_PYTHON:-python3}" -c 'import os,sys
 os.setsid()
 os.execv(sys.argv[1], sys.argv[1:])' \
-            "$_chrome_bin" \
-            --remote-debugging-port=9555 \
-            --user-data-dir="$HOME/.claude/browser-profiles/browser-harness" \
-            --no-first-run --no-default-browser-check \
-            --password-store=basic --use-mock-keychain \
-            --disable-features=ChromeWhatsNewUI,CalculateNativeWinOcclusion \
-            --disable-backgrounding-occluded-windows \
-            "${_extra[@]}" \
-            "${BH_LAUNCH_URL:-https://x.com}" >/dev/null 2>&1 &
-        disown
+                "$_chrome_bin" "${_launch_args[@]}" >/dev/null 2>&1 &
+            disown
+        fi
         for _i in 1 2 3 4 5 6 7 8 9 10 11 12; do
             curl -sf --max-time 2 -o /dev/null http://127.0.0.1:9555/json/version 2>/dev/null && break
             sleep 1