OpenClaw repairs three ways delivery can lie

openclaw/openclaw PR #117697 is the inspected primary source: “fix(whatsapp): preserve source direction for automatic reactions.” The two related records below were inspected as supporting context, not treated as independent confirmation.

The facts

- openclaw/openclaw PR #117697 was created 2026-08-01T23:45:23Z and was open at inspection; its title is “fix(whatsapp): preserve source direction for automatic reactions.” - openclaw/openclaw PR #117711 was created 2026-08-02T00:18:57Z and was open at inspection; its title is “fix: Matrix and Telegram cannot send workspace-relative attachments.” - openclaw/openclaw PR #104223 was created 2026-07-11T06:18:57Z and was open at inspection; its title is “fix(tasks): deliver corrected terminal outcomes.” - The repository reported 384852 stars, 5655 open issues, default branch main, and last push 2026-08-02T00:59:43Z. - The latest tagged-release baseline checked was v2026.7.2-beta.6 published 2026-08-01T05:34:32Z.

What changed

openclaw/openclaw PR #117697 reports: Summary Fixes https://github.com/openclaw/openclaw/issues/117672. Automatic WhatsApp reactions now preserve the normalized inbound message direction when constructing the target key. This makes acknowledgement and status reactions address self-authored messages correctly when the bot is linked to the operator's own account. Scope Keep existing acknowledgement scope, reaction-level, and participant-resolution policy unchanged. Cover acknowledgement send/removal and status set/clear with platform.fromMe: true. Retain an explicit platform.fromMe: false control path. Validation Focused ack-reaction monitor test. Focused status-reaction monitor test. pnpm check:changed and git diff --check before handoff. Credit Thanks @lpulcheri for the report and root-cause analysis in https://github.com/openclaw/openclaw/issues/117672.

openclaw/openclaw PR #117711 reports: What Problem This Solves Fixes an issue where users sending an image or other workspace-relative attachment through Matrix or Telegram would receive a missing-file error or lose the attachment when a direct Gateway send or message-tool action crossed a channel-owned send boundary. Why This Change Was Made Preserve the original host-authorized media-access capability through Matrix and Telegram direct, structured-payload, and message-action owners. Gateway message actions now derive the agent workspace while retaining existing approved roots; they deliberately never expose a host file-reader callback, never trust request-supplied sender identity, and leave unrelated actions unchanged. Adds one reusable real-channel QA scenario for both Gateway entry points. User

openclaw/openclaw PR #104223 reports: What Problem This Solves Fixes an issue where an older terminal notification could finish sending after a task had acquired a newer terminal outcome and then mark that newer outcome as already delivered. Users could receive the stale success/cancellation message while the corrected failure or summary was permanently suppressed. Why This Change Was Made Terminal delivery now uses one canonical projection containing the owner, route, rendered payload, delivery capability, and an idempotency key fingerprinted from the actual destination and content. The registry revalidates that projection before sending, after a successful send, and before fallback. If a newer generation replaces an in-flight notification, the old completion

Why it matters

Delivery is not complete because an API call returned. Direction, destination, payload generation and filesystem authority must survive until the final receipt, or a green send can still tell the user the wrong thing. This is an operator boundary: persisted state, execution ownership and visible controls must describe the same event. A workaround that broadens access, deletes state or hides the symptom would trade a visible defect for an unmeasured one.

Current

The primary record was open when captured on 2026-08-02. The release baseline was v2026.7.2-beta.6 published 2026-08-01T05:34:32Z. Current repository metadata, pull requests, issues, release records, Google News discovery, Hacker News discovery, Lobsters, Metamesh and the rendered ClawCharts row were checked. ClawCharts selected the subject; it did not prove the claim.

Evidence

The primary URL is https://github.com/openclaw/openclaw/pull/117697. Supporting records are https://github.com/openclaw/openclaw/pull/117711 and https://github.com/openclaw/openclaw/pull/104223. Their source bodies, timestamps and states were captured in the daily evidence bundle. Test counts, reproductions and deployment observations remain attributed to their authors unless explicitly identified as independently rerun.

Source boundary

Open work is described as open, closed work as closed, and operator reports as reports. A pull request is evidence of proposed or reviewed direction, not proof of a shipped release. Issue closure would not by itself prove a deployed fix. Search residue, package mirrors and historically published source spines were excluded.

Operator take

Test corrections while an older send is in flight, preserve approved media roots without trusting request-supplied identity, and verify visible delivery exactly once on each real channel boundary. Preserve a before-state receipt, make the smallest reversible change, and verify the original failure independently after intervention.

Caveat

Public project records are mutable. Status, scope and evidence can change after publication. This brief records the inspected state and does not authorize changes to a reader’s deployment.

Source inspected; source state, environment and release boundary remain explicit.