fix(cli): bridge inter-tool commentary events to channel progress by anagnorisis2peripeteia · Pull Request #90883 · openclaw/openclaw

anagnorisis2peripeteia · 2026-06-06T08:39:04Z

Summary

Bridge CLI-runtime item/preamble commentary events into the existing channel progress callback path.

Before this, runCliAgentWithLifecycle forwarded assistant, reasoning, and tool events, but not item/preamble commentary. A CLI backend could emit commentary progress on the agent-event bus and channels would never see it.

This PR keeps the fix in shared CLI/core plumbing:

adds the commentary bridge next to the existing assistant/reasoning/tool bridges
forwards primary CLI runs to opts.onItemEvent
forwards queued follow-up CLI runs through the existing follow-up progress path
keeps the branch bridge-only; renderer/noCompact behavior was removed as separate product/API scope

Verification

node scripts/run-vitest.mjs src/auto-reply/reply/agent-runner-execution.test.ts src/auto-reply/reply/followup-runner.test.ts — 254 tests passed
./node_modules/.bin/oxfmt --check src/auto-reply/reply/agent-runner-cli-dispatch.ts src/auto-reply/reply/agent-runner-execution.test.ts src/auto-reply/reply/agent-runner-execution.ts src/auto-reply/reply/followup-runner.test.ts src/auto-reply/reply/followup-runner.ts
node --max-old-space-size=8192 --import tsx scripts/generate-plugin-sdk-api-baseline.ts --check
git diff --check
pnpm tsgo

Real behavior proof

Behavior addressed: CLI-runtime preamble/commentary progress events reach the existing channel progress path instead of being dropped by runCliAgentWithLifecycle.

Real environment tested: Local OpenClaw setup with the combined #90883 delivery bridge and #89834 Claude CLI producer, observed through the Telegram progress draft flow.

Exact steps or command run after this patch: Ran the existing Telegram/Mantis-style proof flow against the combined stack and triggered a Claude CLI turn that emitted inter-tool commentary while the channel progress draft was active.

Evidence after fix: Recording of the live progress draft showing commentary rendering during the run: https://raw.githubusercontent.com/anagnorisis2peripeteia/openclaw/proof/commentary-persist-v2/commentary-transient.gif

Observed result after fix: The transient progress draft includes the Claude CLI commentary text while the run is still in progress, confirming #90883 carries item/preamble commentary through the shared channel progress callback path.

What was not tested: #90883 by itself does not add the Claude CLI producer; #89834 remains the producer-side PR. Renderer/noCompact behavior is intentionally out of scope for this bridge-only PR.

Notes

This is the delivery bridge only. The Claude CLI producer remains in #89834 and should be reviewed/landed after this if we want the complete Claude-visible path.

clawsweeper · 2026-06-06T08:41:32Z

Codex review: needs maintainer review before merge. Reviewed June 8, 2026, 8:34 AM ET / 12:34 UTC.

Summary
The branch adds an internal CLI item/preamble commentary bridge that forwards primary and queued CLI runtime events to the existing channel progress onItemEvent path, adds focused tests, and refreshes the plugin SDK API hash.

PR surface: Source +51, Tests +129, Generated 0. Total +180 across 6 files.

Reproducibility: yes. from source: current main has no item/preamble subscriber in runCliAgentWithLifecycle, so a CLI backend that emits that event cannot reach opts.onItemEvent through this path. I did not run tests in this read-only review.

Review metrics: none identified.

Merge readiness
Overall: 🐚 platinum hermit
Proof: 🦞 diamond lobster ✨ media proof bonus
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:

Keep review sequenced with feat(cli): emit commentary progress events from Claude CLI parser #89834 so the producer and bridge complete the visible Claude CLI path.
Use final-head Telegram Desktop proof if maintainers want independent transport evidence after the force-push.

Mantis proof suggestion
A native Telegram proof would materially verify the visible progress draft path in the transport UI on the current head. A maintainer can ask Mantis to capture proof by posting a new PR comment that starts with the OpenClaw Mantis account mention, followed by:

telegram desktop proof: verify CLI item/preamble commentary appears in the Telegram progress draft while a CLI run is active.

Risk before merge

