fix(auto-reply): count message tool sends as delivery by mcaxtr · Pull Request #90123 · openclaw/openclaw

mcaxtr · 2026-06-04T02:27:24Z

Problem

message_tool_only auto-reply runs intentionally suppress the normal dispatcher-owned final reply: the visible response is delivered by the model calling the message tool.

That left shared auto-reply with no dispatcher-queued final reply to count. Even when the message tool had already committed visible delivery, dispatchReplyFromConfig could return noVisibleReplyFallbackEligible, so callers could treat a successful visible reply as a no-reply turn and enter fallback handling.

Solution

This makes visible delivery an explicit shared auto-reply signal instead of inferring it from channel-specific behavior or raw message-tool telemetry.

The embedded runner records didDeliverSourceReplyViaMessageTool when the existing message_tool_only terminal-send predicate accepts a committed message.send.
runReplyAgent converts that runner-owned delivery fact into the new generic onObservedReplyDelivery callback.
dispatchReplyFromConfig tracks observedReplyDelivery, returns it in DispatchFromConfigResult, and does not mark the run fallback-eligible when delivery was observed.
Shared dispatch visibility helpers count observedReplyDelivery as visible delivery.
WhatsApp consumes the shared dispatch result so it treats observed message-tool delivery as success without adding WhatsApp-specific detection logic.

The important boundary is that the delivery decision stays with the runner predicate that already validates the message-tool send: implicit source route, committed delivery evidence, not dry-run, not failed, and not a cross-target send.

Verification

Blacksmith Testbox through Crabbox: provider blacksmith-testbox, id tbx_01kt86x1s4rdwkwwp5ph4q2ah3, Actions run 26926097102
CI=true corepack pnpm test src/agents/embedded-agent-runner/run/message-tool-terminal.test.ts src/auto-reply/reply/dispatch-from-config.test.ts src/plugin-sdk/inbound-reply-dispatch.test.ts extensions/whatsapp/src/auto-reply/monitor/inbound-dispatch.test.ts
CI=true corepack pnpm tsgo:core
CI=true corepack pnpm tsgo:extensions
git diff --check origin/main...HEAD

clawsweeper · 2026-06-04T02:28:55Z

Codex review: needs maintainer review before merge. Reviewed June 3, 2026, 10:38 PM ET / 02:38 UTC.

Summary
The PR records qualifying message-tool-only sends as observed source delivery and propagates that signal through shared auto-reply dispatch, channel visibility helpers, and WhatsApp success handling.

PR surface: Source +48, Tests +76. Total +124 across 15 files.

Reproducibility: yes. from source inspection: current main can mark a message-tool-only run fallback-eligible when no dispatcher final was queued, even though the runner/message tool path can have delivered the visible source reply. I did not run tests because this was a read-only review, but the failure path and added regression tests are clear.

Review metrics: 1 noteworthy metric.

Observed-delivery API surface: 3 optional additions. The PR adds an optional callback/result signal across GetReplyOptions, DispatchFromConfigResult, and the channel visible-dispatch result shape, which is additive but touches public/shared dispatch contracts.

Merge readiness
Overall: 🐚 platinum hermit
Proof: 🐚 platinum hermit
Patch quality: 🦞 diamond lobster
Result: ready for maintainer review.

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

Rank-up moves:

none.

Next step before merge

No ClawSweeper repair lane is needed; this is an open maintainer PR with no actionable automated fix identified.

Security
Cleared: The diff only changes TypeScript runtime/test dispatch logic and does not touch CI, dependencies, lockfiles, secrets, install scripts, or package publishing surfaces.

Review details

Best possible solution:

Land this PR, or an equivalent generic observed-delivery bridge, with the runner-owned delivery predicate feeding shared dispatch and channel consumers instead of adding channel-specific message-tool detection.

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

Yes from source inspection: current main can mark a message-tool-only run fallback-eligible when no dispatcher final was queued, even though the runner/message tool path can have delivered the visible source reply. I did not run tests because this was a read-only review, but the failure path and added regression tests are clear.

Is this the best way to solve the issue?

Yes. The patch is the best fix shape because it keeps the committed-delivery decision at the existing runner predicate and only forwards a generic observed-delivery fact through shared dispatch and WhatsApp consumption.

AGENTS.md: found and applied where relevant.

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

Label changes

Label changes:

add P2: This fixes a real but bounded auto-reply delivery-state bug affecting message-tool-only channel replies.
add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🦞 diamond lobster.
add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The external contributor proof gate does not apply because this is a MEMBER/maintainer-labeled PR, and the PR body records Testbox plus exact targeted commands.

Label justifications:

P2: This fixes a real but bounded auto-reply delivery-state bug affecting message-tool-only channel replies.
rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🦞 diamond lobster.
status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The external contributor proof gate does not apply because this is a MEMBER/maintainer-labeled PR, and the PR body records Testbox plus exact targeted commands.

Evidence reviewed

PR surface:

Source +48, Tests +76. Total +124 across 15 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	11	54	6	+48
Tests	4	76	0	+76
Docs	0	0	0	0
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	15	130	6	+124

What I checked:

Repository policy applied: Root AGENTS.md and the scoped guides for agents, embedded runner, channels, plugin SDK, and extensions were read; the review applied the owner-boundary, plugin SDK compatibility, channel visibility, and Codex/dependency-check guidance. (AGENTS.md:1, ac2dbfcfca8a)
Current-main failure path: Current main returns noVisibleReplyFallbackEligible whenever no final reply was queued and empty final is not allowed, without considering a message-tool-only source delivery observed by the runner. (src/auto-reply/reply/dispatch-from-config.ts:2953, ac2dbfcfca8a)
Current WhatsApp gap: Current WhatsApp dispatch only passes { queuedFinal, counts } to hasVisibleInboundReplyDispatch and returns the local didSendReply flag, so a message-tool-only delivery outside the buffered dispatcher can be treated as no visible reply. (extensions/whatsapp/src/auto-reply/monitor/inbound-dispatch.ts:657, ac2dbfcfca8a)
Runner-owned delivery predicate preserved: The PR keeps the source-delivery decision at the existing message_tool_only terminal-send predicate and only marks delivery after an implicit-route, non-dry-run, non-error delivered message.send. (src/agents/embedded-agent-runner/run/message-tool-terminal.ts:155, 20874c18f06c)
Shared dispatch fix: The PR adds onObservedReplyDelivery, forwards it to the reply resolver, returns observedReplyDelivery, and suppresses fallback eligibility only when that observed delivery bit is set. (src/auto-reply/reply/dispatch-from-config.ts:1302, 20874c18f06c)
WhatsApp consumption fix: The PR passes the full shared dispatch result into hasVisibleInboundReplyDispatch and treats observedReplyDelivery as visible delivery for WhatsApp status reactions and the boolean return value. (extensions/whatsapp/src/auto-reply/monitor/inbound-dispatch.ts:801, 20874c18f06c)

Likely related people:

Brian: Current-main blame and recent path history for the message-tool terminal predicate, shared dispatch fallback result, WhatsApp dispatch, and channel visibility helper all point to commit 7b5f75e in this checkout. (role: recent area contributor; confidence: medium; commits: 7b5f75eb98f4; files: src/agents/embedded-agent-runner/run/message-tool-terminal.ts, src/auto-reply/reply/dispatch-from-config.ts, extensions/whatsapp/src/auto-reply/monitor/inbound-dispatch.ts)
Vincent Koc: The latest release commit refreshed plugin SDK baseline content adjacent to the public dispatch-result surface, so this person may be relevant for SDK/release awareness if maintainers want a second routing point. (role: release-adjacent contributor; confidence: low; commits: 2e08f0f4221f; files: src/plugin-sdk/inbound-reply-dispatch.ts, src/auto-reply/reply/dispatch-from-config.types.ts)

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.

…26.6.5) (#963) 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.1` → `2026.6.5` | --- ### Release Notes <details> <summary>openclaw/openclaw (ghcr.io/openclaw/openclaw)</summary> ### [`v2026.6.5`](https://github.com/openclaw/openclaw/blob/HEAD/CHANGELOG.md#202665) [Compare Source](openclaw/openclaw@v2026.6.1...v2026.6.5) ##### Highlights - QQBot now strips model reasoning/thinking scaffolding before native delivery, preventing raw `<thinking>` content from leaking into channel replies. ([#89913](openclaw/openclaw#89913), [#90132](openclaw/openclaw#90132)) Thanks [@openperf](https://github.com/openperf). - MCP tool results now coerce `resource_link`, `resource`, `audio`, malformed image, and future non-text/image blocks at the materialize boundary, preventing Anthropic 400s and poisoned session history after a tool returns richer MCP content. ([#90710](openclaw/openclaw#90710), [#90728](openclaw/openclaw#90728)) Thanks [@RanSHammer](https://github.com/RanSHammer) and [@849261680](https://github.com/849261680). - Anthropic extended-thinking sessions recover after prompt-cache expiry or Gateway restart because stream start events wait for `message_start`, letting pre-generation signature errors trigger the existing recovery retry. ([#90667](openclaw/openclaw#90667), [#90697](openclaw/openclaw#90697)) Thanks [@openperf](https://github.com/openperf). - Parallel is now a bundled `web_search` provider with `PARALLEL_API_KEY` discovery, guarded endpoint handling, cache-safe session ids, onboarding picker support, and docs. ([#85158](openclaw/openclaw#85158)) Thanks [@NormallyGaussian](https://github.com/NormallyGaussian). - Google Vertex ADC users get static catalog rows and runtime model resolution again, while single-provider cooldown recovery and memory adapter status checks are more reliable. ([#90506](openclaw/openclaw#90506), [#90609](openclaw/openclaw#90609), [#90717](openclaw/openclaw#90717), [#90816](openclaw/openclaw#90816)) Thanks [@849261680](https://github.com/849261680). - Matrix can preflight voice notes before mention gating, preserve thread reads/replies through Matrix relations pagination, and carry QA coverage for voice and thread flows. ([#78016](openclaw/openclaw#78016), [#90415](openclaw/openclaw#90415)) - Auth and plugin install state is more durable: auth profiles now live in SQLite, official npm plugin install records keep their trusted pins, and prerelease fallback integrity checks avoid carrying stale integrity forward. ([#89102](openclaw/openclaw#89102), [#88585](openclaw/openclaw#88585)) - macOS node mode no longer silently self-reconnects away from a healthy direct Gateway session, reducing unexpected companion app session churn. ([#90668](openclaw/openclaw#90668), [#90815](openclaw/openclaw#90815)) Thanks [@vrurg](https://github.com/vrurg). - Upgrade and service paths are safer: cron legacy JSON stores migrate during doctor preflight, service env placeholders no longer mask state-dir secrets, WhatsApp startup waits are bounded, and disabled WhatsApp accounts tear down on config reload. ([#90072](openclaw/openclaw#90072), [#90208](openclaw/openclaw#90208), [#90277](openclaw/openclaw#90277), [#90488](openclaw/openclaw#90488), [#90486](openclaw/openclaw#90486), [#87951](openclaw/openclaw#87951), [#87965](openclaw/openclaw#87965)) Thanks [@MonkeyLeeT](https://github.com/MonkeyLeeT), [@sallyom](https://github.com/sallyom), [@mcaxtr](https://github.com/mcaxtr), and [@MukundaKatta](https://github.com/MukundaKatta). ##### Changes - Search/providers: add the Parallel bundled web-search plugin, live provider tests, registration contracts, onboarding/docs wiring, and guarded `api.parallel.ai/v1/search` support. ([#85158](openclaw/openclaw#85158)) Thanks [@NormallyGaussian](https://github.com/NormallyGaussian). - Matrix/channels: add voice-message preflight and thread-aware read/reply behavior, including Matrix QA scenario wiring and docs for voice-message behavior. ([#78016](openclaw/openclaw#78016), [#90415](openclaw/openclaw#90415)) - Skills/ClawHub: install ClawHub skills backed by GitHub repositories through the resolved install API, download the pinned GitHub commit, keep install-policy checks, and report install telemetry after success. ([#90478](openclaw/openclaw#90478)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen). - Google Chat/channels: add native approval card actions and click handling so Google Chat approvals use platform-native cards instead of generic message flow. - Mobile: Android provider/model screens now surface expiring, unavailable, unresolved, and attention states more clearly, while iOS settings and Talk tabs keep diagnostics, gateway rows, attachment labels, and unavailable Talk controls reachable. - Memory: QMD search can use the new rerank toggle, and memory adapter status uses the resolved default model identity when checking plain status. ([#61834](openclaw/openclaw#61834)) - Docs/tooling: add Parallel search docs, refresh weather-skill guidance toward `web_fetch`, clarify legacy `openai-codex` auth, document release/test helper scripts, and tighten changed-test routing docs for CI/debugging work. ([#90028](openclaw/openclaw#90028), [#90250](openclaw/openclaw#90250)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev). - Release/process: switch release trains to `YYYY.M.PATCH` monthly patch numbering, keep pre-transition tags compatible, and pin the June 2026 floor at `2026.6.5` after the published beta. - Platform maintenance: refresh Android, Swift/macOS, Docker, CodeQL, Buildx, Docker build/push, and Codex Action dependencies for this release train. ([#74980](openclaw/openclaw#74980), [#81757](openclaw/openclaw#81757), [#86481](openclaw/openclaw#86481), [#86483](openclaw/openclaw#86483), [#90601](openclaw/openclaw#90601)) - QQBot: add `/bot-group-allways on|off` slash command (with named-account and default-account support) to toggle whether group messages require an `@mention` before the bot replies, and clear the runtime config snapshot after the write so the new account-level `defaultRequireMention` takes effect immediately without restart. ([#91423](openclaw/openclaw#91423)) Thanks [@cxyhhhhh](https://github.com/cxyhhhhh). ##### Fixes - Channel content boundaries: QQBot now strips reasoning/thinking tags before sending, preserving final answers while hiding internal model narration from users. ([#89913](openclaw/openclaw#89913), [#90132](openclaw/openclaw#90132)) Thanks [@openperf](https://github.com/openperf). - Agents/MCP/providers: coerce non-text/image MCP tool-result blocks before they reach provider converters, preserving valid images and turning richer MCP content into text instead of malformed image blocks. ([#90710](openclaw/openclaw#90710), [#90728](openclaw/openclaw#90728)) Thanks [@RanSHammer](https://github.com/RanSHammer) and [@849261680](https://github.com/849261680). - Anthropic/Codex/ACP/agent recovery: defer Anthropic stream start events until `message_start`, strip stale compaction thinking signatures before Anthropic replay, detect unsigned thinking-only stalls, refresh prompt fences after compaction writes, reject empty completion handoffs, preserve parent streaming-off overrides/shared progress commentary, forward heartbeat metadata to context-engine hooks, and cover Codex session/thread migration edge cases. ([#90667](openclaw/openclaw#90667), [#90697](openclaw/openclaw#90697), [#90163](openclaw/openclaw#90163), [#90108](openclaw/openclaw#90108), [#89874](openclaw/openclaw#89874), [#89505](openclaw/openclaw#89505), [#90632](openclaw/openclaw#90632), [#89302](openclaw/openclaw#89302), [#90729](openclaw/openclaw#90729), [#90317](openclaw/openclaw#90317), [#90319](openclaw/openclaw#90319)) Thanks [@openperf](https://github.com/openperf), [@100yenadmin](https://github.com/100yenadmin), and [@ooiuuii](https://github.com/ooiuuii). - Provider/model resolution: preserve Google Vertex ADC auth markers in generated catalogs, re-probe a single-provider primary after cooldown, share Codex model visibility, fail closed for unknown model auth, preserve Codex alias availability, keep unresolved profile refs unknown, and avoid resolving auth while listing models. ([#90506](openclaw/openclaw#90506), [#90609](openclaw/openclaw#90609), [#90717](openclaw/openclaw#90717), [#90702](openclaw/openclaw#90702)) Thanks [@849261680](https://github.com/849261680). - Gateway/macOS/mobile: avoid duplicate Gateway probe warnings by identity, rate-limit node pairing requests while preserving paired-node reconnects, keep macOS node mode on a healthy direct Gateway session, keep iOS diagnostics and gateway rows reachable, and avoid Linux ARM Gradle resource tasks during Android builds. ([#85791](openclaw/openclaw#85791), [#90147](openclaw/openclaw#90147), [#90668](openclaw/openclaw#90668), [#90815](openclaw/openclaw#90815)) Thanks [@giodl73-repo](https://github.com/giodl73-repo) and [@vrurg](https://github.com/vrurg). - TUI/chat/Workboard/auto-reply: optimistic user messages stay stable across stale history reloads, runId reassignment, and abort windows instead of disappearing, jumping, or lingering as ghost rows; Workboard stale lifecycle bulk updates no longer overwrite newer status/provenance; message-tool sends now count as delivery. ([#86205](openclaw/openclaw#86205), [#89600](openclaw/openclaw#89600), [#88592](openclaw/openclaw#88592), [#90123](openclaw/openclaw#90123)) Thanks [@RomneyDa](https://github.com/RomneyDa). - Cron/update/service env: doctor config preflight now migrates legacy cron JSON stores into SQLite before runtime reads, service env planning skips unresolved placeholders that would mask state-dir `.env` values, and session transcript rewrites keep registry markers/discriminants consistent. ([#90072](openclaw/openclaw#90072), [#90208](openclaw/openclaw#90208), [#90277](openclaw/openclaw#90277), [#90488](openclaw/openclaw#90488)) Thanks [@MonkeyLeeT](https://github.com/MonkeyLeeT) and [@sallyom](https://github.com/sallyom). - Security/config/tooling: guard MCP HTTP redirects, protect global agent config defaults, and keep release/test/tooling proof failures bounded and explicit. ([#89732](openclaw/openclaw#89732), [#90145](openclaw/openclaw#90145)) - Channels: WhatsApp restarts when per-account config changes, bounds background startup waits, closes failed sockets, and preserves reconnect behavior; Mattermost slash commands keep their state on `globalThis`; Feishu streaming cards preserve full merged content; voice-call tracks Twilio streams after connect; ClickClack reply tools respect `toolsAllow`. ([#87951](openclaw/openclaw#87951), [#87965](openclaw/openclaw#87965), [#90486](openclaw/openclaw#90486), [#68113](openclaw/openclaw#68113), [#90534](openclaw/openclaw#90534), [#90181](openclaw/openclaw#90181), [#90607](openclaw/openclaw#90607), [#89500](openclaw/openclaw#89500)) Thanks [@MukundaKatta](https://github.com/MukundaKatta), [@mcaxtr](https://github.com/mcaxtr), [@infoanton](https://github.com/infoanton), [@mushuiyu886](https://github.com/mushuiyu886), and [@sahibzada-allahyar](https://github.com/sahibzada-allahyar). - Feishu: retry transient send rate-limit errors (HTTP 429, per-chat code 230020, tenant-level code 11232) with linear backoff, including SDK responses that fulfill with rate-limit bodies instead of throwing, and route streaming-card sends through the retry wrapper. ([#89659](openclaw/openclaw#89659)) Thanks [@ladygege](https://github.com/ladygege). - Release/CI/E2E: main CI guard drift, PR merge diff scoping, live Docker credential staging, base-image qualification, installer Docker classification, Playwright dependency install recovery, API-key auth for Codex live Docker lanes, Parallels option terminators, and JSON-mode progress handling are tighter so release proof fails cleaner. ([#90532](openclaw/openclaw#90532), [#90287](openclaw/openclaw#90287), [#90058](openclaw/openclaw#90058)) Thanks [@RomneyDa](https://github.com/RomneyDa), [@hxy91819](https://github.com/hxy91819), and [@mrunalp](https://github.com/mrunalp). - Release/CI/E2E: Docker E2E and live Docker harness runs now apply default memory, CPU, and process ceilings while preserving explicit per-lane overrides. - Release/CI/E2E: plugin lifecycle matrix resource sampling now fails phases that exceed RSS, wall-clock, or CPU ceilings instead of only logging the measurements. - Release/CI/E2E: Codex npm plugin live assertions now cap transcript discovery and diagnostic log reads so failure proof stays bounded. - Tests/state isolation: QA Lab valid-tool-call metrics now require runtime tool-call evidence when runtime parity data is available instead of counting tool-backed scenario pass status alone. - Tests/state isolation: QA Lab runtime parity now fails planned-only tool-call rows without matching tool results instead of treating matching mock plans as real tool evidence. - Tests/state isolation: provider, media, auth, cron, task, session, sandbox, Gateway, and Codex timeout fixtures now scope more home/state/env data per test, reducing cross-test leakage and making release validation failures less noisy. ([#90027](openclaw/openclaw#90027), [#89974](openclaw/openclaw#89974)) </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/963

fix(auto-reply): count message tool sends as delivery

20874c1

openclaw-barnacle Bot added channel: whatsapp-web Channel integration: whatsapp-web agents Agent runtime and tooling size: S maintainer Maintainer-authored PR labels Jun 4, 2026

mcaxtr merged commit 88dc177 into main Jun 4, 2026
212 of 219 checks passed

mcaxtr deleted the fix/msg-tool-delivery branch June 4, 2026 03:26

github-actions Bot pushed a commit to Desicool/openclaw that referenced this pull request Jun 4, 2026

fix(auto-reply): count message tool sends as delivery (openclaw#90123)

4c526a6

SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request Jun 4, 2026

fix(auto-reply): count message tool sends as delivery (openclaw#90123)

2a79334

SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request Jun 4, 2026

fix(auto-reply): count message tool sends as delivery (openclaw#90123)

c7c82b8

SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request Jun 4, 2026

fix(auto-reply): count message tool sends as delivery (openclaw#90123)

e7d4499

SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request Jun 4, 2026

fix(auto-reply): count message tool sends as delivery (openclaw#90123)

733efb3

traoremp pushed a commit to traoremp/openclaw that referenced this pull request Jun 5, 2026

fix(auto-reply): count message tool sends as delivery (openclaw#90123)

ce4b0b7

849261680 pushed a commit to 849261680/openclaw that referenced this pull request Jun 7, 2026

fix(auto-reply): count message tool sends as delivery (openclaw#90123)

6333ecd

wangmiao0668000666 pushed a commit to wangmiao0668000666/openclaw that referenced this pull request Jun 9, 2026

fix(auto-reply): count message tool sends as delivery (openclaw#90123)

a8576bc

sablehead pushed a commit to sablehead/openclaw that referenced this pull request Jun 10, 2026

fix(auto-reply): count message tool sends as delivery (openclaw#90123)

7f0e22e

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(auto-reply): count message tool sends as delivery#90123

fix(auto-reply): count message tool sends as delivery#90123
mcaxtr merged 1 commit into
mainfrom
fix/msg-tool-delivery

mcaxtr commented Jun 4, 2026

Uh oh!

clawsweeper Bot commented Jun 4, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

mcaxtr commented Jun 4, 2026

Problem

Solution

Verification

Uh oh!

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

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

clawsweeper Bot commented Jun 4, 2026 •

edited

Loading