fix(twitch): strip internal tool-trace banners from outbound text by clawsweeper[bot] · Pull Request #103109 · openclaw/openclaw

clawsweeper · 2026-07-09T21:00:41Z

Makes #102992 merge-ready for the ClawSweeper automerge loop.
The edit pass should inspect the live PR diff, review comments, and failing checks; rebase if needed; keep the contributor branch credited; and stop only when validation is green or an external blocker is proven.
Known failing checks:

Failing check: Scan changed paths (precise):FAILURE (https://github.com/openclaw/openclaw/actions/runs/29032985131/job/86170404954)

Source

Replacement for #102992 because the source branch could not be updated.

Original contributor: @masatohoshino.

clawsweeper · 2026-07-09T21:01:47Z

Codex review: passed. Reviewed July 9, 2026, 5:15 PM ET / 21:15 UTC.

Summary
The PR adds sanitizeAssistantVisibleText as the Twitch outbound sanitizeText hook and adds regression tests for tool-trace banners, XML tool-call scaffolding, and ordinary prose preservation.

PR surface: Source +4, Tests +33. Total +37 across 2 files.

Reproducibility: yes. Source-level reproduction is high confidence: current main and v2026.6.11 lack Twitch sanitizeText, while shared delivery only runs channel sanitization when that hook exists; I did not run a live Twitch send.

Review metrics: none identified.

Root-cause cluster
Relationship: fixed_by_candidate
Canonical: #90684
Summary: This PR is a candidate fix for the Twitch slice of the broader non-Discord outbound sanitizer gap tracked by the canonical issue.

Members:

canonical: Feishu (and non-Discord channels) should apply sanitizeAssistantVisibleText() on outbound text #90684 - The issue describes the same missing sanitizeAssistantVisibleText coverage across non-Discord channel adapters and remains open as the umbrella tracker.
superseded: fix(twitch): strip internal tool-trace banners from outbound text #102992 - The closed unmerged source PR had the same Twitch fix and was replaced by this credited bot branch because the source branch could not be updated.

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Merge readiness
Overall: 🦞 diamond lobster
Proof: 🌊 off-meta tidepool
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.

Next step before merge

[P2] No repair job is needed; this open automerge PR is already the implementation candidate and exact-head checks can gate merge.

Security
Cleared: The diff adds an existing SDK sanitizer hook and focused tests only; it does not change dependencies, workflows, credentials, permissions, or package execution surfaces.

Review details

Best possible solution:

Land this narrow Twitch adapter hook after exact-head automerge checks pass, while keeping the umbrella issue open for the remaining channel slices or any later shared-default decision.

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

Yes. Source-level reproduction is high confidence: current main and v2026.6.11 lack Twitch sanitizeText, while shared delivery only runs channel sanitization when that hook exists; I did not run a live Twitch send.

Is this the best way to solve the issue?

Yes. The existing outbound adapter hook is the narrow owner-boundary fix and matches merged sibling channels; a shared global default would be a broader product-contract change for the umbrella issue.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against ae11ea5ba9a0.

Label changes

Label justifications:

P1: The PR fixes internal assistant/tool scaffolding leaking into public Twitch chat, an urgent user-visible channel privacy and message-quality bug.
rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🌊 off-meta tidepool and patch quality is 🦞 diamond lobster.
status: 🚀 automerge armed: This PR is in ClawSweeper's automerge lane. Not applicable: This is a ClawSweeper bot replacement PR, so the external contributor proof gate does not apply to this branch; the source PR body included production plugin-boundary output but no live Twitch send.

Evidence reviewed

PR surface:

Source +4, Tests +33. Total +37 across 2 files.

View PR surface stats

Area	Files	Added	Net
Source	1	4	+4
Tests	1	33	+33
Docs	0	0	0
Config	0	0	0
Generated	0	0	0
Other	0	0	0
Total	2	37	+37

What I checked:

Repository policy read: Root AGENTS.md and scoped extensions/AGENTS.md were read fully; the scoped extension policy allows production plugin code to import through openclaw/plugin-sdk/*, which matches this PR's new sanitizer import path. (extensions/AGENTS.md:12, ae11ea5ba9a0)
Current main Twitch gap: Current main's Twitch outbound adapter declares direct delivery, a 500-character text limit, and chunker: chunkTextForTwitch, but it has no sanitizeText hook before this PR. (extensions/twitch/src/outbound.ts:31, ae11ea5ba9a0)
Latest release also lacks the hook: The latest release tag v2026.6.11 shows the same Twitch outbound shape without sanitizeText, so this PR is not redundant with shipped behavior. (extensions/twitch/src/outbound.ts:31, e085fa1a3ffd)
PR hook implementation: The PR imports sanitizeAssistantVisibleText from the plugin SDK text-chunking subpath and exposes it as twitchOutbound.sanitizeText. (extensions/twitch/src/outbound.ts:47, 5dad685b60df)
Shared delivery contract: Shared outbound delivery only calls channel text sanitization when the loaded handler exposes sanitizeText, and does so before channel payload normalization and text planning. (src/infra/outbound/deliver.ts:882, ae11ea5ba9a0)
Sanitizer contract: sanitizeAssistantVisibleText is exported through the plugin SDK and documented in source as the canonical user-visible assistant text sanitizer that keeps prose while removing internal scaffolding. (src/shared/text/assistant-visible-text.ts:1074, ae11ea5ba9a0)

Likely related people:

masatohoshino: Authored merged Slack, Signal, and Matrix sanitizer-hook fixes that established the same per-channel pattern, and is credited as co-author of this replacement branch's source work. (role: sibling-fix contributor; confidence: high; commits: cd6d0f9b00f0, c0265460630a, 25490d4c4212; files: extensions/slack/src/channel.ts, extensions/signal/src/channel.ts, extensions/matrix/src/channel.ts)
jaydenfyi: Git history identifies this author on the original Twitch plugin commit that introduced the affected outbound adapter surface. (role: introduced behavior; confidence: high; commits: f5c90f0e5c7a; files: extensions/twitch/src/outbound.ts, extensions/twitch/src/plugin.ts)
Takhoffman: Recent Twitch outbound account-resolution work touched the same outbound adapter area, and this login is recorded as the maintainer requester for the automerge replacement flow. (role: recent area contributor; confidence: medium; commits: 84db697cd66a; files: extensions/twitch/src/outbound.ts)
lin-hongkuan: Current main blame for the Twitch outbound adapter block points to this broad recent commit that reintroduced the current file, so the signal is useful but not specific to the sanitizer gap. (role: current-line provenance; confidence: low; commits: 148ec3282f07; files: extensions/twitch/src/outbound.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.

Review history (1 earlier review cycle)

reviewed 2026-07-09T21:06:07.732Z sha 5dad685 :: passed. :: none

clawsweeper · 2026-07-09T21:08:00Z

🦞🔧
ClawSweeper applied a repair to this PR branch.

Repair: kept the fix on this contributor branch instead of opening a replacement PR.
Validation: pnpm check:changed; pnpm lint; pnpm check:test-types
Updated head: 3f69bfe25e81
Run: https://github.com/openclaw/clawsweeper/actions/runs/29050336629

Current state: exact-head review queued immediately; GitHub checks and the review verdict gate final merge.

Automerge progress:

2026-07-09 21:16:29 UTC review passed 5dad685b60df (structured ClawSweeper verdict: pass (sha=5dad685b60df1ba545dd409d54cc17b7b2b20...)

2026-07-09 21:08:00 UTC repair queued 5dad685b60df (autonomous) Run: https://github.com/openclaw/clawsweeper/actions/runs/29050336629

2026-07-09 21:07:21 UTC review queued 5dad685b60df (queued)

2026-07-09 21:09:38 UTC repair started (running) in 0s Run: https://github.com/openclaw/clawsweeper/actions/runs/29050336629 automerge-openclaw-openclaw-103109

2026-07-09 21:10:01 UTC validation plan (passed) in 24s Run: https://github.com/openclaw/clawsweeper/actions/runs/29050336629 pnpm check:changed; pnpm lint; pnpm check:test-types

2026-07-09 21:10:17 UTC Codex write preflight (passed) in 40s Run: https://github.com/openclaw/clawsweeper/actions/runs/29050336629 danger-full-access

2026-07-09 21:16:01 UTC Codex edit 1 1287140ce6bd (complete) in 6m 24s Run: https://github.com/openclaw/clawsweeper/actions/runs/29050336629 exit 0

2026-07-09 21:28:55 UTC validation and review 1 3f69bfe25e81 (complete) in 19m 17s Run: https://github.com/openclaw/clawsweeper/actions/runs/29050336629 already-current

2026-07-09 21:30:30 UTC repair completed 3f69bfe25e81 (branch updated) in 20m 53s Run: https://github.com/openclaw/clawsweeper/actions/runs/29050336629 initial automerge rebase is delegated to Codex repair

2026-07-09 21:30:30 UTC review queued 3f69bfe25e81 (after repair)

2026-07-09 21:39:20 UTC automerge wait 3f69bfe25e81 (merged) in 29m 42s Run: https://github.com/openclaw/clawsweeper/actions/runs/29050336629 pull request already merged

2026-07-09 21:39:21 UTC repair finished 3f69bfe25e81 (pushed) in 29m 43s Run: https://github.com/openclaw/clawsweeper/actions/runs/29050336629 repair_contributor_branch

Co-authored-by: Masato Hoshino <[email protected]>

…enclaw#103109) * fix(twitch): strip internal tool-trace banners from outbound text Co-authored-by: Masato Hoshino <[email protected]> * fix(twitch): strip internal tool-trace banners from outbound text --------- Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com> Co-authored-by: Masato Hoshino <[email protected]>

…text The Nextcloud Talk outbound adapter had no sanitizeText hook, so internal assistant tool-trace scaffolding (e.g. "⚠️ 🛠️ `exec (agent)` failed", raw <tool_call>/<function_response> XML) leaked verbatim into delivered chat messages. The same one-line sanitizeText hook was already shipped to 13 sibling channels (mattermost openclaw#98693, feishu openclaw#98705, twitch openclaw#103109, signal openclaw#97360, slack openclaw#97367, matrix openclaw#97372, irc openclaw#97214, telegram, googlechat openclaw#90684, qqbot openclaw#90132, discord, whatsapp openclaw#71830, sms). Add sanitizeText: ({ text }) => sanitizeAssistantVisibleText(text) to the outbound base adapter, matching those precedents. Co-Authored-By: Claude <[email protected]>

The Nostr outbound adapter had no sanitizeText hook, so internal assistant tool-trace scaffolding (e.g. "⚠️ 🛠️ `exec (agent)` failed", raw <tool_call>/<function_response> XML) leaked verbatim into delivered Nostr DMs. The same one-line sanitizeText hook was already shipped to 13 sibling channels (twitch openclaw#103109, mattermost openclaw#98693, feishu openclaw#98705, signal openclaw#97360, slack openclaw#97367, matrix openclaw#97372, irc openclaw#97214, telegram, googlechat openclaw#90684, qqbot openclaw#90132, discord, whatsapp openclaw#71830, sms). Add sanitizeText to the NostrOutboundAdapter type and adapter, matching those precedents. Co-Authored-By: Claude <[email protected]>

The Zalo outbound adapter had no sanitizeText hook, so internal assistant tool-trace scaffolding (e.g. "⚠️ 🛠️ `exec (agent)` failed", raw <tool_call>/<function_response> XML) leaked verbatim into delivered Zalo messages. The same one-line sanitizeText hook was already shipped to 13 sibling channels (twitch openclaw#103109, mattermost openclaw#98693, feishu openclaw#98705, signal openclaw#97360, slack openclaw#97367, matrix openclaw#97372, irc openclaw#97214, telegram, googlechat openclaw#90684, qqbot openclaw#90132, discord, whatsapp openclaw#71830, sms). Add sanitizeText: ({ text }) => sanitizeAssistantVisibleText(text) to the outbound adapter, matching those precedents. Co-Authored-By: Claude <[email protected]>

The Nostr outbound adapter had no sanitizeText hook, so internal assistant tool-trace scaffolding (e.g. "⚠️ 🛠️ `exec (agent)` failed", raw <tool_call>/<function_response> XML) leaked verbatim into delivered Nostr DMs. The same one-line sanitizeText hook was already shipped to 13 sibling channels (twitch openclaw#103109, mattermost openclaw#98693, feishu openclaw#98705, signal openclaw#97360, slack openclaw#97367, matrix openclaw#97372, irc openclaw#97214, telegram, googlechat openclaw#90684, qqbot openclaw#90132, discord, whatsapp openclaw#71830, sms). Add sanitizeText to the NostrOutboundAdapter type and adapter, matching those precedents. Co-Authored-By: Claude <[email protected]>

The Zalo outbound adapter had no sanitizeText hook, so internal assistant tool-trace scaffolding (e.g. "⚠️ 🛠️ `exec (agent)` failed", raw <tool_call>/<function_response> XML) leaked verbatim into delivered Zalo messages. The same one-line sanitizeText hook was already shipped to 13 sibling channels (twitch openclaw#103109, mattermost openclaw#98693, feishu openclaw#98705, signal openclaw#97360, slack openclaw#97367, matrix openclaw#97372, irc openclaw#97214, telegram, googlechat openclaw#90684, qqbot openclaw#90132, discord, whatsapp openclaw#71830, sms). Add sanitizeText: ({ text }) => sanitizeAssistantVisibleText(text) to the outbound adapter, matching those precedents. Co-Authored-By: Claude <[email protected]>

The Nostr outbound adapter had no sanitizeText hook, so internal assistant tool-trace scaffolding (e.g. "⚠️ 🛠️ `exec (agent)` failed", raw <tool_call>/<function_response> XML) leaked verbatim into delivered Nostr DMs. The same one-line sanitizeText hook was already shipped to 13 sibling channels (twitch openclaw#103109, mattermost openclaw#98693, feishu openclaw#98705, signal openclaw#97360, slack openclaw#97367, matrix openclaw#97372, irc openclaw#97214, telegram, googlechat openclaw#90684, qqbot openclaw#90132, discord, whatsapp openclaw#71830, sms). Add sanitizeText to the NostrOutboundAdapter type and adapter, matching those precedents. Co-Authored-By: Claude <[email protected]>

The Zalo outbound adapter had no sanitizeText hook, so internal assistant tool-trace scaffolding (e.g. "⚠️ 🛠️ `exec (agent)` failed", raw <tool_call>/<function_response> XML) leaked verbatim into delivered Zalo messages. The same one-line sanitizeText hook was already shipped to 13 sibling channels (twitch openclaw#103109, mattermost openclaw#98693, feishu openclaw#98705, signal openclaw#97360, slack openclaw#97367, matrix openclaw#97372, irc openclaw#97214, telegram, googlechat openclaw#90684, qqbot openclaw#90132, discord, whatsapp openclaw#71830, sms). Add sanitizeText: ({ text }) => sanitizeAssistantVisibleText(text) to the outbound adapter, matching those precedents. Co-Authored-By: Claude <[email protected]>

The Nostr outbound adapter had no sanitizeText hook, so internal assistant tool-trace scaffolding (e.g. "⚠️ 🛠️ `exec (agent)` failed", raw <tool_call>/<function_response> XML) leaked verbatim into delivered Nostr DMs. The same one-line sanitizeText hook was already shipped to 13 sibling channels (twitch openclaw#103109, mattermost openclaw#98693, feishu openclaw#98705, signal openclaw#97360, slack openclaw#97367, matrix openclaw#97372, irc openclaw#97214, telegram, googlechat openclaw#90684, qqbot openclaw#90132, discord, whatsapp openclaw#71830, sms). Add sanitizeText to the NostrOutboundAdapter type and adapter, matching those precedents. Co-Authored-By: Claude <[email protected]>

clawsweeper Bot added channel: twitch Channel integration: twitch clawsweeper:automerge Maintainer opted this PR into bounded ClawSweeper-reviewed automerge clawsweeper Tracked by ClawSweeper automation labels Jul 9, 2026

clawsweeper Bot mentioned this pull request Jul 9, 2026

fix(twitch): strip internal tool-trace banners from outbound text #102992

Closed

openclaw-barnacle Bot added the size: XS label Jul 9, 2026

clawsweeper Bot added rating: 🦞 diamond lobster Very strong PR readiness with only minor maintainer review expected. status: 🚀 automerge armed This PR is in ClawSweeper's automerge lane. P1 High-priority user-facing bug, regression, or broken workflow. labels Jul 9, 2026

clawsweeper Bot and others added 2 commits July 9, 2026 21:23

fix(twitch): strip internal tool-trace banners from outbound text

30cea3f

Co-authored-by: Masato Hoshino <[email protected]>

fix(twitch): strip internal tool-trace banners from outbound text

3f69bfe

clawsweeper Bot force-pushed the clawsweeper/automerge-openclaw-openclaw-102992 branch from 5dad685 to 3f69bfe Compare July 9, 2026 21:30

steipete merged commit 90b6853 into main Jul 9, 2026
90 of 91 checks passed

steipete deleted the clawsweeper/automerge-openclaw-openclaw-102992 branch July 9, 2026 21:39

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

📡 Upstream Digest — 2026-07-09 23:03 UTC curtismercier/openclaw-mods#1247

Open

This was referenced Jul 10, 2026

fix(nextcloud-talk): strip internal tool-trace banners from outbound text #103355

Closed

fix(nostr): strip internal tool-trace banners from outbound text #103361

Open

fix(zalo): strip internal tool-trace banners from outbound text #103377

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

fix(twitch): strip internal tool-trace banners from outbound text#103109

fix(twitch): strip internal tool-trace banners from outbound text#103109
steipete merged 2 commits into
mainfrom
clawsweeper/automerge-openclaw-openclaw-102992

clawsweeper Bot commented Jul 9, 2026

Uh oh!

clawsweeper Bot commented Jul 9, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented Jul 9, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Uh oh!

Conversation

clawsweeper Bot commented Jul 9, 2026

Source

Uh oh!

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

Uh oh!

Uh oh!

clawsweeper Bot commented Jul 9, 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 Jul 9, 2026 •

edited

Loading

clawsweeper Bot commented Jul 9, 2026 •

edited

Loading