fix(whatsapp): periodic delivery-queue drain so enqueued items don't wait for next reconnect by Oviemudiaga · Pull Request #79083 · openclaw/openclaw

Oviemudiaga · 2026-05-07T20:24:19Z

Summary

drainPendingDeliveries for WhatsApp is only invoked from the reconnect handler in extensions/whatsapp/src/auto-reply/monitor.ts (around the Listening for personal WhatsApp inbound messages. log line). When a delivery is enqueued via enqueueDelivery while the provider is already connected, nothing triggers the drain — the entry stays in ~/.openclaw/delivery-queue/ until the next reconnect.

In production this caused a ~26-minute delay: a queued user-facing message sat until a coincidental status 428 Precondition Required reconnect happened to drain the queue.

Fix

Add a 30s periodic drain inside the WhatsApp connect block, with cleanup on close. The new interval uses the same selectEntry predicate as the reconnect drain (filter by channel + accountId), with bypassBackoff: false so retry/backoff semantics are unchanged.

// after the existing reconnect drain
const periodicDrainInterval = setInterval(() => {
  void drainPendingDeliveries({
    drainKey: `whatsapp:${normalizedAccountId}`,
    logLabel: "WhatsApp periodic drain",
    cfg,
    log: reconnectLogger,
    selectEntry: (entry) => ({
      match:
        entry.channel === "whatsapp" &&
        normalizeReconnectAccountId(entry.accountId) === normalizedAccountId,
      bypassBackoff: false,
    }),
  }).catch((err) => {
    reconnectLogger.warn(
      { connectionId: connection.connectionId, error: String(err) },
      "periodic drain failed",
    );
  });
}, 30_000);

// keep-alive guard cleans up immediately:
if (!keepAlive) {
  clearInterval(periodicDrainInterval);
  await controller.shutdown();
  return;
}

// long-lived path cleans up when the close promise settles:
const reason = await controller
  .waitForClose()
  .finally(() => clearInterval(periodicDrainInterval));

Why a periodic timer instead of post-`enqueueDelivery` drain

Considered draining immediately after enqueueDelivery when the matching provider is connected — that gives near-zero latency on the happy path but requires enqueueDelivery callers (and/or enqueueDelivery itself) to know which providers are connected, crossing concerns. A periodic timer is local to the WhatsApp monitor, self-contained, and good enough for the user-visible problem. Happy to switch approaches if maintainers prefer the post-enqueue trigger.

Optional follow-up: make the interval configurable via cfg (e.g. whatsapp.periodicDrainMs, default 30_000). Not included here to keep the diff minimal.

Backwards compatibility

Reconnect drain behavior is unchanged.
Backoff/retry semantics are unchanged (drainPendingDeliveries already honors isEntryEligibleForRecoveryRetry).
No new public API.

Test plan

Maintainers may want unit tests for the periodic-drain behavior — happy to add them with guidance on the preferred test setup for monitor.ts (existing tests in this directory use a specific harness pattern; wanted to keep this PR focused on the fix).
Manual repro: an entry enqueued while WhatsApp was already connected sat in ~/.openclaw/delivery-queue/ until a coincidental reconnect drained it. With this patch (validated against the compiled dist as a hot-patch), the entry is drained within ~30s.

Notes

This was originally hot-patched against the installed @openclaw/whatsapp/dist/monitor-*.js for our environment (script available on request). Once this PR lands and we upgrade past the release that includes it, we can drop the hot-patch.

Real behavior proof

Behavior or issue addressed: Outbound WhatsApp deliveries enqueued while the provider is already connected sit in ~/.openclaw/delivery-queue/ indefinitely. They only send on the next reconnect, with a real-world ~26-minute delay observed.

Real environment tested: OpenClaw 2026.5.6 (c97b9f7) on Linux WSL2, Node 22.x, with WhatsApp channel LINKED against a real Baileys connection. Hot-patched dist file @openclaw/whatsapp/dist/monitor-Ce7y4e_6.js to mirror this diff.

Exact steps or command run after this patch:

Apply this diff's equivalent to the installed dist (script: scripts/apply_bug51_patch.sh).
Restart the gateway: openclaw restart.
Enqueue an outbound WhatsApp message while the channel is already connected (no forced reconnect).
Inspect the live queue and runtime log: ls ~/.openclaw/delivery-queue/ and journalctl --user -u openclaw -f.

Evidence after fix: Redacted live runtime log and queue listing from the patched setup:

[whatsapp] WhatsApp periodic drain
  drainKey=whatsapp:default selectEntry.match=true bypassBackoff=false
  drained=1 acked=1

$ ls ~/.openclaw/delivery-queue/
f53726fb-...json    # pre-patch: sat ~26 min until a coincidental 428 reconnect

$ ls ~/.openclaw/delivery-queue/
(empty within 30s of enqueue, post-patch)

Observed result after fix: Outbound WhatsApp message drained and delivered within one 30s tick of the new periodic timer (vs. ~26 min worst case pre-patch). Reconnect drain path unchanged; backoff/retry semantics preserved (bypassBackoff: false). Recipient confirmed receipt; phone number redacted.

What was not tested: The configurable-interval follow-up (whatsapp.periodicDrainMs) and multi-account WhatsApp setups beyond a single default account.

clawsweeper · 2026-05-07T20:27:44Z

Codex review: needs maintainer review before merge.

Workflow note: Future ClawSweeper reviews update this same comment in place.

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

Summary
The PR adds a WhatsApp monitor interval that drains matching pending outbound delivery-queue entries every 30 seconds while connected, clears it on close, adds a focused e2e test, and records a changelog entry.

Reproducibility: yes. by source inspection and supplied live logs: current main write-ahead queues sends and WhatsApp only drains on reconnect, while the PR body shows a redacted WSL2/Baileys hot-patch draining within one 30s tick. I did not run a live WhatsApp repro in this read-only review.

PR rating
Overall: 🐚 platinum hermit
Proof: 🦞 diamond lobster
Patch quality: 🐚 platinum hermit
Summary: Strong real-world log proof and a focused patch make this a good merge candidate after the remaining CI and cadence decision.

Rank-up moves:

Wait for the in-progress Critical Quality (network-runtime-boundary) check to finish before merge.

What the crustacean ranks mean

🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

PR egg
✨ Hatched: 🥚 common Tiny Test Hopper

       /\  .---.  /\         
      /  \/     \/  \        
     /   ( -   - )   \       
    |       ._.       |      
    |   /|  ===  |\   |      
     \  \|______/|/  /       
      '._  `--'  _.'         
         '-.__.-'            
       _/|_|  |_|\_          
      /__|      |__\         
       .-----------.         
      '-------------'

Rarity: 🥚 common.
Trait: hums during re-review.
Share on X: post this hatch
Copy: My PR egg hatched a 🥚 common Tiny Test Hopper in ClawSweeper.

What is this egg doing here?

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

Real behavior proof
Sufficient (logs): The PR body includes redacted live runtime logs and queue listings from a real WhatsApp/Baileys setup showing an equivalent hot patch draining a queued delivery within one 30s tick.

Risk before merge
Why this matters: - The fixed 30s periodic drain intentionally changes connected-state WhatsApp replay cadence, so maintainers should accept that policy before merge.

Live proof covers a single default WhatsApp account; multi-account behavior is supported by selector logic and test coverage rather than live multi-account proof.
Critical Quality (network-runtime-boundary) was still in progress when checked, so merge should wait for that shard to finish.

Maintainer options:

Land the WhatsApp-local timer after CI (recommended)
Accept the 30s connected-state drain if the remaining check finishes cleanly, because the patch reuses the existing queue drain, selector, active-claim, and backoff contracts.
Require cadence control before merge
If operators need control over periodic recovery work, ask for a config-backed interval and fresh default-plus-config coverage before merging.

Next step before merge
This PR is already the implementation candidate; no repair lane is needed, but a maintainer should accept the 30s WhatsApp replay cadence and wait for the remaining CI shard.

Security
Cleared: The diff only changes WhatsApp delivery-queue scheduling, a focused test, and changelog text; I found no new dependency, secret, permission, CI, or supply-chain risk.

Review details

Best possible solution:

Land the WhatsApp-local periodic drain once the remaining CI completes, unless maintainers want to require a config-backed cadence before accepting connected-state replay.

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

Yes by source inspection and supplied live logs: current main write-ahead queues sends and WhatsApp only drains on reconnect, while the PR body shows a redacted WSL2/Baileys hot-patch draining within one 30s tick. I did not run a live WhatsApp repro in this read-only review.

Is this the best way to solve the issue?

Yes. The WhatsApp monitor owns listener readiness, and a local timer reuses the existing drain/backoff/active-claim contracts without making enqueueDelivery provider-aware; configurable cadence is an optional maintainer policy choice, not required for the narrow fix.

Label justifications:

P1: The PR addresses a user-facing WhatsApp outbound delivery delay where queued messages can wait until the next reconnect.
merge-risk: 🚨 message-delivery: The patch changes when queued WhatsApp messages are replayed while connected, so a bad implementation could affect delivery timing or duplication behavior.

Acceptance criteria:

CI for head 5382490, especially Critical Quality (network-runtime-boundary)
Focused WhatsApp monitor test added by the PR
Existing outbound delivery-queue reconnect-drain tests for active-claim duplicate protection

What I checked:

Current main only drains on reconnect: On current main, monitorWebChannel calls drainPendingDeliveries once after connection setup and then waits for close; there is no connected-state periodic drain in this block. (extensions/whatsapp/src/auto-reply/monitor.ts:525, a559ccc0844a)
Queue eligibility supports replaying fresh entries: enqueueDelivery persists entries with retryCount: 0, and recovery treats a first replay with no lastAttemptAt as eligible, which explains why a connected-state drain can recover an otherwise stranded fresh entry. (src/infra/outbound/delivery-queue-storage.ts:145, a559ccc0844a)
PR implementation reuses existing drain contract: The PR patch adds a 30s setInterval inside the WhatsApp connect block, filters by channel/account, keeps bypassBackoff: false, logs failures, and clears the interval on non-keepalive and close paths. (extensions/whatsapp/src/auto-reply/monitor.ts:541, 538249090767)
Regression coverage added: The PR adds a monitor test that verifies the reconnect drain still runs, the periodic drain fires after 30 seconds with the expected selector, and no further drain occurs after close. (extensions/whatsapp/src/auto-reply.web-auto-reply.connection-and-logging.e2e.test.ts:266, 538249090767)
Duplicate-send guard is already present on main: Current main holds an active delivery claim around live queued sends, and an existing regression test confirms reconnect drains skip in-flight live deliveries, which addresses the main duplication risk for adding a periodic drain. (src/infra/outbound/deliver.ts:1241, a559ccc0844a)
History provenance: The WhatsApp reconnect drain behavior appears to date to commit 95d4673, which moved WhatsApp to the generic drainPendingDeliveries reconnect path. (extensions/whatsapp/src/auto-reply/monitor.ts:525, 95d467398e46)

Likely related people:

mcaxtr: Introduced the current WhatsApp reconnect drain path in 95d4673 and added the latest PR test commit on this branch. (role: introduced behavior and recent test contributor; confidence: high; commits: 95d467398e46, 538249090767, 4cba08df01ea; files: extensions/whatsapp/src/auto-reply/monitor.ts, extensions/whatsapp/src/auto-reply.web-auto-reply.connection-and-logging.e2e.test.ts, src/infra/outbound/delivery-queue-recovery.ts)
steipete: Carried recent WhatsApp monitor/reconnect fixes and merged the active-delivery-claim work that makes periodic drains safe around in-flight sends. (role: recent adjacent owner; confidence: high; commits: aa27a9474fa3, ac7e1c36eb55, 7a6f73a8aae9; files: src/infra/outbound/deliver.ts, src/infra/outbound/delivery-queue.reconnect-drain.test.ts, extensions/whatsapp/src/auto-reply/monitor.ts)
vincentkoc: Recent WhatsApp reconnect and auth-conflict recovery commits touch the same monitor/runtime area, so they are a plausible reviewer for behavior interactions. (role: adjacent WhatsApp reconnect contributor; confidence: medium; commits: 21a92ea0f636, 7950a1802510; files: extensions/whatsapp/src/auto-reply/monitor.ts)

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

