Skip to content

fix(telegram): use SDK dispatch dedupe#91904

Merged
obviyus merged 4 commits into
mainfrom
codex/telegram-sdk-dispatch-dedupe
Jun 10, 2026
Merged

fix(telegram): use SDK dispatch dedupe#91904
obviyus merged 4 commits into
mainfrom
codex/telegram-sdk-dispatch-dedupe

Conversation

@obviyus

@obviyus obviyus commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Replace Telegram dispatch replay dedupe buckets/locks with the SDK persistent claimable dedupe helper.
  • Keep persisted replay protection at the prior 50k window under a dedicated dedupe state owner, with account id folded into the key.
  • Move legacy JSON and shipped bucketed plugin-state imports into doctor-time migration for the SDK namespace/key shape.

Verification

  • node scripts/run-vitest.mjs src/plugin-sdk/memory-host-events.test.ts extensions/telegram/src/state-migrations.test.ts extensions/telegram/src/message-dispatch-dedupe.test.ts extensions/telegram/src/bot.create-telegram-bot.test.ts src/plugin-sdk/api-baseline.test.ts src/commands/doctor-state-migrations.test.ts
  • pnpm plugin-sdk:api:check
  • .agents/skills/autoreview/scripts/autoreview --mode branch --base origin/main
  • Testbox changed gate: tbx_01ktrayhbr7rszsded12tsmayw, provider blacksmith-testbox, passed
  • Post-Testbox rebase sanity: git diff --check; focused Vitest command above

@openclaw-barnacle openclaw-barnacle Bot added channel: telegram Channel integration: telegram size: XL maintainer Maintainer-authored PR labels Jun 10, 2026
@clawsweeper

clawsweeper Bot commented Jun 10, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Codex review: needs real behavior proof before merge. Reviewed June 10, 2026, 5:20 AM ET / 09:20 UTC.

Summary
The PR replaces Telegram message-dispatch replay dedupe with SDK claimable persistent dedupe, changes the persisted owner/key shape, and adds doctor-time migration support for legacy JSON and bucketed plugin-state entries.

PR surface: Source -240, Tests +56. Total -184 across 11 files.

Reproducibility: no. high-confidence reproduction path was established in this review. Source inspection shows the Telegram handler-to-dedupe path, but the PR body and available context do not include a live replay reproduction or after-fix transport proof.

Review metrics: 3 noteworthy metrics.

  • Public SDK exports: 1 runtime-doctor function export added. Doctor SDK is a plugin API and security boundary, so maintainers should explicitly approve any new unscoped state access before merge.
  • Migration contract fields: 1 optional defaultTtlMs field added. Doctor imports now carry TTL into plugin state, which affects upgrade behavior for existing persisted caches.
  • Replay state owner: 1 Telegram dedupe owner/namespace changed. Existing replay protection must migrate cleanly to avoid duplicate or suppressed Telegram dispatch after restart.

Merge readiness
Overall: 🧂 unranked krab
Proof: 🧂 unranked krab
Patch quality: 🧂 unranked krab
Result: blocked until 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:

  • Remove or replace the unscoped public runtime-doctor store export with a scoped/narrow migration path.
  • [P1] Add redacted real Telegram proof that a replayed update is deduped and a new message dispatches exactly once.

Proof guidance:

  • [P1] Needs real behavior proof before merge: The PR body has tests and Testbox only; the contributor should add redacted live Telegram transcript, recording, terminal output, or logs showing replay dedupe and normal dispatch, then update the PR body to trigger re-review or ask a maintainer to comment @clawsweeper re-review.

Mantis proof suggestion
A live Telegram transcript would materially prove the transport dedupe path beyond unit and migration tests. A maintainer can ask Mantis to capture proof by posting a new PR comment that starts with the OpenClaw Mantis account mention, followed by:

telegram live QA: verify replayed Telegram update is deduped and a new message still dispatches exactly once.

Risk before merge

  • [P1] The new public runtime-doctor export can let plugin doctor code open arbitrary non-core plugin-state owners instead of using a context-bound store tied to the active trusted plugin.
  • [P1] The Telegram replay-dedupe owner, namespace, key, and migration changes are upgrade-sensitive: a wrong import or namespace decision can duplicate or suppress Telegram dispatches after restart or replay.
  • [P1] The PR still lacks after-fix real Telegram behavior proof, so tests do not show that a replayed update is deduped while a normal new message still dispatches once.

