fix(imessage): persist echo markers before send by colmbrogan · Pull Request #88969 · openclaw/openclaw

colmbrogan · 2026-06-01T06:55:13Z

Summary

persist a short-lived iMessage echo marker before invoking the bridge send call, closing the race where Messages reflects the outbound row before post-send echo persistence finishes
keep the existing post-send durable marker with the real message id for long catchup windows
wire the pre-send echo hook through durable iMessage delivery paths and expire failed pre-send markers quickly

Real behavior proof

Behavior or issue addressed: Messages self-chat can reflect an assistant outbound reply as an inbound-looking is_from_me=false row before OpenClaw writes the post-send persisted echo marker. That lets the iMessage monitor feed the assistant its own reply and can restart the acknowledgement loop.
Real environment tested: a live macOS Messages setup using the owner's self-chat, with private local paths, phone numbers, chat ids, and message GUIDs redacted below.
Exact steps or command run after this patch: ran openclaw --version; sent a unique proof message through the live iMessage channel with openclaw message send --channel imessage --target <owner-self-chat> --message OPENCLAW-88969-PROOF-20260604T002906Z --json; waited 20 seconds; queried the local Messages SQLite database for the proof token; searched the active main session transcript for the proof token.
Evidence after fix: live send returned handledBy: core, dryRun: false, and messageId: ok; local Messages rows showed the known self-chat reflection shape with an empty is_from_me=1 companion row and an is_from_me=0 reflected row containing OPENCLAW-88969-PROOF-20260604T002906Z; the active session transcript contained the proof token only as an assistant delivery-mirror entry, not as a user/inbound iMessage prompt.
Observed result after fix: the live self-chat reflection row was not routed back to the agent as a new inbound user turn, and no acknowledgement loop or automatic assistant response was triggered by the proof token.
What was not tested: private phone number, local DB path, chat ids, and GUIDs are redacted; the broader mirror-pair refactor is not claimed; the exact public PR head was not rebuilt/restarted into the Gateway for this proof because the already-running live Gateway contained the iMessage echo fixes under local build 120691e, while CI/local checks cover the current PR branch.

Pre-fix live evidence

Before this patch, the live Messages database showed reflected outbound self-chat rows arriving before the post-send persisted echo marker was written. The representative live rows had this shape:

<row>|2026-06-01 03:48:10|0|<owner-self-chat>|<chat>|<owner-self-chat>|<guid>|'<assistant outbound text reflected as inbound-looking row>'|tel:<owner-self-chat>
<row>|2026-06-01 03:48:10|1|<owner-self-chat>|<chat>|<owner-self-chat>|<guid>|NULL|<owner-self-chat>
<row>|2026-06-01 03:48:19|0|<owner-self-chat>|<chat>|<owner-self-chat>|<guid>|'<assistant outbound text reflected as inbound-looking row>'|tel:<owner-self-chat>
<row>|2026-06-01 03:48:19|1|<owner-self-chat>|<chat>|<owner-self-chat>|<guid>|NULL|<owner-self-chat>

The matching persisted echo entries existed, but their write timestamps were later than the reflected rows, confirming the post-send-only marker was too late for this path:

{"scope":"default:imessage:<owner-self-chat>","text":"<assistant outbound text>","timestamp":"<after reflected row>"}
{"scope":"default:imessage:<owner-self-chat>","text":"<assistant outbound text>","timestamp":"<after reflected row>"}

Patched-live runtime evidence

The patched branch was then applied to the live OpenClaw installation as part of the combined iMessage fix branch:

$ openclaw --version
OpenClaw 2026.6.2 (8df0d41)

$ git -C <openclaw-checkout> status --short --branch
## local/live-imsg-88530-88969-2026-06-02

$ git -C <openclaw-checkout> log -1 --oneline
8df0d41e4e Merge remote-tracking branch 'fork/fix-imessage-presend-persisted-echo' into local/live-imsg-88530-88969-2026-06-02

