Fix Discord verbose tool progress delivery by anyech · Pull Request #80042 · openclaw/openclaw

anyech · 2026-05-10T01:11:13Z

Restore verbose Discord tool-progress delivery across message-tool-only and queued follow-up paths, while preserving final-reply privacy boundaries.

Fixes #78365

Summary

Problem: Discord verbose mode could execute tool work without consistently showing visible tool/progress messages in message-tool-only and queued follow-up paths.
Why it matters: users need visible liveness/provenance for long-running Discord operations; silent tool execution looks like a stuck or lost turn.
What changed: tool-progress payloads are explicitly carried through the Discord delivery/sanitizer paths, including queued follow-up execution.
What did not change: this does not make every final assistant reply public; it only restores explicit tool/progress/status payload delivery.

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

Fixes [Bug] Discord plugin regressions: verbose tool progress bubbles missing in v2026.5.4 due to hardcoded 'verbose: false' in adapter #78365
This PR fixes a bug or regression

Real behavior proof

Behavior or issue addressed: In a real Discord verbose-mode thread, tool calls could run while the channel did not consistently receive visible tool/progress messages. This made queued or message-tool-only turns appear silent even though work was executing.
Real environment tested: OpenClaw 2026.5.7 on Linux using Discord integration in a private test thread. Private channel, session, host, and file-path identifiers are redacted.
Exact steps or command run after this patch: Applied the same source-level changes to a local hotfix package, validated the patched Discord delivery bundles, then ran a direct Discord verbose tool-progress canary and a queued/follow-up tool-progress canary.
Evidence after fix: Redacted runtime-log / copied live-output excerpt:

TOOL_PROGRESS_DIRECT_CANARY_OK
visible_discord_progress_message=true
visible_tool_status_payload=true

TOOL_PROGRESS_QUEUED_CANARY_OK
queued_followup_started=true
visible_discord_progress_message=true
visible_tool_status_payload=true

sanitizer_allows_tool_progress_kind=true
final_reply_privacy_boundary_preserved=true

Observed result after fix: The Discord channel showed visible tool/progress messages for both the direct turn and the queued/follow-up path. The delivery sanitizer preserved explicit tool-progress payloads while final replies remained subject to the existing final-reply privacy contract.
What was not tested: No broad auto-publication of normal final replies was tested or added. This proof exercised Discord verbose tool/progress delivery, not every non-Discord channel.
Before evidence (optional): Before the hotfix, the same class of Discord verbose turns could show no visible tool-progress message even though the tool call executed.

Root Cause

Root cause: tool/progress status payloads were not consistently treated as explicit Discord-deliverable payloads across the message-tool-only and queued follow-up delivery paths.
Missing detection / guardrail: coverage did not lock the Discord delivery sanitizer and queued follow-up status propagation together.
Contributing context: message-tool-only final-reply privacy boundaries are intentional, so explicit tool/progress payloads need their own preserved delivery path.

Regression Test Plan

Coverage level that should have caught this:
- Unit test
- Seam / integration test
- End-to-end test
- Existing coverage already sufficient
Target test or file: Discord reply-delivery and auto-reply follow-up dispatch tests.
Scenario the test should lock in: explicit tool/progress payloads remain visible in Discord verbose mode for both direct and queued/follow-up execution paths.
Why this is the smallest reliable guardrail: it covers the payload propagation and sanitizer seam without requiring live Discord credentials in CI.
Existing test that already covers this (if any): N/A; this PR adds the missing guardrails.

User-visible / Behavior Changes

Discord verbose mode once again shows explicit tool/progress messages for affected message-tool-only and queued follow-up paths.

Diagram

Before:
tool execution -> progress payload -> delivery/sanitizer gap -> no visible Discord progress

After:
tool execution -> explicit progress payload -> Discord delivery allowed -> visible progress message

Security Impact

New permissions/capabilities? No
Secrets/tokens handling changed? No
New/changed network calls? No
Command/tool execution surface changed? No
Data access scope changed? No

Repro + Verification

Environment

OS: Linux
Runtime/container: OpenClaw 2026.5.7 local/stage installation
Model/provider: not relevant; tool-progress delivery was exercised with harmless canaries
Integration/channel: Discord
Relevant config: verbose mode enabled; private identifiers redacted

Steps

Enable verbose mode in a private Discord test thread.
Trigger a harmless direct tool-progress canary.
Trigger a harmless queued/follow-up tool-progress canary.
Confirm the Discord channel receives visible tool/progress messages in both paths.

Expected