Maintainer options:

  1. Keep state migration access scoped (recommended)
    Replace the public runtime-doctor store-factory export with a narrow internal/core migration helper or a context-bound API, then rerun SDK API checks and Telegram migration tests.
  2. Explicitly approve the broader SDK surface
    Maintainers can accept that plugin doctor code may open arbitrary non-core plugin state, but that should be an intentional documented contract before merge.
  3. Require live Telegram replay proof
    Keep this PR blocked until a redacted transcript, recording, terminal output, or logs prove replay dedupe and one normal dispatch against the current head.

Next step before merge

  • [P1] Human review is needed for the SDK/security-boundary decision and for the missing real Telegram proof; this is not a safe ClawSweeper repair lane.

Security
Needs attention: The diff introduces a concrete plugin-state boundary concern by exposing an arbitrary plugin-id store factory through a public doctor SDK subpath.

Review findings

  • [P1] Keep doctor state access bound to the active plugin — src/plugin-sdk/runtime-doctor.ts:26
Review details

Best possible solution:

Keep the SDK dedupe refactor only after plugin-state migration access remains bound or narrowly internal, upgrade migration semantics are verified, and redacted live Telegram replay proof shows normal delivery plus duplicate suppression.

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

No high-confidence reproduction path was established in this review. Source inspection shows the Telegram handler-to-dedupe path, but the PR body and available context do not include a live replay reproduction or after-fix transport proof.

Is this the best way to solve the issue?

No. Moving Telegram dispatch replay protection to the SDK dedupe helper is a plausible direction, but the unscoped public doctor store export is not the best boundary for migrating plugin state.

Full review comments:

  • [P1] Keep doctor state access bound to the active plugin — src/plugin-sdk/runtime-doctor.ts:26
    runtime-doctor is a public plugin SDK subpath, and the existing doctor migration context binds plugin-state access to the active pluginId. Exporting createPluginStateSyncKeyedStore here lets any plugin doctor code choose another non-core plugin id and read or write its state, so please keep this as an internal core migration helper or expose a context-bound/narrow migration API instead.
    Confidence: 0.86

Overall correctness: patch is incorrect
Overall confidence: 0.87

AGENTS.md: found and applied where relevant.

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

Label changes

Label justifications:

  • P1: Telegram replay dedupe sits on the transport delivery path, and mistakes can duplicate or suppress real user messages.
  • merge-risk: 🚨 compatibility: The PR changes a public SDK doctor surface and migrates existing Telegram replay-dedupe state into a new owner/namespace.
  • merge-risk: 🚨 message-delivery: Replay-dedupe key or migration mistakes can make Telegram messages dispatch twice or be incorrectly suppressed.
  • merge-risk: 🚨 security-boundary: The added runtime-doctor store export bypasses the existing runtime/plugin-bound state access boundary.
  • rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🧂 unranked krab.
  • 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 has tests and Testbox only; the contributor should add redacted live Telegram transcript, recording, terminal output, or logs showing replay dedupe and normal dispatch, then update the PR body to trigger re-review or ask a maintainer to comment @clawsweeper re-review.
  • mantis: telegram-visible-proof: Mantis should capture Telegram visible proof. This changes Telegram message dispatch replay behavior, which can be shown in a short Telegram proof as duplicate suppression plus normal delivery.
Evidence reviewed

PR surface:

Source -240, Tests +56. Total -184 across 11 files.

View PR surface stats
Area Files Added Removed Net
Source 7 334 574 -240
Tests 4 237 181 +56
Docs 0 0 0 0
Config 0 0 0 0
Generated 0 0 0 0
Other 0 0 0 0
Total 11 571 755 -184

Security concerns:

  • [medium] Unscoped plugin-state store in doctor SDK — src/plugin-sdk/runtime-doctor.ts:26
    The added export lets plugin doctor code open a sync keyed store for any non-core plugin id instead of using the context-bound store that core creates for the active plugin, which can cross plugin state ownership boundaries.
    Confidence: 0.86

What I checked:

Likely related people:

  • vincentkoc: Recent history shows Vincent Koc introduced and fixed the claimable persistent dedupe helper this PR now relies on, and has multiple recent Telegram callback/runtime fixes. (role: persistent dedupe and Telegram adjacent contributor; confidence: high; commits: 028434a00ffd, 6c12ec1ed22c, 77f1ea0de813; files: src/plugin-sdk/persistent-dedupe.ts, extensions/telegram/src/bot-handlers.runtime.ts)
  • steipete: History on runtime-doctor, state migrations, and plugin SDK boundary refactors repeatedly points to Peter Steinberger as a central contributor for this API boundary. (role: SDK and doctor migration boundary owner by history; confidence: high; commits: 62ddc9d9e0d9, 40ffada812b9, 44e7c1142e60; files: src/plugin-sdk/runtime-doctor.ts, src/infra/state-migrations.ts, src/plugins/doctor-contract-registry.ts)
  • obviyus: The PR author also appears in current-main history for recent Telegram callback and handler-seam work, so this is an adjacent ownership signal beyond merely opening this PR. (role: recent Telegram area contributor; confidence: medium; commits: 1265da2a5cae, 049c3c487789, edcf3e9d32d3; files: extensions/telegram/src/bot-handlers.runtime.ts, extensions/telegram/src/message-dispatch-dedupe.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 rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action. P1 High-priority user-facing bug, regression, or broken workflow. merge-risk: 🚨 compatibility 🚨 May break existing users, config, migrations, defaults, or upgrade paths. merge-risk: 🚨 message-delivery 🚨 May drop, duplicate, misroute, suppress, or wrongly target messages. merge-risk: 🚨 security-boundary 🚨 May affect sandboxing, authorization, credentials, or sensitive data. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. mantis: telegram-visible-proof Mantis should capture Telegram visible proof. and removed status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action. labels Jun 10, 2026
@obviyus obviyus force-pushed the codex/telegram-sdk-dispatch-dedupe branch from eef3878 to fa61b16 Compare June 10, 2026 09:12
@obviyus obviyus force-pushed the codex/telegram-sdk-dispatch-dedupe branch from fa61b16 to 40231a3 Compare June 10, 2026 09:22
@obviyus obviyus merged commit 9c6186d into main Jun 10, 2026
8 checks passed
@obviyus obviyus deleted the codex/telegram-sdk-dispatch-dedupe branch June 10, 2026 09:22
@obviyus

obviyus commented Jun 10, 2026

Copy link
Copy Markdown
Contributor Author

Landed via rebase onto main.

  • Scoped tests: pnpm plugin-sdk:api:check; node scripts/run-vitest.mjs src/plugin-sdk/memory-host-events.test.ts extensions/telegram/src/state-migrations.test.ts extensions/telegram/src/message-dispatch-dedupe.test.ts extensions/telegram/src/bot.create-telegram-bot.test.ts src/plugin-sdk/api-baseline.test.ts src/commands/doctor-state-migrations.test.ts; .agents/skills/autoreview/scripts/autoreview --mode branch --base origin/main; Testbox changed gate tbx_01ktrayhbr7rszsded12tsmayw passed on blacksmith-testbox.
  • Changelog: not updated; release generation owns CHANGELOG.md for normal PRs.
  • Unrelated CI: build-artifacts / core-support-boundary failed in test/scripts/check-deadcode-unused-files.test.ts; same failure reproduced on clean origin/main.
  • Land commit: 40231a3d2c
  • Merge commit: 9c6186de436c6d4e5bd2e257b5e05a32b7b0be25

@obviyus obviyus mentioned this pull request Jun 10, 2026
Merged
@clawsweeper clawsweeper Bot mentioned this pull request Jun 10, 2026
Open
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: telegram Channel integration: telegram maintainer Maintainer-authored PR mantis: telegram-visible-proof Mantis should capture Telegram visible proof. merge-risk: 🚨 compatibility 🚨 May break existing users, config, migrations, defaults, or upgrade paths. merge-risk: 🚨 message-delivery 🚨 May drop, duplicate, misroute, suppress, or wrongly target messages. merge-risk: 🚨 security-boundary 🚨 May affect sandboxing, authorization, credentials, or sensitive data. P1 High-priority user-facing bug, regression, or broken workflow. rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. size: XL status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@obviyus