feat(qqbot): add /bot-group-allways command to toggle mention requirement by cxyhhhhh · Pull Request #91423 · openclaw/openclaw

cxyhhhhh · 2026-06-08T12:58:19Z

Summary

Problem: Users cannot conveniently toggle defaultRequireMention for qqbot groups. Config changes via replaceConfigFile() didn't take effect immediately due to getRuntimeConfig() caching the first loaded snapshot.

Solution: Add /bot-group-allways slash command and clear runtime config cache after write.

Changes:

Add /bot-group-allways on|off|status command
Support named accounts and default account
Call clearRuntimeConfigSnapshot() after config write for immediate effect
Add unit tests (309 lines) and update group config tests (56 lines)

Real behavior proof

Before:

17:20:32 [qqbot] Skipped group inbound: reason=skip_no_mention

After:

17:28:13 [reload] config hot reload applied (channels.qqbot.accounts.102901613.defaultRequireMention)

Steps tested:

DM to bot: /bot-group-allways on
Bot replies: "✅ 群自主发言已设置为 on"
Send message in group without @ → AI responds
clearRuntimeConfigSnapshot() called, next getRuntimeConfig() returns fresh config

Tests and validation

npm test -- --testPathPattern="register-group-allways|group"
npm run typecheck
npm run lint

Risk checklist

User-visible behavior change? Yes - new slash command (additive, not breaking)
Config/environment change? Yes - clearRuntimeConfigSnapshot() called after config write
Security/auth change? No
Highest-risk area: clearRuntimeConfigSnapshot() performance impact
Mitigation: Only called after successful replaceConfigFile(), synchronous and fast

Current review state

Next action: Maintainer review for API design and cache invalidation approach

Addressed:

Caching issue with clearRuntimeConfigSnapshot()
Unit tests added
Both named and default account support

clawsweeper · 2026-06-08T13:01:24Z

Codex review: needs real behavior proof before merge. Reviewed June 9, 2026, 3:05 AM ET / 07:05 UTC.

Summary
The branch adds a QQBot /bot-group-allways C2C admin command, an account-level defaultRequireMention fallback in group config resolution, tests, and an explicit runtime config snapshot clear after config writes.

PR surface: Source +138, Tests +367. Total +505 across 5 files.

Reproducibility: yes. for the patch defects from source inspection: current main documents and resolves groups["*"].requireMention, while the PR writes a lower-priority defaultRequireMention and reads status from captured account config. I did not run live QQBot.

Review metrics: 1 noteworthy metric.

Config/default surfaces: 1 added. The PR adds defaultRequireMention as a new QQBot mention-default layer, which is compatibility-sensitive because current users already have the wildcard group default path.

Merge readiness
Overall: 🧂 unranked krab
Proof: 🦐 gold shrimp
Patch quality: 🧂 unranked krab
Result: blocked until stronger real behavior proof is added.

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

Rank-up moves:

Use one supported mention-default contract and read command state from live runtime config.
[P1] Add redacted proof showing the command reply and an unmentioned QQ group message receiving a response after the toggle.

Proof guidance:

[P1] Needs stronger real behavior proof before merge: The screenshot shows QQ group replies, but it does not show the /bot-group-allways command reply or prove that the command toggle caused the unmentioned group response. 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] Merging as-is creates an undocumented account-level QQBot mention default beside the documented groups["*"].requireMention default, so support and upgrades can disagree about which setting controls replies.
[P1] The new command can report success while existing wildcard group config still controls whether unmentioned QQBot group messages reach the agent.
[P1] The explicit runtime snapshot clear after an afterWrite: { mode: "auto" } config write bypasses the normal refreshed snapshot/source metadata path and needs config-owner approval if retained.
[P1] The latest screenshot improves proof that a QQ group can receive replies, but it still does not show the command response or the command-caused before/after toggle path.

Maintainer options:

Keep One Default Path (recommended)
Revise the command to use the documented wildcard group default and read live runtime config before status/no-op decisions.
Accept A New Config Contract
Maintainers can intentionally keep defaultRequireMention, but should add docs, schema/help metadata, upgrade behavior, and tests for precedence against existing group defaults.
Pause Until Command Proof
Keep the PR paused until redacted proof shows the actual command reply and the resulting unmentioned group response in a real QQBot setup.

Next step before merge

[P1] Maintainer review is needed for the QQBot mention-default config contract and for complete external QQBot proof; this is not a safe autonomous repair lane yet.

Security
Cleared: No dependency, workflow, secret-handling, or supply-chain change was found; the group-exposure concern is covered as config/message-delivery merge risk.

Review findings

[P1] Use the existing wildcard group default — extensions/qqbot/src/engine/config/group.ts:80
[P1] Read command state from live config — extensions/qqbot/src/engine/commands/builtin/register-group-allways.ts:32-33

Review details

Best possible solution:

Keep one QQBot mention-default contract by making the admin command read and write groups["*"].requireMention, or explicitly approve and document a defaultRequireMention migration, then show redacted QQBot proof of the command reply plus an unmentioned group response.

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

Yes for the patch defects from source inspection: current main documents and resolves groups["*"].requireMention, while the PR writes a lower-priority defaultRequireMention and reads status from captured account config. I did not run live QQBot.

Is this the best way to solve the issue?

No. A C2C admin command is plausible, but this implementation should either use the existing wildcard group default or land an explicit maintainer-approved config contract, and it should read live runtime config before status/no-op decisions.

Full review comments:

[P1] Use the existing wildcard group default — extensions/qqbot/src/engine/config/group.ts:80
Current QQBot docs and resolver already use groups["*"].requireMention as the every-group default. Adding defaultRequireMention creates a second source of truth with lower precedence, so an existing wildcard entry can keep controlling delivery while this command writes a different key; make the command use the wildcard path or add an explicit maintainer-approved config contract and migration.
Confidence: 0.92
[P1] Read command state from live config — extensions/qqbot/src/engine/commands/builtin/register-group-allways.ts:32-33
The handler checks ctx.accountConfig before fetching runtime config, but that object is copied from the GatewayAccount captured by the connection context. After a config write, the live inbound gate can use refreshed runtime config while this command can still report/no-op from stale account state; load the current QQBot account config from runtime.config.current() before status and same-state checks.
Confidence: 0.9

Overall correctness: patch is incorrect
Overall confidence: 0.9

AGENTS.md: found and applied where relevant.

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

Label changes

Label changes:

add proof: 📸 screenshot: Contributor real behavior proof includes screenshot evidence. The screenshot shows QQ group replies, but it does not show the /bot-group-allways command reply or prove that the command toggle caused the unmentioned group response.

Label justifications:

P2: This is a normal-priority QQBot feature/config PR with concrete compatibility and delivery blockers, not an urgent production regression.
merge-risk: 🚨 compatibility: The PR adds a new QQBot config/default surface that can conflict with the documented groups["*"].requireMention upgrade path.
merge-risk: 🚨 message-delivery: The changed default controls whether unmentioned QQBot group messages are skipped or delivered to the agent.
rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🦐 gold shrimp and patch quality is 🧂 unranked krab.
status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs stronger real behavior proof before merge: The screenshot shows QQ group replies, but it does not show the /bot-group-allways command reply or prove that the command toggle caused the unmentioned group response. 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.
proof: 📸 screenshot: Contributor real behavior proof includes screenshot evidence. The screenshot shows QQ group replies, but it does not show the /bot-group-allways command reply or prove that the command toggle caused the unmentioned group response.

Evidence reviewed

PR surface:

Source +138, Tests +367. Total +505 across 5 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	3	139	1	+138
Tests	2	367	0	+367
Docs	0	0	0	0
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	5	506	1	+505

What I checked:

Repository policy applied: Root AGENTS.md and scoped extensions/AGENTS.md were read; the PR touches bundled plugin config/default behavior, which the policy treats as compatibility-sensitive. (AGENTS.md:1, f57c3b55fdc4)
Current documented QQBot default path: Current docs say groups["*"] sets defaults for every QQBot group and list requireMention as the documented setting with default true. Public docs: docs/channels/qqbot.md. (docs/channels/qqbot.md:170, f57c3b55fdc4)
Current main resolver precedence: Current main resolves QQBot requireMention from specific group, then wildcard group, then the built-in default; there is no account-level mention fallback in the current resolver. (extensions/qqbot/src/engine/config/group.ts:72, f57c3b55fdc4)
PR adds a lower-priority config fallback: The PR adds defaultRequireMention below specific and wildcard group config, so existing wildcard config can override the new command's written value. (extensions/qqbot/src/engine/config/group.ts:80, 995770d78bf7)
PR reads command state from captured account config: The new handler reads ctx.accountConfig?.defaultRequireMention before loading runtime config, then uses that value for status and same-state decisions. (extensions/qqbot/src/engine/commands/builtin/register-group-allways.ts:32, 995770d78bf7)
Current command context uses connection account config: Current main builds slash command context with accountConfig: account.config from the gateway connection context, not by reloading the live runtime config for each command status/no-op check. (extensions/qqbot/src/engine/commands/slash-command-handler.ts:105, f57c3b55fdc4)

Likely related people:

sliverp: History shows prior merged QQBot channel/config work, and this person is also the current assignee who posted the latest QQ proof screenshot. (role: adjacent QQBot contributor; confidence: medium; commits: bf6f506dfae6, 65b781f9ae3a; files: extensions/qqbot/openclaw.plugin.json, docs/channels/qqbot.md, extensions/qqbot/src/channel.ts)
Vincent Koc: Recent history includes QQBot release/baseline and command/auth related work around the current bundled plugin surface. (role: recent area contributor; confidence: medium; commits: 2e08f0f4221f, 72af92ba4e27; files: extensions/qqbot/src/engine/config/group.ts, extensions/qqbot/src/engine/commands/builtin/register-approve.ts, docs/channels/qqbot.md)
Peter Steinberger: History shows prior QQBot docs and config helper work relevant to whether a new public config surface should exist. (role: adjacent docs/config contributor; confidence: medium; commits: cebe697082ad, 6243ca50e0d2; files: docs/channels/qqbot.md, extensions/qqbot/src/config-schema.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.

sliverp · 2026-06-09T06:55:29Z

proof:

@clawsweeper review

clawsweeper · 2026-06-09T06:55:32Z

🦞🧹
ClawSweeper re-review requested.

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

Re-review progress:

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

…equirement Add slash command to configure defaultRequireMention for qqbot accounts. Clear runtime config snapshot cache after config write to ensure getRuntimeConfig() reads fresh values on next message. - Add register-group-allways command (on/off/status) - Support named accounts and default account - Clear runtime config cache after write for immediate effect - Add unit tests for group config resolution

@cxyhhhhh

…equirement (openclaw#91423) (thanks @cxyhhhhh)

sliverp · 2026-06-09T07:45:36Z

Landed via temp rebase onto main.

Gate: skipped per maintainer (small additive feat, isolated to qqbot extension)
Land commit: 56780c8
Merge commit: d12b7b0

Thanks @cxyhhhhh!

…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

@cxyhhhhh

…ment (openclaw#91423) * feat(qqbot): add /bot-group-allways command to toggle group mention requirement Add slash command to configure defaultRequireMention for qqbot accounts. Clear runtime config snapshot cache after config write to ensure getRuntimeConfig() reads fresh values on next message. - Add register-group-allways command (on/off/status) - Support named accounts and default account - Clear runtime config cache after write for immediate effect - Add unit tests for group config resolution * test(qqbot): fix group allways test imports * feat(qqbot): add /bot-group-allways command to toggle group mention requirement (openclaw#91423) (thanks @cxyhhhhh) --------- Co-authored-by: sliverp <870080352@qq.com>

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

sliverp self-assigned this Jun 9, 2026

sliverp force-pushed the feat/group branch from a4bc237 to 995770d Compare June 9, 2026 03:47

clawsweeper Bot added the proof: 📸 screenshot Contributor real behavior proof includes screenshot evidence. label Jun 9, 2026

cxyhhhhh and others added 3 commits June 9, 2026 15:34

test(qqbot): fix group allways test imports

abb4fe4

feat(qqbot): add /bot-group-allways command to toggle group mention r…

56780c8

…equirement (openclaw#91423) (thanks @cxyhhhhh)

sliverp force-pushed the feat/group branch from 995770d to 56780c8 Compare June 9, 2026 07:42

sliverp merged commit d12b7b0 into openclaw:main Jun 9, 2026
30 of 31 checks passed

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

📡 Upstream Digest — 2026-06-09 10:53 UTC curtismercier/openclaw-mods#1044

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat(qqbot): add /bot-group-allways command to toggle mention requirement#91423

feat(qqbot): add /bot-group-allways command to toggle mention requirement#91423
sliverp merged 3 commits into
openclaw:mainfrom
cxyhhhhh:feat/group

cxyhhhhh commented Jun 8, 2026

Uh oh!

clawsweeper Bot commented Jun 8, 2026 •

edited

Loading

Uh oh!

sliverp commented Jun 9, 2026

Uh oh!

clawsweeper Bot commented Jun 9, 2026 •

edited

Loading

Uh oh!

Uh oh!

sliverp commented Jun 9, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

cxyhhhhh commented Jun 8, 2026

Summary

Real behavior proof

Tests and validation

Risk checklist

Current review state

Uh oh!

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

Uh oh!

Uh oh!

sliverp commented Jun 9, 2026

Uh oh!

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

Uh oh!

Uh oh!

Uh oh!

sliverp commented Jun 9, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

clawsweeper Bot commented Jun 8, 2026 •

edited

Loading

clawsweeper Bot commented Jun 9, 2026 •

edited

Loading