Fix stale visible reply recovery by joshavant · Pull Request #91840 · openclaw/openclaw

joshavant · 2026-06-10T04:52:58Z

Summary

Adds a bounded recovery retry for visible reply dispatch when the reply run registry is stuck behind stale active work.
Routes visible stale recovery through the existing diagnostic recovery coordinator so diagnostic session state is cleaned up consistently.
Preserves the diagnostics enable gate and keeps disabled-diagnostics behavior as wait-for-active, not recovery/abort.
Releases inbound dedupe only for busy admission before agent/model work starts; once processing begins, busy completion still commits dedupe to avoid duplicate work.

Verification

node scripts/run-vitest.mjs src/auto-reply/reply/dispatch-from-config.stale-recovery.test.ts src/logging/diagnostic.test.ts src/logging/diagnostic-stuck-session-recovery.runtime.test.ts src/logging/diagnostic-stuck-session-recovery.integration.test.ts
node --import tsx scripts/check-import-cycles.ts
pnpm -s tsgo:core:test
.agents/skills/autoreview/scripts/autoreview --mode local

Real behavior proof

Behavior addressed: A visible channel turn can wait behind stale replyRunRegistry work forever or return busy without retrying after stale recovery.

Real environment tested: Final patch was verified with focused local regression tests; AWS Crabbox live Telegram bot-to-bot proof was run earlier on this branch before the final coordinator/gating cleanup.

Exact steps or command run after this patch: node scripts/run-vitest.mjs src/auto-reply/reply/dispatch-from-config.stale-recovery.test.ts src/logging/diagnostic.test.ts src/logging/diagnostic-stuck-session-recovery.runtime.test.ts src/logging/diagnostic-stuck-session-recovery.integration.test.ts

Evidence after fix: Focused final-patch tests passed: 92 diagnostic tests and 6 stale visible recovery tests, including disabled diagnostics, active lane task, already-in-flight recovery, released-lane wait, stale abort retry, and inbound dedupe release coverage.

Observed result after fix: Stale visible dispatch retries after coordinator recovery when diagnostics are enabled; active recovery outcomes keep waiting; disabled diagnostics keep waiting without invoking recovery; pre-processing busy paths release inbound dedupe for retry.

What was not tested: The live Telegram channel proof was not rerun after the final coordinator/gating cleanup. Earlier proof on this branch passed on AWS Crabbox run_c8e3fd6f041f / lease cbx_dd5487ad6a36: Telegram canary passed in 1018ms and telegram-reply-chain-exact-marker passed in 1783ms with 2/2 scenarios passing.

clawsweeper · 2026-06-10T04:55:19Z

Codex review: needs maintainer review before merge. Reviewed June 10, 2026, 3:48 AM ET / 07:48 UTC.

Summary
The PR adds diagnostic-coordinated stale visible reply recovery, retries reply admission after cleared stale work, adjusts busy-path inbound dedupe handling, and adds focused regression tests.

PR surface: Source +159, Tests +722. Total +881 across 7 files.

Reproducibility: yes. source-reproducible: current main sends visible turns into an unbounded waitForIdle when a reply operation remains active, and waitForIdle only times out for finite timeoutMs. I did not run a failing repro because this review is read-only.

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:

Have a maintainer explicitly accept the session-state and message-delivery recovery risk before landing.

Risk before merge

[P1] The patch can force-clear an exact per-session ReplyOperation after diagnostic recovery; a wrong recovery classification would affect session ownership and visible reply delivery.
[P1] The live proof covers the packaged Telegram reply path after the runtime cleanup, while the actual stale replyRunRegistry recovery branch is proven by focused tests rather than a naturally wedged live session.

Maintainer options:

Land after session-recovery review (recommended)
Maintainers can accept the recovery behavior if they agree that diagnostics-gated force-clear of the unchanged ReplyOperation is the right boundary for stale visible replies.
Ask for stale-lock live proof
If higher assurance is needed, ask for a packaged proof or diagnostic log artifact that injects or naturally hits a stale replyRunRegistry lock and shows recovery.
Pause for registry-owned design
If visible dispatch should not invoke diagnostic recovery, pause this PR and move the fix into a narrower reply-run-registry timeout or reaper design.

Next step before merge

[P2] The PR is protected by the maintainer label and has deliberate session/message-delivery merge risk, so the next action is human maintainer review rather than an automated repair lane.

Security
Cleared: The diff only changes TypeScript runtime and tests under reply dispatch/logging, with no dependency, workflow, secret, package, or supply-chain surface changes.

Review details

Best possible solution:

A human maintainer should review and explicitly accept the bounded recovery semantics, then land this PR if the session/message-delivery tradeoff is acceptable.

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

Yes, source-reproducible: current main sends visible turns into an unbounded waitForIdle when a reply operation remains active, and waitForIdle only times out for finite timeoutMs. I did not run a failing repro because this review is read-only.

Is this the best way to solve the issue?

Yes, this appears to be an acceptable narrow fix: it reuses the existing diagnostic recovery coordinator and preserves disabled-diagnostics behavior instead of adding a separate global registry reaper. The maintainer decision is whether that recovery boundary is acceptable for visible dispatch.

AGENTS.md: found and applied where relevant.

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

Label changes

Label justifications:

P1: The PR targets a broken visible channel reply workflow where subsequent inbound messages can hang or be skipped behind stale session state.
merge-risk: 🚨 message-delivery: The changed admission/recovery path decides whether visible inbound messages wait, retry, or return busy.
merge-risk: 🚨 session-state: The diff can clear per-session reply registry state after diagnostic recovery and therefore changes session ownership behavior.
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 (logs): The PR has live Telegram Docker RTT proof for the branch runtime plus focused stale-recovery regression tests; the final head commit is test-only.
proof: sufficient: Contributor real behavior proof is sufficient. The PR has live Telegram Docker RTT proof for the branch runtime plus focused stale-recovery regression tests; the final head commit is test-only.
mantis: telegram-visible-proof: Mantis should capture Telegram visible proof. The PR changes visible channel reply delivery behavior, so Telegram-visible proof is useful and the PR already provides live Telegram lane evidence.

Evidence reviewed

PR surface:

Source +159, Tests +722. Total +881 across 7 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	4	207	48	+159
Tests	3	722	0	+722
Docs	0	0	0	0
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	7	929	48	+881

What I checked:

Repository policy read: Root AGENTS.md was read fully; no scoped AGENTS.md exists under the touched src/auto-reply or src/logging paths, and the Telegram maintainer note requires real Telegram proof for visible reply-context behavior. (AGENTS.md:1, fd7e1815006a)
Current-main stale wait path: Current main lets visible turns fall through to replyRunRegistry.waitForIdle with no timeout when a reply operation is already active; waitForIdle only installs a timer when timeoutMs is finite. (src/auto-reply/reply/reply-turn-admission.ts:65, fd7e1815006a)
PR recovery implementation: The PR gates stale visible recovery on enabled diagnostics, waits only to the resolved stuck-session abort threshold, requests diagnostic recovery, and force-clears only when the same ReplyOperation remains after a recovery outcome that says active work was cleared. (src/auto-reply/reply/dispatch-from-config.ts:1269, fc29c452bb65)
Regression coverage: The added stale-recovery test covers successful retry, pure stale registry reclaim, fresh-operation identity protection, active-work keep-waiting outcomes, failed recovery, disabled diagnostics, released lanes, and pre-processing dedupe release. (src/auto-reply/reply/dispatch-from-config.stale-recovery.test.ts:52, fc29c452bb65)
Coordinator return-path change: The diagnostic recovery coordinator now exposes requestStuckSessionRecoveryOutcome while preserving the existing fire-and-forget requestStuckSessionRecovery wrapper, giving visible dispatch an auditable recovery result. (src/logging/diagnostic-session-recovery-coordinator.ts:176, fc29c452bb65)
Real behavior proof: The PR discussion includes live AWS Crabbox Telegram Docker RTT proof for a tarball built from the branch at 6be4195, and the final fc29c45 commit only adds a regression test for failed recovery admission. (fc29c452bb65)