Explicit tool/progress payloads are visible in Discord verbose mode.

Actual

After the patch, direct and queued/follow-up canaries both produced visible Discord tool/progress messages.

Evidence

Trace/log snippets
Copied live output

Human Verification

Verified scenarios: direct verbose Discord tool-progress delivery; queued/follow-up verbose Discord tool-progress delivery; sanitizer allows tool-progress payload kind.
Edge cases checked: final-reply privacy boundary remains separate from explicit tool/progress delivery.
What I did not verify: all non-Discord channels and broad final-answer auto-publication.

Review Conversations

I replied to or resolved every bot review conversation I addressed in this PR.
I left unresolved only the conversations that still need reviewer or maintainer judgment.

Compatibility / Migration

Backward compatible? Yes
Config/env changes? No
Migration needed? No

Risks and Mitigations

Risk: accidentally making private final replies public.
- Mitigation: scope is limited to explicit tool/progress payload delivery; final-reply privacy remains unchanged.

clawsweeper · 2026-05-10T01:14:38Z

Codex review: passed.

Workflow note: Future ClawSweeper reviews update this same comment in place.

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 maintainer comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors can comment @clawsweeper re-review or @clawsweeper re-run on their own 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.

Summary
The PR changes Discord reply delivery, sanitizer, and queued follow-up auto-reply paths so explicit verbose tool-progress payloads are delivered while final assistant replies still use the privacy sanitizer.

Reproducibility: yes. source-level: current main strips tool-looking Discord payload text at the front-channel sanitizer, suppresses channel message_tool_only progress, and only forwards compaction events in queued follow-up runs. I did not run a live Discord repro in this read-only review.

Real behavior proof
Sufficient (live_output): The PR body includes redacted copied live output from a real Discord verbose-mode setup showing after-fix direct and queued progress canaries with final-reply privacy preserved.

Mantis proof suggestion
A short real Discord transcript would materially help validate visible direct and queued progress behavior beyond the copied live output. A maintainer can ask Mantis to capture proof by posting a new PR comment that starts with the OpenClaw Mantis account mention, followed by:

visual task: verify Discord verbose mode shows visible tool/progress messages for direct and queued follow-up turns while final replies stay private.

Next step before merge
No repair lane is needed now; the previous missing delivery-kind caller was repaired on the contributor branch and the remaining action is exact-head check and merge gating.

Security
Cleared: The diff is limited to Discord/auto-reply delivery and tests, with no dependency, workflow, permission, secret-handling, or package-execution changes.

Review details

Best possible solution:

Land this narrow Discord delivery fix once exact-head checks finish, then close the linked regression and re-evaluate any remaining Discord status-draft follow-up separately.

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

Yes, source-level: current main strips tool-looking Discord payload text at the front-channel sanitizer, suppresses channel message_tool_only progress, and only forwards compaction events in queued follow-up runs. I did not run a live Discord repro in this read-only review.

Is this the best way to solve the issue?

Yes, after the repair: the patch uses existing ReplyDispatchKind metadata to exempt only explicit tool payloads from final-reply sanitization, forwards queued progress through existing callbacks, and keeps final-reply privacy intact.

What I checked:

Current main strips tool-looking Discord payloads: On current main, Discord front-channel payload sanitization has no delivery-kind input and always runs tool-looking text through the internal trace stripping path, which explains why explicit progress text can disappear. (extensions/discord/src/monitor/reply-safety.ts:72, c93d6d8daa37)
Current main suppresses channel message-tool-only progress: The current source-suppression escape hatch is limited to direct chats, so Discord channel turns in message_tool_only mode do not get this verbose progress delivery path. (src/auto-reply/reply/dispatch-from-config.ts:1047, c93d6d8daa37)
Current main queued followups only observe compaction: Queued embedded follow-up runs on current main only forward compaction events through onAgentEvent, leaving normal tool/item/command progress without channel callbacks. (src/auto-reply/reply/followup-runner.ts:561, c93d6d8daa37)
Repaired PR head threads delivery kind into Discord sends: The repaired head passes info.kind through the Discord supplemental, normal, and fallback delivery calls so deliverDiscordReply can distinguish tool progress from final replies. (extensions/discord/src/monitor/message-handler.process.ts:626, fd845e773ac6)
Repaired PR head preserves only explicit tool payloads: The Discord sanitizer now accepts a kind option and bypasses trace stripping only for kind: tool; final/block payloads still use sanitizeDiscordFrontChannelText. (extensions/discord/src/monitor/reply-safety.ts:72, fd845e773ac6)
Repaired PR head forwards queued progress with verbose gates: The repaired follow-up runner passes toolProgressDetail, shouldEmitToolResult, shouldEmitToolOutput, onToolResult, and onAgentEvent into embedded runs, queues progress delivery, and drains it before final delivery. (src/auto-reply/reply/followup-runner.ts:724, fd845e773ac6)

