v0.8.2 — wake skip check is text-area content, not frontmost

@claudemm caught that v0.7.5's frontmost-app skip over-fired: any
time the user had Claude.app focused (just READING the room),
wakes were dropped. Result: agent looked offline.

Replaced with the precise check claudemm originally proposed —
query value of text area 1 of group 1 of window 1 via accessibility
and skip only when non-empty. Try/silent on failure so accessibility
shape mismatches don't block wakes (better to risk a rare mid-typing
garble than to silently drop every wake).

Applied to all three osascript wake scripts.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: ThinkOffApp

package.json

@@ -1,6 +1,6 @@
 {
   "name": "ide-agent-kit",
-  "version": "0.8.1",
+  "version": "0.8.2",
   "description": "Built for OpenClaw workflows \u2014 ACP session orchestration, room-triggered automation, comment polling, Discord + Moltbook + GitHub connectors, receipts, exec approvals",
   "type": "module",
   "bin": {

scripts/claudemb-wake.sh

@@ -48,16 +48,35 @@ on run argv
     set frontApp to name of first application process whose frontmost is true
   end tell
 
-  -- v0.7.5 — skip the wake when the user is already in the target app.
-  -- @claudemm observed that wakes injected mid-typing garbled
-  -- in-progress prompts (e.g. "your poller is con" + injected
-  -- "check rooms" mid-stream → "youyour poller is constancheckt
-  -- rooms..."). If Claude.app is already frontmost, the user is
-  -- actively typing and doesn't need a wake — the next time they
-  -- send a prompt, the UserPromptSubmit hook will surface the
-  -- queued /tmp messages anyway.
-  if frontApp is appName then
-    log "wake: skipped — " & appName & " already frontmost (user typing)"
+  -- v0.8.2 — skip the wake ONLY when the user is actively typing
+  -- (text already in the prompt input), not just because they have
+  -- Claude.app focused. v0.7.5 used frontmost-app as the proxy and
+  -- over-fired: skipped wake every time the user was reading the
+  -- room with Claude.app focused, making the agent look offline.
+  --
+  -- Precise check: query the actual text-area content via accessibility
+  -- and skip only when non-empty. Try/silent on failure so unknown
+  -- accessibility hierarchies don't block wakes.
+  set userIsTyping to false
+  try
+    tell application "System Events"
+      tell process appName
+        -- Walk the typical Electron / Claude.app prompt path. If the
+        -- accessibility tree shape differs, the inner gets fail and we
+        -- fall through to the wake (correct default).
+        set existingText to value of text area 1 of group 1 of window 1
+        if existingText is not "" and existingText is not missing value then
+          set userIsTyping to true
+        end if
+      end tell
+    end tell
+  on error
+    -- accessibility node not found at expected path — assume not typing,
+    -- fire the wake. Better to risk a rare mid-typing garble than to
+    -- silently drop every wake forever.
+  end try
+  if userIsTyping then
+    log "wake: skipped — user is typing in " & appName
     return
   end if
 

tools/codex_gui_nudge.sh

@@ -18,12 +18,22 @@ on run argv
   -- and tools/gemini_gui_nudge.sh). The old System Events.keystroke routes
   -- to whichever process is frontmost at execution time and silently lands
   -- in the wrong app if focus contention beats the activation delay.
-  -- v0.7.5: skip wake if the target app is already frontmost (user typing).
-  tell application "System Events"
-    set frontApp to name of first application process whose frontmost is true
-  end tell
-  if frontApp is appName then
-    log "gui_nudge: skipped — " & appName & " already frontmost (user typing)"
+  -- v0.8.2 — skip wake only when user is actively typing (text in input),
+  -- not just because target app is frontmost. v0.7.5 over-fired the skip.
+  set userIsTyping to false
+  try
+    tell application "System Events"
+      tell process appName
+        set existingText to value of text area 1 of group 1 of window 1
+        if existingText is not "" and existingText is not missing value then
+          set userIsTyping to true
+        end if
+      end tell
+    end tell
+  on error
+  end try
+  if userIsTyping then
+    log "gui_nudge: skipped — user typing in " & appName
     return
   end if
   tell application appName to activate

tools/gemini_gui_nudge.sh

@@ -22,12 +22,22 @@ on run argv
   -- landed in the user's actual foreground app with NO error logged.
   --
   -- Fix: bind the target via `tell process appName / set frontmost true`.
-  -- v0.7.5: skip wake if the target app is already frontmost (user typing).
-  tell application "System Events"
-    set frontApp to name of first application process whose frontmost is true
-  end tell
-  if frontApp is appName then
-    log "gui_nudge: skipped — " & appName & " already frontmost (user typing)"
+  -- v0.8.2 — skip wake only when user is actively typing (text in input),
+  -- not just because target app is frontmost. v0.7.5 over-fired the skip.
+  set userIsTyping to false
+  try
+    tell application "System Events"
+      tell process appName
+        set existingText to value of text area 1 of group 1 of window 1
+        if existingText is not "" and existingText is not missing value then
+          set userIsTyping to true
+        end if
+      end tell
+    end tell
+  on error
+  end try
+  if userIsTyping then
+    log "gui_nudge: skipped — user typing in " & appName
     return
   end if
   tell application appName to activate