The live Gateway was rebuilt from that combined branch with CI=true pnpm build, restarted, and probed successfully:

CLI version: 2026.6.2
Gateway version: 2026.6.2
Runtime: running
Connectivity probe: ok

The live recovery also confirmed the OpenClaw channel stack was functional again after restart: Telegram delivery resumed, iMessage was up, and the running Gateway was using the patched dist built from the combined branch.

Focused after-fix tests

The new regression holds the bridge send promise open and confirms the echo marker is persisted before the bridge result resolves, which is the exact timing gap observed in the live rows. Focused tests passed:

Test Files  4 passed (4)
Tests  80 passed (80)
[test] passed 1 Vitest shard in 29.85s

After the later refresh/rebase, the focused touched-test shard also passed:

extensions/imessage/src/monitor/deliver.test.ts
extensions/imessage/src/monitor/monitor-provider.echo-cache.test.ts
extensions/imessage/src/send.test.ts

3 files / 49 tests passed

oxlint on all touched iMessage files also completed with exit code 0.

What was not claimed

No private phone number, local Messages path, chat id, or message GUID is intentionally published here. No secrets are included.

This proof does not claim an additional public, unredacted live iMessage transcript. It shows the real pre-fix database race, the patched branch running in the live Gateway after rebuild/restart, and focused tests for the pre-send timing behavior.

Verification

node scripts/run-vitest.mjs extensions/imessage/src/monitor/deliver.test.ts extensions/imessage/src/monitor/monitor-provider.echo-cache.test.ts extensions/imessage/src/send.test.ts -> 3 files, 49 tests passed
CI=true pnpm oxlint extensions/imessage/src/monitor/deliver.ts extensions/imessage/src/monitor/deliver.test.ts extensions/imessage/src/monitor/monitor-provider.echo-cache.test.ts extensions/imessage/src/monitor/persisted-echo-cache.ts extensions/imessage/src/send.ts extensions/imessage/src/send.test.ts -> passed
git diff --check upstream/main...HEAD -> passed
live patched runtime verification: openclaw --version reported OpenClaw 2026.6.2 (8df0d41), Gateway reported CLI and Gateway version 2026.6.2, runtime running, and connectivity probe ok

clawsweeper · 2026-06-01T06:56:59Z

Codex review: needs real behavior proof before merge. Reviewed June 9, 2026, 12:56 AM ET / 04:56 UTC.

Summary
Review failed before ClawSweeper could summarize the requested change.

PR surface: Source +194, Tests +198. Total +392 across 13 files.

Reproducibility: unclear. The review failed before ClawSweeper could establish a reproduction path.

Review metrics: none identified.

Merge readiness
Overall: 🌊 off-meta tidepool
Proof: 🌊 off-meta tidepool
Patch quality: 🌊 off-meta tidepool
Result: rating does not apply to this item.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Risk before merge

[P1] No close action taken because the review did not complete.

Maintainer options:

Decide the mitigation before merge
Retry the Codex review after fixing the execution failure.
Pause or close
Do not merge this PR until maintainers decide whether the risk is worth taking.

Next step before merge

[P1] Review did not complete, so no work-lane recommendation was made.

Review details

Best possible solution:

Retry the Codex review after fixing the execution failure.

Do we have a high-confidence way to reproduce the issue?

Unclear. The review failed before ClawSweeper could establish a reproduction path.

Is this the best way to solve the issue?

Unclear. Retry the review first so ClawSweeper can evaluate the actual issue and fix direction.

AGENTS.md: unclear because the file could not be read completely.

Codex review notes: model gpt-5.5, reasoning high; reviewed against 6fcc9457020e.

Label changes

Label changes:

add rating: 🌊 off-meta tidepool: Overall readiness is 🌊 off-meta tidepool; proof is 🌊 off-meta tidepool and patch quality is 🌊 off-meta tidepool.
remove proof: sufficient: Current real behavior proof status is not_applicable, not sufficient.
remove P1: Current review triage priority is none.
remove rating: 🐚 platinum hermit: Current PR rating is rating: 🌊 off-meta tidepool, so this older rating label is no longer current.
remove merge-risk: 🚨 message-delivery: Current PR review selected no merge-risk labels.
remove status: 👀 ready for maintainer look: Current PR status no longer selects a status label.

Label justifications:

rating: 🌊 off-meta tidepool: Overall readiness is 🌊 off-meta tidepool; proof is 🌊 off-meta tidepool and patch quality is 🌊 off-meta tidepool.

Evidence reviewed

PR surface:

Source +194, Tests +198. Total +392 across 13 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	8	232	38	+194
Tests	5	224	26	+198
Docs	0	0	0	0
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	13	456	64	+392

What I checked:

failure reason: codex execution failed.
codex failure detail: Codex review failed for this PR with exit 1.
codex stdout: Per-item Codex failure; continuing with the rest of the shard.

Likely related people:

unknown: Codex failed before it could trace repository history. (role: review did not complete; confidence: low)

What the crustacean ranks mean

🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

colmbrogan · 2026-06-02T17:56:38Z

Rebased this PR onto current upstream/main and force-with-lease pushed a refreshed branch.

Addressed ClawSweeper's concrete test finding:

Updated extensions/imessage/src/monitor/deliver.test.ts so the chunked delivery test now proves the new timing behavior: per-chunk pre-send echo markers are recorded, post-send message-id markers are preserved, and the old risky full un-chunked pre-send marker is still not recorded.

Local verification after rebase/test refresh:

node scripts/run-vitest.mjs extensions/imessage/src/monitor/deliver.test.ts extensions/imessage/src/monitor/monitor-provider.echo-cache.test.ts extensions/imessage/src/send.test.ts: passed, 3 files / 49 tests.
pnpm oxlint extensions/imessage/src/monitor/deliver.ts extensions/imessage/src/monitor/deliver.test.ts extensions/imessage/src/monitor/monitor-provider.echo-cache.test.ts extensions/imessage/src/monitor/persisted-echo-cache.ts extensions/imessage/src/send.ts extensions/imessage/src/send.test.ts: passed.
git diff --check upstream/main...HEAD: passed.

Remaining proof note: patched-live iMessage proof still needs an operator run/restart window. I have not claimed that proof in this update.

colmbrogan · 2026-06-02T18:31:33Z

Refreshed this PR onto current upstream/main and force-with-lease pushed the rebased branch.

Local verification after refresh:

node scripts/run-vitest.mjs extensions/imessage/src/monitor/deliver.test.ts extensions/imessage/src/monitor/monitor-provider.echo-cache.test.ts extensions/imessage/src/send.test.ts: passed, 3 files / 49 tests.
CI=true pnpm oxlint extensions/imessage/src/monitor/deliver.ts extensions/imessage/src/monitor/deliver.test.ts extensions/imessage/src/monitor/monitor-provider.echo-cache.test.ts extensions/imessage/src/monitor/persisted-echo-cache.ts extensions/imessage/src/send.ts extensions/imessage/src/send.test.ts: passed.
git diff --check upstream/main...HEAD: passed.

Still not claiming patched-live iMessage proof in this update; that remains the explicit operator/live-system proof step.

colmbrogan · 2026-06-03T02:38:49Z

Updated the PR body with redacted patched-live runtime proof from the combined branch now running on the live Gateway.

Key updates:

Redacted private phone/path/chat/GUID details from the earlier proof.
Added live runtime evidence showing OpenClaw 2026.6.2 (8df0d41).
Added live Gateway evidence showing CLI and Gateway version 2026.6.2, runtime running, and connectivity probe ok.
Removed the stale claim that the patched branch had not been restarted live.

@clawsweeper re-review

