fix(telegram): audit follow-ups — block-mode chunk config, dedupe bucket cleanup, grammy contract trust by obviyus · Pull Request #91915 · openclaw/openclaw

obviyus · 2026-06-10T10:14:42Z

Summary

Follow-ups from the telegram audit series (#91871, #91874, #91876, #91904):

Wire streaming.preview.chunk into telegram block mode. channels.telegram.streaming.preview.chunk.maxChars now sizes preview rotation steps when streaming.mode: "block", matching how Discord consults the chunk config only for its block chunker. Other modes keep one growing preview at Telegram's 4096 edit cap, so default (partial) behavior is unchanged. Behavior note: block mode without explicit config moves from 4096 to the shared 800-char default, aligning telegram with Discord/SDK block chunk sizing. Doctor already migrates legacy draftChunk keys into this config for telegram, so it is no longer a silent no-op.
Delete retired dispatch dedupe buckets after doctor import. Adds an optional removeSource hook to plugin-state-import migration plans (invoked only once every legacy entry is covered) and telegram now deletes the retired telegram.message-dispatch-dedupe bucket rows, including :lock rows, after importing into the SDK dedupe namespace from fix(telegram): use SDK dispatch dedupe #91904. The plan keeps emitting while any legacy rows remain (even TTL-expired), so previously-imported installs get swept on their next doctor --fix, after which detection goes quiet. This also deletes the hasCurrentMessageDispatchDedupeTargets gate.
Trust grammy's API contract in handler seams. buildSyntheticContext requires getFile (drops the async () => ({}) fallback) and getChat binds bot.api.getChat directly — grammy's Api declares it concretely. Removes the NO_REPLY pre-count debug block in delivery (the SDK payload projection already normalizes NO_REPLY).

Verification

Regression proof — the new tests fail on main's production code and pass with this branch:

sizes block-mode preview chunks from streaming.preview.chunk ✗ on main (got 4096, config ignored) → ✓
uses the shared block chunk default when block mode has no chunk config ✗ on main → ✓
removes plugin-state legacy sources through removeSource once covered ✗ on main (hook missing) → ✓
migrates shipped Telegram message dispatch plugin-state buckets lifecycle ✗ on main (legacy rows linger, plan never re-emitted for cleanup) → ✓

Local (worktree, node scripts/run-vitest.mjs): bot-message-dispatch (124), state-migrations (8), doctor-state-migrations (46), bot.test (147), bot/delivery + helpers + media-dedup suites — all green.

Remote: blacksmith testbox run --id tbx_01ktrf67rfpa02v4xd82bjv7jv → pnpm check:changed green (tsgo core/test/extensions lanes, oxlint, import cycles, guards). An earlier run caught a Pick<TelegramContext, ...> mismatch at bot-handlers.runtime.ts:473; fixed by tightening buildCallbackSyntheticTextContext and re-run green.

Not tested: live Telegram block-mode streaming against a real bot.

….chunk

…port

clawsweeper · 2026-06-10T10:17:15Z

Codex review: needs real behavior proof before merge. Reviewed June 10, 2026, 6:24 AM ET / 10:24 UTC.

Summary
The branch wires Telegram block-mode preview sizing to streaming.preview.chunk, adds a doctor cleanup hook for legacy plugin-state dedupe buckets, removes grammy duck-typing fallbacks, and documents the Telegram block-mode behavior.

PR surface: Source -10, Tests +130, Docs +1. Total +121 across 10 files.

Reproducibility: yes. Current main hard-caps Telegram draft previews at 4096 characters, so block mode ignores streaming.preview.chunk; I confirmed the source path and the PR adds focused before/after tests, though I did not run them.

Review metrics: 2 noteworthy metrics.

Telegram block-mode default: 1 default changed: 4096 cap to 800 shared maxChars when no chunk config is set. Existing Telegram block-mode users may see more preview rotations after upgrade.
Plugin SDK contract surface: 1 optional migration-plan hook added. The exported channel-contract type change needs baseline and compatibility review before merge.

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

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

Rank-up moves:

Commit the regenerated Plugin SDK API baseline hash for the new channel-contract type field.
[P1] Add live Telegram proof for block-mode preview chunk sizing and final delivery, with private details redacted.

Proof guidance:

[P1] Needs real behavior proof before merge: The PR provides focused tests and a remote changed gate, but no live Telegram proof; the body explicitly says live Telegram block-mode streaming was not tested. 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.

Mantis proof suggestion
A native Telegram Desktop recording would directly show whether block-mode preview rotation honors streaming.preview.chunk.maxChars and still finalizes cleanly. 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 desktop proof: verify Telegram block-mode preview rotation honors streaming.preview.chunk.maxChars and final delivery remains one coherent answer.

Risk before merge

[P1] Telegram block mode without explicit chunk config intentionally changes from one growing 4096-character preview to the shared 800-character preview rotation default, which is user-visible for existing block-mode users.
[P1] No real Telegram proof is included; the PR body explicitly says live Telegram block-mode streaming was not tested.
[P1] The PR changes an exported Plugin SDK channel-contract type without updating the tracked SDK API baseline hash.

Maintainer options:

Refresh contract artifact and prove Telegram live (recommended)
Regenerate the Plugin SDK API baseline and add a live Telegram block-mode proof showing chunk sizing and final delivery before merge.
Accept the block-mode default change
Maintainers can intentionally accept the 4096-to-800 default behavior change, but should make that upgrade impact explicit before landing.
Pause if the default is not settled
If maintainers are not ready to change existing block-mode preview cadence, hold this PR and split the doctor cleanup from the streaming behavior.

Next step before merge

[P1] Protected-label handling and live Telegram proof require maintainer/contributor action; the SDK baseline repair is mechanical but not enough to make automation merge this PR.

Security
Cleared: The diff does not add dependencies, secret handling, workflow permissions, downloads, or new code-execution paths; the state cleanup is doctor-time only.

Review findings

[P2] Regenerate the SDK API baseline — src/channels/plugins/legacy-state-migration.types.ts:22

Review details

Best possible solution:

Update the SDK API baseline, then land only after maintainers accept the block-mode default change and there is live Telegram proof for the visible streaming path.

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

Yes. Current main hard-caps Telegram draft previews at 4096 characters, so block mode ignores streaming.preview.chunk; I confirmed the source path and the PR adds focused before/after tests, though I did not run them.

Is this the best way to solve the issue?

Mostly yes. The fix stays in the Telegram plugin and doctor migration boundaries and the grammy simplification matches the pinned dependency types, but the PR must refresh SDK baseline artifacts and add live Telegram proof before it is the best mergeable form.

Full review comments:

[P2] Regenerate the SDK API baseline — src/channels/plugins/legacy-state-migration.types.ts:22
Adding removeSource changes ChannelLegacyStateMigrationPlan, which is exported through openclaw/plugin-sdk/channel-contract, but the tracked docs/.generated/plugin-sdk-api-baseline.sha256 is unchanged between base and this head. The plugin SDK API check hashes exported type aliases, so this public contract addition needs the generated baseline hash committed before the PR can pass the SDK surface guard.
Confidence: 0.86

Overall correctness: patch is incorrect
Overall confidence: 0.82

AGENTS.md: found and applied where relevant.

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

Label changes

Label changes:

add P2: This is a normal-priority Telegram bugfix/cleanup PR with limited blast radius but real merge gates.
add merge-risk: 🚨 compatibility: The PR changes existing Telegram block-mode default preview sizing and adds an exported SDK type field.
add merge-risk: 🚨 message-delivery: The Telegram preview rotation change affects visible message delivery cadence in block-mode chats.
add merge-risk: 🚨 automation: The public SDK type changes without the tracked API baseline hash update required by repository automation.
add rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🦐 gold shrimp.
add status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: The PR provides focused tests and a remote changed gate, but no live Telegram proof; the body explicitly says live Telegram block-mode streaming was not tested. 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.
add mantis: telegram-visible-proof: Mantis should capture Telegram visible proof. The PR changes visible Telegram block-mode preview rotation behavior that can be demonstrated in a short Telegram Desktop proof.

Label justifications:

P2: This is a normal-priority Telegram bugfix/cleanup PR with limited blast radius but real merge gates.
merge-risk: 🚨 compatibility: The PR changes existing Telegram block-mode default preview sizing and adds an exported SDK type field.
merge-risk: 🚨 message-delivery: The Telegram preview rotation change affects visible message delivery cadence in block-mode chats.
merge-risk: 🚨 automation: The public SDK type changes without the tracked API baseline hash update required by repository automation.
rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🦐 gold shrimp.
status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: The PR provides focused tests and a remote changed gate, but no live Telegram proof; the body explicitly says live Telegram block-mode streaming was not tested. 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.
mantis: telegram-visible-proof: Mantis should capture Telegram visible proof. The PR changes visible Telegram block-mode preview rotation behavior that can be demonstrated in a short Telegram Desktop proof.

Evidence reviewed

PR surface:

Source -10, Tests +130, Docs +1. Total +121 across 10 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	6	67	77	-10
Tests	3	130	0	+130
Docs	1	1	0	+1
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	10	198	77	+121

What I checked:

Protected label: Provided GitHub context lists the protected maintainer label, so this cleanup review must keep the PR open for explicit maintainer handling.
Current main ignores block chunk config: On current main, Telegram draft preview size is still Math.min(textLimit, 4096), so block mode cannot use streaming.preview.chunk.maxChars. (extensions/telegram/src/bot-message-dispatch.ts:827, c84e52192063)
PR implements block chunk sizing: The PR head switches block-mode draft sizing to resolveTelegramDraftStreamingChunking(...).maxChars while keeping non-block previews at the Telegram edit cap. (extensions/telegram/src/bot-message-dispatch.ts:832, 974490cf095e)
Doctor cleanup hook added: The PR adds removeSource execution after plugin-state import entries are covered, which matches the doctor-time migration boundary. (src/infra/state-migrations.ts:1715, 974490cf095e)
Public SDK type surface changed: ChannelLegacyStateMigrationPlan gains an optional removeSource hook and is re-exported from openclaw/plugin-sdk/channel-contract. (src/channels/plugins/legacy-state-migration.types.ts:22, 974490cf095e)
SDK baseline not refreshed: The tracked docs/.generated/plugin-sdk-api-baseline.sha256 is identical on base and PR head despite the public SDK type addition. Public docs: docs/.generated/plugin-sdk-api-baseline.sha256. (docs/.generated/plugin-sdk-api-baseline.sha256:1, 974490cf095e)

Likely related people:

obviyus: Provided related PR context shows obviyus authored the recently merged Telegram audit/dedupe/chunking PRs that this follow-up builds on. (role: recent Telegram audit contributor; confidence: high; commits: b9095bf70d81, 049c3c487789, 9c6186de436c; files: extensions/telegram/src/bot-message-dispatch.ts, extensions/telegram/src/state-migrations.ts, extensions/telegram/src/bot-handlers.runtime.ts)
Vincent Koc: Local history shows recent work on the shared state migration runner touched by this PR. (role: recent adjacent state migration contributor; confidence: medium; commits: 7f1d82ab2518; files: src/infra/state-migrations.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.

obviyus · 2026-06-10T11:00:10Z

Land verification:

Local: node scripts/run-vitest.mjs over bot-message-dispatch (124), state-migrations (8), doctor-state-migrations (46), bot.test (147), bot/delivery (229 incl. shared files), media-dedup + bot/helpers (91) — green.
Regression proof: the four new tests fail with main's production files swapped in (config ignored at 4096; removeSource never invoked; legacy buckets linger) and pass on this branch.
Remote: Blacksmith Testbox tbx_01ktrf67rfpa02v4xd82bjv7jv, pnpm check:changed green (tsgo core/test/extensions, oxlint, import cycles, guards). First run caught a Pick<TelegramContext> mismatch at bot-handlers.runtime.ts:473; fixed and re-run green.

Known failing checks, both dispositioned:

build-artifacts: test/scripts/check-deadcode-unused-files.test.ts › "falls back to bare pnpm when no managed pnpm runner is available" fails identically on plain latest origin/main (reproduced locally on an untouched main checkout) — pre-existing main breakage, unrelated to this diff.
Run agentic native Telegram proof: Mantis reports both baseline and candidate captures skipped ("capture path cannot start Telegram in block preview mode"), artifacts: [] — no comparison was performed; harness capability gap, not a behavior mismatch. Behavior is covered by the regression tests above.

Proof gap: no live Telegram block-mode streaming session against a real bot.

…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. ([#91529](openclaw/openclaw#91529), [#91618](openclaw/openclaw#91618), [#91615](openclaw/openclaw#91615), [#91619](openclaw/openclaw#91619), [#91741](openclaw/openclaw#91741), [#91745](openclaw/openclaw#91745), [#91746](openclaw/openclaw#91746), [#91748](openclaw/openclaw#91748), [#91749](openclaw/openclaw#91749), [#91750](openclaw/openclaw#91750), [#91751](openclaw/openclaw#91751), [#91752](openclaw/openclaw#91752), [#91763](openclaw/openclaw#91763), [#89938](openclaw/openclaw#89938)) Thanks [@joshavant](https://github.com/joshavant), [@pgondhi987](https://github.com/pgondhi987), [@mmaps](https://github.com/mmaps), [@eleqtrizit](https://github.com/eleqtrizit), [@shakkernerd](https://github.com/shakkernerd), and [@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. ([#91189](openclaw/openclaw#91189), [#88682](openclaw/openclaw#88682), [#89588](openclaw/openclaw#89588), [#90212](openclaw/openclaw#90212), [#91876](openclaw/openclaw#91876), [#91874](openclaw/openclaw#91874), [#91904](openclaw/openclaw#91904), [#91478](openclaw/openclaw#91478), [#91915](openclaw/openclaw#91915)) Thanks [@codysai001](https://github.com/codysai001), [@alexzhu0](https://github.com/alexzhu0), [@joelnishanth](https://github.com/joelnishanth), [@snowzlm](https://github.com/snowzlm), [@obviyus](https://github.com/obviyus), and [@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. ([#91335](openclaw/openclaw#91335), [#91449](openclaw/openclaw#91449), [#88969](openclaw/openclaw#88969), [#88530](openclaw/openclaw#88530), [#91783](openclaw/openclaw#91783), [#91785](openclaw/openclaw#91785)) Thanks [@omarshahine](https://github.com/omarshahine), [@jmissig](https://github.com/jmissig), and [@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. ([#91422](openclaw/openclaw#91422), [#89851](openclaw/openclaw#89851), [#91736](openclaw/openclaw#91736), [#91747](openclaw/openclaw#91747), [#91451](openclaw/openclaw#91451), [#80143](openclaw/openclaw#80143)) Thanks [@pgondhi987](https://github.com/pgondhi987), [@anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia), [@lifuyue](https://github.com/lifuyue), [@eleqtrizit](https://github.com/eleqtrizit), [@LiuwqGit](https://github.com/LiuwqGit), and [@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. ([#91531](openclaw/openclaw#91531), [#91538](openclaw/openclaw#91538), [#91568](openclaw/openclaw#91568), [#91583](openclaw/openclaw#91583), [#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. ([#91830](openclaw/openclaw#91830), [#91882](openclaw/openclaw#91882), [#91590](openclaw/openclaw#91590), [#88630](openclaw/openclaw#88630), [#88768](openclaw/openclaw#88768), [#91696](openclaw/openclaw#91696)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@joshavant](https://github.com/joshavant), [@bdjben](https://github.com/bdjben), and [@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. ([#89834](openclaw/openclaw#89834), [#90883](openclaw/openclaw#90883)) Thanks [@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. ([#91256](openclaw/openclaw#91256), [#91568](openclaw/openclaw#91568), [#91583](openclaw/openclaw#91583)) Thanks [@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. ([#91574](openclaw/openclaw#91574), [#91591](openclaw/openclaw#91591), [#90004](openclaw/openclaw#90004), [#90927](openclaw/openclaw#90927), [#90838](openclaw/openclaw#90838)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@brokemac79](https://github.com/brokemac79), and [@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. ([#91324](openclaw/openclaw#91324), [#89138](openclaw/openclaw#89138), [#90457](openclaw/openclaw#90457), [#91837](openclaw/openclaw#91837), [#91851](openclaw/openclaw#91851)) Thanks [@osolmaz](https://github.com/osolmaz), [@mushuiyu886](https://github.com/mushuiyu886), [@ai-hpc](https://github.com/ai-hpc), and [@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. ([#91423](openclaw/openclaw#91423), [#91557](openclaw/openclaw#91557), [#89909](openclaw/openclaw#89909)) Thanks [@cxyhhhhh](https://github.com/cxyhhhhh), [@Solvely-Colin](https://github.com/Solvely-Colin), and [@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. ([#90782](openclaw/openclaw#90782), [#89978](openclaw/openclaw#89978), [#91580](openclaw/openclaw#91580), [#91531](openclaw/openclaw#91531)) Thanks [@RomneyDa](https://github.com/RomneyDa) and [@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. ([#85679](openclaw/openclaw#85679), [#91450](openclaw/openclaw#91450), [#91566](openclaw/openclaw#91566), [#91840](openclaw/openclaw#91840), [#91590](openclaw/openclaw#91590), [#91361](openclaw/openclaw#91361), [#91895](openclaw/openclaw#91895)) Thanks [@openperf](https://github.com/openperf), [@yetval](https://github.com/yetval), [@joshavant](https://github.com/joshavant), [@wangmiao0668000666](https://github.com/wangmiao0668000666), and [@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. ([#89151](openclaw/openclaw#89151), [#91422](openclaw/openclaw#91422), [#91425](openclaw/openclaw#91425), [#91529](openclaw/openclaw#91529), [#90212](openclaw/openclaw#90212)) Thanks [@joelnishanth](https://github.com/joelnishanth), [@pgondhi987](https://github.com/pgondhi987), [@joshavant](https://github.com/joshavant), and [@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. ([#85823](openclaw/openclaw#85823), [#89659](openclaw/openclaw#89659), [#91684](openclaw/openclaw#91684), [#91649](openclaw/openclaw#91649), [#90263](openclaw/openclaw#90263), [#91686](openclaw/openclaw#91686), [#90426](openclaw/openclaw#90426)) Thanks [@itsuzef](https://github.com/itsuzef), [@ladygege](https://github.com/ladygege), [@jacobtomlinson](https://github.com/jacobtomlinson), [@fuller-stack-dev](https://github.com/fuller-stack-dev), and [@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. ([#90666](openclaw/openclaw#90666), [#90678](openclaw/openclaw#90678)) Thanks [@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. ([#87105](openclaw/openclaw#87105), [#91551](openclaw/openclaw#91551), [#91219](openclaw/openclaw#91219), [#91614](openclaw/openclaw#91614), [#91740](openclaw/openclaw#91740), [#91978](openclaw/openclaw#91978)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev) and [@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. ([#91390](openclaw/openclaw#91390), [#91709](openclaw/openclaw#91709), [#91507](openclaw/openclaw#91507), [#91567](openclaw/openclaw#91567), [#88630](openclaw/openclaw#88630), [#91696](openclaw/openclaw#91696)) Thanks [@hxy91819](https://github.com/hxy91819), [@brokemac79](https://github.com/brokemac79), [@RomneyDa](https://github.com/RomneyDa), [@joshavant](https://github.com/joshavant), and [@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. ([#91581](openclaw/openclaw#91581), [#91599](openclaw/openclaw#91599), [#91547](openclaw/openclaw#91547), [#91591](openclaw/openclaw#91591)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev), [@sallyom](https://github.com/sallyom), and [@Patrick-Erichsen](https://github.com/Patrick-Erichsen). - UI: require explicit user intent before opening chat sessions and drain restored chat queues after session switches. ([#91480](openclaw/openclaw#91480)) Thanks [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Android: avoid the `dataSync` foreground-service type for persistent nodes. ([#80082](openclaw/openclaw#80082)) Thanks [@davelutztx](https://github.com/davelutztx). - Native hooks: bound relay lifetimes so abandoned native hook connections cannot linger indefinitely. ([#91550](openclaw/openclaw#91550)) Thanks [@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. --- - [ ] 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/1040

obviyus added 5 commits June 10, 2026 15:27

feat(telegram): size block-mode preview chunks from streaming.preview…

ff84665

….chunk

fix(telegram): delete retired dispatch dedupe buckets after doctor im…

6db62c3

…port

refactor(telegram): trust grammy api contract in handler seams

60b09c9

refactor(telegram): drop NO_REPLY precount debug logging

a78315b

docs(streaming): document Telegram block-mode preview chunk sizing

974490c

openclaw-barnacle Bot added docs Improvements or additions to documentation channel: telegram Channel integration: telegram commands Command implementations size: M maintainer Maintainer-authored PR labels Jun 10, 2026

clawsweeper Bot had a problem deploying to qa-live-shared June 10, 2026 10:26 Failure

obviyus self-assigned this Jun 10, 2026

obviyus merged commit 050c081 into main Jun 10, 2026
243 of 256 checks passed

obviyus deleted the codex/telegram-audit-followups branch June 10, 2026 11:00

clawsweeper Bot mentioned this pull request Jun 10, 2026

fix: add clear separator between metadata and user message #41299

Open

15 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(telegram): audit follow-ups — block-mode chunk config, dedupe bucket cleanup, grammy contract trust#91915

fix(telegram): audit follow-ups — block-mode chunk config, dedupe bucket cleanup, grammy contract trust#91915
obviyus merged 5 commits into
mainfrom
codex/telegram-audit-followups

obviyus commented Jun 10, 2026

Uh oh!

clawsweeper Bot commented Jun 10, 2026 •

edited

Loading

Uh oh!

obviyus commented Jun 10, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

obviyus commented Jun 10, 2026

Summary

Verification

Uh oh!

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

Uh oh!

Uh oh!

obviyus commented Jun 10, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

clawsweeper Bot commented Jun 10, 2026 •

edited

Loading