Business operating system for Claude Code — 57 skills, 21 agents, smart daemon. Unified inbox (WhatsApp/Email/Slack/Telegram), autonomous PR merge, full-AWS monitoring, revenue (Stripe+RevenueCat), e-commerce (Shopify), marketing (Klaviyo/Meta/GA4), voice (Bland/ElevenLabs), APM (Datadog/NewRelic/OTEL), YOLO mode.
Shell agent-teamsai-agentai-automationanthropicautonomous-agentawsbusiness-operationsclaudeclaude-codeclaude-code-plugindevopsecommerceinbox-zeroklaviyomarketingmcpmorning-briefingpr-automationshopifyterminal
fix(security): parameterize whatsapp-bridge LaunchAgent label (F-007) (#270)
Aurora Capitald0966fc49256
diff --git a/claude-ops/CHANGELOG.md b/claude-ops/CHANGELOG.mdindex 0e11c10d..234abc20 100644--- a/claude-ops/CHANGELOG.md+++ b/claude-ops/CHANGELOG.md@@ -251,7 +251,7 @@ Seven PRs (#258, #260, #261, #256, #257, #262, #263) complete the arc from v2.4/- `bin/wacli-health` rewritten to check bridge port 8080 and launchd status.- `bin/wacli-safe` replaced with a deprecation shim.- New `bin/ops-pretool-whatsapp-bridge-health` PreToolUse hook for bridge liveness.- - New `assets/launchagents/com.<user>.whatsapp-bridge.plist` template.+ - New `assets/launchagents/com.${USER}.whatsapp-bridge.plist` template.- `scripts/whatsapp-bridge-migrate.sh`: idempotent FTS5 virtual table + contacts table migration for `messages.db`; seeds contacts from macOS Contacts.app via osascript.### Migration steps (manual, post-merge)diff --git a/claude-ops/README.md b/claude-ops/README.mdindex 2c599f54..04123b05 100644--- a/claude-ops/README.md+++ b/claude-ops/README.md@@ -127,7 +127,7 @@ Full feature parity with the legacy v1 bash script: `--gpu` reports GPU + NeuralThe background memory extractor now prefers the Claude Code OAuth token stored in macOS Keychain (`Claude Code-credentials`) over `ANTHROPIC_API_KEY`. Calls are billed against your Claude Max subscription instead of your API credit. The token is never exported to the shell environment, so parent terminal sessions stay unaffected. Falls back to `ANTHROPIC_API_KEY` (env → keychain → Doppler).### Persistent WhatsApp follower-`whatsapp-bridge` (Baileys) now manages WhatsApp connectivity via the `com.<user>.whatsapp-bridge` LaunchAgent. Previously `whatsapp-bridge-keepalive.sh` kept `whatsapp-bridge --follow` alive — that daemon has been decommissioned (see `legacy/`). Which tore down the persistent connection every 5-20 minutes. Fixed via `INITIAL_BACKFILL_DELAY=30` plus a reentrant guard against overlapping sweeps.+`whatsapp-bridge` (Baileys) now manages WhatsApp connectivity via the `com.${USER}.whatsapp-bridge` LaunchAgent. Previously `whatsapp-bridge-keepalive.sh` kept `whatsapp-bridge --follow` alive — that daemon has been decommissioned (see `legacy/`). Which tore down the persistent connection every 5-20 minutes. Fixed via `INITIAL_BACKFILL_DELAY=30` plus a reentrant guard against overlapping sweeps.### Full Plugin Feature Adoption- All 35 skills: `effort`, `maxTurns`, `disallowedTools`, `model` annotationsdiff --git a/claude-ops/assets/launchagents/com.claude-ops.whatsapp-bridge.plist b/claude-ops/assets/launchagents/com.claude-ops.whatsapp-bridge.plistindex c41d503d..8fd173de 100644--- a/claude-ops/assets/launchagents/com.claude-ops.whatsapp-bridge.plist+++ b/claude-ops/assets/launchagents/com.claude-ops.whatsapp-bridge.plist@@ -3,7 +3,7 @@<plist version="1.0"><dict><key>Label</key>- <string>com.claude-ops.whatsapp-bridge</string>+ <string>com.__USER__.whatsapp-bridge</string><key>ProgramArguments</key><array>diff --git a/claude-ops/bin/ops-autofix b/claude-ops/bin/ops-autofixindex 473f9586..91dabed7 100755--- a/claude-ops/bin/ops-autofix+++ b/claude-ops/bin/ops-autofix@@ -164,7 +164,7 @@ fix_channel_health() {BRIDGE_DB="${WHATSAPP_BRIDGE_DB:-$HOME/.local/share/whatsapp-mcp/whatsapp-bridge/store/messages.db}"RECENT=$(sqlite3 "$BRIDGE_DB" "SELECT COUNT(*) FROM messages WHERE timestamp >= datetime('now','-1 day');" 2>/dev/null || echo "0")if [ "$RECENT" = "0" ]; then- launchctl kickstart -k gui/$(id -u)/com.<user>.whatsapp-bridge 2>/dev/null || true+ launchctl kickstart -k gui/$(id -u)/com.${USER}.whatsapp-bridge 2>/dev/null || trueRECENT2=$(sqlite3 "$BRIDGE_DB" "SELECT COUNT(*) FROM messages WHERE timestamp >= datetime('now','-1 day');" 2>/dev/null || echo "0")if [ "$RECENT2" = "0" ]; thenlog_fail "bridge-health: bridge up but 0 messages in 24h (may need re-pair or sync)"diff --git a/claude-ops/bin/ops-post-update-migrate b/claude-ops/bin/ops-post-update-migrateindex 79b5384c..29584aa2 100755--- a/claude-ops/bin/ops-post-update-migrate+++ b/claude-ops/bin/ops-post-update-migrate@@ -43,13 +43,27 @@ run_migrations() {# 2. Refresh whatsapp-bridge LaunchAgent (idempotent — only writes if template changed)if [[ "$(uname -s)" == "Darwin" ]]; then- local plist_src="$PLUGIN_ROOT/scripts/assets/launchagents/com.claude-ops.whatsapp-bridge.plist"- local plist_dst="$HOME/Library/LaunchAgents/com.claude-ops.whatsapp-bridge.plist"+ local plist_dst="$HOME/Library/LaunchAgents/com.${USER}.whatsapp-bridge.plist"+ local legacy_wa_plist="$HOME/Library/LaunchAgents/com.claude-ops.whatsapp-bridge.plist"+ local legacy_user_plist="$HOME/Library/LaunchAgents/com.<user>.whatsapp-bridge.plist"+ if [[ -f "$legacy_wa_plist" && "$legacy_wa_plist" != "$plist_dst" ]]; then+ launchctl unload "$legacy_wa_plist" 2>/dev/null || true+ rm -f "$legacy_wa_plist" 2>/dev/null || true+ log " ok: removed legacy com.claude-ops whatsapp-bridge LaunchAgent"+ fi+ if [[ -f "$legacy_user_plist" && "$legacy_user_plist" != "$plist_dst" ]]; then+ launchctl unload "$legacy_user_plist" 2>/dev/null || true+ rm -f "$legacy_user_plist" 2>/dev/null || true+ log " ok: removed legacy com.user whatsapp-bridge LaunchAgent"+ fi+ local plist_src="$PLUGIN_ROOT/assets/launchagents/com.claude-ops.whatsapp-bridge.plist"if [[ -f "$plist_src" ]] && [[ ! -f "$plist_dst" || "$plist_src" -nt "$plist_dst" ]]; thenmkdir -p "$HOME/Library/LaunchAgents" 2>/dev/null || truelocal bridge_dir="${WHATSAPP_BRIDGE_HOME:-$HOME/.local/share/whatsapp-mcp/whatsapp-bridge}"sed -e "s#__BRIDGE_BINARY_PATH__#$bridge_dir/whatsapp-bridge#g" \-e "s#__BRIDGE_WORKING_DIR__#$bridge_dir#g" \+ -e "s#__HOME__#$HOME#g" \+ -e "s#__USER__#$USER#g" \"$plist_src" > "$plist_dst" 2>/dev/null && {launchctl unload "$plist_dst" 2>/dev/null || truelaunchctl load "$plist_dst" 2>/dev/null || truediff --git a/claude-ops/bin/ops-pretool-wacli-health b/claude-ops/bin/ops-pretool-wacli-healthindex 7055bb86..04ac7d83 100755--- a/claude-ops/bin/ops-pretool-wacli-health+++ b/claude-ops/bin/ops-pretool-wacli-health@@ -15,7 +15,7 @@ HEALTH_FILE="$HOME/.wacli/.health"if [[ -f "$HEALTH_FILE" ]]; thenSTATUS=$(grep "^status=" "$HEALTH_FILE" | cut -d= -f2)if [[ "$STATUS" == "needs_auth" ]] || [[ "$STATUS" == "needs_reauth" ]]; then- echo "⚠ WhatsApp bridge may not be running. Check: launchctl list com.<user>.whatsapp-bridge"+ echo "⚠ WhatsApp bridge may not be running. Check: launchctl list com.${USER}.whatsapp-bridge"# Don't block — just warn. The skill's own health check will handle it.fifidiff --git a/claude-ops/bin/ops-pretool-whatsapp-bridge-health b/claude-ops/bin/ops-pretool-whatsapp-bridge-healthindex 0e9f11e5..a4010893 100755--- a/claude-ops/bin/ops-pretool-whatsapp-bridge-health+++ b/claude-ops/bin/ops-pretool-whatsapp-bridge-health@@ -12,13 +12,13 @@ fi# Check bridge is listening on port 8080if ! lsof -i :8080 2>/dev/null | grep -q LISTEN; then- echo "⚠ WhatsApp bridge not running on :8080. Restart: launchctl kickstart -k gui/$(id -u)/com.<user>.whatsapp-bridge"+ echo "⚠ WhatsApp bridge not running on :8080. Restart: launchctl kickstart -k gui/$(id -u)/com.${USER}.whatsapp-bridge"# Don't block — just warn. The skill's own health check will handle it.fi# Check launchd registration-if ! launchctl list com.<user>.whatsapp-bridge 2>/dev/null | grep -q '"PID"'; then- echo "⚠ com.<user>.whatsapp-bridge not active in launchd. Check: launchctl list com.<user>.whatsapp-bridge"+if ! launchctl list "com.${USER}.whatsapp-bridge" 2>/dev/null | grep -q '"PID"'; then+ echo "⚠ com.${USER}.whatsapp-bridge not active in launchd. Check: launchctl list com.${USER}.whatsapp-bridge"fiexit 0diff --git a/claude-ops/bin/ops-unread b/claude-ops/bin/ops-unreadindex fe83544e..69b4643d 100755--- a/claude-ops/bin/ops-unread+++ b/claude-ops/bin/ops-unread@@ -31,7 +31,10 @@ if [[ $BRIDGE_RUNNING -eq 1 ]] && [[ -f "$BRIDGE_DB" ]]; then--argjson c "$WA_RECENT" \'.channels.whatsapp = {"recent_chats": $c, "connected": true, "available": true}')elif [[ $BRIDGE_RUNNING -eq 0 ]]; then- RESULT=$(echo "$RESULT" | jq '.channels.whatsapp = {"unread": 0, "available": false, "note": "whatsapp-bridge not running — restart: launchctl kickstart -k gui/$UID/com.<user>.whatsapp-bridge"}')+ RESULT=$(echo "$RESULT" | jq \+ --arg uid "${UID:-}" \+ --arg user "${USER:-}" \+ '.channels.whatsapp = {"unread": 0, "available": false, "note": ("whatsapp-bridge not running — restart: launchctl kickstart -k gui/" + $uid + "/com." + $user + ".whatsapp-bridge")}')elseRESULT=$(echo "$RESULT" | jq '.channels.whatsapp = {"unread": 0, "available": false, "note": "whatsapp-bridge DB not found — run scripts/whatsapp-bridge-migrate.sh"}')fidiff --git a/claude-ops/bin/wacli-health b/claude-ops/bin/wacli-healthindex 83949e33..3ec8b70d 100755--- a/claude-ops/bin/wacli-health+++ b/claude-ops/bin/wacli-health@@ -22,9 +22,9 @@ fi# Check launchd registrationif [[ "$(uname -s)" == "Darwin" ]]; then- if ! launchctl list 2>/dev/null | grep -q "com.<user>.whatsapp-bridge"; then+ if ! launchctl list 2>/dev/null | grep -q "com.${USER}.whatsapp-bridge"; thenhealthy=0- issues+=("com.<user>.whatsapp-bridge not registered in launchd")+ issues+=("com.${USER}.whatsapp-bridge not registered in launchd")fifi@@ -53,7 +53,7 @@ elsefor i in "${issues[@]+"${issues[@]}"}"; doecho " - $i"done- echo "Restart: launchctl kickstart -k gui/$(id -u)/com.<user>.whatsapp-bridge"+ echo "Restart: launchctl kickstart -k gui/$(id -u)/com.${USER}.whatsapp-bridge"fifidiff --git a/claude-ops/scripts/daemon-services.default.json b/claude-ops/scripts/daemon-services.default.jsonindex d34a1313..5582dce5 100644--- a/claude-ops/scripts/daemon-services.default.json+++ b/claude-ops/scripts/daemon-services.default.json@@ -8,7 +8,7 @@},"whatsapp-bridge": {"enabled": true,- "command": "launchctl kickstart -k gui/$UID/com.<user>.whatsapp-bridge",+ "command": "launchctl kickstart -k gui/$UID/com.${USER}.whatsapp-bridge","health_check": "lsof -i :8080 | grep LISTEN","restart_delay": 60,"max_restarts": 10diff --git a/claude-ops/scripts/daemon-services.example.json b/claude-ops/scripts/daemon-services.example.jsonindex 3895e1d0..594e3a5e 100644--- a/claude-ops/scripts/daemon-services.example.json+++ b/claude-ops/scripts/daemon-services.example.json@@ -7,7 +7,7 @@"services": {"whatsapp-bridge": {"enabled": true,- "command": "launchctl kickstart -k gui/$UID/com.<user>.whatsapp-bridge",+ "command": "launchctl kickstart -k gui/$UID/com.${USER}.whatsapp-bridge","health_check": "lsof -i :8080 | grep LISTEN","restart_delay": 60,"max_restarts": 10@@ -48,7 +48,7 @@"health_file": "~/.claude/plugins/data/ops-ops-marketplace/listener-health.txt","restart_delay": 30,"max_restarts": 20,- "_note": "Requires: whatsapp-bridge running (com.<user>.whatsapp-bridge LaunchAgent). Optional: TELEGRAM_BOT_TOKEN, TELEGRAM_OWNER_ID."+ "_note": "Requires: whatsapp-bridge running (com.${USER}.whatsapp-bridge LaunchAgent). Optional: TELEGRAM_BOT_TOKEN, TELEGRAM_OWNER_ID."},"memory-extractor": {"enabled": false,diff --git a/claude-ops/scripts/ops-daemon.sh b/claude-ops/scripts/ops-daemon.shindex aeea0757..a3a11d7c 100755--- a/claude-ops/scripts/ops-daemon.sh+++ b/claude-ops/scripts/ops-daemon.sh@@ -1400,7 +1400,7 @@ ENSURE_SERVICES_INTERVAL="${ENSURE_SERVICES_INTERVAL:-300}" # every 5 min# stderr/stdout, just rapid START log entries).## wacli-keepalive was decommissioned in v2.0.3 — WhatsApp ops moved to the-# Baileys bridge (com.<user>.whatsapp-bridge) and mcp__whatsapp__* tools.+# Baileys bridge (com.${USER}.whatsapp-bridge) and mcp__whatsapp__* tools.# Including it caused noisy "cannot repair — missing bash or source plist"# entries every monitor loop because its plist no longer ships in the package.EXPECTED_SERVICES=()diff --git a/claude-ops/skills/ops-comms/SKILL.md b/claude-ops/skills/ops-comms/SKILL.mdindex 8c661db2..20483878 100644--- a/claude-ops/skills/ops-comms/SKILL.md+++ b/claude-ops/skills/ops-comms/SKILL.md@@ -37,7 +37,7 @@ Before executing, load available context:1. **Daemon health**: Read `${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/daemon-health.json`- Check bridge liveness before any WhatsApp operation: `lsof -i :8080 | grep LISTEN`- - If bridge not running, prompt user to restart: `launchctl kickstart -k gui/$UID/com.<user>.whatsapp-bridge`+ - If bridge not running, prompt user to restart: `launchctl kickstart -k gui/$UID/com.${USER}.whatsapp-bridge`2. **Ops memories**: Before drafting any message, check `${CLAUDE_PLUGIN_DATA_DIR}/memories/`:- `contact_*.md` — load profile for the recipient@@ -53,9 +53,9 @@ Before executing, load available context:**Bridge health** — check bridge is running before any WhatsApp operation:```bashlsof -i :8080 | grep LISTEN-launchctl list com.<user>.whatsapp-bridge+launchctl list com.${USER}.whatsapp-bridge```-If not running: `launchctl kickstart -k gui/$(id -u)/com.<user>.whatsapp-bridge`+If not running: `launchctl kickstart -k gui/$(id -u)/com.${USER}.whatsapp-bridge`| Tool | Params | Output ||------|--------|--------|@@ -131,7 +131,7 @@ If user picks "Edit message", use `AskUserQuestion` with free-text to get the re**Never send a reply based on a single message.** A message like "can you pull it from Klaviyo?" means nothing without knowing what "it" refers to from prior messages.-**Pre-flight:** Check bridge is running: `lsof -i :8080 | grep LISTEN`. If not running, restart: `launchctl kickstart -k gui/$(id -u)/com.<user>.whatsapp-bridge` and wait 5s.+**Pre-flight:** Check bridge is running: `lsof -i :8080 | grep LISTEN`. If not running, restart: `launchctl kickstart -k gui/$(id -u)/com.${USER}.whatsapp-bridge` and wait 5s.```mcp__whatsapp__send_message {recipient: "[contact_jid]", message: "[message]"}diff --git a/claude-ops/skills/ops-dash/SKILL.md b/claude-ops/skills/ops-dash/SKILL.mdindex f7903b03..82f786fd 100644--- a/claude-ops/skills/ops-dash/SKILL.md+++ b/claude-ops/skills/ops-dash/SKILL.md@@ -313,7 +313,7 @@ When user selects `h`:| 5 | Command reference | List all `/ops:*` commands with descriptions || 6 | Shortcuts | `1-9, 0` for actions, `a-h` for power/comms/settings, `b` always goes back, `q` exits || 7 | MCP disconnected | Wait 5s and retry (auto-reconnect hook). After 3 fails, falls back to CLI tools. |-| 8 | WhatsApp | Check bridge liveness: `lsof -i :8080 | grep LISTEN`. If not running, prompt restart: `launchctl kickstart -k gui/$(id -u)/com.<user>.whatsapp-bridge`. Check `launchctl list com.<user>.whatsapp-bridge` for status. If store locked: `kill $(pgrep whatsapp-bridge)`. |+| 8 | WhatsApp | Check bridge liveness: `lsof -i :8080 | grep LISTEN`. If not running, prompt restart: `launchctl kickstart -k gui/$(id -u)/com.${USER}.whatsapp-bridge`. Check `launchctl list com.${USER}.whatsapp-bridge` for status. If store locked: `kill $(pgrep whatsapp-bridge)`. || 9 | Telegram | Needs user-auth (not bot). Run `/ops:setup` → Telegram section. API ID + hash from my.telegram.org. || 10 | Unread | Channel must be configured in `/ops:setup`. Check `ops-unread` script output for errors. |diff --git a/claude-ops/skills/ops-go/SKILL.md b/claude-ops/skills/ops-go/SKILL.mdindex f1121792..606123a1 100644--- a/claude-ops/skills/ops-go/SKILL.md+++ b/claude-ops/skills/ops-go/SKILL.md@@ -53,7 +53,7 @@ Before executing, load available context:**Bridge health** — check before any WhatsApp operation:- Running: `lsof -i :8080 | grep LISTEN` → proceed-- Not running → `launchctl kickstart -k gui/$(id -u)/com.<user>.whatsapp-bridge`, wait 5s+- Not running → `launchctl kickstart -k gui/$(id -u)/com.${USER}.whatsapp-bridge`, wait 5s| Tool | Params | Output ||------|--------|--------|diff --git a/claude-ops/skills/ops-inbox/CHANNELS.md b/claude-ops/skills/ops-inbox/CHANNELS.mdindex b5988af1..fb8e47db 100644--- a/claude-ops/skills/ops-inbox/CHANNELS.md+++ b/claude-ops/skills/ops-inbox/CHANNELS.md@@ -6,20 +6,21 @@ This document explains how to configure each communication channel for the `/ops**Status:** MCP-based via `mcp__whatsapp__*` tools. No CLI needed.-The Baileys `whatsapp-bridge` binary runs as a persistent LaunchAgent (`com.<user>.whatsapp-bridge`)+The Baileys `whatsapp-bridge` binary runs as a persistent LaunchAgent (`com.${USER}.whatsapp-bridge`)and exposes WhatsApp over a local HTTP/MCP interface on port 8080.### Setup1. Ensure the bridge binary is installed at `~/.local/share/whatsapp-mcp/whatsapp-bridge/whatsapp-bridge`-2. Install the LaunchAgent plist from `assets/launchagents/com.<user>.whatsapp-bridge.plist`:+2. Install the LaunchAgent plist from the template at `assets/launchagents/com.claude-ops.whatsapp-bridge.plist`. The installed plist's Label is parameterized per-user via `${USER}` so each macOS user gets their own bridge:```bash- PLIST="$HOME/Library/LaunchAgents/com.<user>.whatsapp-bridge.plist"+ PLIST="$HOME/Library/LaunchAgents/com.${USER}.whatsapp-bridge.plist"BRIDGE_DIR="$HOME/.local/share/whatsapp-mcp/whatsapp-bridge"sed -e "s|__BRIDGE_BINARY_PATH__|$BRIDGE_DIR/whatsapp-bridge|g" \-e "s|__BRIDGE_WORKING_DIR__|$BRIDGE_DIR|g" \-e "s|__HOME__|$HOME|g" \- "${CLAUDE_PLUGIN_ROOT}/assets/launchagents/com.<user>.whatsapp-bridge.plist" > "$PLIST"+ -e "s|__USER__|$USER|g" \+ "${CLAUDE_PLUGIN_ROOT}/assets/launchagents/com.claude-ops.whatsapp-bridge.plist" > "$PLIST"launchctl bootstrap gui/$(id -u) "$PLIST"```3. On first run the bridge prints a QR code to its log — scan from WhatsApp → Linked Devices.@@ -29,13 +30,13 @@ and exposes WhatsApp over a local HTTP/MCP interface on port 8080.```bashlsof -i :8080 | grep LISTEN # bridge running?-launchctl list com.<user>.whatsapp-bridge # launchd status+launchctl list com.${USER}.whatsapp-bridge # launchd statuscat ~/.local/share/whatsapp-mcp/whatsapp-bridge/logs/bridge.err.log | tail -20```### Troubleshooting-- `bridge not running`: `launchctl kickstart -k gui/$(id -u)/com.<user>.whatsapp-bridge`+- `bridge not running`: `launchctl kickstart -k gui/$(id -u)/com.${USER}.whatsapp-bridge`- Auth expired: check `bridge.err.log` for QR prompt; session stored in `whatsapp.db`- Missing messages: restart bridge (re-syncs history on connect)- FTS search slow: run `scripts/whatsapp-bridge-migrate.sh` to add FTS5 indexdiff --git a/claude-ops/skills/ops-inbox/SKILL.md b/claude-ops/skills/ops-inbox/SKILL.mdindex acc753a9..862e0550 100644--- a/claude-ops/skills/ops-inbox/SKILL.md+++ b/claude-ops/skills/ops-inbox/SKILL.md@@ -64,7 +64,7 @@ If you find yourself reaching for any `wacli ...` shell command, stop and use th| Full-text search | `mcp__whatsapp__list_messages {query: "<text>", limit: 20}` | `wacli messages search` || Resolve a contact | `mcp__whatsapp__search_contacts {query: "<name>"}` | `wacli contacts` || Send a reply (after approval) | `mcp__whatsapp__send_message {recipient: "<JID>", message: "<text>"}` | `wacli send` |-| Health check | `lsof -i :8080 \| grep LISTEN` + `launchctl list com.<user>.whatsapp-bridge` | `wacli doctor` / `~/.wacli/.health` |+| Health check | `lsof -i :8080 \| grep LISTEN` + `launchctl list com.${USER}.whatsapp-bridge` | `wacli doctor` / `~/.wacli/.health` |**Rationale:** the bridge exposes a typed MCP surface, returns consistent JSON shapes (`is_from_me`, `content`, `timestamp`, `sender`), supports FTS5 search natively, and avoids store-lock contention with the wacli keepalive daemon. Mixing the two surfaces caused inconsistent state in past sessions.@@ -79,7 +79,7 @@ Before executing, load available context:- `secrets_manager` / `doppler` — how to resolve channel credentials if not in env2. **Daemon health**: Read `${CLAUDE_PLUGIN_DATA_DIR}/daemon-health.json`- - Check `whatsapp-bridge` status — verify `com.<user>.whatsapp-bridge` is running (`lsof -i :8080` or `launchctl list com.<user>.whatsapp-bridge`)+ - Check `whatsapp-bridge` status — verify `com.${USER}.whatsapp-bridge` is running (`lsof -i :8080` or `launchctl list com.${USER}.whatsapp-bridge`)- If bridge is not running, surface the issue before WhatsApp operations3. **Ops memories**: Check `${CLAUDE_PLUGIN_DATA_DIR}/memories/` before drafting any reply:@@ -95,9 +95,9 @@ Before executing, load available context:**Bridge health** — check bridge is running before any WhatsApp operation:```bashlsof -i :8080 | grep LISTEN # bridge listens on :8080-launchctl list com.<user>.whatsapp-bridge # check launchd status+launchctl list com.${USER}.whatsapp-bridge # check launchd status```-If bridge is not running: `launchctl kickstart -k gui/$UID/com.<user>.whatsapp-bridge`+If bridge is not running: `launchctl kickstart -k gui/$UID/com.${USER}.whatsapp-bridge`**MCP tools** (use these instead of any wacli CLI command):@@ -136,7 +136,7 @@ sqlite3 "$DB" "SELECT jid, name, phone FROM contacts WHERE name LIKE '%<name>%'**History backfill** — the whatsmeow bridge automatically syncs history on connection. No manual backfill command exists; if messages are missing, restart the bridge:```bash-launchctl kickstart -k gui/$UID/com.<user>.whatsapp-bridge+launchctl kickstart -k gui/$UID/com.${USER}.whatsapp-bridge```### gog CLI (Gmail/Calendar)@@ -260,7 +260,7 @@ The user does NOT remember every thread. For EVERY message you present, you MUSTFor each channel, detect availability at runtime:1. **Email**: Try `gog` CLI first. If `gog` unavailable, try `mcp__gog__gmail_*` MCP tools. If neither, report unavailable.-2. **WhatsApp**: Check bridge liveness: `lsof -i :8080 | grep LISTEN`. If not listening, prompt the user: "WhatsApp bridge is not running." Use `AskUserQuestion`: `[Restart bridge]`, `[Skip WhatsApp]`. On restart: `launchctl kickstart -k gui/$(id -u)/com.<user>.whatsapp-bridge`, wait 5s, re-check. If bridge is running but MCP tools fail, the bridge may need QR re-pairing — check `~/.local/share/whatsapp-mcp/whatsapp-bridge/logs/bridge.err.log` for auth errors.+2. **WhatsApp**: Check bridge liveness: `lsof -i :8080 | grep LISTEN`. If not listening, prompt the user: "WhatsApp bridge is not running." Use `AskUserQuestion`: `[Restart bridge]`, `[Skip WhatsApp]`. On restart: `launchctl kickstart -k gui/$(id -u)/com.${USER}.whatsapp-bridge`, wait 5s, re-check. If bridge is running but MCP tools fail, the bridge may need QR re-pairing — check `~/.local/share/whatsapp-mcp/whatsapp-bridge/logs/bridge.err.log` for auth errors.3. **Slack**: Read the derived `channels.slack` object from pre-gathered `bin/ops-unread` data (it resolves each `token_env` and reports per-workspace `available`; do NOT read raw `preferences.json → slack_workspaces[]` directly — that array has no `available` flag).- **Multi-workspace** (`"multi_workspace": true`): iterate the `workspaces` array. For each `available: true` entry, scan via `mcp__claude_ai_Slack__*` if the MCP token matches, or via direct curl. To resolve the token for direct curl, validate `token_env` matches `^[A-Za-z_][A-Za-z0-9_]*$` before `${!token_env}` indirect expansion. Aggregate results; label each message block with the workspace name.- **Legacy** (`"multi_workspace": false`): use `mcp__claude_ai_Slack__*` if `channels.slack.available == true` (which itself reflects `SLACK_MCP_ENABLED`).@@ -395,11 +395,11 @@ Reply via: `mcp__whatsapp__send_message` with `{recipient: "<JID>", message: "<m| Chat metadata | `mcp__whatsapp__get_chat {chat_jid}` || Message context | `mcp__whatsapp__get_message_context {chat_jid, message_id}` || Check bridge | `lsof -i :8080 | grep LISTEN` |-| Restart bridge | `launchctl kickstart -k gui/$(id -u)/com.<user>.whatsapp-bridge` |+| Restart bridge | `launchctl kickstart -k gui/$(id -u)/com.${USER}.whatsapp-bridge` |**Bridge troubleshooting:**-- Bridge not running → `launchctl kickstart -k gui/$(id -u)/com.<user>.whatsapp-bridge`; wait 5s, re-check+- Bridge not running → `launchctl kickstart -k gui/$(id -u)/com.${USER}.whatsapp-bridge`; wait 5s, re-check- Auth expired / QR needed → check `~/.local/share/whatsapp-mcp/whatsapp-bridge/logs/bridge.err.log`; bridge prints QR to log on startup if session is invalid- Missing messages → bridge syncs history on connect; if gap persists, restart bridge- FTS not available → run `scripts/whatsapp-bridge-migrate.sh` to add FTS5 index to messages.dbdiff --git a/claude-ops/skills/setup/SKILL.md b/claude-ops/skills/setup/SKILL.mdindex 9d2b1e09..d3018293 100644--- a/claude-ops/skills/setup/SKILL.md+++ b/claude-ops/skills/setup/SKILL.md@@ -1034,7 +1034,7 @@ echo "Services to enable: $SERVICES"Write daemon services config to `$DATA_DIR/daemon-services.json` — merge with the existing config from Step 2c, preserving `briefing-pre-warm` and `memory-extractor`, and enabling the new channel-dependent services. **Every service MUST include a `command` field** — the daemon's `start_service()` skips any service without one. Use `${CLAUDE_PLUGIN_ROOT}` (resolved at runtime) for script paths. Each service entry should include:- `briefing-pre-warm`: `{ "enabled": true, "command": "${CLAUDE_PLUGIN_ROOT}/bin/ops-gather", "cron": "*/2 * * * *" }` — pre-warms /ops:go cache (installed in 2c)-- `whatsapp-bridge`: `{ "enabled": true, "command": "launchctl kickstart -k gui/$UID/com.<user>.whatsapp-bridge", "health_check": "lsof -i :8080 | grep LISTEN", "restart_delay": 60, "max_restarts": 10 }` — only if WhatsApp configured (matches `daemon-services.default.json`; bridge is owned by LaunchAgent, not a plugin script)+- `whatsapp-bridge`: `{ "enabled": true, "command": "launchctl kickstart -k gui/$UID/com.${USER}.whatsapp-bridge", "health_check": "lsof -i :8080 | grep LISTEN", "restart_delay": 60, "max_restarts": 10 }` — only if WhatsApp configured (matches `daemon-services.default.json`; bridge is owned by LaunchAgent, not a plugin script)- `memory-extractor`: `{ "enabled": true, "command": "${CLAUDE_PLUGIN_ROOT}/scripts/ops-memory-extractor.sh", "health_file": "~/.claude/plugins/data/ops-ops-marketplace/memories/.health", "cron": "*/30 * * * *" }` — every 30 min (installed in 2c)- `inbox-digest`: `{ "enabled": true, "command": "${CLAUDE_PLUGIN_ROOT}/scripts/ops-cron-inbox-digest.sh", "cron": "0 */4 * * *" }` — every 4h- `store-health`: `{ "enabled": true, "command": "${CLAUDE_PLUGIN_ROOT}/scripts/ops-cron-store-health.sh", "cron": "0 9 * * *" }` — daily 9am, only if ecom configureddiff --git a/claude-ops/skills/setup/channels/whatsapp.md b/claude-ops/skills/setup/channels/whatsapp.mdindex 0708cc25..247f3094 100644--- a/claude-ops/skills/setup/channels/whatsapp.md+++ b/claude-ops/skills/setup/channels/whatsapp.md@@ -1,6 +1,6 @@### 3b — WhatsApp (bridge health + QR pair)-WhatsApp is handled exclusively by the whatsmeow `whatsapp-bridge` (managed by `com.<user>.whatsapp-bridge` LaunchAgent) and accessed via `mcp__whatsapp__*` tools.+WhatsApp is handled exclusively by the whatsmeow `whatsapp-bridge` (managed by `com.${USER}.whatsapp-bridge` LaunchAgent — `${USER}` is your macOS username, expanded at install time so each user gets their own per-account bridge) and accessed via `mcp__whatsapp__*` tools.#### Step 3b.1 — Presence@@ -8,7 +8,7 @@ Check bridge binary exists and LaunchAgent is installed:```bashls ~/.local/share/whatsapp-mcp/whatsapp-bridge/whatsapp-bridge 2>/dev/null && echo "binary ok"-launchctl list com.<user>.whatsapp-bridge 2>/dev/null | head -3+launchctl list com.${USER}.whatsapp-bridge 2>/dev/null | head -3lsof -i :8080 2>/dev/null | grep LISTEN```@@ -21,15 +21,16 @@ whatsapp-bridge (whatsmeow) is not installed. Install:mkdir -p ~/.local/share/whatsapp-mcp/whatsapp-bridge/logs```-If LaunchAgent not installed, install it from template:+If LaunchAgent not installed, install it from template. The template ships as `com.claude-ops.whatsapp-bridge.plist` with a `__USER__` Label placeholder; sed substitutes the running user so the installed plist's Label becomes `com.${USER}.whatsapp-bridge`:```bash-PLIST_TEMPLATE="${CLAUDE_PLUGIN_ROOT}/assets/launchagents/com.<user>.whatsapp-bridge.plist"-PLIST_DEST="$HOME/Library/LaunchAgents/com.<user>.whatsapp-bridge.plist"+PLIST_TEMPLATE="${CLAUDE_PLUGIN_ROOT}/assets/launchagents/com.claude-ops.whatsapp-bridge.plist"+PLIST_DEST="$HOME/Library/LaunchAgents/com.${USER}.whatsapp-bridge.plist"BRIDGE_DIR="$HOME/.local/share/whatsapp-mcp/whatsapp-bridge"mkdir -p "$BRIDGE_DIR/logs"sed -e "s|__BRIDGE_BINARY_PATH__|$BRIDGE_DIR/whatsapp-bridge|g" \-e "s|__BRIDGE_WORKING_DIR__|$BRIDGE_DIR|g" \-e "s|__HOME__|$HOME|g" \+ -e "s|__USER__|$USER|g" \"$PLIST_TEMPLATE" > "$PLIST_DEST"launchctl bootstrap gui/$(id -u) "$PLIST_DEST"```@@ -87,7 +88,7 @@ All ops skills that use WhatsApp must check `lsof -i :8080 | grep LISTEN` beforeIf bridge is not running:1. Print: "WhatsApp bridge is not running."2. Use `AskUserQuestion`: `[Restart bridge]`, `[Skip WhatsApp]`.-3. On restart: `launchctl kickstart -k gui/$(id -u)/com.<user>.whatsapp-bridge`, wait 5s.+3. On restart: `launchctl kickstart -k gui/$(id -u)/com.${USER}.whatsapp-bridge`, wait 5s.> **Deep-dive:** see `${CLAUDE_PLUGIN_ROOT}/skills/ops-comms/SKILL.md` and `${CLAUDE_PLUGIN_ROOT}/skills/ops-inbox/SKILL.md` for full operational instructions.