[P1] The bridge is delivery-only: the visible Claude CLI commentary path remains incomplete until the companion producer at feat(cli): emit commentary progress events from Claude CLI parser #89834 or another producer lands.
[P1] Forwarding item/preamble events into channel progress changes visible progress delivery for CLI backends that emit those events, so maintainers should keep the targeted runner coverage and Telegram proof in view before merge.

Maintainer options:

Land With Producer Sequencing (recommended)
Merge this bridge when maintainers are ready for the companion producer PR to follow so the end-to-end Claude CLI commentary path is complete.
Request Final-Head Telegram Proof
Ask for fresh Telegram Desktop proof on the current head if maintainers want transport evidence after the force-push and bridge cleanup commit.
Pause The Stack
Keep this PR open if maintainers want the producer and Telegram follow-up ordering settled before adding the shared delivery bridge to main.

Next step before merge

[P2] Human maintainer review is the remaining action because the patch is message-delivery-sensitive and should be sequenced with the companion producer; there is no narrow automated repair to request.

Security
Cleared: No concrete security or supply-chain concern found; the diff is limited to internal TypeScript event forwarding, tests, and generated API hash metadata.

Review details

Best possible solution:

Land the shared bridge after maintainer review of the targeted checks and sequencing with the companion producer PR, while keeping Telegram-specific progress behavior work in the linked follow-up items.

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

Yes, from source: current main has no item/preamble subscriber in runCliAgentWithLifecycle, so a CLI backend that emits that event cannot reach opts.onItemEvent through this path. I did not run tests in this read-only review.

Is this the best way to solve the issue?

Yes, this is the right layer for the fix: the shared CLI lifecycle wrapper already owns assistant, reasoning, and tool event bridges, and this patch extends that pattern instead of special-casing a backend or channel.

AGENTS.md: found and applied where relevant.

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

Label changes

Label changes:

add proof: sufficient: Contributor real behavior proof is sufficient. The PR body supplies a real Telegram recording showing commentary rendered in the live progress draft on the combined producer plus bridge stack.

Label justifications:

P2: This fixes lost CLI commentary progress in channel-visible runs with limited blast radius and an open companion producer path.
merge-risk: 🚨 message-delivery: The diff forwards a new CLI item/preamble event stream into channel progress, so mistakes or sequencing gaps can affect visible progress message delivery.
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 (recording): The PR body supplies a real Telegram recording showing commentary rendered in the live progress draft on the combined producer plus bridge stack.
proof: sufficient: Contributor real behavior proof is sufficient. The PR body supplies a real Telegram recording showing commentary rendered in the live progress draft on the combined producer plus bridge stack.
proof: 🎥 video: Contributor real behavior proof includes video or recording evidence. The PR body supplies a real Telegram recording showing commentary rendered in the live progress draft on the combined producer plus bridge stack.
mantis: telegram-visible-proof: Mantis should capture Telegram visible proof. The change is intended to surface CLI commentary as visible Telegram progress draft text, which a short Telegram Desktop recording can demonstrate.

Evidence reviewed

PR surface:

Source +51, Tests +129, Generated 0. Total +180 across 6 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	3	66	15	+51
Tests	2	129	0	+129
Docs	0	0	0	0
Config	0	0	0	0
Generated	1	2	2	0
Other	0	0	0	0
Total	6	197	17	+180

What I checked:

Repository policy read: Root AGENTS.md and the Telegram maintainer note were read; the review applied the whole-path source check and real Telegram proof expectations for visible streaming behavior. (AGENTS.md:1, 439dcbde3b1f)
Current main lacks a CLI commentary bridge: Current runCliAgentWithLifecycle creates assistant, reasoning, and tool bridges, but has no item/preamble bridge or onCommentaryText callback. (src/auto-reply/reply/agent-runner-cli-dispatch.ts:176, 439dcbde3b1f)
PR adds the missing bridge at the shared CLI boundary: The PR head adds createCommentaryEventBridge, filters stream: "item" plus kind: "preamble", trims non-empty progressText, and drains it with the other CLI bridges. (src/auto-reply/reply/agent-runner-cli-dispatch.ts:190, 4426767e65ef)
Primary and queued callers are covered: The PR maps primary CLI commentary into opts.onItemEvent and maps queued follow-up commentary through forwardFollowupProgressEvent, matching the existing progress path shape. (src/auto-reply/reply/agent-runner-execution.ts:2140, 4426767e65ef)
Downstream channel contract exists: Current Telegram already routes kind: "preamble" item events to progressDraft.pushCommentaryProgress, so the bridge lands on an existing channel rendering contract rather than adding Telegram-specific policy. (extensions/telegram/src/bot-message-dispatch.ts:2340, 439dcbde3b1f)
Sibling producer contract checked: The Codex app-server projector already emits commentary progress as stream: "item", kind: "preamble", supporting onItemEvent as the existing cross-channel shape for commentary progress. (extensions/codex/src/app-server/event-projector.ts:1010, 439dcbde3b1f)