Likely related people:

steipete: Recent main history shows repeated work on Discord reply delivery/safety and auto-reply source-delivery behavior, including reply API consolidation and message-tool-only logging. (role: recent area contributor; confidence: high; commits: 827b0de0ce74, a4b17d65a8ff, 343f859b900c; files: extensions/discord/src/monitor/reply-delivery.ts, extensions/discord/src/monitor/reply-safety.ts, src/auto-reply/reply/dispatch-from-config.ts)
hclsys: Recent main history includes queued follow-up runner routing work in the same file that this PR changes for queued progress forwarding. (role: recent follow-up runner contributor; confidence: medium; commits: f2d8f38315d2; files: src/auto-reply/reply/followup-runner.ts)
Satoshi: Recent commits touched Discord reply safety and startup/reply hardening around the sanitizer surface this PR changes. (role: adjacent Discord reply safety contributor; confidence: medium; commits: 5572c8137cb3, e259938e9643; files: extensions/discord/src/monitor/reply-safety.ts)
Patrick-Erichsen: Recent main history includes Discord reply-delivery failure handling in the same delivery helper modified by this PR. (role: adjacent Discord reply delivery contributor; confidence: medium; commits: 9e97cdb21389; files: extensions/discord/src/monitor/reply-delivery.ts)
TurboTheTurtle: The maintainer review thread identified the queued follow-up verbose-off gating problem that the repaired head now addresses. (role: reviewer; confidence: medium; files: src/auto-reply/reply/followup-runner.ts)

Remaining risk / open question:

Exact-head CI was still pending one Critical Quality check at inspection, so merge should remain gated on required checks completing successfully.
This review did not run a live Discord session; it relies on source inspection, PR tests, CI, and the contributor’s redacted copied live output.

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

TurboTheTurtle

Found one issue in the queued follow-up progress forwarding.

Summary: - The PR changes Discord reply delivery, sanitizer, and queued follow-up auto-reply paths so explicit verbose tool-progress payloads are delivered while final assistant replies still use the privacy sanitizer. - Reproducibility: yes. source-level: current main strips tool-looking Discord payload text at the front-chann ... ds compaction events in queued follow-up runs. I did not run a live Discord repro in this read-only review. Automerge notes: - Ran the ClawSweeper repair loop before final review. - Included post-review commit in the final squash: fix: gate queued follow-up progress when verbose is off - Included post-review commit in the final squash: fix: preserve queued verbose progress under preview suppression - Included post-review commit in the final squash: ci: rerun discord verbose progress PR - Included post-review commit in the final squash: fix: preserve Discord verbose progress after rebase - Included post-review commit in the final squash: fix: serialize discord queued progress - Included post-review commit in the final squash: Fix Discord verbose tool progress delivery Validation: - ClawSweeper review passed for head fd845e773ac6d649ee2dd7ff0defb4676b06b3da. - Required merge gates passed before the squash merge. Prepared head SHA: fd845e773ac6d649ee2dd7ff0defb4676b06b3da Review: openclaw/openclaw#80042 (comment) Co-authored-by: Clawsistant <[email protected]> Co-authored-by: anyech <[email protected]> Co-authored-by: OpenClaw Assistant <[email protected]> Co-authored-by: Shadow <[email protected]> Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com> Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com> Approved-by: thewilloftheshadow Co-authored-by: thewilloftheshadow <[email protected]>

Summary: - The PR changes Discord reply delivery, sanitizer, and queued follow-up auto-reply paths so explicit verbose tool-progress payloads are delivered while final assistant replies still use the privacy sanitizer. - Reproducibility: yes. source-level: current main strips tool-looking Discord payload text at the front-chann ... ds compaction events in queued follow-up runs. I did not run a live Discord repro in this read-only review. Automerge notes: - Ran the ClawSweeper repair loop before final review. - Included post-review commit in the final squash: fix: gate queued follow-up progress when verbose is off - Included post-review commit in the final squash: fix: preserve queued verbose progress under preview suppression - Included post-review commit in the final squash: ci: rerun discord verbose progress PR - Included post-review commit in the final squash: fix: preserve Discord verbose progress after rebase - Included post-review commit in the final squash: fix: serialize discord queued progress - Included post-review commit in the final squash: Fix Discord verbose tool progress delivery Validation: - ClawSweeper review passed for head fd845e7. - Required merge gates passed before the squash merge. Prepared head SHA: fd845e7 Review: openclaw#80042 (comment) Co-authored-by: Clawsistant <[email protected]> Co-authored-by: anyech <[email protected]> Co-authored-by: OpenClaw Assistant <[email protected]> Co-authored-by: Shadow <[email protected]> Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com> Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com> Approved-by: thewilloftheshadow Co-authored-by: thewilloftheshadow <[email protected]>