Likely related people:

steipete: Peter Steinberger is the top shortlog contributor across the touched reply/logging files and authored the reply-dispatch hook surface that sits in this dispatch path. (role: feature-history owner; confidence: medium; commits: 82ce30b7895a; files: src/auto-reply/reply/dispatch-from-config.ts, src/plugins/hooks.ts)
vincentkoc: Vincent Koc recently changed inbound dedupe behavior after dispatch errors, which is adjacent to this PR's busy-path dedupe release change. (role: adjacent owner; confidence: medium; commits: 7c91d0dbc985, 5181e4f7c82b; files: src/auto-reply/reply/dispatch-from-config.ts)
shakkernerd: Current-main blame in this shallow checkout attributes the central reply admission and diagnostic recovery lines to Shakker's latest touch of the affected files. (role: recent area contributor; confidence: medium; commits: 21104cd52eb1; files: src/auto-reply/reply/dispatch-from-config.ts, src/auto-reply/reply/reply-turn-admission.ts, src/logging/diagnostic-session-recovery-coordinator.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.

joshavant · 2026-06-10T06:38:12Z

Addressed the stale reply-registry gap from the review in 6be4195bacac4ce22306589c3c670306334dd053.

What changed:

After visible stuck-session recovery reports that active work was cleared (aborted, released, or noop/no_active_work), dispatch now rechecks replyRunRegistry and force-clears only the exact same ReplyOperation object that blocked admission.
The identity guard intentionally avoids clearing a fresh operation that reused the same session key/session id while recovery was awaited.
Recovery outcomes that prove live work (active_reply_work, active_embedded_run, active_lane_task, already_in_flight) still keep waiting instead of clearing.

Proof run after the patch:

node scripts/run-vitest.mjs src/auto-reply/reply/dispatch-from-config.stale-recovery.test.ts src/auto-reply/reply/reply-run-registry.test.ts
node scripts/run-vitest.mjs src/auto-reply/reply/dispatch-from-config.stale-recovery.test.ts src/logging/diagnostic.test.ts src/logging/diagnostic-stuck-session-recovery.runtime.test.ts src/logging/diagnostic-stuck-session-recovery.integration.test.ts
pnpm -s tsgo:core:test
node --import tsx scripts/check-import-cycles.ts
git diff --check
pnpm -s format:check src/auto-reply/reply/dispatch-from-config.ts src/auto-reply/reply/dispatch-from-config.stale-recovery.test.ts
node scripts/run-oxlint.mjs src/auto-reply/reply/dispatch-from-config.ts src/auto-reply/reply/dispatch-from-config.stale-recovery.test.ts
.agents/skills/autoreview/scripts/autoreview --mode local -> clean, no accepted/actionable findings

CI on 6be4195bacac4ce22306589c3c670306334dd053: all non-Real behavior proof checks are green; PR merge state is CLEAN.

joshavant · 2026-06-10T06:39:51Z

@clawsweeper re-review my crab

clawsweeper · 2026-06-10T06:39:53Z

🦞🧹
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: Superseded
Detail: A newer re-review for this item started before this run finished, so GitHub cancelled this older run. Check the latest ClawSweeper run for the current result.
Run: https://github.com/openclaw/clawsweeper/actions/runs/27260618608
Updated: 2026-06-10T07:37:26.310Z

joshavant · 2026-06-10T07:19:25Z

Fresh live channel proof at current PR head:

Package under test: OpenClaw 2026.6.2 (6be4195) installed from a tarball built from this branch, not the published beta package.
Environment: AWS Crabbox run_c87dc9b4b4a7, lease cbx_efb1f68c1bcd, Docker Telegram RTT lane, exit 0, lease stopped.
Credential source: Convex broker telegram kind, role maintainer; no telegram-user credential was leased.
Result: package Telegram RTT Docker E2E passed (pr-91840-6be4195bac).
Artifact summary:
- telegram-canary: pass, observed SUT message 20223, RTT 1338ms.
- telegram-mentioned-message-reply: pass, 1/1 strict warm sample passed, observed SUT message 20225, RTT 1994ms, reply text exactly OPENCLAW_E2E_OK_1.

This covers the live channel path after the final cleanup commit: installable package -> gateway startup -> Telegram provider startup -> canary -> normal mentioned reply through the channel.

joshavant · 2026-06-10T07:22:14Z

@clawsweeper re-review

clawsweeper · 2026-06-10T07:22:17Z

🦞👀
ClawSweeper picked this up.

Command router queued. I will update this comment with the next step.

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/27260172047
Updated: 2026-06-10T07:32:04.863Z

* fix visible reply stale recovery * fix visible recovery lint loop * fix visible reply registry recovery * test: cover failed visible recovery admission

…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: L maintainer Maintainer-authored PR labels Jun 10, 2026

clawsweeper Bot had a problem deploying to qa-live-shared June 10, 2026 07:33 Failure

This comment has been minimized.

Sign in to view

joshavant added 2 commits June 10, 2026 02:48

fix visible reply stale recovery

8b95ad3

fix visible recovery lint loop

52aa7fb

joshavant added 2 commits June 10, 2026 02:48

fix visible reply registry recovery

5f282e5

test: cover failed visible recovery admission

80e151f

joshavant force-pushed the fix-visible-reply-stale-recovery branch from fc29c45 to 80e151f Compare June 10, 2026 07:49

joshavant merged commit cfdabfb into main Jun 10, 2026
158 of 159 checks passed

joshavant deleted the fix-visible-reply-stale-recovery branch June 10, 2026 07:56

joshavant mentioned this pull request Jun 10, 2026

[Bug]: Stale replyRunRegistry lock causes indefinite inbound dispatch hang — no timeout on waitForIdle() for visible messages #90535

Closed

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

📡 Upstream Digest — 2026-06-10 08:01 UTC curtismercier/openclaw-mods#1051

Open

clawsweeper Bot mentioned this pull request Jun 11, 2026

fix: recover terminal session status on visible inbound turns #89045

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Fix stale visible reply recovery#91840

Fix stale visible reply recovery#91840
joshavant merged 4 commits into
mainfrom
fix-visible-reply-stale-recovery

joshavant commented Jun 10, 2026

Uh oh!

clawsweeper Bot commented Jun 10, 2026 •

edited

Loading

Uh oh!

joshavant commented Jun 10, 2026

Uh oh!

joshavant commented Jun 10, 2026

Uh oh!

clawsweeper Bot commented Jun 10, 2026 •

edited

Loading

Uh oh!

joshavant commented Jun 10, 2026

Uh oh!

joshavant commented Jun 10, 2026

Uh oh!

clawsweeper Bot commented Jun 10, 2026 •

edited

Loading

Uh oh!

This comment has been minimized.

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

joshavant commented Jun 10, 2026

Summary

Verification

Real behavior proof

Uh oh!

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

Uh oh!

Uh oh!

joshavant commented Jun 10, 2026

Uh oh!

joshavant commented Jun 10, 2026

Uh oh!

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

Uh oh!

Uh oh!

joshavant commented Jun 10, 2026

Uh oh!

joshavant commented Jun 10, 2026

Uh oh!

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

Uh oh!

Uh oh!

This comment has been minimized.

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

clawsweeper Bot commented Jun 10, 2026 •

edited

Loading

clawsweeper Bot commented Jun 10, 2026 •

edited

Loading

clawsweeper Bot commented Jun 10, 2026 •

edited

Loading