Likely related people:

vincentkoc: Blame on the current shared CLI dispatch, primary runner, follow-up runner, and Telegram progress hook points to Vincent Koc's recent commit carrying this area on current main. (role: recent area contributor; confidence: medium; commits: 88c1af0a2cb4; files: src/auto-reply/reply/agent-runner-cli-dispatch.ts, src/auto-reply/reply/agent-runner-execution.ts, src/auto-reply/reply/followup-runner.ts)
Mason Huang: The current main commit is a recent auto-reply/provider-routing touch that appears in path history for the runner and test files involved in this PR. (role: recent adjacent contributor; confidence: low; commits: 439dcbde3b1f; files: src/auto-reply/reply/agent-runner-execution.ts, src/auto-reply/reply/agent-runner-execution.test.ts)
obviyus: The live timeline shows obviyus assigned to this PR and the current PR head includes obviyus-authored cleanup/baseline commits after the original contributor change. (role: assigned reviewer and branch contributor; confidence: medium; commits: 821fd7c1c49c, 4426767e65ef; files: src/auto-reply/reply/agent-runner-cli-dispatch.ts, docs/.generated/plugin-sdk-api-baseline.sha256)

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.

anagnorisis2peripeteia · 2026-06-06T08:51:46Z

@clawsweeper re-review

clawsweeper · 2026-06-06T08:51:48Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Complete
Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
Run: https://github.com/openclaw/clawsweeper/actions/runs/27057924785
Updated: 2026-06-06T09:00:46.534Z

anagnorisis2peripeteia · 2026-06-06T11:52:55Z

@clawsweeper re-review

clawsweeper · 2026-06-06T11:52:57Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Complete
Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
Run: https://github.com/openclaw/clawsweeper/actions/runs/27061579367
Updated: 2026-06-06T12:04:00.166Z

Inter-tool commentary (assistant text emitted before a tool call, surfaced by the CLI parser as a stream:"item", kind:"preamble" agent event) landed on the agent-event bus with no subscriber and was silently dropped: runCliAgentWithLifecycle bridges the assistant, reasoning, and tool streams to channel callbacks, but the item/preamble stream had no bridge. Add createCommentaryEventBridge to forward it to onItemEvent, so CLI commentary reaches the channel's commentary render hook. This is the CLI-dispatch delivery half of the commentary feature: the parser emission (claude-cli) feeds the bus; this bridge delivers it to the channel. Addresses the claude-cli case of intermediate-text-lost (openclaw#87326 / openclaw#84486).

obviyus · 2026-06-08T12:36:42Z

Landed via rebase onto main.

Scoped tests: node scripts/run-vitest.mjs src/auto-reply/reply/agent-runner-execution.test.ts src/auto-reply/reply/followup-runner.test.ts; ./node_modules/.bin/oxfmt --check src/auto-reply/reply/agent-runner-cli-dispatch.ts src/auto-reply/reply/agent-runner-execution.test.ts src/auto-reply/reply/agent-runner-execution.ts src/auto-reply/reply/followup-runner.test.ts src/auto-reply/reply/followup-runner.ts; node --max-old-space-size=8192 --import tsx scripts/generate-plugin-sdk-api-baseline.ts --check; git diff --check; pnpm tsgo; .agents/skills/autoreview/scripts/autoreview --mode branch --base origin/main
Real behavior proof: latest Real behavior proof check passed with the sanitized proof section in the PR body.
CI rerun: checks-node-agentic-commands-agent-channel passed on rerun after the transient SIGTERM-test failure.
Changelog: not updated; this is core delivery plumbing for CLI commentary progress, with user-visible producer work still in feat(cli): emit commentary progress events from Claude CLI parser #89834.
Land commit: 4426767
Merge commit: 2858c62

