fix(auto-reply): honor webchat textChunkLimit/chunkMode config overrides [AI-assisted] by clawsweeper[bot] · Pull Request #83742 · openclaw/openclaw

clawsweeper · 2026-05-18T20:01:58Z

Makes #83713 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.

ClawSweeper 🐠 replacement reef notes:

Cluster: automerge-openclaw-openclaw-83713
Source PRs: fix(auto-reply): honor webchat textChunkLimit/chunkMode config overrides [AI-assisted] #83713
Credit: Source PR: fix(auto-reply): honor webchat textChunkLimit/chunkMode config overrides [AI-assisted] #83713
Validation: pnpm check:changed
Replacement reason: ClawSweeper could not update the source PR branch directly, so it opened a writable replacement PR instead.
Automerge requested by: @Takhoffman

Repair fallback: GitHub rejected the repair branch push because it updates workflow files and the ClawSweeper app token does not have workflows permission

Inherited issue-closing references from the source PR:
Closes #83658

Co-author credit kept:

@luyao618: Co-authored-by: Yao 17723416+luyao618@users.noreply.github.com

fish notes: model gpt-5.5, reasoning high; reviewed against cd9ac01.

The webchat channel was explicitly bypassed in resolveTextChunkLimit and resolveChunkMode, hardcoding the 4000-char default and ignoring any channels.webchat.textChunkLimit override in user config. This made long WebChat assistant responses get cut at ~4000 chars with no escape hatch. Drop the INTERNAL_MESSAGE_CHANNEL special-case so webchat goes through the same provider config lookup as every other channel. The 4000-char fallback still applies when no override is configured, preserving existing behavior for users who do not set channels.webchat.textChunkLimit. Closes #83658

…des [AI-assisted]

clawsweeper · 2026-05-18T20:03:08Z

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 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.

Summary
This PR removes the WebChat special-case from auto-reply chunk limit/mode resolution, adds WebChat override regression tests, and records the fix in the changelog.

Reproducibility: yes. from source inspection rather than runtime execution: current main returns the fallback for provider webchat before reading cfg.channels, so a configured channels.webchat.textChunkLimit cannot take effect.

PR rating
Overall: 🐚 platinum hermit
Proof: 🐚 platinum hermit
Patch quality: 🐚 platinum hermit
Summary: Small targeted fix with focused regression coverage and no blocking findings; proof is accepted by override rather than a live WebChat artifact.

Rank-up moves:

A maintainer can request the visual Mantis proof if they want UI-level confirmation beyond the resolver tests.

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.

PR egg
✨ Hatched: 🥚 common Tiny Diff Drake

        /\     /\            
      _/  \___/  \_          
     /  ( o   o )  \         
    |      \_/      |        
    |   /\  ===  /\ |        
     \_/  \_____/  \_/       
        _/|_| |_|\_          
       /__| | | |__\         
          ' ' ' '            
         /_/     \_\         
       .-----------.         
      '-------------'

Rarity: 🥚 common.
Trait: sleeps inside passing CI.
Share on X: post this hatch
Copy: My PR egg hatched a 🥚 common Tiny Diff Drake in ClawSweeper.

What is this egg doing here?

Eggs appear after the PR passes real-behavior proof. It is here for vibes, not verdicts: it does not change labels, ratings, merge decisions, or automation.
The shell reacts to review momentum: open follow-up work warms it up, re-review makes it wobble, and a clean final review lets it hatch.
How to hatch it: reach status: 👀 ready for maintainer look or status: 🚀 automerge armed; that usually means sufficient real-behavior proof, no blocking P0/P1/P2 findings, no security attention needed, and clean correctness.
The hatch is seeded from this repository and PR number, so the same PR keeps the same creature; the reviewed head SHA can only change safe visual details.
Rarity is just collectible sparkle: 🥚 common, 🌱 uncommon, 💎 rare, ✨ glimmer, and 🌈 legendary.

Real behavior proof
Override: A maintainer applied proof: override for this PR.

Mantis proof suggestion
The changed behavior is visible in WebChat when a long assistant reply exceeds the old 4000-character cap and a higher override is configured. 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 WebChat with channels.webchat.textChunkLimit above 4000 renders a long assistant reply without ...(truncated)... and default config still uses 4000.

Next step before merge
No repair lane is needed; the PR has no blocking findings and should proceed through automerge/check gating rather than a separate fix PR.

Security
Cleared: The diff only touches auto-reply resolver logic, focused tests, and the changelog; it adds no dependency, workflow, credential, permission, or code-execution surface.

Review details

Best possible solution:

Land this replacement PR after the normal automerge/check gates so explicit WebChat chunk overrides work while default WebChat chunking remains unchanged.

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

Yes, from source inspection rather than runtime execution: current main returns the fallback for provider webchat before reading cfg.channels, so a configured channels.webchat.textChunkLimit cannot take effect.

Is this the best way to solve the issue?

Yes. Removing only the INTERNAL_MESSAGE_CHANNEL guard is the narrowest maintainable fix because the provider config lookup, fallback handling, and chunk-mode resolution already exist and the PR adds targeted tests for override and default behavior.

Label justifications:

P2: The PR fixes a real WebChat message truncation bug with limited blast radius and no emergency availability or security impact.

What I checked:

Current main ignores WebChat chunk limit config: On current main, resolveTextChunkLimit returns undefined for provider overrides when the provider is INTERNAL_MESSAGE_CHANNEL, and that constant is webchat, so channels.webchat.textChunkLimit cannot be reached. (src/auto-reply/chunk.ts:67, 583a60f8b5a4)
Current main ignores WebChat chunk mode config: On current main, resolveChunkMode returns the default mode before provider config lookup when the provider is webchat. (src/auto-reply/chunk.ts:105, 583a60f8b5a4)
PR implementation keeps the fallback but allows provider lookup: At the PR head, both resolvers only short-circuit when provider is absent, so WebChat now reaches the existing cfg.channels[provider] lookup and still falls back when no override exists. (src/auto-reply/chunk.ts:66, cd9ac01a3634)
PR adds focused regression coverage: The PR adds table cases for channels.webchat.textChunkLimit, the no-override 4000 fallback, and channels.webchat.chunkMode = "newline". (src/auto-reply/chunk.test.ts:334, cd9ac01a3634)
Runtime call path uses the resolver: Block streaming resolves the normalized provider key, calls resolveTextChunkLimit, then uses resolveChunkMode to decide paragraph flushing, so the PR touches the implicated WebChat live reply path. (src/auto-reply/reply/block-streaming.ts:26, 583a60f8b5a4)
Channel config accepts plugin-style channel sections: The channel config schema is passthrough, so channels.webchat is not rejected by schema validation even though WebChat is an internal channel. (src/config/zod-schema.channels-config.ts:64, 583a60f8b5a4)

Likely related people:

steipete: Blame and history show Peter Steinberger on the current resolver body and on the original configurable outbound text chunk limit work plus later chunking refactors. (role: feature-history owner and recent area contributor; confidence: high; commits: 4f4d10863916, 5684e2d658db, 0f9e16ca463b; files: src/auto-reply/chunk.ts, src/auto-reply/reply/block-streaming.ts, src/auto-reply/chunk.test.ts)
tyler6204: History shows Tyler Yust introduced the chunk mode option and related tests that this PR extends to WebChat. (role: chunk mode feature contributor; confidence: medium; commits: 92e794dc1812; files: src/auto-reply/chunk.ts, src/auto-reply/chunk.test.ts, src/auto-reply/reply/block-streaming.ts)
vincentkoc: Recent history shows Vincent Koc changed the canonical streaming/chunk mode config helper used by resolveChunkModeForProvider. (role: adjacent config normalization contributor; confidence: medium; commits: 0fdf9e874b7e; files: src/auto-reply/chunk.ts, src/plugin-sdk/channel-streaming.ts, src/config/types.base.ts)

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

clawsweeper · 2026-05-18T20:09:18Z

ClawSweeper 🐠 automerge status

This repair pass finished without changing the PR. ClawSweeper checked the branch and found no safe patch to push this time.

Executor outcome: no planned fix actions.
Worker summary: No further repair action is needed. The uneditable source PR #83713 was superseded by writable replacement this PR, and this PR is already merged on current main at 424c6d0. Linked issue #83658 and both PRs are already closed, so this result only records skipped keep-closed classifications.

Worker actions:

keep_closed on #83713: skipped - Source PR was already superseded by replacement this PR before this worker result.
keep_closed on this PR: skipped - Replacement PR is the canonical landed fix for this automerge cluster.
keep_closed on #83658: skipped - The issue is already closed after the canonical fix landed.

Nothing moved downstream from this pass: no branch update, replacement PR, merge, or re-review.

fish notes: model gpt-5.5, reasoning high; reviewed against cd9ac01.

Automerge progress:

2026-05-18 20:08:55 UTC review passed cd9ac01a3634 (structured ClawSweeper verdict: pass (sha=cd9ac01a363412f3dc56730d58e9cb05742d4...)

2026-05-18 20:09:17 UTC repair queued cd9ac01a3634 (autonomous) Run: https://github.com/openclaw/clawsweeper/actions/runs/26057633800

2026-05-18 20:09:44 UTC merged cd9ac01a3634 (merged by ClawSweeper automerge)

2026-05-18 20:09:57 UTC review queued cd9ac01a3634 (queued)

2026-05-18 20:13:26 UTC repair started (running) in 1s Run: https://github.com/openclaw/clawsweeper/actions/runs/26057633800 automerge-openclaw-openclaw-83713

2026-05-18 20:13:30 UTC repair completed cd9ac01a3634 (no branch change) in 4s Run: https://github.com/openclaw/clawsweeper/actions/runs/26057633800 no planned fix actions

…des [AI-assisted] (#83742) Summary: - This PR removes the WebChat special-case from auto-reply chunk limit/mode resolution, adds WebChat override regression tests, and records the fix in the changelog. - Reproducibility: yes. from source inspection rather than runtime execution: current main returns the fallbac ... bchat` before reading `cfg.channels`, so a configured `channels.webchat.textChunkLimit` cannot take effect. Automerge notes: - PR branch already contained follow-up commit before automerge: fix(auto-reply): honor webchat textChunkLimit/chunkMode config overri… Validation: - ClawSweeper review passed for head cd9ac01a363412f3dc56730d58e9cb05742d4a8c. - Required merge gates passed before the squash merge. Prepared head SHA: cd9ac01a363412f3dc56730d58e9cb05742d4a8c Review: openclaw/openclaw#83742 (comment) Co-authored-by: luyao618 <364939526@qq.com> 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: takhoffman Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>

…des [AI-assisted] (openclaw#83742) Summary: - This PR removes the WebChat special-case from auto-reply chunk limit/mode resolution, adds WebChat override regression tests, and records the fix in the changelog. - Reproducibility: yes. from source inspection rather than runtime execution: current main returns the fallbac ... bchat` before reading `cfg.channels`, so a configured `channels.webchat.textChunkLimit` cannot take effect. Automerge notes: - PR branch already contained follow-up commit before automerge: fix(auto-reply): honor webchat textChunkLimit/chunkMode config overri… Validation: - ClawSweeper review passed for head cd9ac01. - Required merge gates passed before the squash merge. Prepared head SHA: cd9ac01 Review: openclaw#83742 (comment) Co-authored-by: luyao618 <364939526@qq.com> 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: takhoffman Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>

luyao618 and others added 2 commits May 18, 2026 20:01

fix(auto-reply): honor webchat textChunkLimit/chunkMode config overri…

cd9ac01

…des [AI-assisted]

clawsweeper Bot mentioned this pull request May 18, 2026

fix(auto-reply): honor webchat textChunkLimit/chunkMode config overrides [AI-assisted] #83713

Closed

4 tasks

clawsweeper Bot added status: 🚀 automerge armed This PR is in ClawSweeper's automerge lane. and removed status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. labels May 18, 2026

clawsweeper Bot merged commit 424c6d0 into main May 18, 2026
156 of 166 checks passed

clawsweeper Bot deleted the clawsweeper/automerge-openclaw-openclaw-83713 branch May 18, 2026 20:09

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

📡 Upstream Digest — 2026-05-18 21:03 UTC curtismercier/openclaw-mods#893

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(auto-reply): honor webchat textChunkLimit/chunkMode config overrides [AI-assisted]#83742

fix(auto-reply): honor webchat textChunkLimit/chunkMode config overrides [AI-assisted]#83742
clawsweeper[bot] merged 2 commits into
mainfrom
clawsweeper/automerge-openclaw-openclaw-83713

clawsweeper Bot commented May 18, 2026

Uh oh!

clawsweeper Bot commented May 18, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented May 18, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

clawsweeper Bot commented May 18, 2026

Uh oh!

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

Uh oh!

Uh oh!

clawsweeper Bot commented May 18, 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 May 18, 2026 •

edited

Loading

clawsweeper Bot commented May 18, 2026 •

edited

Loading