clawsweeper · 2026-06-03T02:38:51Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Complete
Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
Run: https://github.com/openclaw/clawsweeper/actions/runs/26860379453
Updated: 2026-06-03T02:46:16.714Z

omarshahine · 2026-06-09T05:25:10Z

Land-ready after maintainer refresh and fixes.

Rebased/refreshed onto current origin/main
Fixed autoreview findings around slow-send pending TTL, non-reversible in-memory pre-send markers, and generic pending text matching
Local focused proof: node scripts/run-vitest.mjs extensions/imessage/src/monitor/deliver.test.ts extensions/imessage/src/monitor/monitor-provider.echo-cache.test.ts extensions/imessage/src/monitor/self-chat-dedupe.test.ts extensions/imessage/src/monitor/catchup.test.ts extensions/imessage/src/send.test.ts -> 5 files / 113 tests passed
Local lint/proof: touched-file CI=true pnpm oxlint ... passed; node scripts/run-tsgo.mjs -p test/tsconfig/tsconfig.extensions.test.json --incremental false --pretty false passed; git diff --check passed
Structured autoreview: clean, no accepted/actionable findings
GitHub CI on head 8cd9e32114885193387e68cd2a921e9a5b3e84f4: relevant checks passed; cancelled entries are superseded duplicate runs

Thanks @colmbrogan.

omarshahine · 2026-06-09T05:25:53Z

Landed via squash merge.

Head reviewed: 8cd9e32114885193387e68cd2a921e9a5b3e84f4
Merge commit: 7e3100a1202263828d9c66f68b9d2ba503a6cbe9
Local proof before merge: focused iMessage shard, touched-file oxlint, extension test typecheck probe, diff check, and structured autoreview clean
GitHub CI: current-head relevant checks passed before merge

Thanks @colmbrogan.

@colmbrogan

Persist short-lived pending iMessage echo markers before bridge sends so self-chat reflected rows cannot race ahead of post-send echo persistence. Keep monitor cache writes post-send, keep pending text out of generic echo matching, and observe skipped from-me catchup rows for self-chat dedupe.\n\nThanks @colmbrogan.