Thanks @anagnorisis2peripeteia!

…26.6.6) (#1040) 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.5` → `2026.6.6` | --- ### Release Notes <details> <summary>openclaw/openclaw (ghcr.io/openclaw/openclaw)</summary> ### [`v2026.6.6`](https://github.com/openclaw/openclaw/blob/HEAD/CHANGELOG.md#202666) [Compare Source](openclaw/openclaw@v2026.6.5...v2026.6.6) ##### Highlights - Security boundaries are substantially tighter across transcripts, sandbox binds, host environment inheritance, MCP stdio, Codex HTTP access, native search policy, elevated sender checks, deleted-agent ACP bypasses, loopback tools, Discord moderation, and Teams group actions; exec approvals now fail closed on timeout. ([#91529](openclaw/openclaw#91529), [#91618](openclaw/openclaw#91618), [#91615](openclaw/openclaw#91615), [#91619](openclaw/openclaw#91619), [#91741](openclaw/openclaw#91741), [#91745](openclaw/openclaw#91745), [#91746](openclaw/openclaw#91746), [#91748](openclaw/openclaw#91748), [#91749](openclaw/openclaw#91749), [#91750](openclaw/openclaw#91750), [#91751](openclaw/openclaw#91751), [#91752](openclaw/openclaw#91752), [#91763](openclaw/openclaw#91763), [#89938](openclaw/openclaw#89938)) Thanks [@joshavant](https://github.com/joshavant), [@pgondhi987](https://github.com/pgondhi987), [@mmaps](https://github.com/mmaps), [@eleqtrizit](https://github.com/eleqtrizit), [@shakkernerd](https://github.com/shakkernerd), and [@drobison00](https://github.com/drobison00). - Telegram delivery is safer and more coherent: account-scoped topics route to the right agent, streamed text survives tool calls, `/compact` works on generic ingress, callback handling uses concrete APIs, draft chunking is shared, durable dispatch dedupe moved into the SDK, and unauthorized DM text stays out of cache and prompt context. ([#91189](openclaw/openclaw#91189), [#88682](openclaw/openclaw#88682), [#89588](openclaw/openclaw#89588), [#90212](openclaw/openclaw#90212), [#91876](openclaw/openclaw#91876), [#91874](openclaw/openclaw#91874), [#91904](openclaw/openclaw#91904), [#91478](openclaw/openclaw#91478), [#91915](openclaw/openclaw#91915)) Thanks [@codysai001](https://github.com/codysai001), [@alexzhu0](https://github.com/alexzhu0), [@joelnishanth](https://github.com/joelnishanth), [@snowzlm](https://github.com/snowzlm), [@obviyus](https://github.com/obviyus), and [@sallyom](https://github.com/sallyom). - iMessage recovery and delivery now cover always-on inbound restart, durable echo markers, block streaming, idle approval discovery, hardened outbound transport, and actionable inbound startup diagnostics. ([#91335](openclaw/openclaw#91335), [#91449](openclaw/openclaw#91449), [#88969](openclaw/openclaw#88969), [#88530](openclaw/openclaw#88530), [#91783](openclaw/openclaw#91783), [#91785](openclaw/openclaw#91785)) Thanks [@omarshahine](https://github.com/omarshahine), [@jmissig](https://github.com/jmissig), and [@colmbrogan](https://github.com/colmbrogan). - Browser and MCP connectivity gained existing-session CDP support, discovered WebSocket validation, default-profile `cdpUrl` handling, safer browser-output boundaries, Streamable HTTP loopback transport, corrected OAuth/SSE authorization handling, and broader schema compatibility. ([#91422](openclaw/openclaw#91422), [#89851](openclaw/openclaw#89851), [#91736](openclaw/openclaw#91736), [#91747](openclaw/openclaw#91747), [#91451](openclaw/openclaw#91451), [#80143](openclaw/openclaw#80143)) Thanks [@pgondhi987](https://github.com/pgondhi987), [@anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia), [@lifuyue](https://github.com/lifuyue), [@eleqtrizit](https://github.com/eleqtrizit), [@LiuwqGit](https://github.com/LiuwqGit), and [@HemantSudarshan](https://github.com/HemantSudarshan). - Control UI startup and first-reply latency are lower through cached model metadata, removal of the startup catalog wait, lazy slash-command loading, and first-event tracing with slow-reply diagnostics. ([#91531](openclaw/openclaw#91531), [#91538](openclaw/openclaw#91538), [#91568](openclaw/openclaw#91568), [#91583](openclaw/openclaw#91583), [#91598](openclaw/openclaw#91598)) - Provider support expands with OpenRouter OAuth onboarding and Claude Fable 5 adaptive thinking, while Codex sessions keep correct compaction ownership, local models skip guardian review, dynamic tool progress normalizes cleanly, and Gemma 4 reasoning replay is preserved. ([#91830](openclaw/openclaw#91830), [#91882](openclaw/openclaw#91882), [#91590](openclaw/openclaw#91590), [#88630](openclaw/openclaw#88630), [#88768](openclaw/openclaw#88768), [#91696](openclaw/openclaw#91696)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@joshavant](https://github.com/joshavant), [@bdjben](https://github.com/bdjben), and [@Coder-Wangyankun](https://github.com/Coder-Wangyankun). ##### Changes - CLI progress: emit Claude CLI commentary progress events and bridge inter-tool commentary into channel progress without exposing internal protocol scaffolding. ([#89834](openclaw/openclaw#89834), [#90883](openclaw/openclaw#90883)) Thanks [@anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia). - Observability: allow trusted diagnostics channels to capture tool input/output content, add first-assistant-event traces, and warn on slow initial replies. ([#91256](openclaw/openclaw#91256), [#91568](openclaw/openclaw#91568), [#91583](openclaw/openclaw#91583)) Thanks [@amknight](https://github.com/amknight). - Plugins/ClawHub: dogfood reusable package publishing, let dry runs skip publish approval, allow declared installed trusted hooks, report managed plugin version drift, and warn instead of failing on retired Skill Workshop configuration. ([#91574](openclaw/openclaw#91574), [#91591](openclaw/openclaw#91591), [#90004](openclaw/openclaw#90004), [#90927](openclaw/openclaw#90927), [#90838](openclaw/openclaw#90838)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@brokemac79](https://github.com/brokemac79), and [@lonexreb](https://github.com/lonexreb). - Memory/providers: move the local llama.cpp runtime into its provider plugin, batch embeddings across files, persist the agent model catalog cache, and keep QMD JSON search one-shot while filtering stale REM recall previews. ([#91324](openclaw/openclaw#91324), [#89138](openclaw/openclaw#89138), [#90457](openclaw/openclaw#90457), [#91837](openclaw/openclaw#91837), [#91851](openclaw/openclaw#91851)) Thanks [@osolmaz](https://github.com/osolmaz), [@mushuiyu886](https://github.com/mushuiyu886), [@ai-hpc](https://github.com/ai-hpc), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Channels/mobile: add the QQBot group mention toggle, improve iPad and iPhone control surfaces, and expose the active connection host in the TUI footer. ([#91423](openclaw/openclaw#91423), [#91557](openclaw/openclaw#91557), [#89909](openclaw/openclaw#89909)) Thanks [@cxyhhhhh](https://github.com/cxyhhhhh), [@Solvely-Colin](https://github.com/Solvely-Colin), and [@baskduf](https://github.com/baskduf). - Performance: prewarm TUI runtime plugins, deduplicate plugin auto-enable fanout, trim dense text-delta snapshots, and reuse prepared startup model metadata. ([#90782](openclaw/openclaw#90782), [#89978](openclaw/openclaw#89978), [#91580](openclaw/openclaw#91580), [#91531](openclaw/openclaw#91531)) Thanks [@RomneyDa](https://github.com/RomneyDa) and [@ai-hpc](https://github.com/ai-hpc). ##### Fixes - Agent/session recovery: drop stale approval follow-ups after session rebind, remove drained reply-queue items by identity, recover stale main and visible replies, preserve Codex context-engine compaction ownership, lower the default compaction timeout to 180 seconds while respecting explicit configuration, and keep provider-failure terminal lifecycle state correct. ([#85679](openclaw/openclaw#85679), [#91450](openclaw/openclaw#91450), [#91566](openclaw/openclaw#91566), [#91840](openclaw/openclaw#91840), [#91590](openclaw/openclaw#91590), [#91361](openclaw/openclaw#91361), [#91895](openclaw/openclaw#91895)) Thanks [@openperf](https://github.com/openperf), [@yetval](https://github.com/yetval), [@joshavant](https://github.com/joshavant), [@wangmiao0668000666](https://github.com/wangmiao0668000666), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - User-visible content boundaries: suppress Codex/Harmony protocol artifacts, neutralize browser and LanceDB memory media directives, redact transcript images, and preserve native `/compact` replies through source suppression. ([#89151](openclaw/openclaw#89151), [#91422](openclaw/openclaw#91422), [#91425](openclaw/openclaw#91425), [#91529](openclaw/openclaw#91529), [#90212](openclaw/openclaw#90212)) Thanks [@joelnishanth](https://github.com/joelnishanth), [@pgondhi987](https://github.com/pgondhi987), [@joshavant](https://github.com/joshavant), and [@snowzlm](https://github.com/snowzlm). - Channel delivery: keep WhatsApp captured replies attached to the successor controller after restart, retry Feishu rate limits, preserve Mattermost thread replies, canonicalize LINE webhook paths, restore Discord reply hydration and runtime timeout exports, and show OpenAI Realtime WebRTC assistant transcripts. ([#85823](openclaw/openclaw#85823), [#89659](openclaw/openclaw#89659), [#91684](openclaw/openclaw#91684), [#91649](openclaw/openclaw#91649), [#90263](openclaw/openclaw#90263), [#91686](openclaw/openclaw#91686), [#90426](openclaw/openclaw#90426)) Thanks [@itsuzef](https://github.com/itsuzef), [@ladygege](https://github.com/ladygege), [@jacobtomlinson](https://github.com/jacobtomlinson), [@fuller-stack-dev](https://github.com/fuller-stack-dev), and [@shushushv](https://github.com/shushushv). - Cron: cancel active task runs cleanly, preserve terminal timeout/cancel state, and recover no-deliver tool warnings instead of silently losing the outcome. ([#90666](openclaw/openclaw#90666), [#90678](openclaw/openclaw#90678)) Thanks [@ai-hpc](https://github.com/ai-hpc). - Gateway/config/auth: share the approval runtime socket token, replace arrays explicitly in `config.patch`, skip the deleted-agent guard only for valid ACP harness sessions, surface headless LaunchAgent state, verify SQLite auth migration before cleanup, and arm QMD startup maintenance. ([#87105](openclaw/openclaw#87105), [#91551](openclaw/openclaw#91551), [#91219](openclaw/openclaw#91219), [#91614](openclaw/openclaw#91614), [#91740](openclaw/openclaw#91740), [#91978](openclaw/openclaw#91978)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev) and [@scotthuang](https://github.com/scotthuang). - Providers/Codex: clarify quota errors, restore the Codex synthetic usage line, canonicalize Codex protocol assets, require API-key auth for realtime voice, normalize ACP model refs, preserve Gemma 4 `reasoning_content`, and avoid guardian review for local models. ([#91390](openclaw/openclaw#91390), [#91709](openclaw/openclaw#91709), [#91507](openclaw/openclaw#91507), [#91567](openclaw/openclaw#91567), [#88630](openclaw/openclaw#88630), [#91696](openclaw/openclaw#91696)) Thanks [@hxy91819](https://github.com/hxy91819), [@brokemac79](https://github.com/brokemac79), [@RomneyDa](https://github.com/RomneyDa), [@joshavant](https://github.com/joshavant), and [@Coder-Wangyankun](https://github.com/Coder-Wangyankun). - Updates/builds: recover package Gateway restarts after refresh failure, expose plugin convergence repair, fall back to Corepack in PATH-less pnpm environments, seed the correct Docker store packages, and keep ClawHub dry-run and publish paths reusable. ([#91581](openclaw/openclaw#91581), [#91599](openclaw/openclaw#91599), [#91547](openclaw/openclaw#91547), [#91591](openclaw/openclaw#91591)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev), [@sallyom](https://github.com/sallyom), and [@Patrick-Erichsen](https://github.com/Patrick-Erichsen). - UI: require explicit user intent before opening chat sessions and drain restored chat queues after session switches. ([#91480](openclaw/openclaw#91480)) Thanks [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Android: avoid the `dataSync` foreground-service type for persistent nodes. ([#80082](openclaw/openclaw#80082)) Thanks [@davelutztx](https://github.com/davelutztx). - Native hooks: bound relay lifetimes so abandoned native hook connections cannot linger indefinitely. ([#91550](openclaw/openclaw#91550)) Thanks [@joshavant](https://github.com/joshavant). </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.erwanleboucher.dev/eleboucher/homelab/pulls/1040

openclaw-barnacle Bot added size: S triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. labels Jun 6, 2026

anagnorisis2peripeteia mentioned this pull request Jun 6, 2026

feat(cli): emit commentary progress events from Claude CLI parser #89834

Merged

clawsweeper Bot temporarily deployed to qa-live-shared June 6, 2026 08:48 Inactive

openclaw-barnacle Bot removed the triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. label Jun 6, 2026

clawsweeper Bot added proof: 🎥 video Contributor real behavior proof includes video or recording evidence. and removed proof: 📸 screenshot Contributor real behavior proof includes screenshot evidence. labels Jun 6, 2026

openclaw-barnacle Bot added triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. and removed proof: sufficient ClawSweeper judged the real behavior proof convincing. labels Jun 6, 2026

anagnorisis2peripeteia mentioned this pull request Jun 6, 2026

feat(streaming): opt-in persistProgress mode for tool+commentary lines #89850

Closed

openclaw-barnacle Bot removed the triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. label Jun 6, 2026

This was referenced Jun 6, 2026

feat(telegram): non-streaming tool+commentary progress accumulator #89890

Closed

Telegram: inter-tool commentary clobbers tool progress in non-persist progress mode (diverges from other streaming channels) #90962

Open

wsyjh8 mentioned this pull request Jun 6, 2026

fix(telegram): keep tool progress after non-final commentary #90997

Open

anagnorisis2peripeteia and others added 3 commits June 8, 2026 17:36

refactor(cli): unify agent event bridge cleanup

821fd7c

build(plugin-sdk): refresh api baseline for cli commentary bridge

4426767

obviyus force-pushed the fix/cli-commentary-delivery branch from 4c466b1 to 4426767 Compare June 8, 2026 12:13

openclaw-barnacle Bot added docs Improvements or additions to documentation size: M triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. and removed size: S proof: sufficient ClawSweeper judged the real behavior proof convincing. labels Jun 8, 2026

obviyus self-assigned this Jun 8, 2026

openclaw-barnacle Bot added proof: supplied External PR includes structured after-fix real behavior proof. and removed triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. labels Jun 8, 2026

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

obviyus merged commit 2858c62 into openclaw:main Jun 8, 2026
449 of 463 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(cli): bridge inter-tool commentary events to channel progress#90883

fix(cli): bridge inter-tool commentary events to channel progress#90883
obviyus merged 3 commits into
openclaw:mainfrom
anagnorisis2peripeteia:fix/cli-commentary-delivery

anagnorisis2peripeteia commented Jun 6, 2026 •

edited by obviyus

Loading

Uh oh!

clawsweeper Bot commented Jun 6, 2026 •

edited

Loading

Uh oh!

anagnorisis2peripeteia commented Jun 6, 2026

Uh oh!

clawsweeper Bot commented Jun 6, 2026 •

edited

Loading

Uh oh!

anagnorisis2peripeteia commented Jun 6, 2026

Uh oh!

clawsweeper Bot commented Jun 6, 2026 •

edited

Loading

Uh oh!

Uh oh!

obviyus commented Jun 8, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

anagnorisis2peripeteia commented Jun 6, 2026 • edited by obviyus Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Verification

Real behavior proof

Notes

Uh oh!

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

Uh oh!

Uh oh!

anagnorisis2peripeteia commented Jun 6, 2026

Uh oh!

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

Uh oh!

Uh oh!

anagnorisis2peripeteia commented Jun 6, 2026

Uh oh!

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

Uh oh!

Uh oh!

Uh oh!

obviyus commented Jun 8, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

anagnorisis2peripeteia commented Jun 6, 2026 •

edited by obviyus

Loading

clawsweeper Bot commented Jun 6, 2026 •

edited

Loading

clawsweeper Bot commented Jun 6, 2026 •

edited

Loading

clawsweeper Bot commented Jun 6, 2026 •

edited

Loading