…wait for reconnect drainPendingDeliveries was only invoked from the WhatsApp reconnect handler. Items enqueued while the provider was already connected sat in ~/.openclaw/delivery-queue/ until the next reconnect happened to drain them. Observed in production as a ~26-minute delay before a coincidental status 428 reconnect rescued a queued message. Add a 30s periodic drain inside the connect block, cleared on close, filtering on channel+accountId with the same selectEntry predicate as the reconnect drain. Backoff/retry semantics are preserved.

mcaxtr · 2026-05-19T02:29:20Z

Merged via squash.

Prepared head SHA: 9a619bb9d953ddd38da0b44f2c30ea9a67455f21
Merge commit: e9989f3a92e5ab28c900d962ea6058fabb94bee7

Thanks @Oviemudiaga!

…026.5.20) (#615) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ghcr.io/openclaw/openclaw](https://openclaw.ai) ([source](https://github.com/openclaw/openclaw)) | patch | `2026.5.19` → `2026.5.20` | --- > ⚠️ **Warning** > > Some dependencies could not be looked up. Check the [Dependency Dashboard](issues/567) for more information. --- ### Release Notes <details> <summary>openclaw/openclaw (ghcr.io/openclaw/openclaw)</summary> ### [`v2026.5.20`](https://github.com/openclaw/openclaw/blob/HEAD/CHANGELOG.md#2026520) [Compare Source](openclaw/openclaw@v2026.5.19...v2026.5.20) ##### Changes - Exec approvals: remove the old `cat SKILL.md && printf ... && <skill-wrapper>` allowlist compatibility path so skill files must be loaded with the read tool and only the real skill executable is auto-allowed. - Discord: let voice sessions follow configured Discord users into voice channels, with allowed-channel checks, multi-user handoff, bounded reconciliation, and DAVE recovery preservation. ([#84264](openclaw/openclaw#84264)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev). - Discord/voice: include bounded `IDENTITY.md`, `USER.md`, and `SOUL.md` profile context in realtime voice session instructions by default, with `voice.realtime.bootstrapContextFiles: []` available to disable it. ([#84499](openclaw/openclaw#84499)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev). - Dependencies: bump the bundled Codex harness to `@openai/codex` `0.132.0` and refresh the app-server model-list docs for the new catalog. - CLI/policy: add the bundled Policy plugin for policy-backed channel conformance checks, doctor lint findings, and opt-in workspace repair. ([#80407](openclaw/openclaw#80407)) Thanks [@giodl73-repo](https://github.com/giodl73-repo). - Agents/config: allow `agents.list[].experimental.localModelLean` so lean local-model mode can be enabled for one configured agent instead of globally. - Providers/xAI: add device-code OAuth login so remote and headless setups can authorize xAI without a localhost browser callback. ([#84005](openclaw/openclaw#84005)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev). - Providers/OpenRouter: honor provider-level `params.provider` routing policy for OpenRouter requests, with model and agent params overriding the defaults. Thanks [@amknight](https://github.com/amknight). ##### Fixes - CLI/tasks: include stale-running task maintenance decisions in `openclaw tasks maintenance --json` so retained and reconcile candidates explain backing-session, cron, CLI, and wedged-subagent state. ([#84691](openclaw/openclaw#84691)) Thanks [@efpiva](https://github.com/efpiva). - Codex app-server: keep system-prompt reports working when bootstrap hooks provide workspace files with only a path and content, so hook-supplied SOUL/IDENTITY/TOOLS/USER context still reports injected characters correctly. ([#84736](openclaw/openclaw#84736)) Thanks [@JARVIS-Glasses](https://github.com/JARVIS-Glasses). - Providers/MiniMax music: stop advertising `durationSeconds` control and remove prompt-injected duration hints, so `music_generate` reports MiniMax duration as an unsupported override instead of suggesting MiniMax can enforce track length. Fixes [#84508](openclaw/openclaw#84508). Thanks [@neeravmakwana](https://github.com/neeravmakwana). - Doctor: warn when sandbox tool policy hides configured MCP server tools before provider requests. ([#84699](openclaw/openclaw#84699)) Thanks [@nxmxbbd](https://github.com/nxmxbbd). - WhatsApp: update Baileys to `7.0.0-rc12`. - Build: suppress per-locale `rolldown-plugin-dts:fake-js` CommonJS dts warnings emitted while bundling the intentionally-inlined `zod/v4/locales/*.d.cts` files, so `pnpm build` output stays readable after the 0.25.1 plugin bump. Thanks [@romneyda](https://github.com/romneyda). - CLI/nodes: route lazy plugin-registration logs to stderr for JSON-mode `openclaw nodes` commands so stdout stays parseable. ([#84684](openclaw/openclaw#84684)) Thanks [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Approvals: route manual `/approve` decisions through the trusted approval runtime so active exec and plugin approvals no longer look unknown or expired. - Mac app: update the About settings copyright year to 2026. ([#84385](openclaw/openclaw#84385)) Thanks [@pejmanjohn](https://github.com/pejmanjohn). - Dependencies: update `@openclaw/fs-safe` to `0.2.7` so OpenClaw's default Python-helper-off policy keeps best-effort Node write fallbacks for private stores, secret writes, run logs, and media attachments on Linux/macOS. - Infra/secrets: restore the fail-closed contract for `tryReadSecretFileSync` so credential loaders that pass `rejectSymlink: true` (Telegram, LINE, Zalo, IRC, Nextcloud Talk tokens) refuse symlinked credential files instead of silently accepting them, and the infra-state CI shard's secret-file symlink test passes again. Thanks [@romneyda](https://github.com/romneyda). - Browser: honor the configured image sanitization limit for screenshots and labeled snapshots so browser-captured images follow the same resize policy as other image results. ([#84595](openclaw/openclaw#84595)) - Doctor: remove unrecognized `models.providers.*.models[*].compat.thinkingFormat` values during `doctor --fix` so stale provider model config can validate after upgrade. Fixes [#77803](openclaw/openclaw#77803). - Doctor: warn when `openclaw.json` stores plaintext secret-bearing config fields, including model provider API keys and sensitive provider headers. ([#84718](openclaw/openclaw#84718)) Thanks [@lukaIvanic](https://github.com/lukaIvanic). - Status: show the configured default, session-selected model, reason, clear hint, and docs link when a session remains pinned to a model that differs from `agents.defaults.model.primary`. - WebChat: clear stale typing indicators when session change events mark the active chat run complete. - Mac app: keep local packaging signed with a stable app identity for permission testing and fix Control UI production builds under current Vite/Highlight.js exports. - macOS app: update the embedded Peekaboo bridge to 3.2.1 so OpenClaw-hosted UI automation works with current Peekaboo CLI capture flows. - Cron: deliver preferred final assistant output for successful scheduled runs when trailing plain tool warnings remain in diagnostics instead of marking the run failed. - fix(mattermost): fail closed on missing channel type \[AI]. ([#84091](openclaw/openclaw#84091)) Thanks [@pgondhi987](https://github.com/pgondhi987). - Recheck rebuilt system.run argv \[AI]. ([#84090](openclaw/openclaw#84090)) Thanks [@pgondhi987](https://github.com/pgondhi987). - CLI: keep the private QA subcommand out of exported command descriptors unless `OPENCLAW_ENABLE_PRIVATE_QA_CLI=1`, so root help and subcommand markers match runtime registration. ([#84519](openclaw/openclaw#84519)) - CLI/cron: bound `openclaw cron show` job lookup pagination so non-advancing or unbounded `cron.list` responses fail instead of hanging the command. Fixes [#83856](openclaw/openclaw#83856). ([#83989](openclaw/openclaw#83989)) - Agents/messages: stop message-tool-only turns after a successful source-channel `message` send while keeping transcript mirrors under the session write lock. ([#84289](openclaw/openclaw#84289)) - Agents: filter silent heartbeat response-tool transcript artifacts out of embedded context snapshots so later user turns are not polluted by heartbeat no-op messages. ([#83477](openclaw/openclaw#83477)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev). - Agents/OpenAI: log repeated strict tool-schema downgrade diagnostics once per provider/model/tool signature, reducing duplicate debug noise while preserving `strict=false` fallback behavior. Fixes [#82930](openclaw/openclaw#82930). ([#82933](openclaw/openclaw#82933)) Thanks [@galiniliev](https://github.com/galiniliev). - Agents/code mode: spell out the `exec` tool's JavaScript/TypeScript, no Node module, and catalog-bridge constraints in model-visible schema text so agents can use enabled tools without trial-and-error. ([#84269](openclaw/openclaw#84269)) Thanks [@Kaspre](https://github.com/Kaspre). - Codex: give `image_generate` dynamic-tool calls a 120s default watchdog when no per-call or configured image timeout is set, so image generation no longer falls back to the generic 30s bridge timeout. ([#84254](openclaw/openclaw#84254)) Thanks [@moritzmmayerhofer](https://github.com/moritzmmayerhofer). - Codex: avoid duplicate dynamic tool terminal diagnostics while large diagnostic backlogs drain without blocking tool responses. ([#82937](openclaw/openclaw#82937)) Thanks [@galiniliev](https://github.com/galiniliev). - CLI/message: include a stable top-level `messageId` in `openclaw message --json` output when channel sends return one. ([#84191](openclaw/openclaw#84191)) Thanks [@100menotu001](https://github.com/100menotu001). - Cron: preserve legacy top-level array `jobs.json` stores when loading or adding scheduled jobs so old cron jobs are no longer treated as an empty store during upgrade. Fixes [#60799](openclaw/openclaw#60799). ([#84433](openclaw/openclaw#84433)) Thanks [@IWhatsskill](https://github.com/IWhatsskill). - Gateway/agents: use an agent's `identity.name` in Gateway agent summaries when `agents.list[].name` is unset, so configured agent labels remain visible in clients. ([#84355](openclaw/openclaw#84355); refs [#57835](openclaw/openclaw#57835)) Thanks [@luoyanglang](https://github.com/luoyanglang). - Channels/replies: keep normal `/verbose` failed-tool progress compact in message-tool replies and prevent late text-only tool output from appearing after the final answer. ([#84303](openclaw/openclaw#84303)) Thanks [@VACInc](https://github.com/VACInc). - Plugins/hooks: apply a default 30-second timeout to `before_compaction` and `after_compaction` hooks so a hung plugin handler no longer blocks compaction completion. ([#84153](openclaw/openclaw#84153)) - Discord: preserve disabled presentation buttons when adapting and rendering Discord message controls. ([#84188](openclaw/openclaw#84188)) Thanks [@100menotu001](https://github.com/100menotu001). - Twitch: add a test-only client-manager registry reset helper so non-isolated Twitch tests can clear cached managers between cases. Fixes [#83887](openclaw/openclaw#83887). ([#84244](openclaw/openclaw#84244)) Thanks [@hclsys](https://github.com/hclsys). - Cron: run main-session scheduled work on a cron-owned wake lane while preserving reply delivery context, so background cron turns no longer block human main-session chat. Fixes [#82766](openclaw/openclaw#82766). ([#82767](openclaw/openclaw#82767)) Thanks [@galiniliev](https://github.com/galiniliev). - Cron: use structured embedded-run denial metadata for isolated scheduled tasks so blocked exec requests fail the job without treating ordinary assistant prose as a denial. ([#84067](openclaw/openclaw#84067)) Thanks [@abnershang](https://github.com/abnershang). - Cron: keep recovered tool warnings diagnostic for successful scheduled runs so final cron output is delivered instead of being replaced by a post-processing warning. ([#84045](openclaw/openclaw#84045)) Thanks [@abnershang](https://github.com/abnershang). - Plugins/perf: thread explicit plugin discovery results through `loadBundledCapabilityRuntimeRegistry`, `resolveBundledPluginSources`, and `listChannelCatalogEntries` so callers that already hold a discovery result skip redundant filesystem walks. Thanks [@SebTardif](https://github.com/SebTardif). - harden update restart script creation \[AI]. ([#84088](openclaw/openclaw#84088)) Thanks [@pgondhi987](https://github.com/pgondhi987). - Docker: keep the bundled Codex plugin in official release image keep lists so the default OpenAI agent harness remains available after Docker pruning. Fixes [#83613](openclaw/openclaw#83613). ([#83626](openclaw/openclaw#83626)) Thanks [@YuanHanzhong](https://github.com/YuanHanzhong). - CLI/channels: preserve the first line of `openclaw channels logs` output when the rolling tail window starts exactly on a line boundary, mirroring the already-fixed `readLogSlice` behavior in `src/logging/log-tail.ts`. - Control UI: treat terminal session status as authoritative over stale active-run flags so completed terminal runs stop showing abort/live UI. ([#84057](openclaw/openclaw#84057)) - CLI: preserve embedded equals signs in inline root option values instead of truncating after the second separator. ([#83995](openclaw/openclaw#83995)) Thanks [@ThiagoCAltoe](https://github.com/ThiagoCAltoe). - Matrix/config: accept `messages.queue.byChannel.matrix` queue overrides and keep queue provider schema/type keys aligned for Matrix, Google Chat, and Mattermost. Thanks [@bdjben](https://github.com/bdjben). - CLI: format `openclaw acp client` failures through the shared error formatter so object-shaped errors stay readable instead of printing `[object Object]`. Fixes [#83904](openclaw/openclaw#83904). ([#84080](openclaw/openclaw#84080)) - Providers/Ollama: default unknown-capabilities models to tool-capable so discovered native Ollama models can use tools when `/api/show` omits capabilities. ([#84055](openclaw/openclaw#84055)) Thanks [@dutifulbob](https://github.com/dutifulbob). - Installer/Windows: launch `install.ps1` onboarding as an attached child process so fresh native Windows installs do not freeze visibly at `Starting setup...` or corrupt the wizard's terminal rendering. - CLI/update: keep restart health checks working across one-version CLI/Gateway protocol skew and use the managed Gateway service Node for all follow-up commands even when the package root is unchanged, so `openclaw update` no longer silently switches the gateway to a different Node binary when multiple Node installations are present. Thanks [@amknight](https://github.com/amknight). - CLI/gateway: include the running Gateway version in `gateway status` JSON output, preserving existing server metadata while falling back to status RPC data for read probes. Fixes [#56222](openclaw/openclaw#56222). Thanks [@galiniliev](https://github.com/galiniliev). - Memory/search: close local embedding providers when active-memory searches time out so pending local model loads and embedding contexts are aborted and released. ([#83858](openclaw/openclaw#83858)) Thanks [@brokemac79](https://github.com/brokemac79). - CLI/nodes: request pending node surface approval scopes before `openclaw nodes approve` so exec-capable node approval can use admin-scoped Gateway credentials instead of failing with `missing scope: operator.admin`. ([#84392](openclaw/openclaw#84392)) Thanks [@joshavant](https://github.com/joshavant). - Gateway: reject slow node event sends before outbound buffers grow unbounded and log the rejected payload diagnostic. ([#84387](openclaw/openclaw#84387)) Thanks [@samzong](https://github.com/samzong). - Agents: include bounded trajectory queued-writer diagnostics in `pi-trajectory-flush` timeout warnings so flush stalls show pending writes, queued bytes, and append state. Fixes [#82961](openclaw/openclaw#82961). ([#82962](openclaw/openclaw#82962)) Thanks [@galiniliev](https://github.com/galiniliev). - Agents/subagents: recover stale completion announces by retrying unsupported transcript-wait wakes without transcript waiting and forcing a message-tool handoff when the requester run is already stale. Fixes [#83699](openclaw/openclaw#83699). ([#83700](openclaw/openclaw#83700)) Thanks [@galiniliev](https://github.com/galiniliev). - Agents/subagents: constrain wildcard subagent target allowlists to configured agents while preserving explicitly listed compatibility targets. Fixes [#84040](openclaw/openclaw#84040). ([#84357](openclaw/openclaw#84357)) Thanks [@joshavant](https://github.com/joshavant). - Providers/Anthropic: route Anthropic model refs selected with Claude CLI auth through the Claude CLI runtime so shorthand refs such as `anthropic/opus-4.7` no longer fall back to embedded Anthropic billing. Fixes [#84222](openclaw/openclaw#84222). ([#84374](openclaw/openclaw#84374)) Thanks [@joshavant](https://github.com/joshavant). - Agents: honor explicit `models.providers.<id>.timeoutSeconds` values above the default idle watchdog for cloud and self-hosted providers, so long first-token waits no longer fall back at \~120s when the provider timeout is higher. ([#83979](openclaw/openclaw#83979)) Thanks [@yujiawei](https://github.com/yujiawei). - Agents/Codex: keep encrypted Responses reasoning replay provenance-bound so stale mirrored Codex transcripts drop invalid encrypted content before request assembly while preserving matching same-session replay. Fixes [#83836](openclaw/openclaw#83836). ([#84367](openclaw/openclaw#84367)) Thanks [@joshavant](https://github.com/joshavant). - Agents/subagents: skip stale embedded-run wake probes for dormant completion requesters, so late subagent completions go straight to requester-agent/direct handoff instead of producing `reason=no_active_run` queue noise. ([#82964](openclaw/openclaw#82964)) Thanks [@galiniliev](https://github.com/galiniliev). - CLI: retry config snapshot reads after a transient failure so one rejected read no longer poisons later commands in the same process. ([#83931](openclaw/openclaw#83931)) Thanks [@honor2030](https://github.com/honor2030). - Media: decode URL path basenames before using them as remote media fallback filenames, so files like `My%20Report.pdf` are surfaced as `My Report.pdf`. Fixes [#84050](openclaw/openclaw#84050). ([#84052](openclaw/openclaw#84052)) Thanks [@jbetala7](https://github.com/jbetala7). - WhatsApp: clarify inbound group diagnostics so observed but unregistered groups point to `channels.whatsapp.groups` without changing routing or sender authorization. ([#83846](openclaw/openclaw#83846)) Thanks [@neeravmakwana](https://github.com/neeravmakwana). - WhatsApp: drain pending outbound deliveries on a 30s periodic timer in addition to the reconnect handler, so messages enqueued while the provider is already connected no longer wait for the next reconnect to send. ([#79083](openclaw/openclaw#79083)) Thanks [@Oviemudiaga](https://github.com/Oviemudiaga). - CLI/TUI: include gateway plugin slash commands in TUI autocomplete, so connected sessions can suggest plugin-owned commands exposed by the running Gateway. ([#83640](openclaw/openclaw#83640)) Thanks [@se7en-agent](https://github.com/se7en-agent). - Gateway/mobile: restore QR setup-code handoff of bounded operator tokens for iOS and Android onboarding while keeping admin and pairing scopes out of bootstrap. ([#83684](openclaw/openclaw#83684)) Thanks [@ngutman](https://github.com/ngutman). - iOS: repair Release archive compilation for the TestFlight build. ([#84255](openclaw/openclaw#84255)) Thanks [@ngutman](https://github.com/ngutman). - Agents/compaction: bound plugin-owned CLI transcript compaction with the host safety timeout so a hung context engine can no longer stall post-turn cleanup. ([#84083](openclaw/openclaw#84083)) Thanks [@100yenadmin](https://github.com/100yenadmin). - Control UI/usage: truncate long context skill, tool, and file names in the usage panel while keeping the full name available on hover. ([#42197](openclaw/openclaw#42197)) Thanks [@Rain120](https://github.com/Rain120). - Codex: respect explicit `models auth order set` and `config.auth.order` precedence over stale `lastGood` in `/codex account`, and show `no working credential` when every explicit-order profile is ineligible instead of marking a lower-ranked profile as active. Fixes [#84386](openclaw/openclaw#84386). ([#84412](openclaw/openclaw#84412)) Thanks [@openperf](https://github.com/openperf). - Agents: honor `messages.suppressToolErrors` for mutating tool failures so configured chat surfaces do not receive separate warning payloads. ([#81561](openclaw/openclaw#81561)) Thanks [@moeedahmed](https://github.com/moeedahmed). - Agents/fallback: surface billing guidance for mixed rate-limit plus billing fallback exhaustion instead of generic failure copy. Fixes [#79396](openclaw/openclaw#79396). ([#79489](openclaw/openclaw#79489)) Thanks [@aayushprsingh](https://github.com/aayushprsingh). </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/615

@mcaxtr