…26.6.6) (#1040) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ghcr.io/openclaw/openclaw](https://openclaw.ai) ([source](https://github.com/openclaw/openclaw)) | patch | `2026.6.5` → `2026.6.6` | --- ### Release Notes <details> <summary>openclaw/openclaw (ghcr.io/openclaw/openclaw)</summary> ### [`v2026.6.6`](https://github.com/openclaw/openclaw/blob/HEAD/CHANGELOG.md#202666) [Compare Source](openclaw/openclaw@v2026.6.5...v2026.6.6) ##### Highlights - Security boundaries are substantially tighter across transcripts, sandbox binds, host environment inheritance, MCP stdio, Codex HTTP access, native search policy, elevated sender checks, deleted-agent ACP bypasses, loopback tools, Discord moderation, and Teams group actions; exec approvals now fail closed on timeout. ([#91529](openclaw/openclaw#91529), [#91618](openclaw/openclaw#91618), [#91615](openclaw/openclaw#91615), [#91619](openclaw/openclaw#91619), [#91741](openclaw/openclaw#91741), [#91745](openclaw/openclaw#91745), [#91746](openclaw/openclaw#91746), [#91748](openclaw/openclaw#91748), [#91749](openclaw/openclaw#91749), [#91750](openclaw/openclaw#91750), [#91751](openclaw/openclaw#91751), [#91752](openclaw/openclaw#91752), [#91763](openclaw/openclaw#91763), [#89938](openclaw/openclaw#89938)) Thanks [@joshavant](https://github.com/joshavant), [@pgondhi987](https://github.com/pgondhi987), [@mmaps](https://github.com/mmaps), [@eleqtrizit](https://github.com/eleqtrizit), [@shakkernerd](https://github.com/shakkernerd), and [@drobison00](https://github.com/drobison00). - Telegram delivery is safer and more coherent: account-scoped topics route to the right agent, streamed text survives tool calls, `/compact` works on generic ingress, callback handling uses concrete APIs, draft chunking is shared, durable dispatch dedupe moved into the SDK, and unauthorized DM text stays out of cache and prompt context. ([#91189](openclaw/openclaw#91189), [#88682](openclaw/openclaw#88682), [#89588](openclaw/openclaw#89588), [#90212](openclaw/openclaw#90212), [#91876](openclaw/openclaw#91876), [#91874](openclaw/openclaw#91874), [#91904](openclaw/openclaw#91904), [#91478](openclaw/openclaw#91478), [#91915](openclaw/openclaw#91915)) Thanks [@codysai001](https://github.com/codysai001), [@alexzhu0](https://github.com/alexzhu0), [@joelnishanth](https://github.com/joelnishanth), [@snowzlm](https://github.com/snowzlm), [@obviyus](https://github.com/obviyus), and [@sallyom](https://github.com/sallyom). - iMessage recovery and delivery now cover always-on inbound restart, durable echo markers, block streaming, idle approval discovery, hardened outbound transport, and actionable inbound startup diagnostics. ([#91335](openclaw/openclaw#91335), [#91449](openclaw/openclaw#91449), [#88969](openclaw/openclaw#88969), [#88530](openclaw/openclaw#88530), [#91783](openclaw/openclaw#91783), [#91785](openclaw/openclaw#91785)) Thanks [@omarshahine](https://github.com/omarshahine), [@jmissig](https://github.com/jmissig), and [@colmbrogan](https://github.com/colmbrogan). - Browser and MCP connectivity gained existing-session CDP support, discovered WebSocket validation, default-profile `cdpUrl` handling, safer browser-output boundaries, Streamable HTTP loopback transport, corrected OAuth/SSE authorization handling, and broader schema compatibility. ([#91422](openclaw/openclaw#91422), [#89851](openclaw/openclaw#89851), [#91736](openclaw/openclaw#91736), [#91747](openclaw/openclaw#91747), [#91451](openclaw/openclaw#91451), [#80143](openclaw/openclaw#80143)) Thanks [@pgondhi987](https://github.com/pgondhi987), [@anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia), [@lifuyue](https://github.com/lifuyue), [@eleqtrizit](https://github.com/eleqtrizit), [@LiuwqGit](https://github.com/LiuwqGit), and [@HemantSudarshan](https://github.com/HemantSudarshan). - Control UI startup and first-reply latency are lower through cached model metadata, removal of the startup catalog wait, lazy slash-command loading, and first-event tracing with slow-reply diagnostics. ([#91531](openclaw/openclaw#91531), [#91538](openclaw/openclaw#91538), [#91568](openclaw/openclaw#91568), [#91583](openclaw/openclaw#91583), [#91598](openclaw/openclaw#91598)) - Provider support expands with OpenRouter OAuth onboarding and Claude Fable 5 adaptive thinking, while Codex sessions keep correct compaction ownership, local models skip guardian review, dynamic tool progress normalizes cleanly, and Gemma 4 reasoning replay is preserved. ([#91830](openclaw/openclaw#91830), [#91882](openclaw/openclaw#91882), [#91590](openclaw/openclaw#91590), [#88630](openclaw/openclaw#88630), [#88768](openclaw/openclaw#88768), [#91696](openclaw/openclaw#91696)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@joshavant](https://github.com/joshavant), [@bdjben](https://github.com/bdjben), and [@Coder-Wangyankun](https://github.com/Coder-Wangyankun). ##### Changes - CLI progress: emit Claude CLI commentary progress events and bridge inter-tool commentary into channel progress without exposing internal protocol scaffolding. ([#89834](openclaw/openclaw#89834), [#90883](openclaw/openclaw#90883)) Thanks [@anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia). - Observability: allow trusted diagnostics channels to capture tool input/output content, add first-assistant-event traces, and warn on slow initial replies. ([#91256](openclaw/openclaw#91256), [#91568](openclaw/openclaw#91568), [#91583](openclaw/openclaw#91583)) Thanks [@amknight](https://github.com/amknight). - Plugins/ClawHub: dogfood reusable package publishing, let dry runs skip publish approval, allow declared installed trusted hooks, report managed plugin version drift, and warn instead of failing on retired Skill Workshop configuration. ([#91574](openclaw/openclaw#91574), [#91591](openclaw/openclaw#91591), [#90004](openclaw/openclaw#90004), [#90927](openclaw/openclaw#90927), [#90838](openclaw/openclaw#90838)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@brokemac79](https://github.com/brokemac79), and [@lonexreb](https://github.com/lonexreb). - Memory/providers: move the local llama.cpp runtime into its provider plugin, batch embeddings across files, persist the agent model catalog cache, and keep QMD JSON search one-shot while filtering stale REM recall previews. ([#91324](openclaw/openclaw#91324), [#89138](openclaw/openclaw#89138), [#90457](openclaw/openclaw#90457), [#91837](openclaw/openclaw#91837), [#91851](openclaw/openclaw#91851)) Thanks [@osolmaz](https://github.com/osolmaz), [@mushuiyu886](https://github.com/mushuiyu886), [@ai-hpc](https://github.com/ai-hpc), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Channels/mobile: add the QQBot group mention toggle, improve iPad and iPhone control surfaces, and expose the active connection host in the TUI footer. ([#91423](openclaw/openclaw#91423), [#91557](openclaw/openclaw#91557), [#89909](openclaw/openclaw#89909)) Thanks [@cxyhhhhh](https://github.com/cxyhhhhh), [@Solvely-Colin](https://github.com/Solvely-Colin), and [@baskduf](https://github.com/baskduf). - Performance: prewarm TUI runtime plugins, deduplicate plugin auto-enable fanout, trim dense text-delta snapshots, and reuse prepared startup model metadata. ([#90782](openclaw/openclaw#90782), [#89978](openclaw/openclaw#89978), [#91580](openclaw/openclaw#91580), [#91531](openclaw/openclaw#91531)) Thanks [@RomneyDa](https://github.com/RomneyDa) and [@ai-hpc](https://github.com/ai-hpc). ##### Fixes - Agent/session recovery: drop stale approval follow-ups after session rebind, remove drained reply-queue items by identity, recover stale main and visible replies, preserve Codex context-engine compaction ownership, lower the default compaction timeout to 180 seconds while respecting explicit configuration, and keep provider-failure terminal lifecycle state correct. ([#85679](openclaw/openclaw#85679), [#91450](openclaw/openclaw#91450), [#91566](openclaw/openclaw#91566), [#91840](openclaw/openclaw#91840), [#91590](openclaw/openclaw#91590), [#91361](openclaw/openclaw#91361), [#91895](openclaw/openclaw#91895)) Thanks [@openperf](https://github.com/openperf), [@yetval](https://github.com/yetval), [@joshavant](https://github.com/joshavant), [@wangmiao0668000666](https://github.com/wangmiao0668000666), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - User-visible content boundaries: suppress Codex/Harmony protocol artifacts, neutralize browser and LanceDB memory media directives, redact transcript images, and preserve native `/compact` replies through source suppression. ([#89151](openclaw/openclaw#89151), [#91422](openclaw/openclaw#91422), [#91425](openclaw/openclaw#91425), [#91529](openclaw/openclaw#91529), [#90212](openclaw/openclaw#90212)) Thanks [@joelnishanth](https://github.com/joelnishanth), [@pgondhi987](https://github.com/pgondhi987), [@joshavant](https://github.com/joshavant), and [@snowzlm](https://github.com/snowzlm). - Channel delivery: keep WhatsApp captured replies attached to the successor controller after restart, retry Feishu rate limits, preserve Mattermost thread replies, canonicalize LINE webhook paths, restore Discord reply hydration and runtime timeout exports, and show OpenAI Realtime WebRTC assistant transcripts. ([#85823](openclaw/openclaw#85823), [#89659](openclaw/openclaw#89659), [#91684](openclaw/openclaw#91684), [#91649](openclaw/openclaw#91649), [#90263](openclaw/openclaw#90263), [#91686](openclaw/openclaw#91686), [#90426](openclaw/openclaw#90426)) Thanks [@itsuzef](https://github.com/itsuzef), [@ladygege](https://github.com/ladygege), [@jacobtomlinson](https://github.com/jacobtomlinson), [@fuller-stack-dev](https://github.com/fuller-stack-dev), and [@shushushv](https://github.com/shushushv). - Cron: cancel active task runs cleanly, preserve terminal timeout/cancel state, and recover no-deliver tool warnings instead of silently losing the outcome. ([#90666](openclaw/openclaw#90666), [#90678](openclaw/openclaw#90678)) Thanks [@ai-hpc](https://github.com/ai-hpc). - Gateway/config/auth: share the approval runtime socket token, replace arrays explicitly in `config.patch`, skip the deleted-agent guard only for valid ACP harness sessions, surface headless LaunchAgent state, verify SQLite auth migration before cleanup, and arm QMD startup maintenance. ([#87105](openclaw/openclaw#87105), [#91551](openclaw/openclaw#91551), [#91219](openclaw/openclaw#91219), [#91614](openclaw/openclaw#91614), [#91740](openclaw/openclaw#91740), [#91978](openclaw/openclaw#91978)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev) and [@scotthuang](https://github.com/scotthuang). - Providers/Codex: clarify quota errors, restore the Codex synthetic usage line, canonicalize Codex protocol assets, require API-key auth for realtime voice, normalize ACP model refs, preserve Gemma 4 `reasoning_content`, and avoid guardian review for local models. ([#91390](openclaw/openclaw#91390), [#91709](openclaw/openclaw#91709), [#91507](openclaw/openclaw#91507), [#91567](openclaw/openclaw#91567), [#88630](openclaw/openclaw#88630), [#91696](openclaw/openclaw#91696)) Thanks [@hxy91819](https://github.com/hxy91819), [@brokemac79](https://github.com/brokemac79), [@RomneyDa](https://github.com/RomneyDa), [@joshavant](https://github.com/joshavant), and [@Coder-Wangyankun](https://github.com/Coder-Wangyankun). - Updates/builds: recover package Gateway restarts after refresh failure, expose plugin convergence repair, fall back to Corepack in PATH-less pnpm environments, seed the correct Docker store packages, and keep ClawHub dry-run and publish paths reusable. ([#91581](openclaw/openclaw#91581), [#91599](openclaw/openclaw#91599), [#91547](openclaw/openclaw#91547), [#91591](openclaw/openclaw#91591)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev), [@sallyom](https://github.com/sallyom), and [@Patrick-Erichsen](https://github.com/Patrick-Erichsen). - UI: require explicit user intent before opening chat sessions and drain restored chat queues after session switches. ([#91480](openclaw/openclaw#91480)) Thanks [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Android: avoid the `dataSync` foreground-service type for persistent nodes. ([#80082](openclaw/openclaw#80082)) Thanks [@davelutztx](https://github.com/davelutztx). - Native hooks: bound relay lifetimes so abandoned native hook connections cannot linger indefinitely. ([#91550](openclaw/openclaw#91550)) Thanks [@joshavant](https://github.com/joshavant). </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.erwanleboucher.dev/eleboucher/homelab/pulls/1040

openclaw-barnacle Bot added channel: imessage Channel integration: imessage size: S triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. labels Jun 1, 2026

openclaw-barnacle Bot added proof: supplied External PR includes structured after-fix real behavior proof. and removed triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. labels Jun 1, 2026

colmbrogan force-pushed the fix-imessage-presend-persisted-echo branch from 1762504 to 25f40d7 Compare June 1, 2026 07:01

colmbrogan force-pushed the fix-imessage-presend-persisted-echo branch from 25f40d7 to 4ee6f99 Compare June 2, 2026 17:56

openclaw-barnacle Bot added size: M and removed size: S labels Jun 2, 2026

colmbrogan force-pushed the fix-imessage-presend-persisted-echo branch from 4ee6f99 to 3b136ff Compare June 2, 2026 18:31

clawsweeper Bot added rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. and removed rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. labels Jun 2, 2026

openclaw-barnacle Bot added triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. and removed proof: supplied External PR includes structured after-fix real behavior proof. labels Jun 3, 2026

colmbrogan force-pushed the fix-imessage-presend-persisted-echo branch 2 times, most recently from 340d654 to fea6ecc Compare June 4, 2026 00:10

openclaw-barnacle Bot added proof: supplied External PR includes structured after-fix real behavior proof. and removed triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. labels Jun 4, 2026

clawsweeper Bot added status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. and removed status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. labels Jun 4, 2026

colmbrogan added 2 commits June 9, 2026 04:26

fix(imessage): persist echo markers before send

0d47e29

fix(imessage): observe skipped from-me catchup rows

505fa3e

omarshahine force-pushed the fix-imessage-presend-persisted-echo branch from fea6ecc to 505fa3e Compare June 9, 2026 04:28

openclaw-barnacle Bot removed the proof: sufficient ClawSweeper judged the real behavior proof convincing. label Jun 9, 2026

omarshahine added 2 commits June 9, 2026 04:32

fix(imessage): cover slow send echo window

d3d49c8

fix(imessage): keep monitor echo cache post-send

47792a5

clawsweeper Bot added the proof: sufficient ClawSweeper judged the real behavior proof convincing. label Jun 9, 2026

fix(imessage): narrow pending echo text matches

8cd9e32

openclaw-barnacle Bot added size: L and removed size: M labels Jun 9, 2026

omarshahine self-assigned this Jun 9, 2026

omarshahine merged commit 7e3100a into openclaw:main Jun 9, 2026
172 of 177 checks passed

github-actions Bot mentioned this pull request Jun 9, 2026

📡 Upstream Digest — 2026-06-09 07:39 UTC curtismercier/openclaw-mods#1043

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(imessage): persist echo markers before send#88969

fix(imessage): persist echo markers before send#88969
omarshahine merged 5 commits into
openclaw:mainfrom
colmbrogan:fix-imessage-presend-persisted-echo

colmbrogan commented Jun 1, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented Jun 1, 2026 •

edited

Loading

Uh oh!

colmbrogan commented Jun 2, 2026

Uh oh!

colmbrogan commented Jun 2, 2026

Uh oh!

colmbrogan commented Jun 3, 2026

Uh oh!

clawsweeper Bot commented Jun 3, 2026 •

edited

Loading

Uh oh!

omarshahine commented Jun 9, 2026

Uh oh!

Uh oh!

omarshahine commented Jun 9, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

colmbrogan commented Jun 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Real behavior proof

Pre-fix live evidence

Patched-live runtime evidence

Focused after-fix tests

What was not claimed

Verification

Uh oh!

clawsweeper Bot commented Jun 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

colmbrogan commented Jun 2, 2026

Uh oh!

colmbrogan commented Jun 2, 2026

Uh oh!

colmbrogan commented Jun 3, 2026

Uh oh!

clawsweeper Bot commented Jun 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

omarshahine commented Jun 9, 2026

Uh oh!

Uh oh!

omarshahine commented Jun 9, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

colmbrogan commented Jun 1, 2026 •

edited

Loading

clawsweeper Bot commented Jun 1, 2026 •

edited

Loading

clawsweeper Bot commented Jun 3, 2026 •

edited

Loading