openclaw-barnacle Bot added channel: discord Channel integration: discord size: M triage: blank-template Candidate: PR template appears mostly untouched. triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. labels May 10, 2026

TurboTheTurtle reviewed May 10, 2026

View reviewed changes

Comment thread src/auto-reply/reply/followup-runner.ts Outdated

anyech force-pushed the fix/discord-verbose-tool-progress branch 2 times, most recently from b17d493 to 0442c1f Compare May 10, 2026 20:45

openclaw-barnacle Bot added cli CLI command changes and removed channel: discord Channel integration: discord size: M labels May 10, 2026

anyech force-pushed the fix/discord-verbose-tool-progress branch from 0442c1f to 43fc7a6 Compare May 10, 2026 20:45

anyech force-pushed the fix/discord-verbose-tool-progress branch from 43fc7a6 to 8269454 Compare May 10, 2026 20:55

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

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

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

stanislasbdx mentioned this pull request May 12, 2026

[Bug]: Discord streaming.mode: "progress" does not create or update status draft #81043

Closed

anyech force-pushed the fix/discord-verbose-tool-progress branch from f588275 to 65b233c Compare May 12, 2026 20:43

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

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

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

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

clawsweeper Bot mentioned this pull request May 14, 2026

[Bug] Discord plugin regressions: verbose tool progress bubbles missing in v2026.5.4 due to hardcoded 'verbose: false' in adapter #78365

Closed

OpenClaw Assistant and others added 4 commits May 17, 2026 22:42

ci: rerun discord verbose progress PR

b1b67d4

fix: preserve Discord verbose progress after rebase

ebdf1ca

fix: serialize discord queued progress

a18c4f6

Fix Discord verbose tool progress delivery

fd845e7

clawsweeper Bot force-pushed the fix/discord-verbose-tool-progress branch from 1ca3736 to fd845e7 Compare May 17, 2026 22:52

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

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

clawsweeper Bot merged commit 57da466 into openclaw:main May 17, 2026
124 of 125 checks passed

github-actions Bot mentioned this pull request May 18, 2026

📡 Upstream Digest — 2026-05-18 02:35 UTC curtismercier/openclaw-mods#887

Open

clawsweeper Bot mentioned this pull request May 20, 2026

fix(channels): suppress verbose failed-tool dumps #84354

Merged

This was referenced May 21, 2026

[Bug]: Default-mode Matrix channel rooms receive internal tool/progress events as visible chat messages #85000

Closed

fix(channels): suppress verbose progress and tool summaries on default-mode channel rooms #85069

Closed

This was referenced Jun 14, 2026

fix(discord): log silent reply drops; allow archives in host-read media #79945

Open

Discord outbound leaks 🛠️ tool-progress lines when agent is in Barnacling state (stripper bypassed) #88341

Closed

This was referenced Jun 27, 2026

fix(auto-reply): hide recovered failed tool progress #97135

Open

[Bug]: Internal tool/status messages leak into Telegram chat even when streaming/tool progress is disabled #79804

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Fix Discord verbose tool progress delivery#80042

Fix Discord verbose tool progress delivery#80042
clawsweeper[bot] merged 7 commits into
openclaw:mainfrom
anyech:fix/discord-verbose-tool-progress

anyech commented May 10, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented May 10, 2026 •

edited

Loading

Uh oh!

TurboTheTurtle left a comment

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

anyech commented May 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

Real behavior proof

Root Cause

Regression Test Plan

User-visible / Behavior Changes

Diagram

Security Impact

Repro + Verification

Environment

Steps

Expected

Actual

Evidence

Human Verification

Review Conversations

Compatibility / Migration

Risks and Mitigations

Uh oh!

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

Uh oh!

Uh oh!

TurboTheTurtle left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

anyech commented May 10, 2026 •

edited

Loading

clawsweeper Bot commented May 10, 2026 •

edited

Loading