iframe-proxy

MukundaKatta · 2026-05-29T08:46:27Z

Summary

On hot config reload, flipping accounts.<name>.enabled true→false for WhatsApp was classified as a no-op, so the channel never restarted and the running Baileys provider kept processing inbound messages until a full gateway restart. (Dynamic reload doesn't disable a running WhatsApp account when its enabled flag flips to false #87951)
Root cause: WhatsApp's reload declaration used noopPrefixes: ["channels.whatsapp"], which swallows every channels.whatsapp.* change (including per-account enabled) as a hot no-op. Its restart prefix ["web"] only covers the provider-level web.* config, not per-account config under channels.whatsapp.accounts.*.
Fix: add channels.whatsapp.accounts to configPrefixes. The reload classifier (buildGatewayReloadPlan) is first-match, and a plugin's configPrefixes (restart-channel) are evaluated before its noopPrefixes, so the more-specific account prefix now wins: per-account changes restart the WhatsApp channel (tearing down a disabled account) while other channels.whatsapp.* settings stay hot no-ops.
Intentionally out of scope: a per-account stop that leaves sibling accounts connected. The reload plan operates at channel granularity, so this restarts the whole WhatsApp channel; credentials stay on disk for re-enable. Account-config changes are infrequent, so the brief reconnect of other accounts is acceptable.

Linked context

Real behavior proof (required for external PRs)

Behavior addressed: accounts.<name>.enabled: false on hot reload did not tear down the WhatsApp provider.
Real environment tested: source trace of the reload classifier (first-match rule precedence, configPrefixes before noopPrefixes in config-reload-plan.ts) plus red/green unit tests. I do not have a live WhatsApp account to capture the live socket teardown.
Command run after this patch:
- pnpm test src/gateway/config-reload.test.ts

Evidence after fix (green): 77/77 pass.

Test Files  1 passed (1)
     Tests  77 passed (77)

Evidence before fix (red — reverting the new configPrefix on the test's mock WhatsApp plugin): the per-account case fails.
```
× restarts the channel when a per-account config field changes ...
Tests  1 failed | 76 passed (77)
```
Observed after fix: buildGatewayReloadPlan(["channels.whatsapp.accounts.default.enabled"]) → restartChannels = {whatsapp} and the path is not a no-op; channels.whatsapp.replyToMode stays a hot no-op (no regression for other settings).
What was not tested: a live WhatsApp account reload + Baileys socket teardown.
Proof limitations: no live WhatsApp. The classification behavior is proven via the core reload-plan test, which uses a mock channel plugin mirroring the real extensions/whatsapp/src/shared.ts declaration.

Tests and validation

Updated the core reload-plan test's mock WhatsApp declaration to mirror the real fix, and added 2 cases: a per-account change restarts the channel; other channels.whatsapp.* changes stay hot no-ops. Red/green verified.
pnpm test src/gateway/config-reload.test.ts — 77 pass.
pnpm tsgo:extensions and pnpm tsgo:core:test — 0 errors.
oxlint and oxfmt --check on touched files — clean.

Risk checklist

Did user-visible behavior change? Yes — WhatsApp per-account config changes (enabled, account add/remove, and other accounts.* fields) now restart the channel on hot reload instead of being silently hot-applied or ignored.
Did config, environment, or migration behavior change? No.
Did security, auth, secrets, network, or tool execution behavior change? No.
Highest-risk area: over-restarting the WhatsApp channel on benign per-account field edits (e.g. allowFrom). Mitigation: a channel restart is the safe, correct way to apply account changes; only channels.whatsapp.accounts.* is affected, other WhatsApp settings stay hot, and the prefix lives in WhatsApp's own declaration (no cross-channel impact).

Current review state

Next action: maintainer review. If a per-account stop (without restarting sibling accounts) is preferred, that is a larger change to the reload plan's granularity; happy to follow up.
Still waiting on: optional live WhatsApp confirmation (I lack a linked account).

clawsweeper · 2026-05-29T08:48:33Z

Codex review: needs real behavior proof before merge. Reviewed June 3, 2026, 11:01 PM ET / 03:01 UTC.

Summary
The PR adds channels.whatsapp.accounts to WhatsApp channel reload metadata and adds reload-plan plus descriptor tests for account-config changes.

PR surface: Source +7, Tests +30. Total +37 across 3 files.

Reproducibility: yes. from source inspection: current main matches channels.whatsapp.accounts.* against the broad WhatsApp no-op prefix, while the linked report provides runtime symptoms. I did not run a live WhatsApp account repro in this read-only review.

Review metrics: 1 noteworthy metric.

Reload metadata surface: 1 restart prefix added. Adding channels.whatsapp.accounts changes hot-reload behavior for every WhatsApp account-config edit and can restart the channel during normal config saves.

Merge readiness
Overall: 🦪 silver shellfish
Proof: 🦪 silver shellfish
Patch quality: 🐚 platinum hermit
Result: blocked until real behavior proof from a real setup is added.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

[P1] Add redacted real gateway or live WhatsApp evidence showing enabled: false hot reload stops the running account and prevents further inbound processing.
Make clear in the PR body whether maintainers should accept whole-channel restart as the intended channel-granularity behavior.

Proof guidance:

[P1] Needs real behavior proof before merge: The PR body includes source tracing and red/green unit-test output, but no real gateway or live WhatsApp reload evidence; contributor action is still needed, with private details redacted. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.

Risk before merge

[P1] The PR still lacks real gateway or live WhatsApp proof that toggling accounts.<name>.enabled to false actually tears down the running Baileys socket and stops inbound processing.
[P1] The fix intentionally restarts the whole WhatsApp channel for any channels.whatsapp.accounts.* edit, so sibling WhatsApp accounts may briefly disconnect and reconnect during account-config changes.

Maintainer options:

Require real reload proof (recommended)
Ask for redacted live output, logs, a terminal screenshot, or a recording showing a running WhatsApp account stops processing inbound after enabled: false on hot reload.
Accept source-level proof
Maintainers may choose to merge with the source trace and unit tests only, explicitly accepting that live Baileys teardown was not demonstrated in the contributor environment.
Pause for per-account reload design
If whole-channel reconnect is not acceptable, pause this PR and design a per-account reload/stop contract instead of extending channel-level reload metadata.

Next step before merge

[P1] The remaining blocker is human review of real behavior proof and acceptance of whole-channel restart semantics, not a narrow code repair for automation.

Security
Cleared: The diff changes plugin reload metadata and tests only; I found no dependency, workflow, secret-handling, package, or new code-execution security concern.

Review details

Best possible solution:

Land the plugin-owned reload metadata fix after redacted real gateway or live WhatsApp teardown proof, with maintainer acceptance that account-config edits restart the WhatsApp channel at channel granularity.

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

Yes from source inspection: current main matches channels.whatsapp.accounts.* against the broad WhatsApp no-op prefix, while the linked report provides runtime symptoms. I did not run a live WhatsApp account repro in this read-only review.

Is this the best way to solve the issue?

Yes, this appears to be the narrowest maintainable fix because the existing plugin-owned reload metadata contract already supports more-specific restart prefixes before no-op prefixes. A per-account stop would be cleaner for sibling accounts but requires a broader reload-granularity design.

AGENTS.md: found and applied where relevant.

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

Label changes

Label changes:

add P2: This fixes a concrete WhatsApp account-disable bug with limited channel scope, but it is not an emergency or broad runtime outage.
add merge-risk: 🚨 availability: Merging changes account-config hot reloads from no-op to whole-channel restart, which can briefly interrupt sibling WhatsApp accounts.

Label justifications:

P2: This fixes a concrete WhatsApp account-disable bug with limited channel scope, but it is not an emergency or broad runtime outage.
merge-risk: 🚨 availability: Merging changes account-config hot reloads from no-op to whole-channel restart, which can briefly interrupt sibling WhatsApp accounts.
rating: 🦪 silver shellfish: Overall readiness is 🦪 silver shellfish; proof is 🦪 silver shellfish and patch quality is 🐚 platinum hermit.
status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: The PR body includes source tracing and red/green unit-test output, but no real gateway or live WhatsApp reload evidence; contributor action is still needed, with private details redacted. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.

Evidence reviewed

PR surface:

Source +7, Tests +30. Total +37 across 3 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	1	8	1	+7
Tests	2	32	2	+30
Docs	0	0	0	0
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	3	40	3	+37

What I checked:

Root policy read: Root review policy was read fully and applies because this is an OpenClaw PR touching gateway reload behavior and a bundled channel plugin. (AGENTS.md:17, ef17cecca945)
Scoped policies read: The relevant extension and gateway scoped guides were read; they reinforce keeping plugin metadata plugin-owned and avoiding gateway/runtime drift. (extensions/AGENTS.md:1, ef17cecca945)
Current main still has the bug path: Current main declares WhatsApp reload metadata with only web as a restart prefix and a broad channels.whatsapp no-op prefix, so channels.whatsapp.accounts.default.enabled is swallowed as no-op today. (extensions/whatsapp/src/shared.ts:178, c7a8114f540f)
Reload classifier ordering supports the fix: Channel configPrefixes become hot restart-channel rules before noopPrefixes, and buildGatewayReloadPlan uses the first matching rule for each changed path. (src/gateway/config-reload-plan.ts:163, c7a8114f540f)
Restart-channel action tears down and restarts the channel: Hot reload handles restartChannels by calling stopChannel(name, undefined, { manual: false }) followed by startChannel(name). (src/gateway/server-reload-handlers.ts:474, c7a8114f540f)
Disabled accounts are skipped after restart: Channel startup resolves the account, checks isEnabled, and records disabled accounts as not running; stop aborts existing account tasks and waits for shutdown. (src/gateway/server-channels.ts:451, c7a8114f540f)

Likely related people:

Vincent Koc: Local blame and recent history tie the current WhatsApp reload descriptor, reload-plan code, and release baseline refresh to this author in the checked-out history. (role: recent area contributor; confidence: medium; commits: 25f3d2d714e9, 2e08f0f4221f; files: extensions/whatsapp/src/shared.ts, src/gateway/config-reload-plan.ts, src/gateway/server-reload-handlers.ts)
Marcus Castro: Recent history includes focused WhatsApp multi-account inbound/default alignment and account connection lifecycle work adjacent to the behavior fixed here. (role: WhatsApp multi-account lifecycle contributor; confidence: medium; commits: 458a52610a4d, aa023e428306; files: extensions/whatsapp/src/shared.ts, extensions/whatsapp/src/auto-reply/monitor.ts, extensions/whatsapp/src/connection-controller.ts)
Peter Steinberger: Recent gateway history includes reload-handler refactoring on the same hot reload surface that consumes the restart-channel plan. (role: gateway reload adjacent contributor; confidence: medium; commits: 812f96cf24e2; files: src/gateway/server-reload-handlers.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.

…led accounts are torn down (openclaw#87951)

mcaxtr · 2026-06-04T03:30:34Z

@mcaxtr

…s so disabled accounts are torn down (openclaw#87965) Merged via squash. Prepared head SHA: 4142d55 Co-authored-by: MukundaKatta <99349238+MukundaKatta@users.noreply.github.com> Co-authored-by: mcaxtr <7562095+mcaxtr@users.noreply.github.com> Reviewed-by: @mcaxtr

@mcaxtr

…s so disabled accounts are torn down (openclaw#87965) Merged via squash. Prepared head SHA: 4142d55 Co-authored-by: MukundaKatta <99349238+MukundaKatta@users.noreply.github.com> Co-authored-by: mcaxtr <7562095+mcaxtr@users.noreply.github.com> Reviewed-by: @mcaxtr

…26.6.5) (#963) 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.1` → `2026.6.5` | --- ### Release Notes <details> <summary>openclaw/openclaw (ghcr.io/openclaw/openclaw)</summary> ### [`v2026.6.5`](https://github.com/openclaw/openclaw/blob/HEAD/CHANGELOG.md#202665) [Compare Source](openclaw/openclaw@v2026.6.1...v2026.6.5) ##### Highlights - QQBot now strips model reasoning/thinking scaffolding before native delivery, preventing raw `<thinking>` content from leaking into channel replies. ([#89913](openclaw/openclaw#89913), [#90132](openclaw/openclaw#90132)) Thanks [@openperf](https://github.com/openperf). - MCP tool results now coerce `resource_link`, `resource`, `audio`, malformed image, and future non-text/image blocks at the materialize boundary, preventing Anthropic 400s and poisoned session history after a tool returns richer MCP content. ([#90710](openclaw/openclaw#90710), [#90728](openclaw/openclaw#90728)) Thanks [@RanSHammer](https://github.com/RanSHammer) and [@849261680](https://github.com/849261680). - Anthropic extended-thinking sessions recover after prompt-cache expiry or Gateway restart because stream start events wait for `message_start`, letting pre-generation signature errors trigger the existing recovery retry. ([#90667](openclaw/openclaw#90667), [#90697](openclaw/openclaw#90697)) Thanks [@openperf](https://github.com/openperf). - Parallel is now a bundled `web_search` provider with `PARALLEL_API_KEY` discovery, guarded endpoint handling, cache-safe session ids, onboarding picker support, and docs. ([#85158](openclaw/openclaw#85158)) Thanks [@NormallyGaussian](https://github.com/NormallyGaussian). - Google Vertex ADC users get static catalog rows and runtime model resolution again, while single-provider cooldown recovery and memory adapter status checks are more reliable. ([#90506](openclaw/openclaw#90506), [#90609](openclaw/openclaw#90609), [#90717](openclaw/openclaw#90717), [#90816](openclaw/openclaw#90816)) Thanks [@849261680](https://github.com/849261680). - Matrix can preflight voice notes before mention gating, preserve thread reads/replies through Matrix relations pagination, and carry QA coverage for voice and thread flows. ([#78016](openclaw/openclaw#78016), [#90415](openclaw/openclaw#90415)) - Auth and plugin install state is more durable: auth profiles now live in SQLite, official npm plugin install records keep their trusted pins, and prerelease fallback integrity checks avoid carrying stale integrity forward. ([#89102](openclaw/openclaw#89102), [#88585](openclaw/openclaw#88585)) - macOS node mode no longer silently self-reconnects away from a healthy direct Gateway session, reducing unexpected companion app session churn. ([#90668](openclaw/openclaw#90668), [#90815](openclaw/openclaw#90815)) Thanks [@vrurg](https://github.com/vrurg). - Upgrade and service paths are safer: cron legacy JSON stores migrate during doctor preflight, service env placeholders no longer mask state-dir secrets, WhatsApp startup waits are bounded, and disabled WhatsApp accounts tear down on config reload. ([#90072](openclaw/openclaw#90072), [#90208](openclaw/openclaw#90208), [#90277](openclaw/openclaw#90277), [#90488](openclaw/openclaw#90488), [#90486](openclaw/openclaw#90486), [#87951](openclaw/openclaw#87951), [#87965](openclaw/openclaw#87965)) Thanks [@MonkeyLeeT](https://github.com/MonkeyLeeT), [@sallyom](https://github.com/sallyom), [@mcaxtr](https://github.com/mcaxtr), and [@MukundaKatta](https://github.com/MukundaKatta). ##### Changes - Search/providers: add the Parallel bundled web-search plugin, live provider tests, registration contracts, onboarding/docs wiring, and guarded `api.parallel.ai/v1/search` support. ([#85158](openclaw/openclaw#85158)) Thanks [@NormallyGaussian](https://github.com/NormallyGaussian). - Matrix/channels: add voice-message preflight and thread-aware read/reply behavior, including Matrix QA scenario wiring and docs for voice-message behavior. ([#78016](openclaw/openclaw#78016), [#90415](openclaw/openclaw#90415)) - Skills/ClawHub: install ClawHub skills backed by GitHub repositories through the resolved install API, download the pinned GitHub commit, keep install-policy checks, and report install telemetry after success. ([#90478](openclaw/openclaw#90478)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen). - Google Chat/channels: add native approval card actions and click handling so Google Chat approvals use platform-native cards instead of generic message flow. - Mobile: Android provider/model screens now surface expiring, unavailable, unresolved, and attention states more clearly, while iOS settings and Talk tabs keep diagnostics, gateway rows, attachment labels, and unavailable Talk controls reachable. - Memory: QMD search can use the new rerank toggle, and memory adapter status uses the resolved default model identity when checking plain status. ([#61834](openclaw/openclaw#61834)) - Docs/tooling: add Parallel search docs, refresh weather-skill guidance toward `web_fetch`, clarify legacy `openai-codex` auth, document release/test helper scripts, and tighten changed-test routing docs for CI/debugging work. ([#90028](openclaw/openclaw#90028), [#90250](openclaw/openclaw#90250)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev). - Release/process: switch release trains to `YYYY.M.PATCH` monthly patch numbering, keep pre-transition tags compatible, and pin the June 2026 floor at `2026.6.5` after the published beta. - Platform maintenance: refresh Android, Swift/macOS, Docker, CodeQL, Buildx, Docker build/push, and Codex Action dependencies for this release train. ([#74980](openclaw/openclaw#74980), [#81757](openclaw/openclaw#81757), [#86481](openclaw/openclaw#86481), [#86483](openclaw/openclaw#86483), [#90601](openclaw/openclaw#90601)) - QQBot: add `/bot-group-allways on|off` slash command (with named-account and default-account support) to toggle whether group messages require an `@mention` before the bot replies, and clear the runtime config snapshot after the write so the new account-level `defaultRequireMention` takes effect immediately without restart. ([#91423](openclaw/openclaw#91423)) Thanks [@cxyhhhhh](https://github.com/cxyhhhhh). ##### Fixes - Channel content boundaries: QQBot now strips reasoning/thinking tags before sending, preserving final answers while hiding internal model narration from users. ([#89913](openclaw/openclaw#89913), [#90132](openclaw/openclaw#90132)) Thanks [@openperf](https://github.com/openperf). - Agents/MCP/providers: coerce non-text/image MCP tool-result blocks before they reach provider converters, preserving valid images and turning richer MCP content into text instead of malformed image blocks. ([#90710](openclaw/openclaw#90710), [#90728](openclaw/openclaw#90728)) Thanks [@RanSHammer](https://github.com/RanSHammer) and [@849261680](https://github.com/849261680). - Anthropic/Codex/ACP/agent recovery: defer Anthropic stream start events until `message_start`, strip stale compaction thinking signatures before Anthropic replay, detect unsigned thinking-only stalls, refresh prompt fences after compaction writes, reject empty completion handoffs, preserve parent streaming-off overrides/shared progress commentary, forward heartbeat metadata to context-engine hooks, and cover Codex session/thread migration edge cases. ([#90667](openclaw/openclaw#90667), [#90697](openclaw/openclaw#90697), [#90163](openclaw/openclaw#90163), [#90108](openclaw/openclaw#90108), [#89874](openclaw/openclaw#89874), [#89505](openclaw/openclaw#89505), [#90632](openclaw/openclaw#90632), [#89302](openclaw/openclaw#89302), [#90729](openclaw/openclaw#90729), [#90317](openclaw/openclaw#90317), [#90319](openclaw/openclaw#90319)) Thanks [@openperf](https://github.com/openperf), [@100yenadmin](https://github.com/100yenadmin), and [@ooiuuii](https://github.com/ooiuuii). - Provider/model resolution: preserve Google Vertex ADC auth markers in generated catalogs, re-probe a single-provider primary after cooldown, share Codex model visibility, fail closed for unknown model auth, preserve Codex alias availability, keep unresolved profile refs unknown, and avoid resolving auth while listing models. ([#90506](openclaw/openclaw#90506), [#90609](openclaw/openclaw#90609), [#90717](openclaw/openclaw#90717), [#90702](openclaw/openclaw#90702)) Thanks [@849261680](https://github.com/849261680). - Gateway/macOS/mobile: avoid duplicate Gateway probe warnings by identity, rate-limit node pairing requests while preserving paired-node reconnects, keep macOS node mode on a healthy direct Gateway session, keep iOS diagnostics and gateway rows reachable, and avoid Linux ARM Gradle resource tasks during Android builds. ([#85791](openclaw/openclaw#85791), [#90147](openclaw/openclaw#90147), [#90668](openclaw/openclaw#90668), [#90815](openclaw/openclaw#90815)) Thanks [@giodl73-repo](https://github.com/giodl73-repo) and [@vrurg](https://github.com/vrurg). - TUI/chat/Workboard/auto-reply: optimistic user messages stay stable across stale history reloads, runId reassignment, and abort windows instead of disappearing, jumping, or lingering as ghost rows; Workboard stale lifecycle bulk updates no longer overwrite newer status/provenance; message-tool sends now count as delivery. ([#86205](openclaw/openclaw#86205), [#89600](openclaw/openclaw#89600), [#88592](openclaw/openclaw#88592), [#90123](openclaw/openclaw#90123)) Thanks [@RomneyDa](https://github.com/RomneyDa). - Cron/update/service env: doctor config preflight now migrates legacy cron JSON stores into SQLite before runtime reads, service env planning skips unresolved placeholders that would mask state-dir `.env` values, and session transcript rewrites keep registry markers/discriminants consistent. ([#90072](openclaw/openclaw#90072), [#90208](openclaw/openclaw#90208), [#90277](openclaw/openclaw#90277), [#90488](openclaw/openclaw#90488)) Thanks [@MonkeyLeeT](https://github.com/MonkeyLeeT) and [@sallyom](https://github.com/sallyom). - Security/config/tooling: guard MCP HTTP redirects, protect global agent config defaults, and keep release/test/tooling proof failures bounded and explicit. ([#89732](openclaw/openclaw#89732), [#90145](openclaw/openclaw#90145)) - Channels: WhatsApp restarts when per-account config changes, bounds background startup waits, closes failed sockets, and preserves reconnect behavior; Mattermost slash commands keep their state on `globalThis`; Feishu streaming cards preserve full merged content; voice-call tracks Twilio streams after connect; ClickClack reply tools respect `toolsAllow`. ([#87951](openclaw/openclaw#87951), [#87965](openclaw/openclaw#87965), [#90486](openclaw/openclaw#90486), [#68113](openclaw/openclaw#68113), [#90534](openclaw/openclaw#90534), [#90181](openclaw/openclaw#90181), [#90607](openclaw/openclaw#90607), [#89500](openclaw/openclaw#89500)) Thanks [@MukundaKatta](https://github.com/MukundaKatta), [@mcaxtr](https://github.com/mcaxtr), [@infoanton](https://github.com/infoanton), [@mushuiyu886](https://github.com/mushuiyu886), and [@sahibzada-allahyar](https://github.com/sahibzada-allahyar). - Feishu: retry transient send rate-limit errors (HTTP 429, per-chat code 230020, tenant-level code 11232) with linear backoff, including SDK responses that fulfill with rate-limit bodies instead of throwing, and route streaming-card sends through the retry wrapper. ([#89659](openclaw/openclaw#89659)) Thanks [@ladygege](https://github.com/ladygege). - Release/CI/E2E: main CI guard drift, PR merge diff scoping, live Docker credential staging, base-image qualification, installer Docker classification, Playwright dependency install recovery, API-key auth for Codex live Docker lanes, Parallels option terminators, and JSON-mode progress handling are tighter so release proof fails cleaner. ([#90532](openclaw/openclaw#90532), [#90287](openclaw/openclaw#90287), [#90058](openclaw/openclaw#90058)) Thanks [@RomneyDa](https://github.com/RomneyDa), [@hxy91819](https://github.com/hxy91819), and [@mrunalp](https://github.com/mrunalp). - Release/CI/E2E: Docker E2E and live Docker harness runs now apply default memory, CPU, and process ceilings while preserving explicit per-lane overrides. - Release/CI/E2E: plugin lifecycle matrix resource sampling now fails phases that exceed RSS, wall-clock, or CPU ceilings instead of only logging the measurements. - Release/CI/E2E: Codex npm plugin live assertions now cap transcript discovery and diagnostic log reads so failure proof stays bounded. - Tests/state isolation: QA Lab valid-tool-call metrics now require runtime tool-call evidence when runtime parity data is available instead of counting tool-backed scenario pass status alone. - Tests/state isolation: QA Lab runtime parity now fails planned-only tool-call rows without matching tool results instead of treating matching mock plans as real tool evidence. - Tests/state isolation: provider, media, auth, cron, task, session, sandbox, Gateway, and Codex timeout fixtures now scope more home/state/env data per test, reducing cross-test leakage and making release validation failures less noisy. ([#90027](openclaw/openclaw#90027), [#89974](openclaw/openclaw#89974)) </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/963

@mcaxtr

…s so disabled accounts are torn down (openclaw#87965) Merged via squash. Prepared head SHA: 4142d55 Co-authored-by: MukundaKatta <99349238+MukundaKatta@users.noreply.github.com> Co-authored-by: mcaxtr <7562095+mcaxtr@users.noreply.github.com> Reviewed-by: @mcaxtr

openclaw-barnacle Bot added channel: whatsapp-web Channel integration: whatsapp-web gateway Gateway runtime size: XS triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. labels May 29, 2026

clawsweeper Bot added rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. labels May 29, 2026

mcaxtr self-assigned this Jun 4, 2026

mcaxtr force-pushed the fix/whatsapp-reload-disable-account-87951 branch 2 times, most recently from df85063 to 24fc42e Compare June 4, 2026 02:53

clawsweeper Bot added P2 Normal backlog priority with limited blast radius. merge-risk: 🚨 availability 🚨 May cause crashes, hangs, restart loops, stalls, or process outages. labels Jun 4, 2026

mcaxtr force-pushed the fix/whatsapp-reload-disable-account-87951 branch 2 times, most recently from 4bae169 to b1a261a Compare June 4, 2026 03:28

MukundaKatta and others added 2 commits June 4, 2026 00:29

fix(whatsapp): restart channel on per-account config changes so disab…

f8e4f82

…led accounts are torn down (openclaw#87951)

test: pin whatsapp reload descriptor

4142d55

mcaxtr force-pushed the fix/whatsapp-reload-disable-account-87951 branch from b1a261a to 4142d55 Compare June 4, 2026 03:29

mcaxtr merged commit d966486 into openclaw:main Jun 4, 2026
39 of 40 checks passed

clawsweeper Bot mentioned this pull request Jun 19, 2026

fix(whatsapp): restart listener on selfChatMode config change #93873

Merged

Sunbelt Computer Software

PL/B Language Development and Support

Navigation Menu

Repository navigation

fix(whatsapp): restart channel when a per-account config field changes so disabled accounts are torn down - #87965

fix(whatsapp): restart channel when a per-account config field changes so disabled accounts are torn down#87965
mcaxtr merged 2 commits into
openclaw:mainfrom
MukundaKatta:fix/whatsapp-reload-disable-account-87951

MukundaKatta commented May 29, 2026

Uh oh!

clawsweeper Bot commented May 29, 2026 •

edited

Loading

Uh oh!

Uh oh!

mcaxtr commented Jun 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Sunbelt Computer Software

PL/B Language Development and Support

Conversation

MukundaKatta commented May 29, 2026

Summary

Linked context

Real behavior proof (required for external PRs)

Tests and validation

Risk checklist

Current review state

Uh oh!

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

Uh oh!

Uh oh!

Uh oh!

mcaxtr commented Jun 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

clawsweeper Bot commented May 29, 2026 •

edited

Loading