openclaw - 💡(How to fix) Fix iMessage monitor: no per-turn watchdog for tool activity during agent silence [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#75847Fetched 2026-05-02 05:29:07
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
2
Timeline (top)
commented ×1mentioned ×1subscribed ×1

Root Cause

Root cause The monitor doesn't track tool activity per turn, so it has no signal to differentiate "silent and idle" from "silent and busy executing tools". (Also blocked on a separate issue: claude-cli backend tool_use events aren't reaching onAgentEvent — see #75846.)

Fix Action

Fix / Workaround

Workaround We've been running this as a local patch since 2026-04-30, gated on the cli-tool-bridge fix. Happy to PR.

RAW_BUFFERClick to expand / collapse

Symptom When an agent is silent past a threshold but is still running tools, the iMessage monitor sends nothing — the user has no signal that work is in progress. On longer turns this looks indistinguishable from a stalled agent.

Root cause The monitor doesn't track tool activity per turn, so it has no signal to differentiate "silent and idle" from "silent and busy executing tools". (Also blocked on a separate issue: claude-cli backend tool_use events aren't reaching onAgentEvent — see #75846.)

Suggested fix Add a per-turn watchdog inside the iMessage monitor that:

  • Tracks last-output timestamp per turn
  • If silent past a threshold AND stream:tool events have fired this turn, sends a single descriptive progress ping (e.g. "Running a script…", "Searching for X…")
  • Resets per turn so it doesn't spam

Affected dist file monitor-*.js

Workaround We've been running this as a local patch since 2026-04-30, gated on the cli-tool-bridge fix. Happy to PR.

Depends on #75846

extent analysis

TL;DR

Implement a per-turn watchdog in the iMessage monitor to track tool activity and send progress updates when an agent is silent but still executing tools.

Guidance

  • Review the suggested fix and consider adding a per-turn watchdog to the iMessage monitor to differentiate between "silent and idle" and "silent and busy executing tools" states.
  • Investigate the separate issue (#75846) blocking the claude-cli backend tool_use events from reaching onAgentEvent to ensure a comprehensive solution.
  • Verify that the stream:tool events are firing correctly for each turn to trigger the progress ping.
  • Consider applying the local patch as a temporary workaround until a permanent fix is implemented.

Example

No code snippet is provided as the issue does not contain sufficient code context.

Notes

The fix relies on resolving the separate issue (#75846) to ensure claude-cli backend tool_use events reach onAgentEvent. The local patch can be used as a temporary workaround.

Recommendation

Apply the workaround by implementing the local patch, as it has been successfully used since 2026-04-30 and is gated on the cli-tool-bridge fix.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING