Skip to content

fix(discord): hydrate reply context metadata#90263

Merged
obviyus merged 4 commits into
openclaw:mainfrom
fuller-stack-dev:codex/reply-context-metadata
Jun 10, 2026
Merged

fix(discord): hydrate reply context metadata#90263
obviyus merged 4 commits into
openclaw:mainfrom
fuller-stack-dev:codex/reply-context-metadata

Conversation

@fuller-stack-dev

@fuller-stack-dev fuller-stack-dev commented Jun 4, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Summary

  • Hydrate Discord inbound messages through REST when a reply message_reference is present but Discord omitted referenced_message, while avoiding forwarded references and known-deleted replies.
  • Expose full reply metadata through plugin hook contracts: replyToIdFull and replyToIsQuote now flow through inbound hooks and before_dispatch event/context payloads.
  • Update hook docs to describe the first-class reply metadata fields available to plugin authors.

Verification

  • node scripts/run-vitest.mjs extensions/discord/src/monitor/message-handler.hydration.test.ts src/hooks/message-hook-mappers.test.ts src/auto-reply/reply/dispatch-from-config.test.ts
  • git diff --check
  • pnpm exec oxfmt --write extensions/discord/src/monitor/message-handler.hydration.ts extensions/discord/src/monitor/message-handler.hydration.test.ts
  • .agents/skills/autoreview/scripts/autoreview --mode local (clean: no accepted/actionable findings)
  • Testbox-through-Crabbox changed gate: node scripts/crabbox-wrapper.mjs run --provider blacksmith-testbox --blacksmith-org openclaw --blacksmith-workflow .github/workflows/ci-check-testbox.yml --blacksmith-job check --blacksmith-ref main --idle-timeout 90m --ttl 240m --timing-json -- corepack pnpm check:changed; provider blacksmith-testbox, id tbx_01kt8wwzkay11kjsaece1z2hyn, exit 0
  • Post-comment lint fix: node scripts/run-bundled-extension-oxlint.mjs; node scripts/run-oxlint.mjs --tsconfig config/tsconfig/oxlint.extensions.json extensions/discord/src/monitor/message-handler.hydration.test.ts; Testbox-through-Crabbox changed gate tbx_01ktaq3cbagqa69jymfqr8atyn, exit 0
  • Post-rebase conflict resolution: Testbox-through-Crabbox changed gate tbx_01ktb43estpzex12cnyxzbbdxj, exit 0

Real behavior proof

Behavior addressed: Discord replies that arrive with message_reference but without referenced_message now hydrate the missing quoted message through the Discord channel-message route before reply context is resolved. Reply-capable channel metadata is also exposed through shared plugin hook fields.

Real environment tested: Local OpenClaw source checkout on the rebased PR branch, executing the production Discord plugin hydration module through Node/tsx with an actual Message instance and a REST client that records the Discord route requested by the hydrator.

Exact steps or command run after this patch: node --import tsx --input-type=module from the OpenClaw repo root, importing Client, Message, and hydrateDiscordMessageIfNeeded from the Discord plugin runtime modules, then passing a gateway-shaped reply payload whose raw data has message_reference and no referenced_message.

Evidence after fix: Terminal capture from the after-fix run:

before.referencedMessage <missing>
rest.calls ["/channels/channel-1/messages/reply-1"]
after.referencedMessage cron: job interrupted by gateway restart
sameMessageObject false

Observed result after fix: The reply starts without a referenced message, the hydrator performs one Discord channel-message fetch for the reply message, and the returned hydrated Message exposes the quoted body through referencedMessage.content.

What was not tested: A live Discord bot token/gateway session was not used in this proof; the exercised path is the production OpenClaw Discord hydration code with a redacted, gateway-shaped reply payload and recorded REST route.

@openclaw-barnacle openclaw-barnacle Bot added docs Improvements or additions to documentation channel: discord Channel integration: discord size: M triage: mock-only-proof Candidate: PR proof only shows tests, mocks, snapshots, lint, typecheck, or CI. labels Jun 4, 2026
@clawsweeper

clawsweeper Bot commented Jun 4, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Codex review: needs maintainer review before merge. Reviewed June 5, 2026, 1:50 AM ET / 05:50 UTC.

Summary
This PR hydrates Discord reply messages whose gateway payload omitted referenced_message, propagates replyToIdFull and replyToIsQuote through plugin hook payloads, and updates tests and hook docs.

PR surface: Source +60, Tests +218, Docs +1. Total +279 across 9 files.

Reproducibility: yes. from source. Current main leaves referencedMessage null when Discord omits referenced_message, and the hydration predicate skips a plain text reply without unresolved mention metadata.

Review metrics: 1 noteworthy metric.

  • Plugin hook fields: 2 added. replyToIdFull and replyToIsQuote become documented plugin hook fields, so maintainers should notice the public API expansion before merge.

Merge readiness
Overall: 🐚 platinum hermit
Proof: 🐚 platinum hermit
Patch quality: 🐚 platinum hermit
Result: ready for maintainer review.

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

Rank-up moves:

  • [P2] Get maintainer acceptance for the two additive public hook fields before merge.

Risk before merge

  • [P1] The PR adds two documented plugin hook fields; once shipped, plugin authors can depend on replyToIdFull and replyToIsQuote, so this needs explicit maintainer acceptance as a public API expansion.
  • [P1] The after-fix proof exercises production code in a local Node/tsx run with a recorded REST client, but it does not prove the omitted-referenced_message shape in a live Discord gateway session.

Maintainer options:

  1. Accept the additive hook contract (recommended)
    Land after a maintainer explicitly accepts replyToIdFull and replyToIsQuote as public plugin hook fields with the documented semantics.
  2. Narrow to Discord hydration only
    If maintainers do not want the hook API expansion here, split the Discord hydration fix from the public hook field additions before merge.
  3. Pause for hook API direction
    Pause or close only if maintainers want a broader reply-metadata design instead of extending the existing hook contract field by field.

Next step before merge

  • [P2] A maintainer should accept or reject the additive public hook API contract; there is no narrow automated repair needed from this review.

Security
Cleared: No concrete security or supply-chain concern was found; the diff adds no dependencies, workflows, install scripts, secret handling, or broader permissions.

Review details

Best possible solution:

Land the focused hydration fix after maintainers accept the additive hook field contract and normal merge gates remain green.

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

Yes, from source. Current main leaves referencedMessage null when Discord omits referenced_message, and the hydration predicate skips a plain text reply without unresolved mention metadata.

Is this the best way to solve the issue?

Yes, with a compatibility caveat. Hydrating only omitted default reply references preserves deleted and forwarded-reference behavior, and the hook additions reuse already-finalized reply metadata instead of creating a Discord-only path.

AGENTS.md: found and applied where relevant.

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

Label changes

Label changes:

  • add proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes after-fix terminal output from a local Node/tsx run that imports production Discord Message and hydration code, records the requested Discord route, and shows hydrated referenced-message content.

Label justifications:

  • P2: The PR fixes a normal Discord reply-context bug and hook metadata gap with limited blast radius.
  • merge-risk: 🚨 compatibility: The diff expands documented plugin hook payload types, making the new fields part of the public plugin compatibility contract once shipped.
  • rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🐚 platinum hermit.
  • status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (terminal): The PR body includes after-fix terminal output from a local Node/tsx run that imports production Discord Message and hydration code, records the requested Discord route, and shows hydrated referenced-message content.
  • proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes after-fix terminal output from a local Node/tsx run that imports production Discord Message and hydration code, records the requested Discord route, and shows hydrated referenced-message content.
Evidence reviewed

PR surface:

Source +60, Tests +218, Docs +1. Total +279 across 9 files.

View PR surface stats
Area Files Added Removed Net
Source 5 61 1 +60
Tests 3 219 1 +218
Docs 1 3 2 +1
Config 0 0 0 0
Generated 0 0 0 0
Other 0 0 0 0
Total 9 283 4 +279

What I checked:

Likely related people:

  • steipete: Recent GitHub commit lookups show Discord extension/docs work and local blame ties the current hydration and hook mapper baselines to Peter Steinberger-authored history. (role: recent area contributor; confidence: high; commits: 23716de4468b, 4c3b4f8ad8f8, 1507a9701b83; files: extensions/discord/src/monitor/message-handler.hydration.ts, src/hooks/message-hook-mappers.ts, docs/plugins/hooks.md)
  • TurboTheTurtle: Commit 9215984 exposed inbound reply metadata before dispatch on the same hook mapper, hook type, and docs surfaces this PR extends. (role: introduced adjacent behavior; confidence: high; commits: 921598442ace; files: src/hooks/message-hook-mappers.ts, src/plugins/hook-message.types.ts, src/plugins/hook-types.ts)
  • vincentkoc: Commits 3bd2ee7 and e593122 added or standardized plugin hook correlation/routing metadata on the same public hook surfaces. (role: adjacent hook owner; confidence: medium; commits: 3bd2ee78b6ac, e593122465e7; files: src/hooks/message-hook-mappers.ts, src/plugins/hook-message.types.ts, src/plugins/hook-types.ts)
  • fuller-stack-dev: The PR author also appears in prior merged Discord message context history, so they are relevant beyond only proposing this branch. (role: recent Discord contributor; confidence: medium; commits: 0014724428d7; files: extensions/discord/src/monitor/message-handler.context.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.

@clawsweeper clawsweeper Bot added the rating: 🌊 off-meta tidepool PR readiness rating does not apply to this item. label Jun 4, 2026
@byungskers

byungskers commented Jun 4, 2026

Copy link
Copy Markdown

The hydration path looks good overall. One case I'd be curious to cover before landing: what happens when the REST fetch for the missing referenced_message returns 404 / missing access? Right now the new tests prove the happy path and the "don't fetch" cases, but a failed fetch seems like the remaining edge that decides whether reply handling degrades quietly or starts surfacing avoidable noise.

@fuller-stack-dev

fuller-stack-dev commented Jun 5, 2026

Copy link
Copy Markdown
Contributor Author

Addressed the REST failure case.

Added keeps the original reply message when hydration fetch fails in extensions/discord/src/monitor/message-handler.hydration.test.ts. It simulates a missing-access/404-style REST failure, verifies hydration attempts the fetch once, returns the original gateway message, and leaves referencedMessage null instead of throwing or fabricating reply context.

Verification:

  • node scripts/run-vitest.mjs extensions/discord/src/monitor/message-handler.hydration.test.ts
  • git diff --check

The earlier ClawSweeper review timed out before evaluating the patch, so requesting a fresh review now that the human comment is addressed.

@clawsweeper re-review

@clawsweeper

clawsweeper Bot commented Jun 5, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

🦞🧹
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:

@clawsweeper clawsweeper Bot added rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. P2 Normal backlog priority with limited blast radius. merge-risk: 🚨 compatibility 🚨 May break existing users, config, migrations, defaults, or upgrade paths. rating: 🌊 off-meta tidepool PR readiness rating does not apply to this item. and removed rating: 🌊 off-meta tidepool PR readiness rating does not apply to this item. rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. labels Jun 5, 2026
@fuller-stack-dev fuller-stack-dev force-pushed the codex/reply-context-metadata branch from 19e824e to ee87ce2 Compare June 5, 2026 05:28
@clawsweeper clawsweeper Bot added proof: sufficient ClawSweeper judged the real behavior proof convincing. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. and removed rating: 🌊 off-meta tidepool PR readiness rating does not apply to this item. labels Jun 5, 2026
@openclaw-barnacle openclaw-barnacle Bot added proof: supplied External PR includes structured after-fix real behavior proof. and removed triage: mock-only-proof Candidate: PR proof only shows tests, mocks, snapshots, lint, typecheck, or CI. proof: sufficient ClawSweeper judged the real behavior proof convincing. labels Jun 5, 2026
@clawsweeper clawsweeper Bot added the proof: sufficient ClawSweeper judged the real behavior proof convincing. label Jun 5, 2026
@openclaw-barnacle openclaw-barnacle Bot removed the proof: sufficient ClawSweeper judged the real behavior proof convincing. label Jun 10, 2026
@obviyus obviyus force-pushed the codex/reply-context-metadata branch from a1ac340 to f381645 Compare June 10, 2026 09:17
@obviyus obviyus merged commit c84e521 into openclaw:main Jun 10, 2026
159 of 160 checks passed
@obviyus

obviyus commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Landed via rebase onto main.

Scoped proof:

  • node scripts/run-vitest.mjs extensions/discord/src/monitor/message-handler.hydration.test.ts src/hooks/message-hook-mappers.test.ts src/auto-reply/reply/dispatch-from-config.test.ts
  • node scripts/run-oxlint.mjs --tsconfig config/tsconfig/oxlint.extensions.json extensions/discord/src/monitor/message-handler.hydration.test.ts extensions/discord/src/monitor/message-handler.hydration.ts
  • .agents/skills/autoreview/scripts/autoreview --mode branch --base origin/main

Changelog: not updated; release-owned per repo policy. PR body has the user-facing release-note context.

CI note: build-artifacts failed in an unrelated tooling test. Failure was scripts/check-deadcode-unused-files.test.ts expecting command pnpm while CI used /opt/hostedtoolcache/node/24.13.0/x64/bin/pnpm. This PR touched only Discord reply hydration, hook metadata propagation, tests, and hook docs.

Land commit: f381645
Merge commit: c84e521

Thanks @fuller-stack-dev!

eleboucher pushed a commit to eleboucher/homelab that referenced this pull request Jun 12, 2026
@eleboucher
fix(container): update image ghcr.io/openclaw/openclaw (2026.6.5 ➔ 20…
bb872cc 
…26.6.6) (#1040)

This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| [ghcr.io/openclaw/openclaw](https://openclaw.ai) ([source](https://github.com/openclaw/openclaw)) | patch | `2026.6.5` → `2026.6.6` |

---

### Release Notes

<details>
<summary>openclaw/openclaw (ghcr.io/openclaw/openclaw)</summary>

### [`v2026.6.6`](https://github.com/openclaw/openclaw/blob/HEAD/CHANGELOG.md#202666)

[Compare Source](openclaw/openclaw@v2026.6.5...v2026.6.6)

##### Highlights

- Security boundaries are substantially tighter across transcripts, sandbox binds, host environment inheritance, MCP stdio, Codex HTTP access, native search policy, elevated sender checks, deleted-agent ACP bypasses, loopback tools, Discord moderation, and Teams group actions; exec approvals now fail closed on timeout. ([#&#8203;91529](openclaw/openclaw#91529), [#&#8203;91618](openclaw/openclaw#91618), [#&#8203;91615](openclaw/openclaw#91615), [#&#8203;91619](openclaw/openclaw#91619), [#&#8203;91741](openclaw/openclaw#91741), [#&#8203;91745](openclaw/openclaw#91745), [#&#8203;91746](openclaw/openclaw#91746), [#&#8203;91748](openclaw/openclaw#91748), [#&#8203;91749](openclaw/openclaw#91749), [#&#8203;91750](openclaw/openclaw#91750), [#&#8203;91751](openclaw/openclaw#91751), [#&#8203;91752](openclaw/openclaw#91752), [#&#8203;91763](openclaw/openclaw#91763), [#&#8203;89938](openclaw/openclaw#89938)) Thanks [@&#8203;joshavant](https://github.com/joshavant), [@&#8203;pgondhi987](https://github.com/pgondhi987), [@&#8203;mmaps](https://github.com/mmaps), [@&#8203;eleqtrizit](https://github.com/eleqtrizit), [@&#8203;shakkernerd](https://github.com/shakkernerd), and [@&#8203;drobison00](https://github.com/drobison00).
- Telegram delivery is safer and more coherent: account-scoped topics route to the right agent, streamed text survives tool calls, `/compact` works on generic ingress, callback handling uses concrete APIs, draft chunking is shared, durable dispatch dedupe moved into the SDK, and unauthorized DM text stays out of cache and prompt context. ([#&#8203;91189](openclaw/openclaw#91189), [#&#8203;88682](openclaw/openclaw#88682), [#&#8203;89588](openclaw/openclaw#89588), [#&#8203;90212](openclaw/openclaw#90212), [#&#8203;91876](openclaw/openclaw#91876), [#&#8203;91874](openclaw/openclaw#91874), [#&#8203;91904](openclaw/openclaw#91904), [#&#8203;91478](openclaw/openclaw#91478), [#&#8203;91915](openclaw/openclaw#91915)) Thanks [@&#8203;codysai001](https://github.com/codysai001), [@&#8203;alexzhu0](https://github.com/alexzhu0), [@&#8203;joelnishanth](https://github.com/joelnishanth), [@&#8203;snowzlm](https://github.com/snowzlm), [@&#8203;obviyus](https://github.com/obviyus), and [@&#8203;sallyom](https://github.com/sallyom).
- iMessage recovery and delivery now cover always-on inbound restart, durable echo markers, block streaming, idle approval discovery, hardened outbound transport, and actionable inbound startup diagnostics. ([#&#8203;91335](openclaw/openclaw#91335), [#&#8203;91449](openclaw/openclaw#91449), [#&#8203;88969](openclaw/openclaw#88969), [#&#8203;88530](openclaw/openclaw#88530), [#&#8203;91783](openclaw/openclaw#91783), [#&#8203;91785](openclaw/openclaw#91785)) Thanks [@&#8203;omarshahine](https://github.com/omarshahine), [@&#8203;jmissig](https://github.com/jmissig), and [@&#8203;colmbrogan](https://github.com/colmbrogan).
- Browser and MCP connectivity gained existing-session CDP support, discovered WebSocket validation, default-profile `cdpUrl` handling, safer browser-output boundaries, Streamable HTTP loopback transport, corrected OAuth/SSE authorization handling, and broader schema compatibility. ([#&#8203;91422](openclaw/openclaw#91422), [#&#8203;89851](openclaw/openclaw#89851), [#&#8203;91736](openclaw/openclaw#91736), [#&#8203;91747](openclaw/openclaw#91747), [#&#8203;91451](openclaw/openclaw#91451), [#&#8203;80143](openclaw/openclaw#80143)) Thanks [@&#8203;pgondhi987](https://github.com/pgondhi987), [@&#8203;anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia), [@&#8203;lifuyue](https://github.com/lifuyue), [@&#8203;eleqtrizit](https://github.com/eleqtrizit), [@&#8203;LiuwqGit](https://github.com/LiuwqGit), and [@&#8203;HemantSudarshan](https://github.com/HemantSudarshan).
- Control UI startup and first-reply latency are lower through cached model metadata, removal of the startup catalog wait, lazy slash-command loading, and first-event tracing with slow-reply diagnostics. ([#&#8203;91531](openclaw/openclaw#91531), [#&#8203;91538](openclaw/openclaw#91538), [#&#8203;91568](openclaw/openclaw#91568), [#&#8203;91583](openclaw/openclaw#91583), [#&#8203;91598](openclaw/openclaw#91598))
- Provider support expands with OpenRouter OAuth onboarding and Claude Fable 5 adaptive thinking, while Codex sessions keep correct compaction ownership, local models skip guardian review, dynamic tool progress normalizes cleanly, and Gemma 4 reasoning replay is preserved. ([#&#8203;91830](openclaw/openclaw#91830), [#&#8203;91882](openclaw/openclaw#91882), [#&#8203;91590](openclaw/openclaw#91590), [#&#8203;88630](openclaw/openclaw#88630), [#&#8203;88768](openclaw/openclaw#88768), [#&#8203;91696](openclaw/openclaw#91696)) Thanks [@&#8203;Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@&#8203;joshavant](https://github.com/joshavant), [@&#8203;bdjben](https://github.com/bdjben), and [@&#8203;Coder-Wangyankun](https://github.com/Coder-Wangyankun).

##### Changes

- CLI progress: emit Claude CLI commentary progress events and bridge inter-tool commentary into channel progress without exposing internal protocol scaffolding. ([#&#8203;89834](openclaw/openclaw#89834), [#&#8203;90883](openclaw/openclaw#90883)) Thanks [@&#8203;anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia).
- Observability: allow trusted diagnostics channels to capture tool input/output content, add first-assistant-event traces, and warn on slow initial replies. ([#&#8203;91256](openclaw/openclaw#91256), [#&#8203;91568](openclaw/openclaw#91568), [#&#8203;91583](openclaw/openclaw#91583)) Thanks [@&#8203;amknight](https://github.com/amknight).
- Plugins/ClawHub: dogfood reusable package publishing, let dry runs skip publish approval, allow declared installed trusted hooks, report managed plugin version drift, and warn instead of failing on retired Skill Workshop configuration. ([#&#8203;91574](openclaw/openclaw#91574), [#&#8203;91591](openclaw/openclaw#91591), [#&#8203;90004](openclaw/openclaw#90004), [#&#8203;90927](openclaw/openclaw#90927), [#&#8203;90838](openclaw/openclaw#90838)) Thanks [@&#8203;Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@&#8203;brokemac79](https://github.com/brokemac79), and [@&#8203;lonexreb](https://github.com/lonexreb).
- Memory/providers: move the local llama.cpp runtime into its provider plugin, batch embeddings across files, persist the agent model catalog cache, and keep QMD JSON search one-shot while filtering stale REM recall previews. ([#&#8203;91324](openclaw/openclaw#91324), [#&#8203;89138](openclaw/openclaw#89138), [#&#8203;90457](openclaw/openclaw#90457), [#&#8203;91837](openclaw/openclaw#91837), [#&#8203;91851](openclaw/openclaw#91851)) Thanks [@&#8203;osolmaz](https://github.com/osolmaz), [@&#8203;mushuiyu886](https://github.com/mushuiyu886), [@&#8203;ai-hpc](https://github.com/ai-hpc), and [@&#8203;TurboTheTurtle](https://github.com/TurboTheTurtle).
- Channels/mobile: add the QQBot group mention toggle, improve iPad and iPhone control surfaces, and expose the active connection host in the TUI footer. ([#&#8203;91423](openclaw/openclaw#91423), [#&#8203;91557](openclaw/openclaw#91557), [#&#8203;89909](openclaw/openclaw#89909)) Thanks [@&#8203;cxyhhhhh](https://github.com/cxyhhhhh), [@&#8203;Solvely-Colin](https://github.com/Solvely-Colin), and [@&#8203;baskduf](https://github.com/baskduf).
- Performance: prewarm TUI runtime plugins, deduplicate plugin auto-enable fanout, trim dense text-delta snapshots, and reuse prepared startup model metadata. ([#&#8203;90782](openclaw/openclaw#90782), [#&#8203;89978](openclaw/openclaw#89978), [#&#8203;91580](openclaw/openclaw#91580), [#&#8203;91531](openclaw/openclaw#91531)) Thanks [@&#8203;RomneyDa](https://github.com/RomneyDa) and [@&#8203;ai-hpc](https://github.com/ai-hpc).

##### Fixes

- Agent/session recovery: drop stale approval follow-ups after session rebind, remove drained reply-queue items by identity, recover stale main and visible replies, preserve Codex context-engine compaction ownership, lower the default compaction timeout to 180 seconds while respecting explicit configuration, and keep provider-failure terminal lifecycle state correct. ([#&#8203;85679](openclaw/openclaw#85679), [#&#8203;91450](openclaw/openclaw#91450), [#&#8203;91566](openclaw/openclaw#91566), [#&#8203;91840](openclaw/openclaw#91840), [#&#8203;91590](openclaw/openclaw#91590), [#&#8203;91361](openclaw/openclaw#91361), [#&#8203;91895](openclaw/openclaw#91895)) Thanks [@&#8203;openperf](https://github.com/openperf), [@&#8203;yetval](https://github.com/yetval), [@&#8203;joshavant](https://github.com/joshavant), [@&#8203;wangmiao0668000666](https://github.com/wangmiao0668000666), and [@&#8203;TurboTheTurtle](https://github.com/TurboTheTurtle).
- User-visible content boundaries: suppress Codex/Harmony protocol artifacts, neutralize browser and LanceDB memory media directives, redact transcript images, and preserve native `/compact` replies through source suppression. ([#&#8203;89151](openclaw/openclaw#89151), [#&#8203;91422](openclaw/openclaw#91422), [#&#8203;91425](openclaw/openclaw#91425), [#&#8203;91529](openclaw/openclaw#91529), [#&#8203;90212](openclaw/openclaw#90212)) Thanks [@&#8203;joelnishanth](https://github.com/joelnishanth), [@&#8203;pgondhi987](https://github.com/pgondhi987), [@&#8203;joshavant](https://github.com/joshavant), and [@&#8203;snowzlm](https://github.com/snowzlm).
- Channel delivery: keep WhatsApp captured replies attached to the successor controller after restart, retry Feishu rate limits, preserve Mattermost thread replies, canonicalize LINE webhook paths, restore Discord reply hydration and runtime timeout exports, and show OpenAI Realtime WebRTC assistant transcripts. ([#&#8203;85823](openclaw/openclaw#85823), [#&#8203;89659](openclaw/openclaw#89659), [#&#8203;91684](openclaw/openclaw#91684), [#&#8203;91649](openclaw/openclaw#91649), [#&#8203;90263](openclaw/openclaw#90263), [#&#8203;91686](openclaw/openclaw#91686), [#&#8203;90426](openclaw/openclaw#90426)) Thanks [@&#8203;itsuzef](https://github.com/itsuzef), [@&#8203;ladygege](https://github.com/ladygege), [@&#8203;jacobtomlinson](https://github.com/jacobtomlinson), [@&#8203;fuller-stack-dev](https://github.com/fuller-stack-dev), and [@&#8203;shushushv](https://github.com/shushushv).
- Cron: cancel active task runs cleanly, preserve terminal timeout/cancel state, and recover no-deliver tool warnings instead of silently losing the outcome. ([#&#8203;90666](openclaw/openclaw#90666), [#&#8203;90678](openclaw/openclaw#90678)) Thanks [@&#8203;ai-hpc](https://github.com/ai-hpc).
- Gateway/config/auth: share the approval runtime socket token, replace arrays explicitly in `config.patch`, skip the deleted-agent guard only for valid ACP harness sessions, surface headless LaunchAgent state, verify SQLite auth migration before cleanup, and arm QMD startup maintenance. ([#&#8203;87105](openclaw/openclaw#87105), [#&#8203;91551](openclaw/openclaw#91551), [#&#8203;91219](openclaw/openclaw#91219), [#&#8203;91614](openclaw/openclaw#91614), [#&#8203;91740](openclaw/openclaw#91740), [#&#8203;91978](openclaw/openclaw#91978)) Thanks [@&#8203;fuller-stack-dev](https://github.com/fuller-stack-dev) and [@&#8203;scotthuang](https://github.com/scotthuang).
- Providers/Codex: clarify quota errors, restore the Codex synthetic usage line, canonicalize Codex protocol assets, require API-key auth for realtime voice, normalize ACP model refs, preserve Gemma 4 `reasoning_content`, and avoid guardian review for local models. ([#&#8203;91390](openclaw/openclaw#91390), [#&#8203;91709](openclaw/openclaw#91709), [#&#8203;91507](openclaw/openclaw#91507), [#&#8203;91567](openclaw/openclaw#91567), [#&#8203;88630](openclaw/openclaw#88630), [#&#8203;91696](openclaw/openclaw#91696)) Thanks [@&#8203;hxy91819](https://github.com/hxy91819), [@&#8203;brokemac79](https://github.com/brokemac79), [@&#8203;RomneyDa](https://github.com/RomneyDa), [@&#8203;joshavant](https://github.com/joshavant), and [@&#8203;Coder-Wangyankun](https://github.com/Coder-Wangyankun).
- Updates/builds: recover package Gateway restarts after refresh failure, expose plugin convergence repair, fall back to Corepack in PATH-less pnpm environments, seed the correct Docker store packages, and keep ClawHub dry-run and publish paths reusable. ([#&#8203;91581](openclaw/openclaw#91581), [#&#8203;91599](openclaw/openclaw#91599), [#&#8203;91547](openclaw/openclaw#91547), [#&#8203;91591](openclaw/openclaw#91591)) Thanks [@&#8203;fuller-stack-dev](https://github.com/fuller-stack-dev), [@&#8203;sallyom](https://github.com/sallyom), and [@&#8203;Patrick-Erichsen](https://github.com/Patrick-Erichsen).
- UI: require explicit user intent before opening chat sessions and drain restored chat queues after session switches. ([#&#8203;91480](openclaw/openclaw#91480)) Thanks [@&#8203;TurboTheTurtle](https://github.com/TurboTheTurtle).
- Android: avoid the `dataSync` foreground-service type for persistent nodes. ([#&#8203;80082](openclaw/openclaw#80082)) Thanks [@&#8203;davelutztx](https://github.com/davelutztx).
- Native hooks: bound relay lifetimes so abandoned native hook connections cannot linger indefinitely. ([#&#8203;91550](openclaw/openclaw#91550)) Thanks [@&#8203;joshavant](https://github.com/joshavant).

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about these updates again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xMDEuMSIsInVwZGF0ZWRJblZlciI6IjQzLjEwMS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZS9jb250YWluZXIiLCJ0eXBlL3BhdGNoIl19-->

Reviewed-on: https://git.erwanleboucher.dev/eleboucher/homelab/pulls/1040
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

channel: discord Channel integration: discord docs Improvements or additions to documentation merge-risk: 🚨 compatibility 🚨 May break existing users, config, migrations, defaults, or upgrade paths. P2 Normal backlog priority with limited blast radius. proof: supplied External PR includes structured after-fix real behavior proof. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. size: M status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@fuller-stack-dev @byungskers @obviyus