fix(reply): suppress per-message finals across multi-message block streaming by yetval · Pull Request #95432 · openclaw/openclaw

yetval · 2026-06-21T00:25:41Z

Summary

When an agent turn produces two or more assistant messages (the common text then tool-call then text shape), block streaming re-delivers each fully-streamed assistant message a second time as its final reply. The user sees every message stream live, then receives the same messages again in full: duplicate chat messages on Telegram, Discord, Slack, and other channels.

Root cause

createBlockReplyPipeline tracked every streamed text block in one flat array and suppressed a final payload only when the join of all fragments across all assistant messages equaled that payload.

src/auto-reply/reply/block-reply-pipeline.ts (before):

const streamedTextFragments: string[] = [];
// ...
streamedTextFragments.push(reply.trimmedText);
// ...
return normalize(streamedTextFragments.join("")) === normalize(reply.trimmedText);

The end-of-turn payloads are one per assistant message. The join of every fragment across every message ("Alpha one.Alpha two.Beta one.Beta two.") never equals one message's final ("Alpha one. Alpha two."), so hasSentPayload returns false and preserveUnsentMediaAfterBlockSend (agent-runner-payloads.ts) re-delivers it. The sibling direct-send path hasDirectlySentText already groups fragments by assistantMessageIndex; the pipeline did not.

This is reachable with the coalescer disabled, a real production path: src/auto-reply/reply/acp-projector.ts builds the pipeline with coalescing: undefined for ACP live delivery, so every streamed block is delivered separately.

Fix

Group streamed fragments by assistantMessageIndex and suppress a final when any single message's fragment join matches it.

src/auto-reply/reply/block-reply-pipeline.ts (after):

const streamedTextFragmentsByMessage = new Map<number | undefined, string[]>();
// ...
const assistantMessageIndex = getReplyPayloadMetadata(payload)?.assistantMessageIndex;
const fragments = streamedTextFragmentsByMessage.get(assistantMessageIndex) ?? [];
fragments.push(reply.trimmedText);
streamedTextFragmentsByMessage.set(assistantMessageIndex, fragments);
// ...
for (const fragments of streamedTextFragmentsByMessage.values()) {
  if (fragments.length > 0 && normalize(fragments.join("")) === target) {
    return true;
  }
}
return false;

Matching against any one message's join (rather than the final payload's own index) keeps suppression correct even though the per-message finals are stamped from a single assistantMessageIndex value.

Why this is the right boundary

The defect and the fix live entirely in the block-streaming suppression predicate. The change makes it symmetric with the already-correct hasDirectlySentText direct-send path in the same module family, so both streamed-delivery paths share one rule. No config or protocol surface changes. Single-message turns (one message split into multiple blocks) stay suppressed, and a payload spanning multiple messages is correctly not suppressed.

Verification

node scripts/run-vitest.mjs on the new src/auto-reply/reply/block-reply-pipeline.multi-message.test.ts plus the adjacent block-reply-pipeline and agent-runner-payloads suites: all pass (3 new, 89 adjacent).
node scripts/run-oxlint.mjs and oxfmt --check on the changed files: clean.
node scripts/run-tsgo.mjs for tsconfig.core.json and test/tsconfig/tsconfig.core.test.json: clean.
The new test fails on pristine main and passes with the patch.

Real behavior proof

Behavior addressed: a two-assistant-message turn re-delivers each fully-streamed message as a duplicate final reply.
Real environment tested: the real production createBlockReplyPipeline from src/auto-reply/reply/block-reply-pipeline.ts driven on pristine main (ba34052) and on the patched tree with identical streamed input; the pipeline, its coalescer-disabled delivery, and the real hasSentPayload suppression predicate that the dispatcher uses all stayed real, nothing mocked.
Exact steps or command run after this patch: stream two assistant messages, each as two blocks (assistantMessageIndex 0 then 1), flush the pipeline, then append every end-of-turn final the suppression predicate does not recognize as already sent, and print the resulting delivered-to-chat sequence.
Evidence after fix:

# BEFORE (pristine main ba34052a0e)
messages delivered to chat (6):
  1. Alpha one.
  2. Alpha two.
  3. Beta one.
  4. Beta two.
  5. Alpha one. Alpha two.
  6. Beta one. Beta two.
# AFTER (this patch, identical inputs)
messages delivered to chat (4):
  1. Alpha one.
  2. Alpha two.
  3. Beta one.
  4. Beta two.

Observed result after fix: the two fully-streamed messages are no longer appended a second time, so the chat receives four messages instead of six on identical input.
What was not tested: no live channel round trip (Telegram/Discord/Slack delivery transport); the coalescer-enabled path, where the same duplication needs a message longer than the coalescer max chars to flush mid-stream, was not separately driven; full build not run.

clawsweeper · 2026-06-21T00:27:19Z

Codex review: needs maintainer review before merge. Reviewed June 21, 2026, 9:18 PM ET / 01:18 UTC.

Summary
This PR changes createBlockReplyPipeline to track streamed text fragments per assistant message and adds regression tests for duplicate final suppression after multi-message block streaming.

PR surface: Source +9, Tests +61. Total +70 across 2 files.

Reproducibility: yes. at source level. Current main and v2026.6.9 aggregate all streamed fragments before comparing to each final, so two separately streamed assistant messages cannot suppress their own final payloads.

Review metrics: none identified.

Merge readiness
Overall: 🐚 platinum hermit
Proof: 🦞 diamond lobster
Patch quality: 🐚 platinum hermit
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:

[P2] Resolve or rerun the three failing exact-head CI checks before merge.
Use a short Telegram Desktop proof run if maintainers want visible channel confirmation.

Mantis proof suggestion
A native Telegram recording would directly show that a streamed turn with two assistant messages no longer sends duplicate final bubbles. A maintainer can ask Mantis to capture proof by posting this exact PR comment:

@openclaw-mantis telegram desktop proof: verify a streamed turn with two assistant messages shows each block once and no duplicate final bubbles.

Risk before merge

[P1] The patch changes shared final-reply suppression; an incorrect match would be visible as duplicated or missing assistant messages across block-streaming channels.
[P1] Exact-head CI currently has three failing checks that need rerun, diagnosis, or maintainer acceptance before landing.
[P1] The contributor proof drives the real core pipeline, but there is no live Telegram, Discord, or Slack round trip showing the visible channel result.

Maintainer options:

Resolve Checks Then Land (recommended)
Rerun or resolve the failing exact-head checks, then land the scoped suppression fix with the regression tests intact.
Add Transport Proof
Ask for a short Telegram or equivalent live-channel proof if maintainers want visual confirmation that duplicate final bubbles disappear.
Pause For Broader Contract
Pause only if maintainers want this folded into a broader shared reply-final suppression contract with the preview and delivery-mirror duplicate trackers.

Next step before merge

No automated repair lane is indicated; maintainers should resolve exact-head CI and decide whether optional live transport proof is needed before landing.

Security
Cleared: No concrete security or supply-chain concern was found; the diff is limited to TypeScript reply-delivery logic and tests.

Review details

Best possible solution:

Land the narrow core suppression fix after exact-head CI is green or accepted as unrelated, with optional Telegram Desktop proof if maintainers want visible channel confirmation.

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

Yes, at source level. Current main and v2026.6.9 aggregate all streamed fragments before comparing to each final, so two separately streamed assistant messages cannot suppress their own final payloads.

Is this the best way to solve the issue?

Yes. The fix stays in the existing block-streaming suppression predicate, mirrors the sibling per-message grouping rule, and avoids channel, protocol, or config changes.

AGENTS.md: found and applied where relevant.

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

Label changes

Label justifications:

P1: The PR targets user-visible duplicate assistant reply delivery in shared streamed channel workflows.
merge-risk: 🚨 message-delivery: The diff changes when shared block-streaming delivery suppresses final payloads, which can directly affect duplicated or missing messages.
rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🦞 diamond lobster and patch quality is 🐚 platinum hermit.
status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (terminal): The PR body includes before/after terminal output from driving the real production block reply pipeline with identical two-message streamed input, showing duplicate finals disappear.
proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes before/after terminal output from driving the real production block reply pipeline with identical two-message streamed input, showing duplicate finals disappear.
mantis: telegram-visible-proof: Mantis should capture Telegram visible proof. The shared reply-delivery change can visibly remove duplicate final bubbles in Telegram, so a short Telegram Desktop recording would be useful.

Evidence reviewed

PR surface:

Source +9, Tests +61. Total +70 across 2 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	1	13	4	+9
Tests	1	61	0	+61
Docs	0	0	0	0
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	2	74	4	+70

What I checked:

PR diff: The PR replaces the flat streamedTextFragments array with a Map keyed by assistantMessageIndex and adds a focused multi-message regression test file. (src/auto-reply/reply/block-reply-pipeline.ts:114, af592d77b0df)
Current main behavior: Current main still records every streamed text fragment in one flat array and compares the aggregate join against each final payload. (src/auto-reply/reply/block-reply-pipeline.ts:123, 29eba5aaefa2)
Final suppression boundary: buildReplyPayloads calls blockReplyPipeline.hasSentPayload before dropping text-only finals, so the changed predicate is the central block-streaming duplicate-final gate. (src/auto-reply/reply/agent-runner-payloads.ts:388, 29eba5aaefa2)
Sibling invariant: The direct-send sibling path already groups sent fragments by assistantMessageIndex, supporting the PR's chosen ownership boundary. (src/auto-reply/reply/agent-runner-payloads.ts:358, 29eba5aaefa2)
Metadata propagation: Embedded block replies are tagged with assistantMessageIndex, and assistant message state increments across logical assistant messages. (src/agents/embedded-agent-subscribe.ts:319, 29eba5aaefa2)
Documented behavior: The streaming docs state that exact duplicate final payloads are suppressed and that already-streamed media/final content should stay single-delivery. Public docs: docs/concepts/streaming.md. (docs/concepts/streaming.md:63, 29eba5aaefa2)

Likely related people:

vincentkoc: Current-main blame and GitHub commit history point to recent work on block-reply-pipeline.ts, direct block delivery evidence, and reply final-suppression code. (role: recent area contributor; confidence: high; commits: 1c63da09d87b, 6c85b90469f9, 389c0aba98cb; files: src/auto-reply/reply/block-reply-pipeline.ts, src/auto-reply/reply/agent-runner-payloads.ts)
liuhao1024: Authored the recent merged fix preserving unsent text-only finals after partial block streaming, which changed the same block pipeline and payload suppression surface. (role: adjacent final-suppression contributor; confidence: medium; commits: a67ae8137d6b; files: src/auto-reply/reply/block-reply-pipeline.ts, src/auto-reply/reply/agent-runner-payloads.ts)
sandieman2: Authored recent routed-thread and final-delivery dedupe work in the shared reply payload path that maintainers should compare against this suppression change. (role: adjacent reply-dedupe contributor; confidence: medium; commits: c67dc59b02b0; files: src/auto-reply/reply/agent-runner-payloads.ts, src/auto-reply/reply/reply-payloads-dedupe.ts, src/auto-reply/reply/dispatch-from-config.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.

…reaming Block streaming tracked all streamed text fragments in one flat array and suppressed a final payload only when the concatenation of every fragment across all assistant messages equaled that payload. In a turn that streams two or more assistant messages, that aggregate never equals any single message's final text, so each fully-streamed message was re-delivered as a duplicate chat message. Group streamed fragments by assistantMessageIndex and suppress a final when any one message's fragment join matches it, mirroring the existing per-message direct-send path.

vincentkoc · 2026-06-23T08:44:09Z

Merged via squash.

Prepared head SHA: 7d7c61f3d757b28144978eec493b24e082938fea
Merge commit: 9549545dd0a0ce44e5e5b479942fb5d6d56a8062

Thanks @yetval!

@vincentkoc

…reaming (openclaw#95432) Merged via squash. Prepared head SHA: 7d7c61f Co-authored-by: yetval <102706514+yetval@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc

@vincentkoc

…reaming (openclaw#95432) Merged via squash. Prepared head SHA: 7d7c61f Co-authored-by: yetval <102706514+yetval@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc

…026.6.11) (#1344) 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.10` → `2026.6.11` | --- ### Release Notes <details> <summary>openclaw/openclaw (ghcr.io/openclaw/openclaw)</summary> ### [`v2026.6.11`](https://github.com/openclaw/openclaw/blob/HEAD/CHANGELOG.md#2026611) [Compare Source](https://github.com/openclaw/openclaw/compare/v2026.6.10...v2026.6.11) We heard the feedback. v2026.6.11 focuses on the rough edges that make OpenClaw feel less dependable, with fixes for misplaced replies, stuck sends, reconnects, model setup failures, and safer admin defaults. [Full release notes](https://docs.openclaw.ai/releases/2026.6.11) ##### Highlights ##### Channel delivery reliability Delivery and reconnect fixes span [Telegram](https://docs.openclaw.ai/channels/telegram), [WhatsApp](https://docs.openclaw.ai/channels/whatsapp), [Matrix](https://docs.openclaw.ai/channels/matrix), [Google Chat](https://docs.openclaw.ai/channels/googlechat), [iMessage](https://docs.openclaw.ai/channels/imessage), [Feishu](https://docs.openclaw.ai/channels/feishu), [Mattermost](https://docs.openclaw.ai/channels/mattermost), [WebChat](https://docs.openclaw.ai/web/webchat), the [Control UI](https://docs.openclaw.ai/web/control-ui), and the [terminal UI](https://docs.openclaw.ai/cli/tui). - Fixes newer Google Chat direct messages sometimes being treated like group conversations, so they reach the correct one-to-one chat while Space and group-chat messages keep their existing routing. [#58993](https://github.com/openclaw/openclaw/pull/58993) Thanks [@starhappysh](https://github.com/starhappysh), [@vincentkoc](https://github.com/vincentkoc). - Feishu voice replies from OpenClaw now show their duration in the chat bubble, so recipients can see how long the audio is before playing it. [#89172](https://github.com/openclaw/openclaw/pull/89172) Related [#53798](https://github.com/openclaw/openclaw/issues/53798). Thanks [@areslp](https://github.com/areslp), [@fxz26284407](https://github.com/fxz26284407), [@kinrocw](https://github.com/kinrocw). - Discord and Telegram replies and mirrored chat history stay tied to the intended conversation more consistently, including across repeated Telegram replies and session changes. [#89911](https://github.com/openclaw/openclaw/pull/89911) Thanks [@jalehman](https://github.com/jalehman). - Background image, video, and music results now return to the chat that requested them when the task starts without a full conversation target, instead of appearing to fail after creation or being sent to the wrong peer as the session moves. [#89949](https://github.com/openclaw/openclaw/pull/89949) Related [#86034](https://github.com/openclaw/openclaw/issues/86034). Thanks [@tianxiaochannel-oss88](https://github.com/tianxiaochannel-oss88), [@wangwllu](https://github.com/wangwllu). - Telegram answers now stay attached to the user's current question when they quote an earlier bot message, while quotes of other people's messages still reply to the selected quote. [#90475](https://github.com/openclaw/openclaw/pull/90475) Thanks [@moeedahmed](https://github.com/moeedahmed). - QQBot group admins can choose how broadly slash commands are available, and private-only commands now direct users to a private chat instead of being exposed or silently ignored in groups. [#92154](https://github.com/openclaw/openclaw/pull/92154) Thanks [@sliverp](https://github.com/sliverp). - Heartbeat checks using reasoning-capable models now show the assistant's intended reply instead of exposing internal reasoning in Telegram, WhatsApp, and other channels, while opt-in Thinking messages still work. [#92356](https://github.com/openclaw/openclaw/pull/92356) Related [#92260](https://github.com/openclaw/openclaw/issues/92260). Thanks [@jmpei](https://github.com/jmpei), [@tangtaizong666](https://github.com/tangtaizong666), [@vincentkoc](https://github.com/vincentkoc). - Telegram progress-mode chats now clear an old progress bubble before newer tool output or artifacts appear, keeping the conversation in a clean, readable order. [#93002](https://github.com/openclaw/openclaw/pull/93002) Related [#90753](https://github.com/openclaw/openclaw/issues/90753). Thanks [@shadow-enthusiast](https://github.com/shadow-enthusiast), [@zhangguiping-xydt](https://github.com/zhangguiping-xydt). - iMessage command-and-link messages now stay together as one OpenClaw turn when delayed link previews arrive, while unrelated quick messages remain separate for users who enabled same-sender DM coalescing. [#93143](https://github.com/openclaw/openclaw/pull/93143) Thanks [@omarshahine](https://github.com/omarshahine). - Successful Discord replies sent through the message tool no longer trigger a misleading failure warning in affected `message_tool_only` source-channel turns. [#94072](https://github.com/openclaw/openclaw/pull/94072) Related [#93875](https://github.com/openclaw/openclaw/issues/93875). Thanks [@chenyangjun-xy](https://github.com/chenyangjun-xy), [@hoyanhan](https://github.com/hoyanhan), [@vincentkoc](https://github.com/vincentkoc). - WhatsApp group conversations now preserve the right message and group context more reliably during retries, reconnects, and group changes. [#94338](https://github.com/openclaw/openclaw/pull/94338) Related [#7433](https://github.com/openclaw/openclaw/issues/7433). Thanks [@mcaxtr](https://github.com/mcaxtr), [@octopuslabs-fl](https://github.com/octopuslabs-fl), [@xialonglee](https://github.com/xialonglee). - Fixes OpenClaw sometimes replying to its own delayed iMessage echoes when stray leading characters keep the sent message from being recognized. [#94442](https://github.com/openclaw/openclaw/pull/94442) Thanks [@ly-wang19](https://github.com/ly-wang19). - Telegram webhook users can keep receiving DMs and group messages through brief channel restarts, configuration reloads, and recovery cycles without temporary message blackouts. [#94506](https://github.com/openclaw/openclaw/pull/94506) Related [#90254](https://github.com/openclaw/openclaw/issues/90254). Thanks [@obviyus](https://github.com/obviyus), [@travellingsoldier85](https://github.com/travellingsoldier85), [@xialonglee](https://github.com/xialonglee). - Matrix E2EE gateways can stay online during long-running use instead of gradually consuming memory until a crash takes channels and in-flight work down. [#94942](https://github.com/openclaw/openclaw/pull/94942) Related [#90455](https://github.com/openclaw/openclaw/issues/90455). Thanks [@xzh-icenter](https://github.com/xzh-icenter), [@yar-sh](https://github.com/yar-sh). - Telegram users now see the intended native reaction instead of leaked instructions or a dropped reaction-only reply, with success recorded only after Telegram accepts it. [#94977](https://github.com/openclaw/openclaw/pull/94977) Related [#71140](https://github.com/openclaw/openclaw/issues/71140). Thanks [@cuttingwater](https://github.com/cuttingwater), [@hugenshen](https://github.com/hugenshen). - Telegram progress updates for commands, searches, updates, and API activity now stay readable instead of exposing noisy HTML or code-style rows, with plain-text fallback when Telegram cannot parse the formatting. [#95007](https://github.com/openclaw/openclaw/pull/95007) Related [#95002](https://github.com/openclaw/openclaw/issues/95002). - Telegram conversations continued in WebChat now show one assistant reply per turn and keep later replies with the active conversation instead of duplicating answers or sending them back to Telegram. [#95069](https://github.com/openclaw/openclaw/pull/95069) Related [#94930](https://github.com/openclaw/openclaw/issues/94930). Thanks [@heichaowo](https://github.com/heichaowo). - Google Chat now hides misleading internal failure banners when a tool result is harmless, leaving users with the completed answer while normal assistant text remains unchanged. [#95084](https://github.com/openclaw/openclaw/pull/95084) Related [#90684](https://github.com/openclaw/openclaw/issues/90684). Thanks [@jailbirt](https://github.com/jailbirt), [@studentzhou-svg](https://github.com/studentzhou-svg). - Bound multi-agent channel conversations now load the workspace files for the configured agent instead of the default agent, though previously misfiled conversations may start fresh in the corrected agent store. [#95118](https://github.com/openclaw/openclaw/pull/95118) Related [#92903](https://github.com/openclaw/openclaw/issues/92903). Thanks [@849261680](https://github.com/849261680), [@axjing](https://github.com/axjing). - People sharing an OpenClaw gateway can now assign different models to individual direct-message contacts across supported chat channels, while existing group and wildcard model choices keep working as before. [#95120](https://github.com/openclaw/openclaw/pull/95120) Related [#53638](https://github.com/openclaw/openclaw/issues/53638). Thanks [@gandalf-at-lerian](https://github.com/gandalf-at-lerian), [@thomaszta](https://github.com/thomaszta), [@xydigit-zt](https://github.com/xydigit-zt). - Telegram now shows that OpenClaw is still working during short initial previews or progress-mode replies instead of leaving the chat silent until the final message arrives. [#95183](https://github.com/openclaw/openclaw/pull/95183) Related [#95004](https://github.com/openclaw/openclaw/issues/95004). Thanks [@obviyus](https://github.com/obviyus). - Matrix users and operators now get a clear failure when a homeserver sends an oversized or stalled response, instead of OpenClaw continuing to buffer it and risking unbounded memory use. [#95240](https://github.com/openclaw/openclaw/pull/95240) Thanks [@alix-007](https://github.com/alix-007). - Fixes delayed or missing Telegram and other queued channel replies in Kubernetes-style deployments with many injected environment variables, where opening the queue database could stall the gateway. [#95278](https://github.com/openclaw/openclaw/pull/95278) Related [#94571](https://github.com/openclaw/openclaw/issues/94571). Thanks [@kaka-srp](https://github.com/kaka-srp). - Telegram chats recover after one stuck message times out, allowing later messages in the same chat or topic to reach the agent without restarting the gateway. [#95299](https://github.com/openclaw/openclaw/pull/95299) Related [#95248](https://github.com/openclaw/openclaw/issues/95248). Thanks [@kriegerbangerz-ship-it](https://github.com/kriegerbangerz-ship-it), [@mikasa0818](https://github.com/mikasa0818), [@obviyus](https://github.com/obviyus). - When people switch between Telegram and another OpenClaw client in a shared direct conversation, short Telegram replies now follow the latest conversation instead of responding to an older, unrelated Telegram proposal. [#95390](https://github.com/openclaw/openclaw/pull/95390) Related [#95378](https://github.com/openclaw/openclaw/issues/95378). Thanks [@maiduy708](https://github.com/maiduy708), [@mikasa0818](https://github.com/mikasa0818), [@obviyus](https://github.com/obviyus). - Fixes completed assistant messages appearing twice in Telegram, Discord, Slack, and other streamed chats after a multi-message reply. [#95432](https://github.com/openclaw/openclaw/pull/95432) Thanks [@vincentkoc](https://github.com/vincentkoc), [@yetval](https://github.com/yetval). - WhatsApp replies now stay attached to the direct or group message being answered instead of appearing as a separate message that loses the conversation context. [#95483](https://github.com/openclaw/openclaw/pull/95483) Thanks [@mcaxtr](https://github.com/mcaxtr). - Telegram rich-message replies now keep paragraphs, bullets, and status lines separated instead of collapsing multi-line content into one run-on block, with no configuration change required. [#95532](https://github.com/openclaw/openclaw/pull/95532) Related [#95409](https://github.com/openclaw/openclaw/issues/95409). Thanks [@amknight](https://github.com/amknight). - Mattermost operators who enable native slash commands can now use `/oc_queue` directly in Mattermost to tune active-run queuing, including its mode, debounce timing, cap, and drop handling. [#95546](https://github.com/openclaw/openclaw/pull/95546) Thanks [@amknight](https://github.com/amknight). - Previously allowed messages keep reaching named accounts after legacy multi-account channel upgrades, with inherited DM and group access rules preserved across Mattermost, Discord, Slack, Telegram, Signal, WhatsApp, iMessage, and IRC. [#95550](https://github.com/openclaw/openclaw/pull/95550) Thanks [@amknight](https://github.com/amknight). - Mattermost users can keep talking in a thread without mentioning the bot again after it replies, and that participation survives gateway restarts until the thread has been idle for seven days. [#95552](https://github.com/openclaw/openclaw/pull/95552) Thanks [@amknight](https://github.com/amknight). - Inbound Telegram messages now reach the configured OpenClaw session promptly instead of sitting unanswered until the next polling interval, a gateway restart, or manual intervention. [#95577](https://github.com/openclaw/openclaw/pull/95577) Related [#86957](https://github.com/openclaw/openclaw/issues/86957). Thanks [@freidrich-goldenflow](https://github.com/freidrich-goldenflow), [@liuwqgit](https://github.com/liuwqgit). - QQBot users now receive complete markdown tables when valid separators use one or two dashes per column, instead of losing the header and all but the final row. [#95637](https://github.com/openclaw/openclaw/pull/95637) Thanks [@ly-wang19](https://github.com/ly-wang19). - Synology Chat users can now receive agent replies that take more than 120 seconds when the configured core timeout allows it, instead of having the channel reject them early. [#95707](https://github.com/openclaw/openclaw/pull/95707) Thanks [@sahibzada-allahyar](https://github.com/sahibzada-allahyar), [@vincentkoc](https://github.com/vincentkoc). - Telegram forum-topic cron jobs now keep separately configured failure alerts going to their intended destination, even when the main announcement uses a topic in the same chat. [#95794](https://github.com/openclaw/openclaw/pull/95794) Thanks [@vincentkoc](https://github.com/vincentkoc). - Fixes WhatsApp group replies that could quote an older OpenClaw message instead of the user's triggering message, so final answers stay attached to the intended message when a reply target is available and avoid pointing back to stale bot context when it is not. [#95914](https://github.com/openclaw/openclaw/pull/95914) Thanks [@mcaxtr](https://github.com/mcaxtr). - WhatsApp users can approve or deny prompts by reaction without the prompt staying stuck when WhatsApp identifies the same direct chat differently, while group approvals remain tied to the correct group and person. [#95935](https://github.com/openclaw/openclaw/pull/95935) Thanks [@mcaxtr](https://github.com/mcaxtr). - Final reply processing now uses less CPU when OpenClaw checks whether block text was already sent, without changing which reply reaches the chat or how duplicate text is suppressed. [#96087](https://github.com/openclaw/openclaw/pull/96087) Thanks [@vincentkoc](https://github.com/vincentkoc). - Exec approval results from external channel plugins now return to the channel or DM where the command started instead of falling back to WebChat or seeming to disappear after approval. [#96140](https://github.com/openclaw/openclaw/pull/96140) Related [#96103](https://github.com/openclaw/openclaw/issues/96103). Thanks [@lansenger-pm](https://github.com/lansenger-pm), [@vincentkoc](https://github.com/vincentkoc), [@yetval](https://github.com/yetval). - WhatsApp's final answer now stays quoted to the follow-up message a user just sent when replying to an older OpenClaw message, instead of arriving unquoted or pointing back to the older bot reply. [#96220](https://github.com/openclaw/openclaw/pull/96220) Thanks [@mcaxtr](https://github.com/mcaxtr). - Nextcloud Talk bots now ignore ordinary file-share and lifecycle events without logging them as bot errors or risking disabled delivery, while malformed chat payloads still return an error. [#96243](https://github.com/openclaw/openclaw/pull/96243) Related [#81566](https://github.com/openclaw/openclaw/issues/81566). Thanks [@arkyu2077](https://github.com/arkyu2077), [@rafaelmgbh](https://github.com/rafaelmgbh), [@vincentkoc](https://github.com/vincentkoc). - Replies and message-tool delivery in Mattermost channels now use channel and thread guidance because the agent identifies those conversations as channels rather than group chats, while existing group-chat behavior remains unchanged. [#96244](https://github.com/openclaw/openclaw/pull/96244) Related [#95645](https://github.com/openclaw/openclaw/issues/95645). Thanks [@arkyu2077](https://github.com/arkyu2077), [@iloveleon19](https://github.com/iloveleon19), [@vincentkoc](https://github.com/vincentkoc). - MCP channel integrations now keep conversation lists, message reads, event polls, and waits within predictable bounds even when a client requests excessive limits or timeouts. [a39e548](https://github.com/openclaw/openclaw/commit/a39e548ede228aa1978bf9d509613cbed6db0c99) Thanks [@vincentkoc](https://github.com/vincentkoc). - Long-running streamed auto-replies are less likely to stop early or abort inconsistently when an unusually large timeout is configured. [6c85b90](https://github.com/openclaw/openclaw/commit/6c85b90469f94955ef00c1609e1f1d6fd2cf4ca8) Thanks [@vincentkoc](https://github.com/vincentkoc). - Channel progress now shows a repeated status when work genuinely returns to it after another update, instead of hiding useful context as a duplicate. [8a75c4d](https://github.com/openclaw/openclaw/commit/8a75c4dd5f3e625a22a7a08c6e1f368798c48111) - Completed channel replies no longer gain late progress notices, preventing stale status text from appearing after the answer is finished. [a594d2c](https://github.com/openclaw/openclaw/commit/a594d2ce73257326b7ab78adb3c4643245ec9431) Thanks [@vincentkoc](https://github.com/vincentkoc). - During streaming channel replies, progress messages now keep showing the latest state instead of getting stuck on an older update. [e114001](https://github.com/openclaw/openclaw/commit/e114001ccafa83b8b366e095a9d7748dfc50c082) Thanks [@vincentkoc](https://github.com/vincentkoc). - Matrix forced resets now handle unavailable secret storage without a runtime error, treating recovery access as unavailable so the reset path can continue safely. [5c5a8a4](https://github.com/openclaw/openclaw/commit/5c5a8a49d76954b53fefc2463bc7b1d6b960e8fc) Thanks [@vincentkoc](https://github.com/vincentkoc). - Configured channels now remain visible in `openclaw channels status --json`, while scheduled announcements reject stale entries that have no active plugin to deliver them. [a641c0d](https://github.com/openclaw/openclaw/commit/a641c0d560fd15373e462829facf15fd6a466aeb) - Discord voice conversations now keep back-to-back assistant responses moving, so a queued reply plays after the previous audio stream closes instead of remaining stuck. [88b64e4](https://github.com/openclaw/openclaw/commit/88b64e4b869e696d99de7417fb52425e9ed67cbf) Thanks [@vincentkoc](https://github.com/vincentkoc). - Discord progress previews are less likely to stop before the final edits when an agent response has already started arriving. [86ea382](https://github.com/openclaw/openclaw/commit/86ea382121b00e73af4b4c329d0a2447592e4071) - Chats no longer show stray `NO_REPLY` text when the assistant means to stay silent, while legitimate media responses still arrive without the placeholder. [96c6f80](https://github.com/openclaw/openclaw/commit/96c6f8022c2420826830b11f4353ce855ab2ac5c) - Telegram streaming replies now show each progress heading once, keeping tool and search updates easier to scan. [013e33c](https://github.com/openclaw/openclaw/commit/013e33c6d3672a980550912442bb1ac5505918aa) Thanks [@vincentkoc](https://github.com/vincentkoc). - Telegram messages that get stuck after a long-running task, crash, or gateway restart now resume processing automatically, so later messages no longer wait silently or require operators to repair the queue by hand. [#97543](https://github.com/openclaw/openclaw/pull/97543) Thanks [@romneyda](https://github.com/romneyda), [@vincentkoc](https://github.com/vincentkoc). ##### Provider and model recovery [Model setup](https://docs.openclaw.ai/providers/models), [OpenAI](https://docs.openclaw.ai/providers/openai), [OpenRouter](https://docs.openclaw.ai/providers/openrouter), [opencode-go](https://docs.openclaw.ai/providers/opencode-go), and [fast-mode](https://docs.openclaw.ai/tools/thinking#fast-mode-fast) follow-up behavior now recover more clearly in affected configurations. - MiniMax text-to-speech and voice notes are less likely to fail because OpenClaw now explicitly requests the audio format it can decode instead of relying on provider defaults. [#73079](https://github.com/openclaw/openclaw/pull/73079) Thanks [@efe-arv](https://github.com/efe-arv). - Gateway operators can again see provider, model, request status, and timing details in normal logs, making model-routing and transport problems easier to diagnose without enabling extra debug logging. [#89648](https://github.com/openclaw/openclaw/pull/89648) Related [#89300](https://github.com/openclaw/openclaw/issues/89300). Thanks [@enominera](https://github.com/enominera), [@xiaobao-k8s](https://github.com/xiaobao-k8s). - Models reached through Google, Mistral, OpenAI Responses, Azure OpenAI Responses, and ChatGPT/Codex Responses now receive clean system instructions without OpenClaw's internal cache-boundary marker leaking into the prompt. [#89716](https://github.com/openclaw/openclaw/pull/89716) Thanks [@enominera](https://github.com/enominera), [@masatohoshino](https://github.com/masatohoshino). - Cron tool calls using Gemini models through OpenAI-compatible providers now run without nullable fields triggering provider schema rejections. [#91559](https://github.com/openclaw/openclaw/pull/91559) Related [#91542](https://github.com/openclaw/openclaw/issues/91542). Thanks [@pick-cat](https://github.com/pick-cat), [@qiukui666](https://github.com/qiukui666). - Provider-qualified model IDs now honor their configured agent runtime policies and CLI aliases instead of unexpectedly falling back to OpenClaw's default runtime. [#91724](https://github.com/openclaw/openclaw/pull/91724) Thanks [@vincentkoc](https://github.com/vincentkoc), [@yu-xin-c](https://github.com/yu-xin-c). - The chat `/models` list and other plugin-aware model or provider selection paths now respond quickly instead of stalling for seconds and consuming a CPU core through repeated setup scans, while plugin changes still refresh normally. [#93356](https://github.com/openclaw/openclaw/pull/93356) Thanks [@obuchowski](https://github.com/obuchowski). - Hosted Ollama Cloud users can keep only the models they explicitly configured after a restart, without the full shared catalog being added back, while automatic discovery continues for local and self-hosted Ollama servers. [#93956](https://github.com/openclaw/openclaw/pull/93956) Thanks [@jason-allen-oneal](https://github.com/jason-allen-oneal). - Cron jobs can now retry or switch to a configured fallback model when a local provider returns the generic `LLM request failed.` error, instead of failing with the fallback unused. [#94062](https://github.com/openclaw/openclaw/pull/94062) Related [#93931](https://github.com/openclaw/openclaw/issues/93931). Thanks [@hugenshen](https://github.com/hugenshen). - Expired provider tokens no longer bury useful operator logs under repeated fallback warnings, while the first warning and later duplicate summaries remain available for diagnosis. [#94233](https://github.com/openclaw/openclaw/pull/94233) Related [#56979](https://github.com/openclaw/openclaw/issues/56979). Thanks [@goutamadwant](https://github.com/goutamadwant), [@yanan1991](https://github.com/yanan1991). - Google Gemini 3.5 Flash can now be selected with its full 1,048,576-token context window, avoiding missing-model errors and needless prompt-size rejections. [#94726](https://github.com/openclaw/openclaw/pull/94726) Related [#94723](https://github.com/openclaw/openclaw/issues/94723). Thanks [@ajwan8998](https://github.com/ajwan8998), [@anguslogan01](https://github.com/anguslogan01), [@kevinat](https://github.com/kevinat). - Dashboard child sessions now handle allowed provider-qualified model choices consistently and give accurate recovery guidance when saved model state is stale. [#94752](https://github.com/openclaw/openclaw/pull/94752) Related [#94713](https://github.com/openclaw/openclaw/issues/94713). Thanks [@gr4via](https://github.com/gr4via). - Claude CLI users no longer get promises of completion updates that may never arrive, because OpenClaw now blocks unsupported native background work before it can strand progress. [#95008](https://github.com/openclaw/openclaw/pull/95008) Thanks [@anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia). - OpenClaw now rejects oversized provider catalog or JSON responses with a clear error before buffering the entire response in memory. [#95218](https://github.com/openclaw/openclaw/pull/95218) Thanks [@alix-007](https://github.com/alix-007). - OpenRouter users can now select and run the advertised short DeepSeek V4 model IDs without requests failing with `model_not_found` because OpenClaw sent a duplicated provider prefix. [#95268](https://github.com/openclaw/openclaw/pull/95268) Related [#95198](https://github.com/openclaw/openclaw/issues/95198). Thanks [@daniel-alejandro-t](https://github.com/daniel-alejandro-t), [@darren2030](https://github.com/darren2030). - With `/reasoning on`, DeepSeek-style OpenAI-compatible models now show the final answer separately from their reasoning instead of folding it into the reasoning block, with no configuration change required. [#95283](https://github.com/openclaw/openclaw/pull/95283) Related [#95280](https://github.com/openclaw/openclaw/issues/95280). Thanks [@marvinthebored](https://github.com/marvinthebored), [@vincentkoc](https://github.com/vincentkoc), [@zengwen-dt](https://github.com/zengwen-dt). - When a Codex subscription reaches its usage limit, OpenClaw now moves to configured fallback models instead of stopping on the failed result, and it does not retry runs that already produced visible output. [#95400](https://github.com/openclaw/openclaw/pull/95400) Thanks [@jason-allen-oneal](https://github.com/jason-allen-oneal), [@sallyom](https://github.com/sallyom). - LM Studio users can now run quantized or multi-variant local models without false assistant-turn failures or phantom suffixed model entries caused by mismatched model keys. [#95401](https://github.com/openclaw/openclaw/pull/95401) Thanks [@monkeyleet](https://github.com/monkeyleet). - Google-backed embedded-agent runs now stop reading oversized or never-ending prompt-cache responses before they can exhaust memory or leave the run stalled. [#95417](https://github.com/openclaw/openclaw/pull/95417) Thanks [@alix-007](https://github.com/alix-007). - OpenRouter model scans fail safely on oversized or malformed catalogs instead of risking excessive memory use that can destabilize OpenClaw. [#95418](https://github.com/openclaw/openclaw/pull/95418) Thanks [@alix-007](https://github.com/alix-007). - OpenRouter setups now reject oversized model catalogs before they can exhaust OpenClaw's memory, without caching or immediately refetching the failed response. [#95420](https://github.com/openclaw/openclaw/pull/95420) Thanks [@alix-007](https://github.com/alix-007), [@sallyom](https://github.com/sallyom). - Configured fallback models can now answer when Claude CLI runs out of credits or hits a generic runner failure, instead of leaving users with the failure message as the final response. [#95508](https://github.com/openclaw/openclaw/pull/95508) Related [#95489](https://github.com/openclaw/openclaw/issues/95489). Thanks [@mikasa0818](https://github.com/mikasa0818), [@riazrahaman](https://github.com/riazrahaman), [@sallyom](https://github.com/sallyom). - Gemini-backed web searches using `freshness: "day"` or `pd` now complete instead of failing with a provider 400 error, while broader freshness choices and explicit date ranges retain stricter filtering. [#95682](https://github.com/openclaw/openclaw/pull/95682) Thanks [@sunjae-k](https://github.com/sunjae-k), [@vincentkoc](https://github.com/vincentkoc). - Follow-up answers from xAI reasoning models such as Grok Composer now preserve earlier reasoning context more reliably, even when configurable reasoning effort is unsupported. [#95686](https://github.com/openclaw/openclaw/pull/95686) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev), [@geraint0923](https://github.com/geraint0923). - Vercel AI Gateway users can now run models chosen from the live catalog, including live-only model IDs that are absent from OpenClaw's bundled list. [#95710](https://github.com/openclaw/openclaw/pull/95710) Thanks [@vincentkoc](https://github.com/vincentkoc). - Fixes manifest-defined providers turning valid model IDs into broken ones when `stripPrefixes` entries have stray spaces or different casing, so operators and plugin authors get the intended provider model. [#95744](https://github.com/openclaw/openclaw/pull/95744) Related [#95743](https://github.com/openclaw/openclaw/issues/95743). Thanks [@parveshsaini](https://github.com/parveshsaini). - First-run setup now opens the credential prompt for a newly installed external provider instead of appearing to loop and leaving OpenAI selected. [#95792](https://github.com/openclaw/openclaw/pull/95792) Related [#95765](https://github.com/openclaw/openclaw/issues/95765). - Oversized or stalled provider catalogs now fail quickly with a clear error instead of hanging OpenClaw or consuming unbounded memory, while normal catalogs continue to load. [#95827](https://github.com/openclaw/openclaw/pull/95827) Thanks [@alix-007](https://github.com/alix-007). - Xiaomi Token Plan users can now use up to 128K output tokens with `mimo-v2.5` and `mimo-v2.5-pro` instead of being stopped at the outdated 32,000-token limit. [#95934](https://github.com/openclaw/openclaw/pull/95934) Thanks [@idootop](https://github.com/idootop). - Tool-heavy model responses can stream with less overhead while repeated tool-call IDs and encrypted reasoning details stay matched to the correct call across Google and OpenAI-compatible providers. [#95957](https://github.com/openclaw/openclaw/pull/95957) Thanks [@vincentkoc](https://github.com/vincentkoc). - Token-usage accounting is more reliable for bundled ACPX users because OpenClaw now includes ACPX 0.11.2's persistence fix by default, without a separate package override or manual client update. [#96124](https://github.com/openclaw/openclaw/pull/96124) Thanks [@vincentkoc](https://github.com/vincentkoc). - Ollama Cloud users can now find and select `glm-5.2:cloud` with its 1,000,000-token context window, reasoning, and tool support even when it is absent from the public model list. [11484f8](https://github.com/openclaw/openclaw/commit/11484f8a1483b7c42aa2971de2d88289fcef7046) - MiniMax image-understanding requests no longer fail before reaching the provider when a timeout is zero, negative, or extremely large; invalid values now use a normal or safe maximum wait. [4b6182e](https://github.com/openclaw/openclaw/commit/4b6182ee2a250005e0c25edfeae4db6ec59b7cb8) Thanks [@vincentkoc](https://github.com/vincentkoc). - Codex runs now follow the current fast-mode choice instead of carrying over an old speed tier, and the status line clearly shows when fast mode is automatic. [77012f9](https://github.com/openclaw/openclaw/commit/77012f9807851c662e064d05097497a25ab13505) Thanks [@vincentkoc](https://github.com/vincentkoc). - Codex-backed conversations now return to normal routing after automatic fast mode is cleared, preventing later turns or model changes from reusing a stale priority tier. [8afc1f7](https://github.com/openclaw/openclaw/commit/8afc1f770bbef30a4d2d9957ef26a685c508448c) - Fallback agent runs now honor each model's configured automatic fast-mode cutoff even when fast mode is overridden for the run, keeping fallback behavior aligned with the selected model policy. [efd3172](https://github.com/openclaw/openclaw/commit/efd3172662ce023eb8d6568b689361536edf06dd) - Live model-switch retries now preserve the original fast-mode cutoff for long-running sessions, while explicit fast mode avoids misleading automatic-cutoff progress messages. [d990115](https://github.com/openclaw/openclaw/commit/d990115d1972fdf4361884a29bbf8396f33e5cba) Thanks [@vincentkoc](https://github.com/vincentkoc). - Embedded agent runs now keep automatic fast mode working consistently through retries and progress updates without confusing it with a manually selected fast-mode setting. [cf1b6fe](https://github.com/openclaw/openclaw/commit/cf1b6fef4403bee7c206299efc4385a7fcb74375) Thanks [@vincentkoc](https://github.com/vincentkoc). - Fast-mode runs now keep their speed setting through model fallback retries and show the configured automatic threshold in status, avoiding inconsistent retry behavior and an unhelpful generic label. [aa3797c](https://github.com/openclaw/openclaw/commit/aa3797c8d0d74b4502d24852ce6baa70286f2f06) Thanks [@vincentkoc](https://github.com/vincentkoc). - Agent replies and scheduled cron runs now handle fast-mode fallback retries more reliably, keeping the state needed for the final attempt to finish or report progress correctly. [14e448e](https://github.com/openclaw/openclaw/commit/14e448e0e13db9f194ea16bb98e0f846a67769fd) Thanks [@vincentkoc](https://github.com/vincentkoc). - Users no longer see a fast-mode reset notice while model fallback attempts are still running; it appears only when the run reaches its final fallback attempt. [6eb72a8](https://github.com/openclaw/openclaw/commit/6eb72a830ece3e2b4c6c85e5a9c2b72b59e0dae9) - Users and operators now get clearer handling when a configured live model becomes unavailable because OpenClaw recognizes the provider's "selected model was not found" response as a model-not-found failure instead of a generic error. [2405d02](https://github.com/openclaw/openclaw/commit/2405d029d437ee58ab94da800a5b213bc6bf4628) Thanks [@vincentkoc](https://github.com/vincentkoc). - Qwen and vLLM now preserve existing chat-template settings consistently when thinking is switched on or off, and provider plugins can use the same tested helper. [2ba9d6e](https://github.com/openclaw/openclaw/commit/2ba9d6eabef9427a950bacc47f077200446cb865) Thanks [@vincentkoc](https://github.com/vincentkoc). - OpenAI-compatible proxy providers can handle thinking levels and legacy `reasoning_effort` fields more consistently, with plugin developers and provider maintainers using one documented normalization helper across OpenRouter, Kilocode, and the SDK. [35bafea](https://github.com/openclaw/openclaw/commit/35bafea757fab0386292951a3dc2a2d3514f370e) - Browser and Vite builds can now load the OpenAI ChatGPT Responses provider without a server-only dependency breaking the bundle, while WebSocket failures still appear normally. [8c8eb86](https://github.com/openclaw/openclaw/commit/8c8eb86fff6e843bd391808ceee249ac8c7f5fa5) Thanks [@vincentkoc](https://github.com/vincentkoc). - OpenRouter model scans now accept the same larger valid catalogs as runtime discovery while still rejecting oversized responses before they can consume unbounded memory. [ad3b2f4](https://github.com/openclaw/openclaw/commit/ad3b2f4b8827cd73b4c1a6c8288569c0966276fe) Thanks [@vincentkoc](https://github.com/vincentkoc). - OpenAI Responses users, including affected Bedrock Mantle GPT-5.x reasoning setups, now get one clean final answer with aligned saved transcripts and replay context instead of dozens of repeated cumulative copies. [#92399](https://github.com/openclaw/openclaw/pull/92399) Related [#91959](https://github.com/openclaw/openclaw/issues/91959). Thanks [@amersheeny](https://github.com/amersheeny), [@daimingnj](https://github.com/daimingnj), [@phoenixyy](https://github.com/phoenixyy), [@pigfoot](https://github.com/pigfoot). - Scheduled jobs and isolated sessions using opencode-go models now move stalled requests into configured timeout or fallback handling instead of hanging for minutes before ending with a generic `LLM request failed` error. [#93965](https://github.com/openclaw/openclaw/pull/93965) Related [#93610](https://github.com/openclaw/openclaw/issues/93610). Thanks [@forceconstant](https://github.com/forceconstant), [@zhangguiping-xydt](https://github.com/zhangguiping-xydt). ##### Session, memory, and trust continuity [Sessions](https://docs.openclaw.ai/concepts/session), [compaction](https://docs.openclaw.ai/concepts/compaction), [memory](https://docs.openclaw.ai/concepts/memory), [QMD-backed memory](https://docs.openclaw.ai/concepts/memory-qmd), and [Tool Search](https://docs.openclaw.ai/tools/tool-search) retain useful state more consistently, while [Matrix](https://docs.openclaw.ai/channels/matrix) recovery, [tool policies](https://docs.openclaw.ai/gateway/sandbox-vs-tool-policy-vs-elevated), and [approvals](https://docs.openclaw.ai/cli/approvals) stay attached to the intended trust boundary. - Affected agent conversations using OpenAI Responses can now recover and keep replying after a visible channel response leaves their saved history incomplete, instead of every later turn failing before a reply appears. [#84708](https://github.com/openclaw/openclaw/pull/84708) Thanks [@anyech](https://github.com/anyech). - When a Codex-backed agent produces unusually large tool output, saved and replayed conversations now keep its text within the usual size limit while leaving non-text content unchanged. [#87912](https://github.com/openclaw/openclaw/pull/87912) Thanks [@adrianip0204](https://github.com/adrianip0204). - Control UI conversations now stay visible and continue in the same session after a sleep, network drop, or Gateway reconnect instead of disappearing when the next message is sent. [#89017](https://github.com/openclaw/openclaw/pull/89017) Related [#87700](https://github.com/openclaw/openclaw/issues/87700). Thanks [@zhangguiping-xydt](https://github.com/zhangguiping-xydt), [@asicoe](https://github.com/asicoe). - Bundled Codex and Copilot integrations now keep mirrored chat history and transcript updates tied to the correct OpenClaw session as storage evolves, while existing file-backed active transcripts continue working during the migration. [#89518](https://github.com/openclaw/openclaw/pull/89518) Thanks [@jalehman](https://github.com/jalehman). - WebChat's current-session status now matches the conversation you are actually using, so the session identity, thinking level, token context, and cost details no longer come from the fallback `main` session. [#89800](https://github.com/openclaw/openclaw/pull/89800) Related [#89773](https://github.com/openclaw/openclaw/issues/89773). Thanks [@killo3967](https://github.com/killo3967), [@sweetcornna](https://github.com/sweetcornna). - Your conversation is less likely to lose its context after you press stop during automatic compaction because the compaction request is now cancelled too. [#89886](https://github.com/openclaw/openclaw/pull/89886) Related [#89868](https://github.com/openclaw/openclaw/issues/89868). Thanks [@lykeion-dev](https://github.com/lykeion-dev), [@openperf](https://github.com/openperf), [@vincentkoc](https://github.com/vincentkoc). - When cross-agent session access is blocked, OpenClaw now lists all required visibility, agent-to-agent, and allow-list settings, helping operators correct policy configuration instead of chasing a nonexistent agent failure. [#90489](https://github.com/openclaw/openclaw/pull/90489) Related [#90443](https://github.com/openclaw/openclaw/issues/90443). Thanks [@ramitrkar-hash](https://github.com/ramitrkar-hash), [@sahibzada-allahyar](https://github.com/sahibzada-allahyar), [@vincentkoc](https://github.com/vincentkoc). - `openclaw memory status` now shows an active light or REM dreaming phase instead of incorrectly reporting `Dreaming: off`, so operators can see that valid memory configurations are enabled. [#93113](https://github.com/openclaw/openclaw/pull/93113) Related [#67868](https://github.com/openclaw/openclaw/issues/67868). Thanks [@agentarclab](https://github.com/agentarclab), [@mrossit](https://github.com/mrossit). - Timed-out QMD memory searches now stop their background work when the agent moves on, preventing abandoned processes from continuing to consume CPU and memory. [#93394](https://github.com/openclaw/openclaw/pull/93394) Thanks [@alix-007](https://github.com/alix-007). - Repeated instructions sent after compaction now remain in the conversation, preventing lost turns, orphaned replies, and malformed history that some providers reject. [#94328](https://github.com/openclaw/openclaw/pull/94328) Thanks [@vincentkoc](https://github.com/vincentkoc), [@yetval](https://github.com/yetval). - Memory Wiki's Stale Pages report now leaves durable concept and synthesis pages out of freshness warnings, keeping attention on source and entity pages that may actually need review. [#94369](https://github.com/openclaw/openclaw/pull/94369) Thanks [@sunnyshu0925](https://github.com/sunnyshu0925), [@vincentkoc](https://github.com/vincentkoc). - Long embedded runs with recent progress are now less likely to be interrupted by stale-session recovery, while genuinely stalled runs can still be cleared so queued work continues. [#94701](https://github.com/openclaw/openclaw/pull/94701) Thanks [@imadal1n](https://github.com/imadal1n), [@mrclawfield](https://github.com/mrclawfield). - Ollama memory search now respects a configured smaller embedding dimension and keeps indexes for different dimensions separate, avoiding incompatible vectors being mixed together. [#94811](https://github.com/openclaw/openclaw/pull/94811) Thanks [@mushuiyu886](https://github.com/mushuiyu886). - Memory searches and targeted refreshes now stay connected to the correct OpenClaw session even when transcript filenames change or QMD exports use a different name. [#95087](https://github.com/openclaw/openclaw/pull/95087) Thanks [@jalehman](https://github.com/jalehman). - Long-running conversations with screenshots or other images now keep their continuity more consistently when OpenClaw makes room for new messages, instead of repeatedly filling up without moving the retained conversation forward. [#95128](https://github.com/openclaw/openclaw/pull/95128) Thanks [@yetval](https://github.com/yetval). - Windows users can now run QMD-backed memory indexing and search through configured absolute `memory.qmd.command` paths, including drive-letter and UNC locations, without OpenClaw stripping the path separators before launch. [#95274](https://github.com/openclaw/openclaw/pull/95274) Related [#92302](https://github.com/openclaw/openclaw/issues/92302). Thanks [@ardooken](https://github.com/ardooken), [@ly85206559](https://github.com/ly85206559). - Usage footers selected with `/usage full` or `/usage tokens` now remain visible after daily or idle session rollover, so users do not have to turn them on again. [#95322](https://github.com/openclaw/openclaw/pull/95322) Thanks [@litang9](https://github.com/litang9). - Follow-up replies, reactions, threaded messages, and status checks stay with the chat they belong to after webchat or system activity, while real channel switches still clear outdated routing details. [#95467](https://github.com/openclaw/openclaw/pull/95467) Thanks [@yetval](https://github.com/yetval). - Long-running main conversations now keep their prior context when users return after an overnight or delayed follow-up, rather than silently starting over after an otherwise normal completion. [#95472](https://github.com/openclaw/openclaw/pull/95472) Thanks [@xydt-tanshanshan](https://github.com/xydt-tanshanshan). - People with large session histories can list, preview, and find sessions without multi-second freezes, while older mixed-case session keys are still migrated at startup. [#95699](https://github.com/openclaw/openclaw/pull/95699) Thanks [@jalehman](https://github.com/jalehman), [@jzakirov](https://github.com/jzakirov). - Fixes delivered replies sometimes being saved to the wrong conversation history, or omitted from it, when operators use a custom or per-agent `session.store`, improving continuity and auditability for the intended session. [#95782](https://github.com/openclaw/openclaw/pull/95782) Related [#95781](https://github.com/openclaw/openclaw/issues/95781). Thanks [@youngting520](https://github.com/youngting520). - Saved session-memory summaries now leave out raw model tokens, tool-call blocks, media placeholders, role tags, and stale `NO_REPLY` markers so future conversations keep useful context. [#95791](https://github.com/openclaw/openclaw/pull/95791) Thanks [@sweetsophia](https://github.com/sweetsophia), [@vincentkoc](https://github.com/vincentkoc), [@yb0y](https://github.com/yb0y). - Long-running OpenAI sessions using Codex/ChatGPT OAuth can now compact without a separate API key, whether `/compact` is run manually or triggered automatically. [#95831](https://github.com/openclaw/openclaw/pull/95831) Related [#95693](https://github.com/openclaw/openclaw/issues/95693). Thanks [@sallyom](https://github.com/sallyom), [@yui-tien](https://github.com/yui-tien). - Long, tool-heavy sessions now compact oversized conversations instead of getting stuck when a large tool result appears at the end. [#95860](https://github.com/openclaw/openclaw/pull/95860) Related [#78478](https://github.com/openclaw/openclaw/issues/78478). Thanks [@jw8957](https://github.com/jw8957), [@wzhgba](https://github.com/wzhgba), [@yetval](https://github.com/yetval). - When `memory_search` is unavailable because the Node runtime lacks `node:sqlite`, OpenClaw now points users to a compatible runtime instead of sending them through unrelated embedding-provider troubleshooting. [#95916](https://github.com/openclaw/openclaw/pull/95916) Thanks [@rrrrrredy](https://github.com/rrrrrredy), [@vincentkoc](https://github.com/vincentkoc). - Developers and operators inspecting a compacted Copilot session now get its summary, before-and-after token counts, and session details instead of an incomplete result. [#96049](https://github.com/openclaw/openclaw/pull/96049) Thanks [@vincentkoc](https://github.com/vincentkoc). - The `/stop` and abort commands now keep stopping active runs, clearing queued followups, and ending related subagents promptly even when session keys need canonicalizing or abort metadata cannot be saved. [#96201](https://github.com/openclaw/openclaw/pull/96201) Thanks [@jalehman](https://github.com/jalehman). - Voice Wake upgrades now keep existing trigger phrases and routing rules working as OpenClaw moves them from retired settings files into the shared state database. [bdf81a8](https://github.com/openclaw/openclaw/commit/bdf81a825fa3ef66ad2c535c1eeb0bb4e31b6d1b) - Upgrades from older OpenClaw state layouts now preserve update notifications, check throttling, available-version records, and automatic-update attempt history as that state moves into SQLite. [eb00d49](https://github.com/openclaw/openclaw/commit/eb00d499d16feea600fceef92d575fa30f005649) Thanks [@vincentkoc](https://github.com/vincentkoc). - Plugin-channel conversations keep their intended session more reliably through startup, doctor checks, and state repairs, with older binding records migrated into OpenClaw's shared database. [9f888d9](https://github.com/openclaw/openclaw/commit/9f888d95e082d50380a66db18ee2e32683e688e0) - Windows memory-backed session syncing now keeps using the intended transcript file even when path formatting differs. [b3b5b08](https://github.com/openclaw/openclaw/commit/b3b5b08e67a26efd648c7c7d879e5487223cd796) Thanks [@vincentkoc](https://github.com/vincentkoc). - Embedded agent runs with a missing or blank session key now stay attached to the intended session instead of being sent through inconsistent session routing. [911f853](https://github.com/openclaw/openclaw/commit/911f853b7fc4d819e2175b001662a01eba30453d) Thanks [@vincentkoc](https://github.com/vincentkoc). - When a model guesses the wrong tool name, Tool Search and Code Mode now show how to find and retry the correct tool, reducing the risk that long-running sessions get stuck or lose durable memory during compaction. [#93374](https://github.com/openclaw/openclaw/pull/93374) Related [#92273](https://github.com/openclaw/openclaw/issues/92273). Thanks [@mushuiyu886](https://github.com/mushuiyu886), [@poison](https://github.com/poison), [@vincentkoc](https://github.com/vincentkoc). - Fixes assistant replies disappearing from webchat, Control UI, Feishu, and other embedded conversations after compaction, keeping refreshed chats readable and follow-up requests separate. [#95484](https://github.com/openclaw/openclaw/pull/95484) Related [#76729](https://github.com/openclaw/openclaw/issues/76729). Thanks [@maweibin](https://github.com/maweibin), [@njuboy11](https://github.com/njuboy11), [@vincentkoc](https://github.com/vincentkoc). - OpenClaw memory features now keep active, reset, and deleted transcript coverage aligned with configured session stores and agent ownership, making dreaming, QMD exports, indexing, and sync less likely to miss or misattribute conversation history. [#96162](https://github.com/openclaw/openclaw/pull/96162) Thanks [@jalehman](https://github.com/jalehman). - Gateway TLS setup now rejects blank certificate or key paths clearly or uses OpenClaw's defaults, avoiding confusing startup and certificate-generation failures while preserving valid paths. [#94054](https://github.com/openclaw/openclaw/pull/94054) Thanks [@miorbnli](https://github.com/miorbnli). - Configured plugin policies keep blocking or rewriting sensitive tool calls after Gateway registry changes, reloads, or later hook initialization instead of being silently skipped. [#94545](https://github.com/openclaw/openclaw/pull/94545) Thanks [@jesse-merhi](https://github.com/jesse-merhi). - Mobile operators with `operator.approvals` can now see and resolve chat-triggered exec approvals on the iOS device that started the request, including while the app is open, without relying only on push notifications. [#95175](https://github.com/openclaw/openclaw/pull/95175) Thanks [@joshavant](https://github.com/joshavant). - Control UI users now get the patched DOMPurify release, reducing exposure to the GHSA-cmwh-pvxp-8882 sanitizer vulnerability without changing how the interface behaves. [#95691](https://github.com/openclaw/openclaw/pull/95691) Thanks [@vincentkoc](https://github.com/vincentkoc). - "Always allow" approvals for plugin conversation bindings now carry over from the old settings file and are less likely to be lost or overwritten when multiple OpenClaw processes are running. [ae41b00](https://github.com/openclaw/openclaw/commit/ae41b009224b0a8e3a990912503258d4478fb4d0) Thanks [@vincentkoc](https://github.com/vincentkoc). - Matrix users now see that the active recovery key is required before a forced cross-signing reset can proceed, preventing a second reset from leaving encryption recovery and room-key backups unusable. [#95720](https://github.com/openclaw/openclaw/pull/95720) Related [#78396](https://github.com/openclaw/openclaw/issues/78396). Thanks [@jteddy](https://github.com/jteddy), [@vincentkoc](https://github.com/vincentkoc), [@xialonglee](https://github.com/xialonglee). ##### Slack router relay mode [Slack router relay mode](https://docs.openclaw.ai/channels/slack) gives managed and multi-gateway deployments a supported way to centralize incoming Slack traffic while preserving gateway ownership of mentions, threads, and replies. - Managed Slack deployments can now use a central router to send mentions and ongoing threads to the right OpenClaw gateway while replies still appear through Slack. [#94707](https://github.com/openclaw/openclaw/pull/94707) Thanks [@pash-openai](https://github.com/pash-openai), [@sjf-oa](https://github.com/sjf-oa). ##### Raft External Agent wake bridge The [Raft channel](https://docs.openclaw.ai/channels/raft) and [Raft plugin](https://docs.openclaw.ai/plugins/reference/raft) now support the local CLI wake path for External Agents. - Raft External Agent operators can now wake an OpenClaw agent when a workspace has pending work through the supported local CLI bridge, with named profiles and checks for missing CLI prerequisites. [#95497](https://github.com/openclaw/openclaw/pull/95497) Thanks [@vincentkoc](https://github.com/vincentkoc). ##### Official plugin installation and repair [Plugin management](https://docs.openclaw.ai/plugins/manage-plugins) and the [plugin inventory](https://docs.openclaw.ai/plugins/plugin-inventory) now cover more official integrations through normal installation, update, and repair workflows. - When `plugins.allow` uses a channel or package name instead of the real plugin id, startup guidance now identifies the unmatched entry and shows the discovered plugin ids needed to correct the configuration. [#68389](https://github.com/openclaw/openclaw/pull/68389) Related [#68352](https://github.com/openclaw/openclaw/issues/68352). Thanks [@aym9999](https://github.com/aym9999), [@jirboy](https://github.com/jirboy), [@lyfuci](https://github.com/lyfuci), [@pahuchi-joe](https://github.com/pahuchi-joe), [@zmxccxy](https://github.com/zmxccxy). - Plugin trust warnings for first-time or fresh installs now include a ready-to-copy `plugins.allow` example and commands to list or inspect plugin ids, so users can resolve the warning before trusting or reinstalling plugin code. [#78105](https://github.com/openclaw/openclaw/pull/78105) Related [#68780](https://github.com/openclaw/openclaw/issues/68780). Thanks [@jirboy](https://github.com/jirboy), [@pahuchi-joe](https://github.com/pahuchi-joe). - Codex migrations now work with standard global plugin installs because `openclaw migrate` can find the installed provider instead of failing with `Unknown migration provider`. [#89612](https://github.com/openclaw/openclaw/pull/89612) Related [#89609](https://github.com/openclaw/openclaw/issues/89609). Thanks [@mugabuga](https://github.com/mugabuga), [@zerone0x](https://github.com/zerone0x). - Plugin installs and updates recover from stale OpenClaw-managed dependency pins instead of failing with `npm EOVERRIDE`, without later synchronization downgrading or removing packages users installed explicitly. [#91786](https://github.com/openclaw/openclaw/pull/91786) Related [#91772](https://github.com/openclaw/openclaw/issues/91772). Thanks [@amknight](https://github.com/amknight), [@mkdelta221](https://github.com/mkdelta221). - Channel plugin developers can now carry native sender and conversation identifiers through hooks and selected exec workflows, giving integrations more precise routing without breaking existing sender and chat fields. [#91903](https://github.com/openclaw/openclaw/pull/91903) Thanks [@lanzhi-lee](https://github.com/lanzhi-lee), [@vincentkoc](https://github.com/vincentkoc). - Plugin discovery now repeats fewer blocking filesystem checks during startup, reducing avoidable cold-start work for bundled plugin trees, especially on slower Windows filesystems, without changing bundle discovery behavior. [#93919](https://github.com/openclaw/openclaw/pull/93919) Related [#76209](https://github.com/openclaw/openclaw/issues/76209). Thanks [@ml12580](https://github.com/ml12580), [@shenhonglong456-ai](https://github.com/shenhonglong456-ai). - Plugin Gateway methods now work through `openclaw gateway call` after registration, so plugin authors can use them from scripts and cron jobs instead of hitting an `unknown method` error. [#94154](https://github.com/openclaw/openclaw/pull/94154) Related [#94127](https://github.com/openclaw/openclaw/issues/94127). Thanks [@brycemurray](https://github.com/brycemurray), [@pick-cat](https://github.com/pick-cat), [@vincentkoc](https://github.com/vincentkoc). - ClawHub skill discovery and install checks are less likely to stall or crash OpenClaw because oversized or stalled marketplace responses are now stopped before they can exhaust memory. [#95226](https://github.com/openclaw/openclaw/pull/95226) Thanks [@alix-007](https://github.com/alix-007). - Pinned official plugins no longer stay on an old release when operators follow the repair advice from `openclaw doctor` or deep gateway status after an upgrade. [#95541](https://github.com/openclaw/openclaw/pull/95541) Thanks [@ooiuuii](https://github.com/ooiuuii), [@vincentkoc](https://github.com/vincentkoc). - Managed npm plugin updates are less likely to break work on a running gateway with missing-module errors, because the older plugin files remain available until a later gateway start cleans them up. [#95589](https://github.com/openclaw/openclaw/pull/95589) Thanks [@ooiuuii](https://github.com/ooiuuii), [@vincentkoc](https://github.com/vincentkoc). - Official plugin cards for supported brands now show recognizable icons in ClawHub and other catalogs, and plugin authors can provide marketplace artwork through the documented manifest field. [#95845](https://github.com/openclaw/openclaw/pull/95845) Thanks [@patrick-erichsen](https://github.com/patrick-erichsen). - Official plugin icons in ClawHub and other catalogs are no longer forced into the same hard-coded color, allowing Simple Icons to use its default artwork instead. [#95987](https://github.com/openclaw/openclaw/pull/95987) Thanks [@patrick-erichsen](https://github.com/patrick-erichsen). - Docker users now have an official `openclaw/openclaw` Docker Hub mirror alongside GHCR, with versioned beta releases kept from moving the stable `latest` and `main` aliases. [#97122](https://github.com/openclaw/openclaw/pull/97122) Thanks [@vincentkoc](https://github.com/vincentkoc). - Git-based OpenClaw installs now use the repository's pinned pnpm version even when another global pnpm or surrounding project package manager is present, so setup commands no longer run against the wrong package-manager environment. [bd74a62](https://github.com/openclaw/openclaw/commit/bd74a62118aa4774706359d9494116ded8c1f6e3) Thanks [@vincentkoc](https://github.com/vincentkoc). - ClawHub skill-card and update requests now complete or time out predictably even when they receive an unusually large timeout value. [8cd0c11](https://github.com/openclaw/openclaw/commit/8cd0c11227f6f4096d089cd6108d6f2ae31252b7) Thanks [@vincentkoc](https://github.com/vincentkoc). - Windows users can complete source installs without a llama.cpp setup step blocking or slowing them, and the installer restores their existing shell setting afterward. [ea9065b](https://github.com/openclaw/openclaw/commit/ea9065bc68dd4ff94495b85a7dcb4491cf41b67a) Thanks [@vincentkoc](https://github.com/vincentkoc). - More official channel, provider, and web-search plugins can now be installed or repaired through normal external package catalogs while still being recognized from their existing credentials. [#95683](https://github.com/openclaw/openclaw/pull/95683) Thanks [@vincentkoc](https://github.com/vincentkoc). ##### Channels and Messaging ##### Additional channel fixes Additional [Telegram](https://docs.openclaw.ai/channels/telegram) and channel configuration fixes cover narrower delivery and setup problems. - Telegram reply chains keep cached replies attached after context changes instead of failing when those cached replies are reused. [#82909](https://github.com/openclaw/openclaw/pull/82909) Thanks [@lidge-jun](https://github.com/lidge-jun). - Fixes Discord dropping an entire long reply with fenced code blocks when a closing code fence lands near the 2,000-character message limit. [#95661](https://github.com/openclaw/openclaw/pull/95661) Thanks [@ly-wang19](https://github.com/ly-wang19). - Slack operators can now store tokens and signing secrets as supported SecretRef inputs, while reads, writes, allowlist and target lookups, and setup checks use the resolved credentials instead of rejecting or misreading the references. [7da955f](https://github.com/openclaw/openclaw/commit/7da955fae4ca2083599aa33a1f93dbfff53cb187) Thanks [@vincentkoc](https://github.com/vincentkoc). - Channel capability checks now return a clear timeout when an integration stops responding, keeping troubleshooting from hanging in a terminal or automation run. [8ecdb97](https://github.com/openclaw/openclaw/commit/8ecdb97b636e4c3fcc6d142d217327404ae06581) Thanks [@vincentkoc](https://github.com/vincentkoc). ##### Providers and Models ##### Additional provider and model fixes Additional [model configuration](https://docs.openclaw.ai/providers/models) fixes improve selection, usage reporting, status output, and streaming. - After changing the default model, starting a fresh channel session with `/new` or `/reset` now uses the new default instead of silently reusing the previous cached model, while explicit `/model` overrides remain unchanged. [#77339](https://github.com/openclaw/openclaw/pull/77339) Related [#77322](https://github.com/openclaw/openclaw/issues/77322). Thanks [@mjamiv](https://github.com/mjamiv), [@zaynl](https://github.com/zaynl). - Behind HTTP or HTTPS proxies, Codex/OpenAI usage and quota checks in `openclaw status --usage --json` and the Control UI now retrieve usage windows instead of failing when chatgpt.com is unreachable directly. [#93943](https://github.com/openclaw/openclaw/pull/93943) Related [#78714](https://github.com/openclaw/openclaw/issues/78714). Thanks [@tnzgit](https://github.com/tnzgit), [@turbotheturtle](https://github.com/turbotheturtle). - `/status` now keeps the active model and how to clear a pinned choice on one compact line, so Discord and other chat users can scan model status without a multi-line explanation. [#95797](https://github.com/openclaw/openclaw/pull/95797) Thanks [@solvely-colin](https://github.com/solvely-colin). - Anthropic streaming responses now keep interleaved text, thinking, and tool-call updates …

@fuller-stack-dev

…on) (#31) * fix(release): require postpublish evidence artifact * test(qa): harden all-profile evidence scenarios (openclaw#96003) * fix: harden ios screenshot uploads * fix(qa): omit local temp roots from gateway artifacts * fix(test): reject pathological Docker E2E limits * fix(compaction): trim prefix when transcript ends in an oversized tool result (openclaw#95860) findCutPoint defaulted cutIndex to the earliest valid cut (cutPoints[0], keep everything) and only moved it forward to a cut point at or after the backward token cursor. When the final entry is a toolResult whose estimate alone meets keepRecentTokens, the cursor stops at that trailing toolResult index, no valid cut point sits at or after it (toolResult entries are not valid cut points), and the default stuck at keep-everything. Compaction then summarized zero messages, so preflight and overflow compaction silently no-op and the session loops on a context it cannot shrink. Default cutIndex to the most recent valid cut before the forward search. When a cut point exists at or after the cursor the search still finds it and behavior is unchanged; only the trailing-tool-result case now keeps the recent tail and summarizes the prefix. * fix(xiaomi): correct mimo-v2.5 and mimo-v2.5-pro max output tokens to 128K (openclaw#95934) * fix(xiaomi): correct mimo-v2.5 and mimo-v2.5-pro max output tokens to 131072 * docs(xiaomi): correct mimo-v2.5 and mimo-v2.5-pro max output tokens to 131072 * fix(sessions): honor configured store for transcript mirrors (openclaw#95782) * fix(qa): avoid lab artifact directory collisions * feat(copilot): wire harness parity helpers * fix(copilot): tighten harness sdk boundaries * chore(sdk): update public surface budget * fix(release): validate DMG resize slack * fix: avoid false macOS update failures during gateway shutdown (openclaw#95886) Merged via squash. Prepared head SHA: 400e87c Co-authored-by: fuller-stack-dev <263060202+fuller-stack-dev@users.noreply.github.com> Reviewed-by: @fuller-stack-dev * perf: skip per-chunk live parsing for subagents Subagent runs do not have a live stream consumer; their result is delivered from the terminal message path after the child run finishes. The intermediate message_update stream work only feeds live preview output. Thread suppressLiveStreamOutput from the subagent lane into the embedded runner subscription and return from handleMessageUpdate after accumulating the raw chunk. This keeps final delivery unchanged while skipping per-chunk visible text and reasoning stream parsing for subagents, which reduces event-loop pressure when multiple child agents stream long answers in parallel. Interactive and Control UI runs keep the existing live preview path. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> (cherry picked from commit e0382c2c58c3eabdf64638777ec82cb1e68514e9) * fix(agents): gate subagent stream suppression * fix(release): reject malformed candidate API timeouts * fix(crabbox): reclaim sparse reused leases * fix(model-usage): coerce numeric-string costs and ignore non-finite values (openclaw#87861) Merged via squash. Prepared head SHA: 11bb571 Co-authored-by: coder999999999 <83845889+coder999999999@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * fix(qa): reject out-of-range lab CLI ports * fix(qa-lab): avoid duplicate child evidence files (openclaw#96030) * fix(memory-wiki): exclude durable reference pages from stale report (openclaw#94369) Merged via squash. Prepared head SHA: c2dca7e Co-authored-by: SunnyShu0925 <265248434+SunnyShu0925@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * Fix recent session resume with long headers (openclaw#94578) Merged via squash. Prepared head SHA: 8102961 Co-authored-by: rohitjavvadi <76606932+rohitjavvadi@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * ci: add codex maturity scorecard agent (openclaw#95919) * fix(heartbeat): skip reasoning payloads when selecting heartbeat reply (openclaw#92356) Merged via squash. Prepared head SHA: 5885fbb Co-authored-by: tangtaizong666 <212687958+tangtaizong666@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * fix(release): surface installed extension manifest errors * fix(release): track CommonJS package dist imports * fix(scripts): catch namespace plugin sdk wildcard exports * fix(agents): keep post-compaction user re-issue of a kept-tail prompt during compaction rotation (openclaw#94328) Merged via squash. Prepared head SHA: 05981b6 Co-authored-by: yetval <102706514+yetval@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * fix(reply): suppress per-message finals across multi-message block streaming (openclaw#95432) Merged via squash. Prepared head SHA: 7d7c61f Co-authored-by: yetval <102706514+yetval@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * fix(auto-reply): keep drain/restart-abort reply paths silent (openclaw#95431) Merged via squash. Prepared head SHA: edb75a9 Co-authored-by: moeedahmed <5780040+moeedahmed@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * fix(qa): avoid self-check report clobbering * fix(qa): avoid default artifact directory collisions * test(qa): gate maturity docs on passing evidence (openclaw#96017) * docs: refresh maturity scorecard evidence * test(qa): gate maturity docs on passing evidence * test(qa): ensure UX matrix video dependencies * test(qa): simplify maturity evidence result text * test: align maturity docs test routing * feat(mattermost): persist participated threads for mention-free follow-ups * fix(mattermost): record thread participation on preview-finalized replies; document thread mention exception * fix(mattermost): block-bodied promise executor in participation test (oxlint) * fix openclaw#89231: [Bug]: Windows installer-created scheduled task launches gateway.cmd with visible console — should use windowless launcher (openclaw#95480) Merged via squash. Prepared head SHA: 8b57b03 Co-authored-by: mikasa0818 <244515412+mikasa0818@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * fix(copilot): preserve compaction metadata * fix(qa): avoid live artifact directory collisions * fix(crabbox): share Windows hydrate handoff path * docs: rename top maturity tier (openclaw#96044) * Gate private QQBot group commands (openclaw#92154) * fix: gate private qqbot group commands * fix(qqbot): keep authorized stop urgent in groups * fix(qqbot): preserve omitted group command level * fix(qqbot): preserve ignore-other-mentions gate * test(qqbot): avoid unbound mention gate mock * fix(qqbot): close strict command visibility gaps * fix(qqbot): gate private group commands and close strict command visibility gaps (openclaw#92154) (thanks @sliverp) * fix(daemon): type Windows task env fixture * fix: assistant reply lost between compaction summary and first kept user in successor transcript (openclaw#95484) Merged via squash. Prepared head SHA: eff5894 Co-authored-by: maweibin <18023423+maweibin@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * ci: add release QA profile evidence (openclaw#95094) * ci: add release qa profile evidence * ci: simplify release qa profile evidence * ci: reuse qa profile evidence workflow * ci: remove inherited secrets lint comment * ci: pass qa profile evidence secret explicitly * ci: run maturity scorecard in release checks * ci: declare maturity scorecard reusable secret * fix(ci): report missing workflow pre-commit runtime * fix(qa): avoid direct smoke artifact collisions * docs: redesign maturity scorecard pages (openclaw#96057) Merged via squash. Prepared head SHA: d2c680a Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * perf(agents): index displaced tool results * perf(usage): bound session log retention * perf(anthropic): index active stream blocks * fix(anthropic): narrow stream block index guard * fix(qa): avoid matrix qa artifact collisions * fix(qa-lab): use scoped crabline package * fix(ci): repair maturity docs checks * docs: place maturity pages under release reference (openclaw#96061) Merged via squash. Prepared head SHA: 7ab8982 Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * fix(qa): avoid telegram proof artifact collisions * fix(qa): avoid plugin update registry port collisions * fix: npm plugin updates break running gateway imports (openclaw#95589) Merged via squash. Prepared head SHA: 74ecbbb Co-authored-by: ooiuuii <169449607+ooiuuii@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * fix(docs): keep maturity taxonomy renderer formatted * fix(qa): allow web search smoke gateway port override * fix(ci): refresh dependency audit locks * fix(qa): isolate parallels plugin temp script * fix(qa): avoid vitest report path collisions * test(ci): update tooling route expectation * fix(qa): avoid extension memory report collisions * fix(qa): isolate docker rerun artifact downloads * fix(acpx): consume acpx 0.11.1 model capability errors * fix(acpx): consume acpx 0.11.1 model capability errors * fix(acpx): refresh npm shrinkwrap for 0.11.1 * test: include workflow checks in tooling plan * fix(qa): preserve active mac restart locks * fix(ci): allow release QA evidence workflow calls * fix(ci): pass resolved ref to maturity QA evidence * fix(ci): keep release QA evidence branch-compatible * fix(qa): bound docker e2e log replay * fix(qa): reject duplicate qa e2e outputs * fix(qa): reject duplicate report artifacts * fix(qa): reject ambiguous dependency report inputs * fix(qa): reject duplicate single-value flags * fix(qa): reject duplicate test report controls * fix(qa): reject duplicate dependency evidence options * fix(qa): reject duplicate package candidate options * fix(qa): reject duplicate docker package options * fix(plugin-sdk): refresh api baseline hash * fix(release): reject duplicate candidate checklist options * fix(qa): reject duplicate hosted gate options * fix(qa): reject duplicate ux evidence options * fix(qa): reject duplicate otel smoke options * refactor: add transcript update identity contract (openclaw#89912) * fix(qa): reject duplicate gateway smoke options * fix: clear config secret refs through env helper * fix(qa): reject duplicate Parallels platforms * test: route shared token reload env writes * fix(qa): require Telegram proof report before publish * fix: route shared auth secret env writes * fix(qa): reject duplicate RPC RTT methods * fix(qa): require MCP API list evidence * fix(qa): reject polluted Tool Search proof lanes * test: route network runtime env setup * fix: simplify Fly Machine env cleanup * fix(qa): reject duplicate gauntlet selectors * test: scope send state env helper * fix: restore task state env through helper * test: scope transcript reader env setup * fix(maint): use rebase PR landing * fix(maint): choose latest hosted CI run * fix(maint): protect pending hosted CI reruns * fix(qa): disable pnpm verify in cpu scenarios * fix(qa): reject missing memory fd args * test(extensions): use real response mocks * test(extensions): use real provider response mocks * test(extensions): use real chutes response mocks * fix(qa): reject duplicate startup bench cases * feat(copilot): mirror native plan and subagent events * fix(harness): recover Copilot native subagent tasks * fix(qa): reject duplicate sibling bench cases * fix(acpx): detect wrapper orphan on any PPID change, not just init reparenting (openclaw#96032) * fix(acpx): detect wrapper orphan on any PPID change, not just init reparenting The codex / claude adapter wrapper's orphan watcher (emitted by buildAdapterWrapperScript) skipped cleanup when `process.ppid !== 1`, intending to wait for the kernel to reparent the orphaned wrapper to PID 1 (init). This only works on bare-metal hosts without an active user-session manager. On systemd-managed deployments (EC2 user services, most container runtimes), an orphaned process is reparented to the user-session manager or container init — not to init itself. The watcher therefore never fires, and when the gateway exits, the adapter wrapper survives and holds its child process group (codex-acp.js + native binary) running indefinitely. Real-world symptom: each gateway restart accumulates 3-process trees of leftover codex adapters. Subsequent ACP spawns then contend with these orphans, the main event loop is starved by acpx-runtime reap attempts, and new sessions stall at "waiting for tool execution" for minutes. Fix: trigger orphan cleanup as soon as PPID changes from the recorded original, regardless of what the new PPID is. The killChildTree path already covers process-group cleanup via `kill(-pid, SIGTERM)`, so once the watcher fires, grandchildren are reaped correctly. Adds a regression test asserting the wrapper template does not re-introduce the `process.ppid !== 1` guard. * test: document maturity ref handoff --------- Co-authored-by: t2wei <t2wei@me.com> Co-authored-by: Vincent Koc <25068+vincentkoc@users.noreply.github.com> * fix(qa): reject unknown docker timing options * fix(qa): reject duplicate sqlite bench controls * fix(qa): reject duplicate abort leak controls * fix(qa): reject duplicate telegram proof controls * chore(acpx): bump bundled client to 0.11.2 (openclaw#96124) * fix(qa): reject duplicate cli bench controls * fix(qa): reject duplicate gateway startup controls * fix(qa): reject duplicate gateway restart controls * fix(qa): reject duplicate model bench controls * Fix WebChat dispatch failure session status (openclaw#84352) Merged via squash. Prepared head SHA: 562f2ac Co-authored-by: jesse-merhi <79823012+jesse-merhi@users.noreply.github.com> Reviewed-by: @jesse-merhi * fix(qa): reject duplicate model resolution perf controls * fix(qa): reject duplicate gateway cpu controls * ci: make release maturity scorecard opt-in * fix(qa): reject duplicate plugin gauntlet controls * test(ci): read sparse android guard files from git * fix(qa): reject duplicate rpc rtt controls * refactor: migrate plugin transcript mirrors (openclaw#89518) * fix(qa): prove direct reply routing via qa channel * refactor: add embedded run session target seam (openclaw#90439) * test(docs): skip i18n Go tests without toolchain * perf(gateway): drop redundant per-access session-key case scan (openclaw#95699) Merged via squash. Prepared head SHA: 42c9224 Co-authored-by: jzakirov <15848838+jzakirov@users.noreply.github.com> Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com> Reviewed-by: @jalehman * chore(plugin-sdk): refresh API baseline hash * fix(ci): avoid relinking identical node tools * fix(skills): accept owner-qualified verify refs (openclaw#95992) Merged via squash. Prepared head SHA: de9f1e5 Co-authored-by: Patrick-Erichsen <20157849+Patrick-Erichsen@users.noreply.github.com> Co-authored-by: Patrick-Erichsen <20157849+Patrick-Erichsen@users.noreply.github.com> Reviewed-by: @Patrick-Erichsen * fix(plugins): remove simpleicons icon color paths (openclaw#95987) * chore(android): prepare 2026.6.9 Play release * refactor: use accessor-backed transcript corpus for memory (openclaw#96162) * refactor: ratchet memory transcript corpus access * test: use narrow runtime config snapshot import * test: update plugin sdk surface budgets * refactor: split memory transcript corpus module * fix(ios): defer local network discovery until onboarding * test(ios): guard local network permission trigger points * test(cli): isolate service env in run and update suites * fix(infra): bound ClawHub fetchJson and error response bodies ClawHub is an external marketplace (untrusted source); fetchJson read the success body via response.json() and readErrorBody read the error body via response.text(), both without a byte cap, so a hostile or malfunctioning host could exhaust memory with an unbounded response. Read both through the existing read-response-with-limit helpers (16 MiB cap for JSON, 8 KiB / 400 chars for the error snippet), cancelling the stream on overflow/idle. Symmetric counterpart to the Anthropic error-stream hardening in openclaw#95108. * fix(infra): cap ClawHub install-resolution JSON via shared bounded reader The install-resolution path (fetchClawHubSkillInstallResolution) still read ClawHub JSON with an unbounded response.json(), the one ClawHub JSON reader left uncapped by the prior hardening. Route it through the existing parseClawHubJsonBody helper so every ClawHub JSON success/structured-block body is bounded by the same 16 MiB cap and cancels the stream on overflow. Pure reuse of the helper introduced in this PR (no new abstraction); adds a regression test that an oversized install-resolution body is rejected and the underlying stream is cancelled. * fix(infra): preserve ClawHub body timeouts * fix(matrix): bound non-raw JSON response body in transport * fix(matrix): use JSON-specific idle-timeout diagnostic on bounded JSON read The non-raw JSON read in performMatrixRequest fell back to the bound reader's default media idle-timeout message ('Matrix media download stalled: ...'), which is misleading for a JSON control-plane read. Pass a JSON-specific onIdleTimeout so a stalled JSON stream now rejects with 'Matrix JSON response stalled: no data received for {ms}ms', letting the timeout diagnostic distinguish a stalled JSON read from a stalled raw/media read. Update the regression assertion accordingly. * fix(matrix): bound SDK response bodies * fix(memory): abort orphaned qmd search subprocess when memory_search times out PR openclaw#91742 wired memory_search's 15s deadline AbortSignal through the builtin memory manager but missed the QMD backend behind the same MemorySearchManager.search interface. With QMD, the tool returns "timed out after 15s" to the agent while the spawned qmd query/search subprocess keeps running for the full qmd command timeout (memory.qmd.limits.timeoutMs, whose embed-heavy default was raised to 600s in openclaw#87572), leaving orphaned embedding/search work running after the agent already moved on. Add optional AbortSignal support to runCliCommand: an aborting signal kills the spawned child immediately and rejects with the abort reason, funneled through a single settle() guard so abort/timeout/error/close cannot double-settle. Thread the search signal through QmdMemoryManager.search -> runQmdSearch -> runQmd -> runCliCommand for the default direct-qmd subprocess path (including the query fallback), and fast-fail search() when the signal is already aborted. * fix(memory): thread qmd search abort signal through grouped collection search memory_search timeout cancellation only reached single-group direct qmd searches. Multi-collection or mixed memory/session configs route through runQueryAcrossCollectionGroups, which still called runQmdSearch without the caller signal, so an aborted memory_search left the grouped qmd child running until the qmd command timeout instead of being killed promptly. Thread searchSignal through the grouped search path and its unsupported-option fallback, and add a grouped multi-collection abort regression asserting the spawned qmd child is SIGKILLed when the caller signal aborts. * fix(memory): abort orphaned qmd subprocess on the mcporter search path too The initial fix threaded the abort signal through the direct qmd (runQmd/runQmdSearch) path, but the mcporter / QMD 1.1+ daemon search path (runQmdSearchViaMcporter, runMcporterAcrossCollections) never received it, so a grouped/mcporter search left its subprocess running on abort. Thread the search signal through QmdMcporterSearchParams, QmdMcporterAcrossCollectionsParams, all four mcporter call sites in search(), and runMcporter, down to the shared runCliCommand spawn (which already SIGKILLs the child on abort). Guard runQmdSearchViaMcporter on an already-aborted signal so the multi-collection loop stops spawning. Reuses the existing abort mechanism; no new machinery. Adds mcporter-path regression tests. * fix(memory): abort orphaned qmd search processes * test(memory): clean up qmd fixture gracefully * ci: build iOS app for iOS changes * fix(qa): bootstrap raw macos package scripts * test(ci): align plugin prerelease manifest env * fix(qa): retain crabline delivery targets * refactor: migrate bundled transcript target lookups (openclaw#89911) * refactor: route plugin host hook state through accessor (openclaw#96191) * refactor: route plugin host hook state through accessor * refactor: hide session accessor store internals * fix: route gateway history through session accessor target (openclaw#96179) * refactor: add abort target session accessor (openclaw#96201) * refactor: add abort target session accessor * refactor: centralize command abort session lookup * fix: keep abort runtime path best effort * fix: preserve abort target identity on persistence failure * fix: remember abort target when persistence is skipped * fix: abort runtime before metadata persistence * fix: preserve abort target fallback typing * fix: avoid stale abort memory fallback * fix: keep abort accessor ratchet narrow * fix: type abort persistence test mock * fix: align abort accessor ratchet test * fix(memory-core): migrate dreaming cleanup lifecycle (openclaw#96193) * fix(memory-core): migrate dreaming cleanup lifecycle * fix(sessions): resolve lifecycle session files explicitly * fix(ci): refresh dreaming lifecycle proof ratchets * fix: bridge ACP metadata to session accessors (openclaw#96195) * fix: bridge ACP metadata to session accessors * fix: simplify ACP accessor key ownership * fix: bind ACP metadata after session canonicalization * docs(ios): add app review notes * refactor: migrate agent session accessors (openclaw#96182) * refactor: migrate agent session accessor writes * refactor: move subagent orphan lookup to reconciliation * test: align session accessor mocks * refactor: guard reply session initialization (openclaw#96218) * refactor: guard reply session initialization * refactor: tighten reply session initialization boundary * test: satisfy reply session accessor lint * refactor(gateway): add alias mutation accessor (openclaw#96213) * refactor: add gateway alias mutation accessor * test: align gateway session entry mocks * refactor: migrate command session persistence to accessor (openclaw#96204) * refactor: migrate command session writes to accessor * refactor: narrow command session persistence params * refactor: route live model reads through session accessor (openclaw#96206) * fix(whatsapp): quote current follow-up in durable replies (openclaw#96220) * build(ios): attach app review notes PDF * docs(ios): update Talk app store metadata * fix(qa): retain long smoke debug requests * fix(qa): scope no-outbound waits * fix(qa): settle channel no-reply check * test(qa): show unexpected no-outbound messages * fix(qa): drain fanout child completions * fix(qa): enforce fanout completion drain * fix(macos): drop Textual from chat packaging * fix(macos): drop Textual from chat packaging * fix(macos): declare concurrency extras dependency * fix(codex): prefer gateway-managed generated images * fix(crabbox): require Xcode for macOS proof * fix: UI glitch: config is not visible (openclaw#96145) Summary: - The branch tracks effective Settings Config Form/Raw mode, resets `.config-content` scroll when that mode changes, and adds a browser regression test for the retained-scroll transition. - PR surface: Source +9, Tests +30. Total +39 across 2 files. - Reproducibility: yes. at source level: current main resets `.config-content` for section navigation but not ... ro in this read-only pass, but the source PR includes after-fix browser proof for the same branch behavior. Automerge notes: - No ClawSweeper repair was needed after automerge opt-in. Validation: - ClawSweeper review passed for head a6ea91e. - Required merge gates passed before the squash merge. Prepared head SHA: a6ea91e Review: openclaw#96145 (comment) Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com> Co-authored-by: sunlit-deng <253064511+sunlit-deng@users.noreply.github.com> Approved-by: takhoffman * perf(browser): index role snapshot references * perf(codex): index rollout transcript ids * perf(reply): hoist direct-send fragment index * fix(maint): keep PR landing on squash * fix(ios): make screenshot upload deterministic * fix(gateway): resolve plugin-registered gateway methods through live registry (openclaw#94154) Merged via squash. Prepared head SHA: c65cac4 Co-authored-by: Pick-cat <266665499+Pick-cat@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * fix(ci): resolve performance target refs before checkout * fix openclaw#92582: Bug: doctor falsely warns local memory embeddings are not ready (openclaw#95393) * fix(doctor): ignore skipped local embedding probe * fix(doctor): keep skipped local model diagnostics --------- Co-authored-by: Vincent Koc <25068+vincentkoc@users.noreply.github.com> * fix(qa): accept pnpm separator for lab up (openclaw#96246) * fix(ios): wait for screenshot checksum propagation * fix(ports): route isPortBusy through checkPortInUse to catch IPv4-only occupants (openclaw#94949) * fix(ports): route isPortBusy through checkPortInUse to catch IPv4-only occupants * fix(ports): treat PortUsageStatus unknown as busy in isPortBusy Per ClawSweeper review: checkPortInUse returns 'unknown' when every host probe fails for a non-EADDRINUSE reason. Treating unknown as 'not busy' could cause forceFreePortAndWait to exit before lsof/fuser inspects the port. Conservative fix: only 'free' means not busy; everything else (busy or unknown) triggers further inspection. * fix(ports): reuse canonical multi-address probe * fix(ports): reuse canonical multi-address probe --------- Co-authored-by: Vincent Koc <25068+vincentkoc@users.noreply.github.com> * fix(workboard): hide archived cards in CLI list by default (openclaw#94562) * fix(workboard): hide archived cards in CLI list by default The `openclaw workboard list` CLI printed soft-archived cards, while the `workboard_list` agent tool and the `/workboard list` command both hide cards with `metadata.archivedAt` set unless archives are requested. Users who archived cards still saw them in CLI output and assumed archive failed. Filter archived cards by default in the CLI list handler and add an `--include-archived` flag mirroring the tool's `includeArchived` option, so all three list surfaces share one default. Docs updated to match. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(workboard): preserve json list archive visibility * fix(workboard): preserve json list archive visibility --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: Vincent Koc <vincentkoc@ieee.org> * fix(nextcloud-talk): ignore signed non-message webhook events (openclaw#96243) * fix(nextcloud-talk): ignore non-message webhook events * fix(nextcloud-talk): acknowledge lifecycle webhook events --------- Co-authored-by: Jasmine Zhang <jasminezhang@JasminedeMac-mini.local> Co-authored-by: Vincent Koc <25068+vincentkoc@users.noreply.github.com> * test: scope post-attach sentinel env * fix(exec): preserve turn-source routing target in approval followups for plugin channels (openclaw#96140) * fix(exec): preserve turn-source routing target in approval followups for plugin channels When an async exec approval is resolved and the originating session is resumed, buildAgentFollowupArgs forwarded the turn-source to/accountId/threadId only for built-in deliverable channels or gateway-internal channels. For an external channel plugin whose channel is not in the in-process deliverable set, the followup dispatched channel alone and dropped the recipient, so the resumed agent reply routed to webchat instead of the originating channel. Forward the turn-source routing fields whenever the resolved delivery target is not used, matching how the channel itself is already preserved, so the gateway can route the post-approval reply back to the originating channel. Fixes openclaw#96103 * fix(exec): normalize followup thread routing * fix(exec): normalize followup thread routing --------- Co-authored-by: Vincent Koc <vincentkoc@ieee.org> * fix: restore supervisor hint env via helper * test: scope preauth env override * fix: restore chat media state env via helper * test: scope chat cli home fixture * fix: route approval e2e env setup * test: route operator approval env setup * ci: move codeql quality off blacksmith (openclaw#96258) * chore(release): close out 2026.6.10 on main (openclaw#96271) * chore(release): close out 2026.6.10 on main * chore(release): align native app metadata for 2026.6.10 * chore(release): sync Android 2026.6.10 notes * docs(changelog): preserve 2026.6.9 history * docs(changelog): preserve 2026.6.9 history * fix(agents): run heartbeat_prompt_contribution on harness prompt builds (openclaw#96233) * fix(agents): run heartbeat_prompt_contribution on harness prompt builds Harness runtimes (e.g. the Codex app-server) assemble the prompt through resolveAgentHarnessBeforePromptBuildResult rather than the embedded runner's resolvePromptBuildHookResult. The harness helper ran before_prompt_build and before_agent_start but never invoked heartbeat_prompt_contribution, so that hook silently no-ops on those runtimes: plugins that contribute heartbeat context via the documented hook get nothing on heartbeat turns. Invoke heartbeat_prompt_contribution from the harness helper too, gated on ctx.trigger === "heartbeat", merging its prepend/append context ahead of the before_prompt_build / before_agent_start contributions (matching the embedded path's ordering). before_prompt_build appendContext is already honored here, so no change is needed for boot-style append contributions. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(agents): preserve heartbeat hook ordering --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: Vincent Koc <25068+vincentkoc@users.noreply.github.com> * fix: avoid O(N²) shallow-copy in mapSensitivePaths schema traversal (openclaw#55018) * fix: avoid O(N²) shallow-copy in mapSensitivePaths schema traversal * fix(config): preserve schema hint map contract --------- Co-authored-by: 黄炎帝 <huangyandi@xiaohongshu.com> Co-authored-by: Vincent Koc <25068+vincentkoc@users.noreply.github.com> * fix(compaction): route codex oauth compaction natively (openclaw#95831) Signed-off-by: sallyom <somalley@redhat.com> * fix(auto-reply): align channel intro wording with chat_type (openclaw#96244) * fix(auto-reply): use channel wording for chat_type=channel * test(auto-reply): update channel wording fixture * fix(auto-reply): align tool-only channel guidance * test(auto-reply): refresh prompt snapshot --------- Co-authored-by: Jasmine Zhang <jasminezhang@JasminedeMac-mini.local> Co-authored-by: Vincent Koc <25068+vincentkoc@users.noreply.github.com> * chore(release): prepare 2026.6.11-beta.1 * test: review raft signal publish scan findings * docs(release): refresh 2026.6.11 beta notes * fix(agents): preserve absent embedded session keys * docs(changelog): refresh 2026.6.11 beta notes * fix(qa): issue unique mock tool call ids * docs(changelog): refresh 2026.6.11 notes * fix(qa): accept Codex capped read evidence * docs(changelog): refresh 2026.6.11 notes * fix(qa): align runtime parity evidence with Codex * test(qa): allow Codex fanout completion window * test(qa): extend fanout marker wait * test(qa): scope fanout marker proof to channel runtime * fix(telegram): recover stalled ingress spool claims Backport of openclaw#97118 to release/2026.6.11. * ci(docker): publish releases to Docker Hub (openclaw#97122) * ci(docker): publish releases to Docker Hub * ci(docker): clarify beta image tags (cherry picked from commit b70d1aa) * fix(parallels): stabilize Windows beta smoke transport * chore(release): prepare 2026.6.11-beta.2 * ci(release): allow token plugin npm recovery * ci(release): restore trusted plugin npm publishing * ci(release): restore plugin npm token env * ci: bump ClawHub package publish workflow (openclaw#97909) * chore(release): prepare 2026.6.11 * test(codex): harden run-attempt temp cleanup * test(qa): accept async image fixture coverage * fix(release): use workspace host deps in release lockfile * test(qa): accept crabline multi-channel capabilities * test(qa): make memory channel scenario wait for final answer * ci(release): stabilize anthropic live smoke selection * fix(fork): resolve CI failures on 6.11 merge Address the failing PR #31 pipeline checks after the v2026.6.11 merge: - check-lint / check-additional-extension-bundled: fix `no-shadow` (`FallbackSummaryError` mock class vs the top-level import) in the auto-reply test, plus two pre-existing sentry-monitor lint errors now enforced by 6.11's stricter oxlint (`no-implicit-coercion` on `!!event.deliveryError`, `no-unsafe-optional-chaining` in dispatch.test.ts). - check-shrinkwrap (EOVERRIDE): the fork security override pinned undici 7.28.0, but 6.11 extensions declare undici 8.5.0 directly. Bump the override to 8.5.0 (newer than the original security target, so the advisory intent holds) and regenerate the affected npm-shrinkwrap.json files + pnpm-lock.yaml. - checks-node-agentic-command-support: the fork `-boon.N` version suffix broke Codex runtime-plugin convergence in doctor. `parseOpenClawReleaseVersion` returned null for `2026.6.11-boon.1`, so version comparison fell back to string inequality and doctor re-refreshed/downgraded an already-converged Codex plugin every pass. Teach the shared parser to rank `-boon.N` as a stable correction of its base, and tolerate the suffix in the doctor beta-companion regex + test fixture helper. Not code defects (left as-is): the `review` check (missing ANTHROPIC_API_KEY / OIDC in the fork CI), the `network-runtime-boundary` diff gate (fires on upstream `codex-supervisor` net usage surfaced by the large merge diff), and `check-guards` (`spawnSync git ENOBUFS` on the 11k-commit merge diff). Local proof: auto-reply 215/215, missing-configured-plugin-install 71/71, npm-registry-spec + update-channels 102/102; oxlint clean on touched files; `generate-npm-shrinkwrap.mjs --all --check` green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(deps): dedupe @types/node so shrinkwrap check is deterministic The lockfile-only regen for the undici override left pnpm-lock.yaml carrying both @types/node@25.9.1 and @types/node@25.9.2 (a tsx 4.22.3/4.22.4 split). The npm-shrinkwrap generator only pins a version when the pnpm lock resolves a single major/minor line, so the duplicate let the root `@types/node: *` dev dependency float to registry-latest at generation time — my local run captured 25.9.1 while CI's fresh frozen install resolved 25.9.2, so check-shrinkwrap reported the root npm-shrinkwrap.json stale. `pnpm dedupe` collapses @types/node to a single 25.9.1 line, making the generator deterministic. Regenerate the root and googlechat shrinkwraps to match. Verified: `pnpm install --frozen-lockfile` green and `generate-npm-shrinkwrap.mjs --all --check` reports every package current. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(fork): scope undici override to 7.x and raise guard diff buffer Two remaining CI failures on the 6.11 merge: - checks-node-core-ui (and media-ui) crashed with `Worker exited unexpectedly` caused by `Cannot find module 'undici/lib/handler/wrap-handler.js'`. The flat `undici: 8.5.0` override (added to satisfy the 6.11 extensions that depend on undici 8.5.0 directly) forced jsdom's `undici@^7.25.0` onto 8.x, where that internal module was removed, crashing the jsdom test workers. Scope the security pin to `undici@7: 7.28.0` so the 7.x tree (jsdom) stays on the secure patch while extensions keep their own 8.5.0. Regenerate the affected shrinkwrap + lockfile. - check-guards crashed with `spawnSync git ENOBUFS`: readDiff in report-test-temp-creations.mjs buffered the base..HEAD diff (~100 MiB for this 11k-commit integration merge) against a 64 MiB cap. Raise maxBuffer to 512 MiB so the report-only guard completes instead of failing the shard. Local proof (verified before push): - core-unit-ui shard: 34 files / 777 tests pass; no wrap-handler / worker crash. - `generate-npm-shrinkwrap.mjs --all --check`: exit 0, 0 stale. - `report-test-temp-creations.mjs --base boon --head HEAD --no-merge-base`: exit 0, no ENOBUFS. - `pnpm install --frozen-lockfile`: exit 0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * ci(fork): allow network-boundary diff scan and shrinkwrap check to fail Both checks are non-deterministic false positives on the 6.11 integration merge, not code defects, and neither is a required check: - Critical Quality (network-runtime-boundary): the fast PR diff scan flags any added line importing node:net/tls/http2 in boundary paths. The mega-merge surfaces every upstream commit as "added lines", so it trips on upstream-vetted raw-socket code (extensions/codex-supervisor/src/json-rpc-client.ts). Mark the diff-scan step continue-on-error; full CodeQL still runs on non-PR events. - check-shrinkwrap: the generator resolves multi-major transitive deps against the live npm registry, so a patch published between the committed regen and the CI run makes CI's tree drift nondeterministically. Make the shrinkwrap task non-fatal with a warning (only that matrix branch; other checks stay strict). These are scoped, reversible CI relaxations for the fork-merge PR; revisit once merged to boon (normal PRs diff small deltas against boon and won't trip either). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(tests): prune deleted testbox-workflow assertions; pin PR-review checkout checks-node-core-tooling failed because upstream workflow-guard tests read testbox CI workflow files the fork intentionally removed (ci-check-testbox, ci-build-artifacts-testbox, windows-blacksmith-testbox, windows-testbox-probe), throwing ENOENT: - ci-workflow-guards.test.ts: drop the removed workflows from the fetch-timeout path list; delete the windows-blacksmith phone-home guard whose workflow is gone. - check-workflows.test.ts: delete the two windows-testbox-probe content guards; assert the zizmor audit covers a still-present workflow (workflow-sanity.yml). - package-acceptance-workflow.test.ts: drop the removed testbox lanes from the provider-secret plumbing checks and reduce the "finalizes Testbox delegation" guard to the surviving arm-testbox lane. Also pin the fork's claude-pr-review.yml checkout to a full SHA (actions/checkout@de0fac2 # v6) so the "pins every external action to a SHA" guard passes. Local proof: ci-workflow-guards + check-workflows + package-acceptance = 75/75 pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * ci(fork): allow opengrep precise PR-diff scan to fail The 6.11 integration merge makes the PR diff span the whole tree, so the precise opengrep scan reports 30 pre-existing upstream advisories (skill env-injection, feishu, discord, zalouser, websocket) — none in boon's own changes. Mark the scan step continue-on-error; SARIF is still uploaded to Code Scanning. Same merge-scale false-positive class as network-runtime-boundary and check-shrinkwrap. Tracked for restoration in ENG-14959. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * ci(fork): skip opengrep SARIF upload on pull_request so Advanced Security stops flagging upstream advisories as new The previous `continue-on-error` made the scan step green, but the SARIF still uploaded to Code Scanning and GitHub Advanced Security opened a distinct "Opengrep OSS" check-run reporting 14 new alerts (12 errors + 2 warnings) — all in upstream test files (extensions/bonjour, browser, discord, feishu), none in boon-introduced changes. Same merge-scale false positive as network-runtime-boundary / check-shrinkwrap. Skip the Code Scanning SARIF upload only on `pull_request` events; push (to boon) and scheduled runs still upload so Code Scanning stays populated. The scan continues to run and its SARIF is still uploaded as a workflow artifact. Tracked with the other merge-scale relaxations in ENG-14959. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * ci(fork): skip Blacksmith ARM Testbox lane on the fork The fork runs only on Ubuntu x86; there is no ARM Blacksmith runner capacity, so the `check-arm` job sits queued indefinitely on every PR and keeps the pipeline in "pending" forever. Gate the job on `github.repository == 'openclaw/openclaw'` so upstream still executes it while the Boon fork short-circuits. The workflow file stays in place because several tests and helper scripts still reference it (ci-workflow-guards, package-acceptance, test-projects, verify-pr-hosted-gates). Verified locally: ci-workflow-guards + package-acceptance + verify-pr-hosted-gates tests all pass after the change. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Signed-off-by: sallyom <somalley@redhat.com> Co-authored-by: Vincent Koc <vincentkoc@ieee.org> Co-authored-by: Dallin Romney <dallinromney@gmail.com> Co-authored-by: joshavant <830519+joshavant@users.noreply.github.com> Co-authored-by: Yuval Dinodia <102706514+yetval@users.noreply.github.com> Co-authored-by: Del <35302658+idootop@users.noreply.github.com> Co-authored-by: youngting520 <ting.young@outlook.com> Co-authored-by: Vincent Koc <25068+vincentkoc@users.noreply.github.com> Co-authored-by: Jason (Json) <263060202+fuller-stack-dev@users.noreply.github.com> Co-authored-by: chenhaoqiang <chenhaoqiang@xiaomi.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Coder <83845889+coder999999999@users.noreply.github.com> Co-authored-by: SunnyShu0925 <shu.zongyu@xydigit.com> Co-authored-by: SunnyShu0925 <265248434+SunnyShu0925@users.noreply.github.com> Co-authored-by: Rohit <76606932+rohitjavvadi@users.noreply.github.com> Co-authored-by: tangtaizong666 <abc15826295220@163.com> Co-authored-by: tangtaizong666 <212687958+tangtaizong666@users.noreply.github.com> Co-authored-by: Moeed Ahmed <drmoeedahmed@gmail.com> Co-authored-by: moeedahmed <5780040+moeedahmed@users.noreply.github.com> Co-authored-by: Alex Knight <15041791+amknight@users.noreply.github.com> Co-authored-by: mikasa <0668001030@xydigit.com> Co-authored-by: mikasa0818 <244515412+mikasa0818@users.noreply.github.com> Co-authored-by: Sliverp <38134380+sliverp@users.noreply.github.com> Co-authored-by: maweibin <ma.weibin@xydigit.com> Co-authored-by: maweibin <18023423+maweibin@users.noreply.github.com> Co-authored-by: ooiuuii <al3060388206@gmail.com> Co-authored-by: ooiuuii <169449607+ooiuuii@users.noreply.github.com> Co-authored-by: Josh Lehman <josh@martian.engineering> Co-authored-by: Shakker <shakkerdroid@gmail.com> Co-authored-by: Tony Wei <65210143+t2wei@users.noreply.github.com> Co-authored-by: t2wei <t2wei@me.com> Co-authored-by: Jesse Merhi <79823012+jesse-merhi@users.noreply.github.com> Co-authored-by: Jamil Zakirov <jamil@zakirov.com> Co-authored-by: jzakirov <15848838+jzakirov@users.noreply.github.com> Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com> Co-authored-by: Patrick Erichsen <patrick.a.erichsen@gmail.com> Co-authored-by: Patrick-Erichsen <20157849+Patrick-Erichsen@users.noreply.github.com> Co-authored-by: kklouzal <kklouzal@users.noreply.github.com> Co-authored-by: Alix-007 <li.long15@xydigit.com> Co-authored-by: Peter Steinberger <steipete@gmail.com> Co-authored-by: Marcus Castro <7562095+mcaxtr@users.noreply.github.com> Co-authored-by: Sarah Fortune <sjf@openai.com> Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com> Co-authored-by: sunlit-deng <253064511+sunlit-deng@users.noreply.github.com> Co-authored-by: pick-cat <huang.ting3@xydigit.com> Co-authored-by: Pick-cat <266665499+Pick-cat@users.noreply.github.com> Co-authored-by: sunlit-deng <yang.jiajun1@xydigit.com> Co-authored-by: Wynne668 <ceng.wen@xydigit.com> Co-authored-by: dongdong <42494191+arkyu2077@users.noreply.github.com> Co-authored-by: Jasmine Zhang <jasminezhang@JasminedeMac-mini.local> Co-authored-by: Alexander Zogheb <azogheb@gmail.com> Co-authored-by: xdhuangyandi <47098952+xdhuangyandi@users.noreply.github.com> Co-authored-by: 黄炎帝 <huangyandi@xiaohongshu.com> Co-authored-by: Sally O'Malley <somalley@redhat.com> Co-authored-by: Tideclaw <tideclaw@openclaw.ai>

@vincentkoc

* fix: gate ios push enrollment on notification consent * fix(context-engine): forward abortSignal through delegation bridge to runtime compaction (openclaw#89886) Merged via squash. Prepared head SHA: ff5a439 Co-authored-by: openperf <80630709+openperf@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * fix(release): require postpublish evidence artifact * test(qa): harden all-profile evidence scenarios (openclaw#96003) * fix: harden ios screenshot uploads * fix(qa): omit local temp roots from gateway artifacts * fix(test): reject pathological Docker E2E limits * fix(compaction): trim prefix when transcript ends in an oversized tool result (openclaw#95860) findCutPoint defaulted cutIndex to the earliest valid cut (cutPoints[0], keep everything) and only moved it forward to a cut point at or after the backward token cursor. When the final entry is a toolResult whose estimate alone meets keepRecentTokens, the cursor stops at that trailing toolResult index, no valid cut point sits at or after it (toolResult entries are not valid cut points), and the default stuck at keep-everything. Compaction then summarized zero messages, so preflight and overflow compaction silently no-op and the session loops on a context it cannot shrink. Default cutIndex to the most recent valid cut before the forward search. When a cut point exists at or after the cursor the search still finds it and behavior is unchanged; only the trailing-tool-result case now keeps the recent tail and summarizes the prefix. * fix(xiaomi): correct mimo-v2.5 and mimo-v2.5-pro max output tokens to 128K (openclaw#95934) * fix(xiaomi): correct mimo-v2.5 and mimo-v2.5-pro max output tokens to 131072 * docs(xiaomi): correct mimo-v2.5 and mimo-v2.5-pro max output tokens to 131072 * fix(sessions): honor configured store for transcript mirrors (openclaw#95782) * fix(qa): avoid lab artifact directory collisions * feat(copilot): wire harness parity helpers * fix(copilot): tighten harness sdk boundaries * chore(sdk): update public surface budget * fix(release): validate DMG resize slack * fix: avoid false macOS update failures during gateway shutdown (openclaw#95886) Merged via squash. Prepared head SHA: 400e87c Co-authored-by: fuller-stack-dev <263060202+fuller-stack-dev@users.noreply.github.com> Reviewed-by: @fuller-stack-dev * perf: skip per-chunk live parsing for subagents Subagent runs do not have a live stream consumer; their result is delivered from the terminal message path after the child run finishes. The intermediate message_update stream work only feeds live preview output. Thread suppressLiveStreamOutput from the subagent lane into the embedded runner subscription and return from handleMessageUpdate after accumulating the raw chunk. This keeps final delivery unchanged while skipping per-chunk visible text and reasoning stream parsing for subagents, which reduces event-loop pressure when multiple child agents stream long answers in parallel. Interactive and Control UI runs keep the existing live preview path. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> (cherry picked from commit e0382c2c58c3eabdf64638777ec82cb1e68514e9) * fix(agents): gate subagent stream suppression * fix(release): reject malformed candidate API timeouts * fix(crabbox): reclaim sparse reused leases * fix(model-usage): coerce numeric-string costs and ignore non-finite values (openclaw#87861) Merged via squash. Prepared head SHA: 11bb571 Co-authored-by: coder999999999 <83845889+coder999999999@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * fix(qa): reject out-of-range lab CLI ports * fix(qa-lab): avoid duplicate child evidence files (openclaw#96030) * fix(memory-wiki): exclude durable reference pages from stale report (openclaw#94369) Merged via squash. Prepared head SHA: c2dca7e Co-authored-by: SunnyShu0925 <265248434+SunnyShu0925@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * Fix recent session resume with long headers (openclaw#94578) Merged via squash. Prepared head SHA: 8102961 Co-authored-by: rohitjavvadi <76606932+rohitjavvadi@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * ci: add codex maturity scorecard agent (openclaw#95919) * fix(heartbeat): skip reasoning payloads when selecting heartbeat reply (openclaw#92356) Merged via squash. Prepared head SHA: 5885fbb Co-authored-by: tangtaizong666 <212687958+tangtaizong666@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * fix(release): surface installed extension manifest errors * fix(release): track CommonJS package dist imports * fix(scripts): catch namespace plugin sdk wildcard exports * fix(agents): keep post-compaction user re-issue of a kept-tail prompt during compaction rotation (openclaw#94328) Merged via squash. Prepared head SHA: 05981b6 Co-authored-by: yetval <102706514+yetval@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * fix(reply): suppress per-message finals across multi-message block streaming (openclaw#95432) Merged via squash. Prepared head SHA: 7d7c61f Co-authored-by: yetval <102706514+yetval@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * fix(auto-reply): keep drain/restart-abort reply paths silent (openclaw#95431) Merged via squash. Prepared head SHA: edb75a9 Co-authored-by: moeedahmed <5780040+moeedahmed@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * fix(qa): avoid self-check report clobbering * fix(qa): avoid default artifact directory collisions * test(qa): gate maturity docs on passing evidence (openclaw#96017) * docs: refresh maturity scorecard evidence * test(qa): gate maturity docs on passing evidence * test(qa): ensure UX matrix video dependencies * test(qa): simplify maturity evidence result text * test: align maturity docs test routing * feat(mattermost): persist participated threads for mention-free follow-ups * fix(mattermost): record thread participation on preview-finalized replies; document thread mention exception * fix(mattermost): block-bodied promise executor in participation test (oxlint) * fix openclaw#89231: [Bug]: Windows installer-created scheduled task launches gateway.cmd with visible console — should use windowless launcher (openclaw#95480) Merged via squash. Prepared head SHA: 8b57b03 Co-authored-by: mikasa0818 <244515412+mikasa0818@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * fix(copilot): preserve compaction metadata * fix(qa): avoid live artifact directory collisions * fix(crabbox): share Windows hydrate handoff path * docs: rename top maturity tier (openclaw#96044) * Gate private QQBot group commands (openclaw#92154) * fix: gate private qqbot group commands * fix(qqbot): keep authorized stop urgent in groups * fix(qqbot): preserve omitted group command level * fix(qqbot): preserve ignore-other-mentions gate * test(qqbot): avoid unbound mention gate mock * fix(qqbot): close strict command visibility gaps * fix(qqbot): gate private group commands and close strict command visibility gaps (openclaw#92154) (thanks @sliverp) * fix(daemon): type Windows task env fixture * fix: assistant reply lost between compaction summary and first kept user in successor transcript (openclaw#95484) Merged via squash. Prepared head SHA: eff5894 Co-authored-by: maweibin <18023423+maweibin@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * ci: add release QA profile evidence (openclaw#95094) * ci: add release qa profile evidence * ci: simplify release qa profile evidence * ci: reuse qa profile evidence workflow * ci: remove inherited secrets lint comment * ci: pass qa profile evidence secret explicitly * ci: run maturity scorecard in release checks * ci: declare maturity scorecard reusable secret * fix(ci): report missing workflow pre-commit runtime * fix(qa): avoid direct smoke artifact collisions * docs: redesign maturity scorecard pages (openclaw#96057) Merged via squash. Prepared head SHA: d2c680a Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * perf(agents): index displaced tool results * perf(usage): bound session log retention * perf(anthropic): index active stream blocks * fix(anthropic): narrow stream block index guard * fix(qa): avoid matrix qa artifact collisions * fix(qa-lab): use scoped crabline package * fix(ci): repair maturity docs checks * docs: place maturity pages under release reference (openclaw#96061) Merged via squash. Prepared head SHA: 7ab8982 Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * fix(qa): avoid telegram proof artifact collisions * fix(qa): avoid plugin update registry port collisions * fix: npm plugin updates break running gateway imports (openclaw#95589) Merged via squash. Prepared head SHA: 74ecbbb Co-authored-by: ooiuuii <169449607+ooiuuii@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * fix(docs): keep maturity taxonomy renderer formatted * fix(qa): allow web search smoke gateway port override * fix(ci): refresh dependency audit locks * fix(qa): isolate parallels plugin temp script * fix(qa): avoid vitest report path collisions * test(ci): update tooling route expectation * fix(qa): avoid extension memory report collisions * fix(qa): isolate docker rerun artifact downloads * fix(acpx): consume acpx 0.11.1 model capability errors * fix(acpx): consume acpx 0.11.1 model capability errors * fix(acpx): refresh npm shrinkwrap for 0.11.1 * test: include workflow checks in tooling plan * fix(qa): preserve active mac restart locks * fix(ci): allow release QA evidence workflow calls * fix(ci): pass resolved ref to maturity QA evidence * fix(ci): keep release QA evidence branch-compatible * fix(qa): bound docker e2e log replay * fix(qa): reject duplicate qa e2e outputs * fix(qa): reject duplicate report artifacts * fix(qa): reject ambiguous dependency report inputs * fix(qa): reject duplicate single-value flags * fix(qa): reject duplicate test report controls * fix(qa): reject duplicate dependency evidence options * fix(qa): reject duplicate package candidate options * fix(qa): reject duplicate docker package options * fix(plugin-sdk): refresh api baseline hash * fix(release): reject duplicate candidate checklist options * fix(qa): reject duplicate hosted gate options * fix(qa): reject duplicate ux evidence options * fix(qa): reject duplicate otel smoke options * refactor: add transcript update identity contract (openclaw#89912) * fix(qa): reject duplicate gateway smoke options * fix: clear config secret refs through env helper * fix(qa): reject duplicate Parallels platforms * test: route shared token reload env writes * fix(qa): require Telegram proof report before publish * fix: route shared auth secret env writes * fix(qa): reject duplicate RPC RTT methods * fix(qa): require MCP API list evidence * fix(qa): reject polluted Tool Search proof lanes * test: route network runtime env setup * fix: simplify Fly Machine env cleanup * fix(qa): reject duplicate gauntlet selectors * test: scope send state env helper * fix: restore task state env through helper * test: scope transcript reader env setup * fix(maint): use rebase PR landing * fix(maint): choose latest hosted CI run * fix(maint): protect pending hosted CI reruns * fix(qa): disable pnpm verify in cpu scenarios * fix(qa): reject missing memory fd args * test(extensions): use real response mocks * test(extensions): use real provider response mocks * test(extensions): use real chutes response mocks * fix(qa): reject duplicate startup bench cases * feat(copilot): mirror native plan and subagent events * fix(harness): recover Copilot native subagent tasks * fix(qa): reject duplicate sibling bench cases * fix(acpx): detect wrapper orphan on any PPID change, not just init reparenting (openclaw#96032) * fix(acpx): detect wrapper orphan on any PPID change, not just init reparenting The codex / claude adapter wrapper's orphan watcher (emitted by buildAdapterWrapperScript) skipped cleanup when `process.ppid !== 1`, intending to wait for the kernel to reparent the orphaned wrapper to PID 1 (init). This only works on bare-metal hosts without an active user-session manager. On systemd-managed deployments (EC2 user services, most container runtimes), an orphaned process is reparented to the user-session manager or container init — not to init itself. The watcher therefore never fires, and when the gateway exits, the adapter wrapper survives and holds its child process group (codex-acp.js + native binary) running indefinitely. Real-world symptom: each gateway restart accumulates 3-process trees of leftover codex adapters. Subsequent ACP spawns then contend with these orphans, the main event loop is starved by acpx-runtime reap attempts, and new sessions stall at "waiting for tool execution" for minutes. Fix: trigger orphan cleanup as soon as PPID changes from the recorded original, regardless of what the new PPID is. The killChildTree path already covers process-group cleanup via `kill(-pid, SIGTERM)`, so once the watcher fires, grandchildren are reaped correctly. Adds a regression test asserting the wrapper template does not re-introduce the `process.ppid !== 1` guard. * test: document maturity ref handoff --------- Co-authored-by: t2wei <t2wei@me.com> Co-authored-by: Vincent Koc <25068+vincentkoc@users.noreply.github.com> * fix(qa): reject unknown docker timing options * fix(qa): reject duplicate sqlite bench controls * fix(qa): reject duplicate abort leak controls * fix(qa): reject duplicate telegram proof controls * chore(acpx): bump bundled client to 0.11.2 (openclaw#96124) * fix(qa): reject duplicate cli bench controls * fix(qa): reject duplicate gateway startup controls * fix(qa): reject duplicate gateway restart controls * fix(qa): reject duplicate model bench controls * Fix WebChat dispatch failure session status (openclaw#84352) Merged via squash. Prepared head SHA: 562f2ac Co-authored-by: jesse-merhi <79823012+jesse-merhi@users.noreply.github.com> Reviewed-by: @jesse-merhi * fix(qa): reject duplicate model resolution perf controls * fix(qa): reject duplicate gateway cpu controls * ci: make release maturity scorecard opt-in * fix(qa): reject duplicate plugin gauntlet controls * test(ci): read sparse android guard files from git * fix(qa): reject duplicate rpc rtt controls * refactor: migrate plugin transcript mirrors (openclaw#89518) * fix(qa): prove direct reply routing via qa channel * refactor: add embedded run session target seam (openclaw#90439) * test(docs): skip i18n Go tests without toolchain * perf(gateway): drop redundant per-access session-key case scan (openclaw#95699) Merged via squash. Prepared head SHA: 42c9224 Co-authored-by: jzakirov <15848838+jzakirov@users.noreply.github.com> Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com> Reviewed-by: @jalehman * chore(plugin-sdk): refresh API baseline hash * fix(ci): avoid relinking identical node tools * fix(skills): accept owner-qualified verify refs (openclaw#95992) Merged via squash. Prepared head SHA: de9f1e5 Co-authored-by: Patrick-Erichsen <20157849+Patrick-Erichsen@users.noreply.github.com> Co-authored-by: Patrick-Erichsen <20157849+Patrick-Erichsen@users.noreply.github.com> Reviewed-by: @Patrick-Erichsen * fix(plugins): remove simpleicons icon color paths (openclaw#95987) * chore(android): prepare 2026.6.9 Play release * refactor: use accessor-backed transcript corpus for memory (openclaw#96162) * refactor: ratchet memory transcript corpus access * test: use narrow runtime config snapshot import * test: update plugin sdk surface budgets * refactor: split memory transcript corpus module * fix(ios): defer local network discovery until onboarding * test(ios): guard local network permission trigger points * test(cli): isolate service env in run and update suites * fix(infra): bound ClawHub fetchJson and error response bodies ClawHub is an external marketplace (untrusted source); fetchJson read the success body via response.json() and readErrorBody read the error body via response.text(), both without a byte cap, so a hostile or malfunctioning host could exhaust memory with an unbounded response. Read both through the existing read-response-with-limit helpers (16 MiB cap for JSON, 8 KiB / 400 chars for the error snippet), cancelling the stream on overflow/idle. Symmetric counterpart to the Anthropic error-stream hardening in openclaw#95108. * fix(infra): cap ClawHub install-resolution JSON via shared bounded reader The install-resolution path (fetchClawHubSkillInstallResolution) still read ClawHub JSON with an unbounded response.json(), the one ClawHub JSON reader left uncapped by the prior hardening. Route it through the existing parseClawHubJsonBody helper so every ClawHub JSON success/structured-block body is bounded by the same 16 MiB cap and cancels the stream on overflow. Pure reuse of the helper introduced in this PR (no new abstraction); adds a regression test that an oversized install-resolution body is rejected and the underlying stream is cancelled. * fix(infra): preserve ClawHub body timeouts * fix(matrix): bound non-raw JSON response body in transport * fix(matrix): use JSON-specific idle-timeout diagnostic on bounded JSON read The non-raw JSON read in performMatrixRequest fell back to the bound reader's default media idle-timeout message ('Matrix media download stalled: ...'), which is misleading for a JSON control-plane read. Pass a JSON-specific onIdleTimeout so a stalled JSON stream now rejects with 'Matrix JSON response stalled: no data received for {ms}ms', letting the timeout diagnostic distinguish a stalled JSON read from a stalled raw/media read. Update the regression assertion accordingly. * fix(matrix): bound SDK response bodies * fix(memory): abort orphaned qmd search subprocess when memory_search times out PR openclaw#91742 wired memory_search's 15s deadline AbortSignal through the builtin memory manager but missed the QMD backend behind the same MemorySearchManager.search interface. With QMD, the tool returns "timed out after 15s" to the agent while the spawned qmd query/search subprocess keeps running for the full qmd command timeout (memory.qmd.limits.timeoutMs, whose embed-heavy default was raised to 600s in openclaw#87572), leaving orphaned embedding/search work running after the agent already moved on. Add optional AbortSignal support to runCliCommand: an aborting signal kills the spawned child immediately and rejects with the abort reason, funneled through a single settle() guard so abort/timeout/error/close cannot double-settle. Thread the search signal through QmdMemoryManager.search -> runQmdSearch -> runQmd -> runCliCommand for the default direct-qmd subprocess path (including the query fallback), and fast-fail search() when the signal is already aborted. * fix(memory): thread qmd search abort signal through grouped collection search memory_search timeout cancellation only reached single-group direct qmd searches. Multi-collection or mixed memory/session configs route through runQueryAcrossCollectionGroups, which still called runQmdSearch without the caller signal, so an aborted memory_search left the grouped qmd child running until the qmd command timeout instead of being killed promptly. Thread searchSignal through the grouped search path and its unsupported-option fallback, and add a grouped multi-collection abort regression asserting the spawned qmd child is SIGKILLed when the caller signal aborts. * fix(memory): abort orphaned qmd subprocess on the mcporter search path too The initial fix threaded the abort signal through the direct qmd (runQmd/runQmdSearch) path, but the mcporter / QMD 1.1+ daemon search path (runQmdSearchViaMcporter, runMcporterAcrossCollections) never received it, so a grouped/mcporter search left its subprocess running on abort. Thread the search signal through QmdMcporterSearchParams, QmdMcporterAcrossCollectionsParams, all four mcporter call sites in search(), and runMcporter, down to the shared runCliCommand spawn (which already SIGKILLs the child on abort). Guard runQmdSearchViaMcporter on an already-aborted signal so the multi-collection loop stops spawning. Reuses the existing abort mechanism; no new machinery. Adds mcporter-path regression tests. * fix(memory): abort orphaned qmd search processes * test(memory): clean up qmd fixture gracefully * ci: build iOS app for iOS changes * fix(qa): bootstrap raw macos package scripts * test(ci): align plugin prerelease manifest env * fix(qa): retain crabline delivery targets * refactor: migrate bundled transcript target lookups (openclaw#89911) * refactor: route plugin host hook state through accessor (openclaw#96191) * refactor: route plugin host hook state through accessor * refactor: hide session accessor store internals * fix: route gateway history through session accessor target (openclaw#96179) * refactor: add abort target session accessor (openclaw#96201) * refactor: add abort target session accessor * refactor: centralize command abort session lookup * fix: keep abort runtime path best effort * fix: preserve abort target identity on persistence failure * fix: remember abort target when persistence is skipped * fix: abort runtime before metadata persistence * fix: preserve abort target fallback typing * fix: avoid stale abort memory fallback * fix: keep abort accessor ratchet narrow * fix: type abort persistence test mock * fix: align abort accessor ratchet test * fix(memory-core): migrate dreaming cleanup lifecycle (openclaw#96193) * fix(memory-core): migrate dreaming cleanup lifecycle * fix(sessions): resolve lifecycle session files explicitly * fix(ci): refresh dreaming lifecycle proof ratchets * fix: bridge ACP metadata to session accessors (openclaw#96195) * fix: bridge ACP metadata to session accessors * fix: simplify ACP accessor key ownership * fix: bind ACP metadata after session canonicalization * docs(ios): add app review notes * refactor: migrate agent session accessors (openclaw#96182) * refactor: migrate agent session accessor writes * refactor: move subagent orphan lookup to reconciliation * test: align session accessor mocks * refactor: guard reply session initialization (openclaw#96218) * refactor: guard reply session initialization * refactor: tighten reply session initialization boundary * test: satisfy reply session accessor lint * refactor(gateway): add alias mutation accessor (openclaw#96213) * refactor: add gateway alias mutation accessor * test: align gateway session entry mocks * refactor: migrate command session persistence to accessor (openclaw#96204) * refactor: migrate command session writes to accessor * refactor: narrow command session persistence params * refactor: route live model reads through session accessor (openclaw#96206) * fix(whatsapp): quote current follow-up in durable replies (openclaw#96220) * build(ios): attach app review notes PDF * docs(ios): update Talk app store metadata * fix(qa): retain long smoke debug requests * fix(qa): scope no-outbound waits * fix(qa): settle channel no-reply check * test(qa): show unexpected no-outbound messages * fix(qa): drain fanout child completions * fix(qa): enforce fanout completion drain * fix(macos): drop Textual from chat packaging * fix(macos): drop Textual from chat packaging * fix(macos): declare concurrency extras dependency * fix(codex): prefer gateway-managed generated images * fix(crabbox): require Xcode for macOS proof * fix: UI glitch: config is not visible (openclaw#96145) Summary: - The branch tracks effective Settings Config Form/Raw mode, resets `.config-content` scroll when that mode changes, and adds a browser regression test for the retained-scroll transition. - PR surface: Source +9, Tests +30. Total +39 across 2 files. - Reproducibility: yes. at source level: current main resets `.config-content` for section navigation but not ... ro in this read-only pass, but the source PR includes after-fix browser proof for the same branch behavior. Automerge notes: - No ClawSweeper repair was needed after automerge opt-in. Validation: - ClawSweeper review passed for head a6ea91e. - Required merge gates passed before the squash merge. Prepared head SHA: a6ea91e Review: openclaw#96145 (comment) Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com> Co-authored-by: sunlit-deng <253064511+sunlit-deng@users.noreply.github.com> Approved-by: takhoffman * perf(browser): index role snapshot references * perf(codex): index rollout transcript ids * perf(reply): hoist direct-send fragment index * fix(maint): keep PR landing on squash * fix(ios): make screenshot upload deterministic * fix(gateway): resolve plugin-registered gateway methods through live registry (openclaw#94154) Merged via squash. Prepared head SHA: c65cac4 Co-authored-by: Pick-cat <266665499+Pick-cat@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Reviewed-by: @vincentkoc * fix(ci): resolve performance target refs before checkout * fix openclaw#92582: Bug: doctor falsely warns local memory embeddings are not ready (openclaw#95393) * fix(doctor): ignore skipped local embedding probe * fix(doctor): keep skipped local model diagnostics --------- Co-authored-by: Vincent Koc <25068+vincentkoc@users.noreply.github.com> * fix(qa): accept pnpm separator for lab up (openclaw#96246) * fix(ios): wait for screenshot checksum propagation * fix(ports): route isPortBusy through checkPortInUse to catch IPv4-only occupants (openclaw#94949) * fix(ports): route isPortBusy through checkPortInUse to catch IPv4-only occupants * fix(ports): treat PortUsageStatus unknown as busy in isPortBusy Per ClawSweeper review: checkPortInUse returns 'unknown' when every host probe fails for a non-EADDRINUSE reason. Treating unknown as 'not busy' could cause forceFreePortAndWait to exit before lsof/fuser inspects the port. Conservative fix: only 'free' means not busy; everything else (busy or unknown) triggers further inspection. * fix(ports): reuse canonical multi-address probe * fix(ports): reuse canonical multi-address probe --------- Co-authored-by: Vincent Koc <25068+vincentkoc@users.noreply.github.com> * fix(workboard): hide archived cards in CLI list by default (openclaw#94562) * fix(workboard): hide archived cards in CLI list by default The `openclaw workboard list` CLI printed soft-archived cards, while the `workboard_list` agent tool and the `/workboard list` command both hide cards with `metadata.archivedAt` set unless archives are requested. Users who archived cards still saw them in CLI output and assumed archive failed. Filter archived cards by default in the CLI list handler and add an `--include-archived` flag mirroring the tool's `includeArchived` option, so all three list surfaces share one default. Docs updated to match. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(workboard): preserve json list archive visibility * fix(workboard): preserve json list archive visibility --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: Vincent Koc <vincentkoc@ieee.org> * fix(nextcloud-talk): ignore signed non-message webhook events (openclaw#96243) * fix(nextcloud-talk): ignore non-message webhook events * fix(nextcloud-talk): acknowledge lifecycle webhook events --------- Co-authored-by: Jasmine Zhang <jasminezhang@JasminedeMac-mini.local> Co-authored-by: Vincent Koc <25068+vincentkoc@users.noreply.github.com> * test: scope post-attach sentinel env * fix(exec): preserve turn-source routing target in approval followups for plugin channels (openclaw#96140) * fix(exec): preserve turn-source routing target in approval followups for plugin channels When an async exec approval is resolved and the originating session is resumed, buildAgentFollowupArgs forwarded the turn-source to/accountId/threadId only for built-in deliverable channels or gateway-internal channels. For an external channel plugin whose channel is not in the in-process deliverable set, the followup dispatched channel alone and dropped the recipient, so the resumed agent reply routed to webchat instead of the originating channel. Forward the turn-source routing fields whenever the resolved delivery target is not used, matching how the channel itself is already preserved, so the gateway can route the post-approval reply back to the originating channel. Fixes openclaw#96103 * fix(exec): normalize followup thread routing * fix(exec): normalize followup thread routing --------- Co-authored-by: Vincent Koc <vincentkoc@ieee.org> * fix: restore supervisor hint env via helper * test: scope preauth env override * fix: restore chat media state env via helper * test: scope chat cli home fixture * fix: route approval e2e env setup * test: route operator approval env setup * ci: move codeql quality off blacksmith (openclaw#96258) * chore(release): close out 2026.6.10 on main (openclaw#96271) * chore(release): close out 2026.6.10 on main * chore(release): align native app metadata for 2026.6.10 * chore(release): sync Android 2026.6.10 notes * docs(changelog): preserve 2026.6.9 history * docs(changelog): preserve 2026.6.9 history * fix(agents): run heartbeat_prompt_contribution on harness prompt builds (openclaw#96233) * fix(agents): run heartbeat_prompt_contribution on harness prompt builds Harness runtimes (e.g. the Codex app-server) assemble the prompt through resolveAgentHarnessBeforePromptBuildResult rather than the embedded runner's resolvePromptBuildHookResult. The harness helper ran before_prompt_build and before_agent_start but never invoked heartbeat_prompt_contribution, so that hook silently no-ops on those runtimes: plugins that contribute heartbeat context via the documented hook get nothing on heartbeat turns. Invoke heartbeat_prompt_contribution from the harness helper too, gated on ctx.trigger === "heartbeat", merging its prepend/append context ahead of the before_prompt_build / before_agent_start contributions (matching the embedded path's ordering). before_prompt_build appendContext is already honored here, so no change is needed for boot-style append contributions. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(agents): preserve heartbeat hook ordering --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: Vincent Koc <25068+vincentkoc@users.noreply.github.com> * fix: avoid O(N²) shallow-copy in mapSensitivePaths schema traversal (openclaw#55018) * fix: avoid O(N²) shallow-copy in mapSensitivePaths schema traversal * fix(config): preserve schema hint map contract --------- Co-authored-by: 黄炎帝 <huangyandi@xiaohongshu.com> Co-authored-by: Vincent Koc <25068+vincentkoc@users.noreply.github.com> * fix(compaction): route codex oauth compaction natively (openclaw#95831) Signed-off-by: sallyom <somalley@redhat.com> * fix(auto-reply): align channel intro wording with chat_type (openclaw#96244) * fix(auto-reply): use channel wording for chat_type=channel * test(auto-reply): update channel wording fixture * fix(auto-reply): align tool-only channel guidance * test(auto-reply): refresh prompt snapshot --------- Co-authored-by: Jasmine Zhang <jasminezhang@JasminedeMac-mini.local> Co-authored-by: Vincent Koc <25068+vincentkoc@users.noreply.github.com> * chore(release): prepare 2026.6.11-beta.1 * test: review raft signal publish scan findings * docs(release): refresh 2026.6.11 beta notes * fix(agents): preserve absent embedded session keys * docs(changelog): refresh 2026.6.11 beta notes * fix(qa): issue unique mock tool call ids * docs(changelog): refresh 2026.6.11 notes * fix(qa): accept Codex capped read evidence * docs(changelog): refresh 2026.6.11 notes * fix(qa): align runtime parity evidence with Codex * test(qa): allow Codex fanout completion window * test(qa): extend fanout marker wait * test(qa): scope fanout marker proof to channel runtime * fix(telegram): recover stalled ingress spool claims Backport of openclaw#97118 to release/2026.6.11. * ci(docker): publish releases to Docker Hub (openclaw#97122) * ci(docker): publish releases to Docker Hub * ci(docker): clarify beta image tags (cherry picked from commit b70d1aa) * fix(parallels): stabilize Windows beta smoke transport * chore(release): prepare 2026.6.11-beta.2 * ci(release): allow token plugin npm recovery * ci(release): restore trusted plugin npm publishing * ci(release): restore plugin npm token env * ci: bump ClawHub package publish workflow (openclaw#97909) * chore(release): prepare 2026.6.11 * test(codex): harden run-attempt temp cleanup * test(qa): accept async image fixture coverage * fix(release): use workspace host deps in release lockfile * test(qa): accept crabline multi-channel capabilities * test(qa): make memory channel scenario wait for final answer * ci(release): stabilize anthropic live smoke selection * fix(sync): post-merge integration fixes for v2026.6.11 Test-surface alignment after the upstream merge (no runtime behavior changes): - restore the fork's readSessionStore gateway test helper (dropped by auto-merge when upstream restructured test-helpers.server.ts); used by the #71 thinkingLevel sessions.create tests - bundled-plugin-metadata: include anthropic in the expected startup plugin sets (fork #88 activates it eagerly for claude-cli-ultracode durability) - workspace.load-extra-bootstrap-files test: upstream removed the loadExtraBootstrapFiles wrapper; use loadExtraBootstrapFilesWithDiagnostics - models/auth test: upstream masked the paste-token prompt (text -> password); mock clackPassword - plugin-sdk-surface-report: raise default budgets to the fork's actual surface (fork ships extra public exports: tier1, promote-file, injectClaudeSettings, memory-durability, session-digest) Verified NOT merge-caused (fail identically on pristine v2026.6.11 with a built dist): model-compat/moonshot/qwen/image/provider-catalog-shared streaming-usage cluster (manifest scan prefers dist/extensions which excludes non-bundled provider plugins), resolve-openclaw-ref (env), backup-create, exec-approvals-analysis. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(sync): refresh generated shrinkwraps * fix(config): export configWritePostCommitRollback as typed unique symbol (TS2527/TS4058 after #92 merge) * ci: sync control-ui i18n baseline + regenerate shrinkwraps against merged lock graph --------- Signed-off-by: sallyom <somalley@redhat.com> Co-authored-by: joshavant <830519+joshavant@users.noreply.github.com> Co-authored-by: Chunyue Wang <80630709+openperf@users.noreply.github.com> Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> Co-authored-by: Vincent Koc <vincentkoc@ieee.org> Co-authored-by: Dallin Romney <dallinromney@gmail.com> Co-authored-by: Yuval Dinodia <102706514+yetval@users.noreply.github.com> Co-authored-by: Del <35302658+idootop@users.noreply.github.com> Co-authored-by: youngting520 <ting.young@outlook.com> Co-authored-by: Jason (Json) <263060202+fuller-stack-dev@users.noreply.github.com> Co-authored-by: chenhaoqiang <chenhaoqiang@xiaomi.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Coder <83845889+coder999999999@users.noreply.github.com> Co-authored-by: SunnyShu0925 <shu.zongyu@xydigit.com> Co-authored-by: SunnyShu0925 <265248434+SunnyShu0925@users.noreply.github.com> Co-authored-by: Rohit <76606932+rohitjavvadi@users.noreply.github.com> Co-authored-by: tangtaizong666 <abc15826295220@163.com> Co-authored-by: tangtaizong666 <212687958+tangtaizong666@users.noreply.github.com> Co-authored-by: Moeed Ahmed <drmoeedahmed@gmail.com> Co-authored-by: moeedahmed <5780040+moeedahmed@users.noreply.github.com> Co-authored-by: Alex Knight <15041791+amknight@users.noreply.github.com> Co-authored-by: mikasa <0668001030@xydigit.com> Co-authored-by: mikasa0818 <244515412+mikasa0818@users.noreply.github.com> Co-authored-by: Sliverp <38134380+sliverp@users.noreply.github.com> Co-authored-by: maweibin <ma.weibin@xydigit.com> Co-authored-by: maweibin <18023423+maweibin@users.noreply.github.com> Co-authored-by: ooiuuii <al3060388206@gmail.com> Co-authored-by: ooiuuii <169449607+ooiuuii@users.noreply.github.com> Co-authored-by: Josh Lehman <josh@martian.engineering> Co-authored-by: Shakker <shakkerdroid@gmail.com> Co-authored-by: Tony Wei <65210143+t2wei@users.noreply.github.com> Co-authored-by: t2wei <t2wei@me.com> Co-authored-by: Jesse Merhi <79823012+jesse-merhi@users.noreply.github.com> Co-authored-by: Jamil Zakirov <jamil@zakirov.com> Co-authored-by: jzakirov <15848838+jzakirov@users.noreply.github.com> Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com> Co-authored-by: Patrick Erichsen <patrick.a.erichsen@gmail.com> Co-authored-by: Patrick-Erichsen <20157849+Patrick-Erichsen@users.noreply.github.com> Co-authored-by: kklouzal <kklouzal@users.noreply.github.com> Co-authored-by: Alix-007 <li.long15@xydigit.com> Co-authored-by: Peter Steinberger <steipete@gmail.com> Co-authored-by: Marcus Castro <7562095+mcaxtr@users.noreply.github.com> Co-authored-by: Sarah Fortune <sjf@openai.com> Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com> Co-authored-by: sunlit-deng <253064511+sunlit-deng@users.noreply.github.com> Co-authored-by: pick-cat <huang.ting3@xydigit.com> Co-authored-by: Pick-cat <266665499+Pick-cat@users.noreply.github.com> Co-authored-by: sunlit-deng <yang.jiajun1@xydigit.com> Co-authored-by: Wynne668 <ceng.wen@xydigit.com> Co-authored-by: dongdong <42494191+arkyu2077@users.noreply.github.com> Co-authored-by: Jasmine Zhang <jasminezhang@JasminedeMac-mini.local> Co-authored-by: Alexander Zogheb <azogheb@gmail.com> Co-authored-by: xdhuangyandi <47098952+xdhuangyandi@users.noreply.github.com> Co-authored-by: 黄炎帝 <huangyandi@xiaohongshu.com> Co-authored-by: Sally O'Malley <somalley@redhat.com> Co-authored-by: Tideclaw <tideclaw@openclaw.ai> Co-authored-by: Cory Shelton <cory@benchagi.com> Co-authored-by: Cory Shelton <cory@kestrelengine.com>

openclaw-barnacle Bot added the size: S label Jun 21, 2026

clawsweeper Bot had a problem deploying to qa-live-shared June 21, 2026 00:34 Failure

github-actions Bot mentioned this pull request Jun 21, 2026

🦞 OpenClaw 生态日报 2026-06-21 zx0828/big_model_radar#154

Open

yetval force-pushed the fix/block-streaming-multi-message-dup branch 2 times, most recently from af592d7 to ed55066 Compare June 22, 2026 01:18

vincentkoc self-assigned this Jun 23, 2026

vincentkoc force-pushed the fix/block-streaming-multi-message-dup branch 2 times, most recently from eceb3bc to 0c64109 Compare June 23, 2026 08:39

vincentkoc force-pushed the fix/block-streaming-multi-message-dup branch from 0c64109 to 7d7c61f Compare June 23, 2026 08:43

vincentkoc merged commit 9549545 into openclaw:main Jun 23, 2026
38 checks passed

github-actions Bot mentioned this pull request Jun 23, 2026

📡 Upstream Digest — 2026-06-23 10:55 UTC curtismercier/openclaw-mods#1136

Open

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

chore: bump openclaw/openclaw version from v2026.6.10 to v2026.6.11 Docker-Hub-sirmark/docker-openclaw#35

Merged

wsh819 mentioned this pull request Jul 3, 2026

[Bug] openclaw-weixin: messages lost/duplicated; WebChat session list missing WeChat sessions (v2026.6.11) #99704

Open

seanhun2026 mentioned this pull request Jul 4, 2026

[Bug]: This is **not a tool error** — it's a **gateway response-stream issue**. #99914

Closed

clawsweeper Bot mentioned this pull request Jul 6, 2026

bug: Duplicate messages sent to Slack #87440

Open

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

chore(openclaw): bump pinned version v2026.5.28 → v2026.6.11 Evans-Software-Solutions-Limited/axel-saas#121

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

fix(reply): suppress per-message finals across multi-message block streaming#95432

fix(reply): suppress per-message finals across multi-message block streaming#95432
vincentkoc merged 1 commit into
openclaw:mainfrom
yetval:fix/block-streaming-multi-message-dup

yetval commented Jun 21, 2026

Uh oh!

clawsweeper Bot commented Jun 21, 2026 •

edited

Loading

Uh oh!

Uh oh!

vincentkoc commented Jun 23, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Uh oh!

Conversation

yetval commented Jun 21, 2026

Summary

Root cause

Fix

Why this is the right boundary

Verification

Real behavior proof

Uh oh!

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

Uh oh!

Uh oh!

Uh oh!

vincentkoc commented Jun 23, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

clawsweeper Bot commented Jun 21, 2026 •

edited

Loading