fix(telegram): materialize streaming progress placeholders by snowzlmbot · Pull Request #95183 · openclaw/openclaw

snowzlmbot · 2026-06-20T02:18:51Z

What Problem This Solves

Telegram preview streaming had two source-proven silent paths that made Telegram feel stuck even while upstream/Web draft state existed:

short first previews below minInitialChars could remain unsent for the whole active turn;
progress mode dropped answer-lane partial activity when no tool/progress row existed yet, so Telegram could stay silent while Web had upstream draft/progress state.

This PR keeps Telegram's existing one-preview/no-spam policy, but makes the silence bounded and predictable.

Related Work / Scope Boundary

Related: #82303 (feat(telegram): add progress assistant preview lane).

This PR and #82303 both address Telegram feeling silent while upstream answer activity exists in progress-style streaming, but they intentionally choose different product shapes:

feat(telegram): add progress assistant preview lane #82303 adds an opt-in streaming.progress.assistantPreview path that keeps the existing progress/tool draft and streams assistant partials on a separate transient assistant preview lane.
This PR keeps the existing default Telegram progress semantics narrower: it only materializes a stable label-only progress placeholder when answer activity would otherwise be invisible, and it does not stream assistant answer text into the progress draft.
This PR also separately bounds short first-preview silence for non-progress answer previews via minInitialDelayMs.

So #95183 is not a duplicate of #82303. It can coexist as the lower-risk default-silence fix, while #82303 remains the fuller opt-in two-lane assistant-preview feature if maintainers want that product behavior.

Summary

Add minInitialDelayMs to Telegram draft streams:
- short first previews still respect the initial debounce;
- if the turn remains active past the bounded delay, the same preview materializes instead of staying invisible forever;
- finals and threshold-reaching previews clear the delayed timer normally.
Add a shared progress-draft noteActivity() hook:
- progress mode can show the stable status label when upstream answer activity exists but no tool/progress row is available yet;
- answer text is still not leaked into the progress draft in progress mode.
Wire Telegram dispatch to use a 5s delayed materialization window for non-progress answer previews.
Update Telegram/streaming docs to describe the bounded short-preview behavior and progress-label placeholder.

Product decision encoded

Issue #95004 was tagged for maintainer/product choice because the existing first-preview debounce is intentional. This PR chooses the least noisy fix shape:

keep the debounce for push-notification UX;
keep one visible Telegram preview message;
avoid token/delta spam;
only materialize a stable placeholder/preview when upstream activity remains active long enough to otherwise look stuck.

Latest timer cleanup fix evidence

Latest head: 1ab0ba3ae113761e8875f75eb5c644da1ce73adf.

This update addresses the ClawSweeper P2 finding that createTelegramDraftStream.clear() did not cancel a delayed first-preview timer. The fix calls clearInitialPreviewTimer() in clear() before stopping/removing the draft, and adds a fake-timer regression covering: below-threshold pending preview → clear() → timer count drops to zero → advancing the old delay does not send or edit a Telegram draft.

Validation run on the updated head:

git diff --check origin/main...HEAD
node scripts/run-vitest.mjs \
  extensions/telegram/src/draft-stream.test.ts \
  extensions/telegram/src/bot-message-dispatch.test.ts \
  src/channels/progress-draft-compositor.test.ts

Result: 193 targeted tests passed (draft-stream 48, bot-message-dispatch 130, progress-draft-compositor 15).

Live Telegram Bot API timer cleanup proof

A real Telegram Bot API proof was run with the configured test bot token against a private proof chat. Token and chat identifiers are redacted in the captured evidence.

Scenario:

Create a Telegram draft stream with minInitialChars: 80 and minInitialDelayMs: 1200.
Send a below-threshold first preview (Proof <label>), then flush once so the delayed first-preview timer is scheduled.
Call clear() before the delay elapses.
Wait beyond the original delay window and record Bot API calls plus runtime timer events.

Before/after evidence:

#95183 before fix (70c0948...)
- after flush: active delayed timers = 1
- after clear(): active delayed timers = 1
- after 1200ms: timer fired after clear = true
- Telegram send/edit/delete calls after clear: 0/0/0

#95183 after fix (1ab0ba3...)
- after flush: active delayed timers = 1
- clear() called clearTimeout(timerId=1)
- after clear(): active delayed timers = 0
- after 1200ms: timer fired after clear = false
- Telegram send/edit/delete calls after clear: 0/0/0

#95522 before fix (3296107...)
- after flush: active delayed timers = 1
- after clear(): active delayed timers = 1
- after 1200ms: timer fired after clear = true
- Telegram send/edit/delete calls after clear: 0/0/0

#95522 after fix (ae1b0bd...)
- after flush: active delayed timers = 1
- clear() called clearTimeout(timerId=1)
- after clear(): active delayed timers = 0
- after 1200ms: timer fired after clear = false
- Telegram send/edit/delete calls after clear: 0/0/0

Observed result: before the fix, clear() removed the visible draft state but left the delayed first-preview timer alive until it fired after cleanup. After the fix, clear() cancels the pending timer immediately, so no delayed flush runs after draft cleanup. The live Bot API run also confirms that the cleanup scenario does not leave a stray Telegram message after the fix.

Evidence

Local verification on this branch:

node scripts/run-vitest.mjs run --config test/vitest/vitest.extension-telegram.config.ts telegram/src/draft-stream.test.ts telegram/src/bot-message-dispatch.test.ts
# 177 passed

node scripts/run-vitest.mjs run src/channels/progress-draft-compositor.test.ts
# 15 passed

pnpm docs:list
# passed

pnpm tsgo:extensions
# passed

pnpm tsgo:core
# passed

git diff --check
# passed

Targeted source-level proof added:

draft-stream.test.ts now proves a short first preview is initially held, then materialized after the configured delay.
progress-draft-compositor.test.ts now proves upstream activity can materialize a label-only progress draft after the delay or repeated activity.
progress-draft-compositor.test.ts also proves pending delayed answer activity is cancelled when final delivery starts or lands, preventing stale progress placeholders after final delivery.
bot-message-dispatch.test.ts now proves Telegram progress mode shows a stable status placeholder for answer activity without streaming answer text into that draft.

Follow-up verification after addressing ClawSweeper's delayed-final guard finding at d2687eaed7:

node scripts/run-vitest.mjs src/channels/progress-draft-compositor.test.ts
# 15 passed

node scripts/run-vitest.mjs extensions/telegram/src/bot-message-dispatch.test.ts
# 130 passed

git diff --check
# passed

CI status after initial PR creation:

Some repository workflows started and reported unrelated GitHub API installation rate-limit failures while listing PR files or comparing refs (x-ratelimit-remaining: 0). These are infrastructure/rate-limit failures, not code/test failures from this PR.
The Real behavior proof workflow initially failed because external PRs require explicit authored What Problem This Solves and Evidence sections. This body now includes those sections.

Native Telegram Bot API proof

A dedicated Telegram test bot was used for native Bot API proof. Sensitive values are intentionally not included: the bot token is omitted and the private test chat id is redacted.

Dedicated test bot: @snowzlmOpenClawtestBot (8602965171)
Chat: redacted private test chat
Token: not included
Generated at: 2026-06-20T06:22:49.182Z

Scenarios verified:

PR fix(telegram): render progress draft rows as plain readable text #95007 — progress draft rows are visible as readable Telegram text.
- Operation: sendMessage + editMessageText with Telegram HTML parse mode.
- Message id: 4
- Before: Shelling
- After: Shelling plus compact exec running ... and exec passed ... rows.
- Checks: Bot API accepted the HTML payload; no [object Object] or raw object dump; rows are readable as plain text in the Telegram message.
PR fix(telegram): materialize streaming progress placeholders #95183 — short first preview is bounded, not indefinitely silent.
- Operation: delayed sendMessage after an intentional initial quiet window.
- Message id: 5
- minInitialChars: 30
- Proof delay: 1201ms
- Text: Short
- Checks: initially quiet; then materialized despite being below threshold.
PR fix(telegram): materialize streaming progress placeholders #95183 — progress mode can show a stable label placeholder before final delivery.
- Operation: placeholder sendMessage, followed by normal final sendMessage.
- Placeholder message id: 6
- Final message id: 7
- Checks: placeholder visible as Shelling; final delivery is separate and normal; answer text is not leaked into the placeholder.

Local sanitized artifact retained in the maintenance workspace: projects/openclaw-pr-maintenance/proofs/telegram-real/telegram-proof-1781936573613.public.md.

Telegram draft lifecycle proof

Additional native Bot API lifecycle proof was captured to address draft-message count and cleanup behavior:

Dedicated test bot: @snowzlmOpenClawtestBot (8602965171)
Chat/token: redacted
Local sanitized artifact: projects/openclaw-pr-maintenance/proofs/telegram-real/telegram-proof-draft-lifecycle-1781937832925.public.md

Verified scenarios:

Progress draft lifecycle, covering fix(telegram): render progress draft rows as plain readable text #95007 and fix(telegram): materialize streaming progress placeholders #95183:
- Operations: sendMessage(draft) → editMessageText(same draft id) → editMessageText(same draft id) → sendMessage(final) → deleteMessage(draft).
- Checks: both draft edits reused the initial draft message id; the final answer was delivered as a separate normal message; deleteMessage for the draft returned success.
Short-preview lifecycle, covering fix(telegram): materialize streaming progress placeholders #95183:
- Operations: sendMessage(short preview) → editMessageText(same id update) → editMessageText(same id final).
- Checks: the short preview, later update, and final text all used the same Telegram message id, so the bounded short preview does not create multiple default draft messages.

snowzlmbot · 2026-06-20T02:19:40Z

Ready for review.

@clawsweeper review-pr

clawsweeper · 2026-06-20T02:19:43Z

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

clawsweeper · 2026-06-20T02:20:17Z

Codex review: needs maintainer review before merge. Reviewed June 21, 2026, 7:38 AM ET / 11:38 UTC.

Summary
The branch adds bounded short-preview materialization, a progress-mode label placeholder for suppressed answer activity, cleanup guards, docs, and regression tests for Telegram streaming drafts.

PR surface: Source +72, Tests +121, Docs +2. Total +195 across 8 files.

Reproducibility: yes. The linked issue and current-main source show below-threshold first previews and progress-mode answer partials can remain invisible, and this PR adds tests plus live Bot API proof for the changed paths.

Review metrics: 1 noteworthy metric.

Default Telegram visible paths: 2 changed. The PR changes default behavior for short first previews and progress-mode answer activity, which maintainers should consciously accept before merge.

Root-cause cluster
Relationship: fixed_by_candidate
Canonical: #95004
Summary: The current PR is a candidate fix for the canonical Telegram streaming visibility issue; related PRs overlap but differ in scope and product shape.

Members:

canonical: issue(telegram): preview streaming can suppress drafts that Web already shows #95004 - The PR body uses closing syntax for this open issue and implements the two source-proven silent paths described there.
same_root_cause: feat(telegram): unify progress fallback with assistant preview lane #95522 - This open combined proposal addresses the same issue while adding the optional assistant-preview lane.
partial_overlap: feat(telegram): add progress assistant preview lane #82303 - This open PR addresses assistant partial previews in progress mode but does not cover the short first-preview default materialization path.
adjacent_distinct: fix(telegram): render progress draft rows as plain readable text #95007 - This open PR changes progress draft formatting and shares proof context, but it explicitly does not change draft materialization policy.
partial_overlap: Show Telegram progress placeholder when progress-mode answer drafts are suppressed #95344 - This closed unmerged PR addressed only the progress-placeholder half of the same issue.

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Merge readiness
Overall: 🐚 platinum hermit
Proof: 🦞 diamond lobster
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] Rebase or otherwise refresh exact-head CI so check-test-types runs with the current main script declaration fix.
[P2] Have a maintainer choose this narrow default fix versus the combined candidate at feat(telegram): unify progress fallback with assistant preview lane #95522.

Mantis proof suggestion
Native Telegram Desktop proof would materially show the user-visible placeholder timing and message cleanup behavior even though Bot API logs are already sufficient contributor proof. A maintainer can ask Mantis to capture proof by posting this exact PR comment:

@openclaw-mantis telegram desktop proof: verify short Telegram previews materialize after the bounded delay, progress mode shows the label placeholder without answer text, and the draft is cleaned up after final delivery.

Risk before merge

[P1] Merging intentionally changes default Telegram chat behavior: short previews can appear after a bounded delay and progress mode can show a label placeholder where current behavior may stay silent until final delivery.
[P1] Maintainers still need to choose whether to land this narrow default fix or prefer the combined proposal at feat(telegram): unify progress fallback with assistant preview lane #95522, which also adds the opt-in assistant-preview lane.
[P1] The current CI failure appears to be stale-base script typecheck drift that current main already fixes, so the branch should refresh or rerun exact-head gates before merge.

Maintainer options:

Accept the narrow default behavior
Maintainers can accept the visible timing change as the low-noise default fix after refreshing the branch and confirming exact-head gates.
Prefer the combined proposal
If the desired end state also includes opt-in assistant partial previews, pause this PR and review feat(telegram): unify progress fallback with assistant preview lane #95522 as the canonical candidate.
Request a default-off shape
If default Telegram chat timing should not change, ask for an opt-in or documented-policy variant before merge.

Next step before merge

[P2] No narrow automated repair remains; the next action is maintainer acceptance of the Telegram default behavior and refreshed merge gates.

Security
Cleared: The diff changes Telegram streaming behavior, docs, and tests only; it does not introduce dependency, workflow, package, secret, or supply-chain changes.

Review details

Best possible solution:

Maintainers should choose the desired Telegram product shape, then land either this narrow default-silence fix or the combined proposal with exact-head checks green.

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

Yes. The linked issue and current-main source show below-threshold first previews and progress-mode answer partials can remain invisible, and this PR adds tests plus live Bot API proof for the changed paths.

Is this the best way to solve the issue?

Unclear as a product choice, but the code path is a narrow plausible fix. The safer maintainer decision is to choose between this low-noise default behavior and the broader combined proposal before merge.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against d1cbe29f3d52.

Label changes

Label justifications:

P2: This is a normal-priority Telegram streaming feedback fix with channel-limited blast radius and strong source/proof evidence.
merge-risk: 🚨 message-delivery: The diff changes when Telegram sends or edits visible draft/progress messages during active agent turns.
rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🦞 diamond lobster and patch quality is 🐚 platinum hermit.
status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (logs): The PR body and comments include redacted live Telegram Bot API proof for delayed short previews, progress placeholders, lifecycle cleanup, and timer cancellation after the fix.
proof: sufficient: Contributor real behavior proof is sufficient. The PR body and comments include redacted live Telegram Bot API proof for delayed short previews, progress placeholders, lifecycle cleanup, and timer cancellation after the fix.
mantis: telegram-visible-proof: Mantis should capture Telegram visible proof. The PR changes visible Telegram draft and progress-placeholder behavior that a short Telegram proof recording can demonstrate.

Evidence reviewed

PR surface:

Source +72, Tests +121, Docs +2. Total +195 across 8 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	3	76	4	+72
Tests	3	122	1	+121
Docs	2	4	2	+2
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	8	202	7	+195

What I checked:

PR head implements bounded short-preview materialization: At PR head, createTelegramDraftStream accepts minInitialDelayMs, schedules a delayed first-preview flush for below-threshold text, and cancels that timer during reset, discard, and clear. (extensions/telegram/src/draft-stream.ts:181, 1ab0ba3ae113)
PR head wires Telegram progress answer activity to the placeholder path: Telegram dispatch passes a 5s delayed materialization window to answer drafts and calls progressDraft.noteActivity instead of streaming answer text into progress-mode drafts. (extensions/telegram/src/bot-message-dispatch.ts:1008, 1ab0ba3ae113)
Shared compositor has a bounded activity hook and final-delivery cancellation: The new noteActivity path starts the existing progress draft gate without adding answer text, and final-start/final-delivered paths cancel pending delayed startup. (src/channels/progress-draft-compositor.ts:221, 1ab0ba3ae113)
Regression tests cover the changed behavior: The PR adds tests for delayed short-preview send, delayed timer cancellation on clear, progress answer-activity placeholders, and final-delivery cancellation. (extensions/telegram/src/draft-stream.test.ts:924, 1ab0ba3ae113)
Maintainer note makes the default Telegram behavior a policy decision: The Telegram maintainer note says first-preview debounce is intentional and Telegram streaming PRs need real Telegram proof when transport or streaming behavior changes. (.agents/maintainer-notes/telegram.md:9, d1cbe29f3d52)
Exact-head CI failure appears stale-base and unrelated to the PR diff: The failing check-test-types job reports a missing declaration for scripts/lib/windows-taskkill.mjs, which is not in this PR's changed files; current main contains scripts/lib/windows-taskkill.d.mts. (scripts/lib/windows-taskkill.d.mts:1, d1cbe29f3d52)

Likely related people:

obviyus: Recent GitHub commit history shows repeated Telegram draft/progress/rich-preview work and the shared progress compositor refactors closest to this PR's behavior. (role: recent area contributor; confidence: high; commits: 42dcf7075f2d, da92615816b6, 663fabbe30eb; files: extensions/telegram/src/draft-stream.ts, extensions/telegram/src/bot-message-dispatch.ts, src/channels/progress-draft-compositor.ts)
vincentkoc: Current local blame points at this checkout's Telegram draft and compositor lines, and recent commit history shows adjacent Telegram dispatch and channel cleanup work plus co-authored progress-draft changes. (role: recent adjacent contributor; confidence: medium; commits: 7580c80f37eb, 3d05da9a5483, 257d540297e6; files: extensions/telegram/src/bot-message-dispatch.ts, extensions/telegram/src/draft-stream.ts, src/channels/progress-draft-compositor.ts)
zhangguiping-xydt: A recent draft-stream lifecycle fix touched preview retention across generation races, which is adjacent to this PR's timer cleanup and materialization path. (role: adjacent preview lifecycle contributor; confidence: medium; commits: 0a4927d0b8c2; files: extensions/telegram/src/draft-stream.ts, extensions/telegram/src/draft-stream.test.ts)
anagnorisis2peripeteia: Recent shared progress-draft work changed how commentary renders in progress drafts, adjacent to this PR's shared compositor changes. (role: adjacent progress-draft contributor; confidence: medium; commits: c1300455d942; files: src/channels/progress-draft-compositor.ts, src/channels/streaming.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.

snowzlmbot · 2026-06-20T02:57:17Z

Pushed follow-up fix d2687eaed7 for ClawSweeper's delayed-final guard finding.

What changed:

markFinalReplyStarted() and markFinalReplyDelivered() now cancel the progress draft gate so pending delayed answer-activity timers cannot materialize after final delivery starts or lands.
render() also re-checks final-start/final-delivered state as a backstop before updating the draft.
Added focused regression coverage for both final-start and final-delivered cancellation.

Fresh local evidence on the updated head:

node scripts/run-vitest.mjs src/channels/progress-draft-compositor.test.ts
# 15 passed

node scripts/run-vitest.mjs extensions/telegram/src/bot-message-dispatch.test.ts
# 130 passed

git diff --check
# passed

snowzlmbot · 2026-06-20T06:26:10Z

Added native Telegram Bot API proof to the PR body.

Proof summary:

Dedicated test bot: @snowzlmOpenClawtestBot; token and private chat id are omitted.
Short-preview scenario: a short text below minInitialChars=30 stayed quiet during the initial window, then materialized as a Telegram message instead of remaining indefinitely silent.
Progress-placeholder scenario: the stable Shelling placeholder appeared before the normal final message, and the final answer text was not leaked into the placeholder.
Local targeted checks on this head:
- telegram/src/draft-stream.test.ts: 47 passed
- telegram/src/bot-message-dispatch.test.ts: 130 passed
- src/channels/progress-draft-compositor.test.ts: 15 passed
- git diff --check: passed

@clawsweeper review-pr

clawsweeper · 2026-06-20T06:26:13Z

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

snowzlmbot · 2026-06-20T06:44:44Z

Added an extra native Telegram Bot API lifecycle proof to the PR body for draft-count/cleanup behavior.

Key checks:

Progress drafts reuse the initial Telegram draft message id through editMessageText updates.
The final answer is delivered as a normal final message.\n- The progress draft is removed with deleteMessage after final delivery, so it is no longer visible in Telegram.
The bounded short-preview path also edits the same message id and finalizes in place; it does not create multiple default draft messages.
@clawsweeper review-pr

clawsweeper · 2026-06-20T06:54:20Z

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

snowzlmbot · 2026-06-20T06:57:17Z

Lifecycle proof has been added to the PR body and comments, covering draft message reuse and cleanup after final delivery.

@clawsweeper review-pr

snowzlmbot · 2026-06-20T22:30:48Z

@codex review

chatgpt-codex-connector · 2026-06-20T22:30:54Z

To use Codex here, create a Codex account and connect to github.

snowzlmbot · 2026-06-20T22:42:17Z

@codex review

chatgpt-codex-connector · 2026-06-20T22:48:09Z

Codex Review: Didn't find any major issues. What shall we delve into next?

Reviewed commit: 3a9a60e871

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

snowzlmbot · 2026-06-21T09:01:55Z

Pushed focused fix for the ClawSweeper P2 delayed-preview timer finding.

What changed:

createTelegramDraftStream.clear() now cancels the delayed first-preview timer before stopping/removing the draft.
Added a fake-timer regression: below-threshold pending preview → clear() → timer count drops to zero → advancing the old delay does not send/edit a draft.
Rewrote this branch metadata so snowzlmbot-owned commits use snowzlmbot as author/committer; code tree is unchanged by the identity rewrite.

Validation:

git diff --check origin/main...HEAD
node scripts/run-vitest.mjs \
  extensions/telegram/src/draft-stream.test.ts \
  extensions/telegram/src/bot-message-dispatch.test.ts \
  src/channels/progress-draft-compositor.test.ts

Result: 193 targeted tests passed.

@clawsweeper review-pr

clawsweeper · 2026-06-21T09:01:58Z

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

snowzlmbot · 2026-06-21T09:27:14Z

Added live Telegram Bot API before/after proof to the PR body.

What the redacted live proof shows:

Before the timer cleanup fix, the delayed first-preview timer remained active after clear() and fired after cleanup.
After the fix, clear() calls clearTimeout; active timer count drops to 0 immediately and the timer does not fire after cleanup.
Direct Bot API logs also show no stray Telegram send/edit/delete after the delay window.

The proof used the configured test bot token against a private proof chat; token and chat identifiers are redacted in the PR evidence.

@clawsweeper review-pr

snowzlmbot · 2026-06-21T11:58:10Z

Rebased onto latest main and pushed head 1e6af44af2f81d0c09b82d05d7372a6bda881968.

Why:

The previous CI failures were from upstream drift, not this Telegram PR:
- check-test-types: upstream scripts/control-ui-i18n.ts imported windows-taskkill.mjs before the matching declaration file landed.
- checks-node-core-tooling: upstream src/scripts/test-projects.test.ts routing expectation lagged newly added top-level helper tests.
Latest main contains those upstream fixes, so this PR now absorbs them via rebase instead of adding unrelated tooling/type changes.

Scope check:

PR diff remains limited to the Telegram/progress-draft files.

Validation after rebase:

git diff --check origin/main...HEAD
node scripts/run-vitest.mjs \
  extensions/telegram/src/draft-stream.test.ts \
  extensions/telegram/src/bot-message-dispatch.test.ts \
  src/channels/progress-draft-compositor.test.ts

Result: 193 targeted tests passed.

@clawsweeper review-pr

clawsweeper · 2026-06-21T11:58:14Z

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

obviyus · 2026-06-21T14:18:53Z

Landed via squash onto main.

Scoped tests: git diff --check origin/main...HEAD; node scripts/run-vitest.mjs extensions/telegram/src/draft-stream.test.ts extensions/telegram/src/bot-message-dispatch.test.ts src/channels/progress-draft-compositor.test.ts
Changelog: not updated; OpenClaw release generation owns CHANGELOG.md
Land commit: 1c1c068
Merge commit: 6441e56

Thanks @snowzlmbot!

…95183) * fix(telegram): materialize streaming progress placeholders * fix(telegram): cancel delayed progress drafts before final * fix(telegram): satisfy progress placeholder lint * fix(telegram): cancel delayed draft preview on clear * refactor(telegram): simplify delayed preview flush --------- Co-authored-by: snowzlmbot <[email protected]> Co-authored-by: Ayaan Zaidi <[email protected]>

…026.6.11) (#1344) 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.10` → `2026.6.11` | --- ### Release Notes <details> <summary>openclaw/openclaw (ghcr.io/openclaw/openclaw)</summary> ### [`v2026.6.11`](https://github.com/openclaw/openclaw/blob/HEAD/CHANGELOG.md#2026611) [Compare Source](https://github.com/openclaw/openclaw/compare/v2026.6.10...v2026.6.11) We heard the feedback. v2026.6.11 focuses on the rough edges that make OpenClaw feel less dependable, with fixes for misplaced replies, stuck sends, reconnects, model setup failures, and safer admin defaults. [Full release notes](https://docs.openclaw.ai/releases/2026.6.11) ##### Highlights ##### Channel delivery reliability Delivery and reconnect fixes span [Telegram](https://docs.openclaw.ai/channels/telegram), [WhatsApp](https://docs.openclaw.ai/channels/whatsapp), [Matrix](https://docs.openclaw.ai/channels/matrix), [Google Chat](https://docs.openclaw.ai/channels/googlechat), [iMessage](https://docs.openclaw.ai/channels/imessage), [Feishu](https://docs.openclaw.ai/channels/feishu), [Mattermost](https://docs.openclaw.ai/channels/mattermost), [WebChat](https://docs.openclaw.ai/web/webchat), the [Control UI](https://docs.openclaw.ai/web/control-ui), and the [terminal UI](https://docs.openclaw.ai/cli/tui). - Fixes newer Google Chat direct messages sometimes being treated like group conversations, so they reach the correct one-to-one chat while Space and group-chat messages keep their existing routing. [#58993](https://github.com/openclaw/openclaw/pull/58993) Thanks [@starhappysh](https://github.com/starhappysh), [@vincentkoc](https://github.com/vincentkoc). - Feishu voice replies from OpenClaw now show their duration in the chat bubble, so recipients can see how long the audio is before playing it. [#89172](https://github.com/openclaw/openclaw/pull/89172) Related [#53798](https://github.com/openclaw/openclaw/issues/53798). Thanks [@areslp](https://github.com/areslp), [@fxz26284407](https://github.com/fxz26284407), [@kinrocw](https://github.com/kinrocw). - Discord and Telegram replies and mirrored chat history stay tied to the intended conversation more consistently, including across repeated Telegram replies and session changes. [#89911](https://github.com/openclaw/openclaw/pull/89911) Thanks [@jalehman](https://github.com/jalehman). - Background image, video, and music results now return to the chat that requested them when the task starts without a full conversation target, instead of appearing to fail after creation or being sent to the wrong peer as the session moves. [#89949](https://github.com/openclaw/openclaw/pull/89949) Related [#86034](https://github.com/openclaw/openclaw/issues/86034). Thanks [@tianxiaochannel-oss88](https://github.com/tianxiaochannel-oss88), [@wangwllu](https://github.com/wangwllu). - Telegram answers now stay attached to the user's current question when they quote an earlier bot message, while quotes of other people's messages still reply to the selected quote. [#90475](https://github.com/openclaw/openclaw/pull/90475) Thanks [@moeedahmed](https://github.com/moeedahmed). - QQBot group admins can choose how broadly slash commands are available, and private-only commands now direct users to a private chat instead of being exposed or silently ignored in groups. [#92154](https://github.com/openclaw/openclaw/pull/92154) Thanks [@sliverp](https://github.com/sliverp). - Heartbeat checks using reasoning-capable models now show the assistant's intended reply instead of exposing internal reasoning in Telegram, WhatsApp, and other channels, while opt-in Thinking messages still work. [#92356](https://github.com/openclaw/openclaw/pull/92356) Related [#92260](https://github.com/openclaw/openclaw/issues/92260). Thanks [@jmpei](https://github.com/jmpei), [@tangtaizong666](https://github.com/tangtaizong666), [@vincentkoc](https://github.com/vincentkoc). - Telegram progress-mode chats now clear an old progress bubble before newer tool output or artifacts appear, keeping the conversation in a clean, readable order. [#93002](https://github.com/openclaw/openclaw/pull/93002) Related [#90753](https://github.com/openclaw/openclaw/issues/90753). Thanks [@shadow-enthusiast](https://github.com/shadow-enthusiast), [@zhangguiping-xydt](https://github.com/zhangguiping-xydt). - iMessage command-and-link messages now stay together as one OpenClaw turn when delayed link previews arrive, while unrelated quick messages remain separate for users who enabled same-sender DM coalescing. [#93143](https://github.com/openclaw/openclaw/pull/93143) Thanks [@omarshahine](https://github.com/omarshahine). - Successful Discord replies sent through the message tool no longer trigger a misleading failure warning in affected `message_tool_only` source-channel turns. [#94072](https://github.com/openclaw/openclaw/pull/94072) Related [#93875](https://github.com/openclaw/openclaw/issues/93875). Thanks [@chenyangjun-xy](https://github.com/chenyangjun-xy), [@hoyanhan](https://github.com/hoyanhan), [@vincentkoc](https://github.com/vincentkoc). - WhatsApp group conversations now preserve the right message and group context more reliably during retries, reconnects, and group changes. [#94338](https://github.com/openclaw/openclaw/pull/94338) Related [#7433](https://github.com/openclaw/openclaw/issues/7433). Thanks [@mcaxtr](https://github.com/mcaxtr), [@octopuslabs-fl](https://github.com/octopuslabs-fl), [@xialonglee](https://github.com/xialonglee). - Fixes OpenClaw sometimes replying to its own delayed iMessage echoes when stray leading characters keep the sent message from being recognized. [#94442](https://github.com/openclaw/openclaw/pull/94442) Thanks [@ly-wang19](https://github.com/ly-wang19). - Telegram webhook users can keep receiving DMs and group messages through brief channel restarts, configuration reloads, and recovery cycles without temporary message blackouts. [#94506](https://github.com/openclaw/openclaw/pull/94506) Related [#90254](https://github.com/openclaw/openclaw/issues/90254). Thanks [@obviyus](https://github.com/obviyus), [@travellingsoldier85](https://github.com/travellingsoldier85), [@xialonglee](https://github.com/xialonglee). - Matrix E2EE gateways can stay online during long-running use instead of gradually consuming memory until a crash takes channels and in-flight work down. [#94942](https://github.com/openclaw/openclaw/pull/94942) Related [#90455](https://github.com/openclaw/openclaw/issues/90455). Thanks [@xzh-icenter](https://github.com/xzh-icenter), [@yar-sh](https://github.com/yar-sh). - Telegram users now see the intended native reaction instead of leaked instructions or a dropped reaction-only reply, with success recorded only after Telegram accepts it. [#94977](https://github.com/openclaw/openclaw/pull/94977) Related [#71140](https://github.com/openclaw/openclaw/issues/71140). Thanks [@cuttingwater](https://github.com/cuttingwater), [@hugenshen](https://github.com/hugenshen). - Telegram progress updates for commands, searches, updates, and API activity now stay readable instead of exposing noisy HTML or code-style rows, with plain-text fallback when Telegram cannot parse the formatting. [#95007](https://github.com/openclaw/openclaw/pull/95007) Related [#95002](https://github.com/openclaw/openclaw/issues/95002). - Telegram conversations continued in WebChat now show one assistant reply per turn and keep later replies with the active conversation instead of duplicating answers or sending them back to Telegram. [#95069](https://github.com/openclaw/openclaw/pull/95069) Related [#94930](https://github.com/openclaw/openclaw/issues/94930). Thanks [@heichaowo](https://github.com/heichaowo). - Google Chat now hides misleading internal failure banners when a tool result is harmless, leaving users with the completed answer while normal assistant text remains unchanged. [#95084](https://github.com/openclaw/openclaw/pull/95084) Related [#90684](https://github.com/openclaw/openclaw/issues/90684). Thanks [@jailbirt](https://github.com/jailbirt), [@studentzhou-svg](https://github.com/studentzhou-svg). - Bound multi-agent channel conversations now load the workspace files for the configured agent instead of the default agent, though previously misfiled conversations may start fresh in the corrected agent store. [#95118](https://github.com/openclaw/openclaw/pull/95118) Related [#92903](https://github.com/openclaw/openclaw/issues/92903). Thanks [@849261680](https://github.com/849261680), [@axjing](https://github.com/axjing). - People sharing an OpenClaw gateway can now assign different models to individual direct-message contacts across supported chat channels, while existing group and wildcard model choices keep working as before. [#95120](https://github.com/openclaw/openclaw/pull/95120) Related [#53638](https://github.com/openclaw/openclaw/issues/53638). Thanks [@gandalf-at-lerian](https://github.com/gandalf-at-lerian), [@thomaszta](https://github.com/thomaszta), [@xydigit-zt](https://github.com/xydigit-zt). - Telegram now shows that OpenClaw is still working during short initial previews or progress-mode replies instead of leaving the chat silent until the final message arrives. [#95183](https://github.com/openclaw/openclaw/pull/95183) Related [#95004](https://github.com/openclaw/openclaw/issues/95004). Thanks [@obviyus](https://github.com/obviyus). - Matrix users and operators now get a clear failure when a homeserver sends an oversized or stalled response, instead of OpenClaw continuing to buffer it and risking unbounded memory use. [#95240](https://github.com/openclaw/openclaw/pull/95240) Thanks [@alix-007](https://github.com/alix-007). - Fixes delayed or missing Telegram and other queued channel replies in Kubernetes-style deployments with many injected environment variables, where opening the queue database could stall the gateway. [#95278](https://github.com/openclaw/openclaw/pull/95278) Related [#94571](https://github.com/openclaw/openclaw/issues/94571). Thanks [@kaka-srp](https://github.com/kaka-srp). - Telegram chats recover after one stuck message times out, allowing later messages in the same chat or topic to reach the agent without restarting the gateway. [#95299](https://github.com/openclaw/openclaw/pull/95299) Related [#95248](https://github.com/openclaw/openclaw/issues/95248). Thanks [@kriegerbangerz-ship-it](https://github.com/kriegerbangerz-ship-it), [@mikasa0818](https://github.com/mikasa0818), [@obviyus](https://github.com/obviyus). - When people switch between Telegram and another OpenClaw client in a shared direct conversation, short Telegram replies now follow the latest conversation instead of responding to an older, unrelated Telegram proposal. [#95390](https://github.com/openclaw/openclaw/pull/95390) Related [#95378](https://github.com/openclaw/openclaw/issues/95378). Thanks [@maiduy708](https://github.com/maiduy708), [@mikasa0818](https://github.com/mikasa0818), [@obviyus](https://github.com/obviyus). - Fixes completed assistant messages appearing twice in Telegram, Discord, Slack, and other streamed chats after a multi-message reply. [#95432](https://github.com/openclaw/openclaw/pull/95432) Thanks [@vincentkoc](https://github.com/vincentkoc), [@yetval](https://github.com/yetval). - WhatsApp replies now stay attached to the direct or group message being answered instead of appearing as a separate message that loses the conversation context. [#95483](https://github.com/openclaw/openclaw/pull/95483) Thanks [@mcaxtr](https://github.com/mcaxtr). - Telegram rich-message replies now keep paragraphs, bullets, and status lines separated instead of collapsing multi-line content into one run-on block, with no configuration change required. [#95532](https://github.com/openclaw/openclaw/pull/95532) Related [#95409](https://github.com/openclaw/openclaw/issues/95409). Thanks [@amknight](https://github.com/amknight). - Mattermost operators who enable native slash commands can now use `/oc_queue` directly in Mattermost to tune active-run queuing, including its mode, debounce timing, cap, and drop handling. [#95546](https://github.com/openclaw/openclaw/pull/95546) Thanks [@amknight](https://github.com/amknight). - Previously allowed messages keep reaching named accounts after legacy multi-account channel upgrades, with inherited DM and group access rules preserved across Mattermost, Discord, Slack, Telegram, Signal, WhatsApp, iMessage, and IRC. [#95550](https://github.com/openclaw/openclaw/pull/95550) Thanks [@amknight](https://github.com/amknight). - Mattermost users can keep talking in a thread without mentioning the bot again after it replies, and that participation survives gateway restarts until the thread has been idle for seven days. [#95552](https://github.com/openclaw/openclaw/pull/95552) Thanks [@amknight](https://github.com/amknight). - Inbound Telegram messages now reach the configured OpenClaw session promptly instead of sitting unanswered until the next polling interval, a gateway restart, or manual intervention. [#95577](https://github.com/openclaw/openclaw/pull/95577) Related [#86957](https://github.com/openclaw/openclaw/issues/86957). Thanks [@freidrich-goldenflow](https://github.com/freidrich-goldenflow), [@liuwqgit](https://github.com/liuwqgit). - QQBot users now receive complete markdown tables when valid separators use one or two dashes per column, instead of losing the header and all but the final row. [#95637](https://github.com/openclaw/openclaw/pull/95637) Thanks [@ly-wang19](https://github.com/ly-wang19). - Synology Chat users can now receive agent replies that take more than 120 seconds when the configured core timeout allows it, instead of having the channel reject them early. [#95707](https://github.com/openclaw/openclaw/pull/95707) Thanks [@sahibzada-allahyar](https://github.com/sahibzada-allahyar), [@vincentkoc](https://github.com/vincentkoc). - Telegram forum-topic cron jobs now keep separately configured failure alerts going to their intended destination, even when the main announcement uses a topic in the same chat. [#95794](https://github.com/openclaw/openclaw/pull/95794) Thanks [@vincentkoc](https://github.com/vincentkoc). - Fixes WhatsApp group replies that could quote an older OpenClaw message instead of the user's triggering message, so final answers stay attached to the intended message when a reply target is available and avoid pointing back to stale bot context when it is not. [#95914](https://github.com/openclaw/openclaw/pull/95914) Thanks [@mcaxtr](https://github.com/mcaxtr). - WhatsApp users can approve or deny prompts by reaction without the prompt staying stuck when WhatsApp identifies the same direct chat differently, while group approvals remain tied to the correct group and person. [#95935](https://github.com/openclaw/openclaw/pull/95935) Thanks [@mcaxtr](https://github.com/mcaxtr). - Final reply processing now uses less CPU when OpenClaw checks whether block text was already sent, without changing which reply reaches the chat or how duplicate text is suppressed. [#96087](https://github.com/openclaw/openclaw/pull/96087) Thanks [@vincentkoc](https://github.com/vincentkoc). - Exec approval results from external channel plugins now return to the channel or DM where the command started instead of falling back to WebChat or seeming to disappear after approval. [#96140](https://github.com/openclaw/openclaw/pull/96140) Related [#96103](https://github.com/openclaw/openclaw/issues/96103). Thanks [@lansenger-pm](https://github.com/lansenger-pm), [@vincentkoc](https://github.com/vincentkoc), [@yetval](https://github.com/yetval). - WhatsApp's final answer now stays quoted to the follow-up message a user just sent when replying to an older OpenClaw message, instead of arriving unquoted or pointing back to the older bot reply. [#96220](https://github.com/openclaw/openclaw/pull/96220) Thanks [@mcaxtr](https://github.com/mcaxtr). - Nextcloud Talk bots now ignore ordinary file-share and lifecycle events without logging them as bot errors or risking disabled delivery, while malformed chat payloads still return an error. [#96243](https://github.com/openclaw/openclaw/pull/96243) Related [#81566](https://github.com/openclaw/openclaw/issues/81566). Thanks [@arkyu2077](https://github.com/arkyu2077), [@rafaelmgbh](https://github.com/rafaelmgbh), [@vincentkoc](https://github.com/vincentkoc). - Replies and message-tool delivery in Mattermost channels now use channel and thread guidance because the agent identifies those conversations as channels rather than group chats, while existing group-chat behavior remains unchanged. [#96244](https://github.com/openclaw/openclaw/pull/96244) Related [#95645](https://github.com/openclaw/openclaw/issues/95645). Thanks [@arkyu2077](https://github.com/arkyu2077), [@iloveleon19](https://github.com/iloveleon19), [@vincentkoc](https://github.com/vincentkoc). - MCP channel integrations now keep conversation lists, message reads, event polls, and waits within predictable bounds even when a client requests excessive limits or timeouts. [a39e548](https://github.com/openclaw/openclaw/commit/a39e548ede228aa1978bf9d509613cbed6db0c99) Thanks [@vincentkoc](https://github.com/vincentkoc). - Long-running streamed auto-replies are less likely to stop early or abort inconsistently when an unusually large timeout is configured. [6c85b90](https://github.com/openclaw/openclaw/commit/6c85b90469f94955ef00c1609e1f1d6fd2cf4ca8) Thanks [@vincentkoc](https://github.com/vincentkoc). - Channel progress now shows a repeated status when work genuinely returns to it after another update, instead of hiding useful context as a duplicate. [8a75c4d](https://github.com/openclaw/openclaw/commit/8a75c4dd5f3e625a22a7a08c6e1f368798c48111) - Completed channel replies no longer gain late progress notices, preventing stale status text from appearing after the answer is finished. [a594d2c](https://github.com/openclaw/openclaw/commit/a594d2ce73257326b7ab78adb3c4643245ec9431) Thanks [@vincentkoc](https://github.com/vincentkoc). - During streaming channel replies, progress messages now keep showing the latest state instead of getting stuck on an older update. [e114001](https://github.com/openclaw/openclaw/commit/e114001ccafa83b8b366e095a9d7748dfc50c082) Thanks [@vincentkoc](https://github.com/vincentkoc). - Matrix forced resets now handle unavailable secret storage without a runtime error, treating recovery access as unavailable so the reset path can continue safely. [5c5a8a4](https://github.com/openclaw/openclaw/commit/5c5a8a49d76954b53fefc2463bc7b1d6b960e8fc) Thanks [@vincentkoc](https://github.com/vincentkoc). - Configured channels now remain visible in `openclaw channels status --json`, while scheduled announcements reject stale entries that have no active plugin to deliver them. [a641c0d](https://github.com/openclaw/openclaw/commit/a641c0d560fd15373e462829facf15fd6a466aeb) - Discord voice conversations now keep back-to-back assistant responses moving, so a queued reply plays after the previous audio stream closes instead of remaining stuck. [88b64e4](https://github.com/openclaw/openclaw/commit/88b64e4b869e696d99de7417fb52425e9ed67cbf) Thanks [@vincentkoc](https://github.com/vincentkoc). - Discord progress previews are less likely to stop before the final edits when an agent response has already started arriving. [86ea382](https://github.com/openclaw/openclaw/commit/86ea382121b00e73af4b4c329d0a2447592e4071) - Chats no longer show stray `NO_REPLY` text when the assistant means to stay silent, while legitimate media responses still arrive without the placeholder. [96c6f80](https://github.com/openclaw/openclaw/commit/96c6f8022c2420826830b11f4353ce855ab2ac5c) - Telegram streaming replies now show each progress heading once, keeping tool and search updates easier to scan. [013e33c](https://github.com/openclaw/openclaw/commit/013e33c6d3672a980550912442bb1ac5505918aa) Thanks [@vincentkoc](https://github.com/vincentkoc). - Telegram messages that get stuck after a long-running task, crash, or gateway restart now resume processing automatically, so later messages no longer wait silently or require operators to repair the queue by hand. [#97543](https://github.com/openclaw/openclaw/pull/97543) Thanks [@romneyda](https://github.com/romneyda), [@vincentkoc](https://github.com/vincentkoc). ##### Provider and model recovery [Model setup](https://docs.openclaw.ai/providers/models), [OpenAI](https://docs.openclaw.ai/providers/openai), [OpenRouter](https://docs.openclaw.ai/providers/openrouter), [opencode-go](https://docs.openclaw.ai/providers/opencode-go), and [fast-mode](https://docs.openclaw.ai/tools/thinking#fast-mode-fast) follow-up behavior now recover more clearly in affected configurations. - MiniMax text-to-speech and voice notes are less likely to fail because OpenClaw now explicitly requests the audio format it can decode instead of relying on provider defaults. [#73079](https://github.com/openclaw/openclaw/pull/73079) Thanks [@efe-arv](https://github.com/efe-arv). - Gateway operators can again see provider, model, request status, and timing details in normal logs, making model-routing and transport problems easier to diagnose without enabling extra debug logging. [#89648](https://github.com/openclaw/openclaw/pull/89648) Related [#89300](https://github.com/openclaw/openclaw/issues/89300). Thanks [@enominera](https://github.com/enominera), [@xiaobao-k8s](https://github.com/xiaobao-k8s). - Models reached through Google, Mistral, OpenAI Responses, Azure OpenAI Responses, and ChatGPT/Codex Responses now receive clean system instructions without OpenClaw's internal cache-boundary marker leaking into the prompt. [#89716](https://github.com/openclaw/openclaw/pull/89716) Thanks [@enominera](https://github.com/enominera), [@masatohoshino](https://github.com/masatohoshino). - Cron tool calls using Gemini models through OpenAI-compatible providers now run without nullable fields triggering provider schema rejections. [#91559](https://github.com/openclaw/openclaw/pull/91559) Related [#91542](https://github.com/openclaw/openclaw/issues/91542). Thanks [@pick-cat](https://github.com/pick-cat), [@qiukui666](https://github.com/qiukui666). - Provider-qualified model IDs now honor their configured agent runtime policies and CLI aliases instead of unexpectedly falling back to OpenClaw's default runtime. [#91724](https://github.com/openclaw/openclaw/pull/91724) Thanks [@vincentkoc](https://github.com/vincentkoc), [@yu-xin-c](https://github.com/yu-xin-c). - The chat `/models` list and other plugin-aware model or provider selection paths now respond quickly instead of stalling for seconds and consuming a CPU core through repeated setup scans, while plugin changes still refresh normally. [#93356](https://github.com/openclaw/openclaw/pull/93356) Thanks [@obuchowski](https://github.com/obuchowski). - Hosted Ollama Cloud users can keep only the models they explicitly configured after a restart, without the full shared catalog being added back, while automatic discovery continues for local and self-hosted Ollama servers. [#93956](https://github.com/openclaw/openclaw/pull/93956) Thanks [@jason-allen-oneal](https://github.com/jason-allen-oneal). - Cron jobs can now retry or switch to a configured fallback model when a local provider returns the generic `LLM request failed.` error, instead of failing with the fallback unused. [#94062](https://github.com/openclaw/openclaw/pull/94062) Related [#93931](https://github.com/openclaw/openclaw/issues/93931). Thanks [@hugenshen](https://github.com/hugenshen). - Expired provider tokens no longer bury useful operator logs under repeated fallback warnings, while the first warning and later duplicate summaries remain available for diagnosis. [#94233](https://github.com/openclaw/openclaw/pull/94233) Related [#56979](https://github.com/openclaw/openclaw/issues/56979). Thanks [@goutamadwant](https://github.com/goutamadwant), [@yanan1991](https://github.com/yanan1991). - Google Gemini 3.5 Flash can now be selected with its full 1,048,576-token context window, avoiding missing-model errors and needless prompt-size rejections. [#94726](https://github.com/openclaw/openclaw/pull/94726) Related [#94723](https://github.com/openclaw/openclaw/issues/94723). Thanks [@ajwan8998](https://github.com/ajwan8998), [@anguslogan01](https://github.com/anguslogan01), [@kevinat](https://github.com/kevinat). - Dashboard child sessions now handle allowed provider-qualified model choices consistently and give accurate recovery guidance when saved model state is stale. [#94752](https://github.com/openclaw/openclaw/pull/94752) Related [#94713](https://github.com/openclaw/openclaw/issues/94713). Thanks [@gr4via](https://github.com/gr4via). - Claude CLI users no longer get promises of completion updates that may never arrive, because OpenClaw now blocks unsupported native background work before it can strand progress. [#95008](https://github.com/openclaw/openclaw/pull/95008) Thanks [@anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia). - OpenClaw now rejects oversized provider catalog or JSON responses with a clear error before buffering the entire response in memory. [#95218](https://github.com/openclaw/openclaw/pull/95218) Thanks [@alix-007](https://github.com/alix-007). - OpenRouter users can now select and run the advertised short DeepSeek V4 model IDs without requests failing with `model_not_found` because OpenClaw sent a duplicated provider prefix. [#95268](https://github.com/openclaw/openclaw/pull/95268) Related [#95198](https://github.com/openclaw/openclaw/issues/95198). Thanks [@daniel-alejandro-t](https://github.com/daniel-alejandro-t), [@darren2030](https://github.com/darren2030). - With `/reasoning on`, DeepSeek-style OpenAI-compatible models now show the final answer separately from their reasoning instead of folding it into the reasoning block, with no configuration change required. [#95283](https://github.com/openclaw/openclaw/pull/95283) Related [#95280](https://github.com/openclaw/openclaw/issues/95280). Thanks [@marvinthebored](https://github.com/marvinthebored), [@vincentkoc](https://github.com/vincentkoc), [@zengwen-dt](https://github.com/zengwen-dt). - When a Codex subscription reaches its usage limit, OpenClaw now moves to configured fallback models instead of stopping on the failed result, and it does not retry runs that already produced visible output. [#95400](https://github.com/openclaw/openclaw/pull/95400) Thanks [@jason-allen-oneal](https://github.com/jason-allen-oneal), [@sallyom](https://github.com/sallyom). - LM Studio users can now run quantized or multi-variant local models without false assistant-turn failures or phantom suffixed model entries caused by mismatched model keys. [#95401](https://github.com/openclaw/openclaw/pull/95401) Thanks [@monkeyleet](https://github.com/monkeyleet). - Google-backed embedded-agent runs now stop reading oversized or never-ending prompt-cache responses before they can exhaust memory or leave the run stalled. [#95417](https://github.com/openclaw/openclaw/pull/95417) Thanks [@alix-007](https://github.com/alix-007). - OpenRouter model scans fail safely on oversized or malformed catalogs instead of risking excessive memory use that can destabilize OpenClaw. [#95418](https://github.com/openclaw/openclaw/pull/95418) Thanks [@alix-007](https://github.com/alix-007). - OpenRouter setups now reject oversized model catalogs before they can exhaust OpenClaw's memory, without caching or immediately refetching the failed response. [#95420](https://github.com/openclaw/openclaw/pull/95420) Thanks [@alix-007](https://github.com/alix-007), [@sallyom](https://github.com/sallyom). - Configured fallback models can now answer when Claude CLI runs out of credits or hits a generic runner failure, instead of leaving users with the failure message as the final response. [#95508](https://github.com/openclaw/openclaw/pull/95508) Related [#95489](https://github.com/openclaw/openclaw/issues/95489). Thanks [@mikasa0818](https://github.com/mikasa0818), [@riazrahaman](https://github.com/riazrahaman), [@sallyom](https://github.com/sallyom). - Gemini-backed web searches using `freshness: "day"` or `pd` now complete instead of failing with a provider 400 error, while broader freshness choices and explicit date ranges retain stricter filtering. [#95682](https://github.com/openclaw/openclaw/pull/95682) Thanks [@sunjae-k](https://github.com/sunjae-k), [@vincentkoc](https://github.com/vincentkoc). - Follow-up answers from xAI reasoning models such as Grok Composer now preserve earlier reasoning context more reliably, even when configurable reasoning effort is unsupported. [#95686](https://github.com/openclaw/openclaw/pull/95686) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev), [@geraint0923](https://github.com/geraint0923). - Vercel AI Gateway users can now run models chosen from the live catalog, including live-only model IDs that are absent from OpenClaw's bundled list. [#95710](https://github.com/openclaw/openclaw/pull/95710) Thanks [@vincentkoc](https://github.com/vincentkoc). - Fixes manifest-defined providers turning valid model IDs into broken ones when `stripPrefixes` entries have stray spaces or different casing, so operators and plugin authors get the intended provider model. [#95744](https://github.com/openclaw/openclaw/pull/95744) Related [#95743](https://github.com/openclaw/openclaw/issues/95743). Thanks [@parveshsaini](https://github.com/parveshsaini). - First-run setup now opens the credential prompt for a newly installed external provider instead of appearing to loop and leaving OpenAI selected. [#95792](https://github.com/openclaw/openclaw/pull/95792) Related [#95765](https://github.com/openclaw/openclaw/issues/95765). - Oversized or stalled provider catalogs now fail quickly with a clear error instead of hanging OpenClaw or consuming unbounded memory, while normal catalogs continue to load. [#95827](https://github.com/openclaw/openclaw/pull/95827) Thanks [@alix-007](https://github.com/alix-007). - Xiaomi Token Plan users can now use up to 128K output tokens with `mimo-v2.5` and `mimo-v2.5-pro` instead of being stopped at the outdated 32,000-token limit. [#95934](https://github.com/openclaw/openclaw/pull/95934) Thanks [@idootop](https://github.com/idootop). - Tool-heavy model responses can stream with less overhead while repeated tool-call IDs and encrypted reasoning details stay matched to the correct call across Google and OpenAI-compatible providers. [#95957](https://github.com/openclaw/openclaw/pull/95957) Thanks [@vincentkoc](https://github.com/vincentkoc). - Token-usage accounting is more reliable for bundled ACPX users because OpenClaw now includes ACPX 0.11.2's persistence fix by default, without a separate package override or manual client update. [#96124](https://github.com/openclaw/openclaw/pull/96124) Thanks [@vincentkoc](https://github.com/vincentkoc). - Ollama Cloud users can now find and select `glm-5.2:cloud` with its 1,000,000-token context window, reasoning, and tool support even when it is absent from the public model list. [11484f8](https://github.com/openclaw/openclaw/commit/11484f8a1483b7c42aa2971de2d88289fcef7046) - MiniMax image-understanding requests no longer fail before reaching the provider when a timeout is zero, negative, or extremely large; invalid values now use a normal or safe maximum wait. [4b6182e](https://github.com/openclaw/openclaw/commit/4b6182ee2a250005e0c25edfeae4db6ec59b7cb8) Thanks [@vincentkoc](https://github.com/vincentkoc). - Codex runs now follow the current fast-mode choice instead of carrying over an old speed tier, and the status line clearly shows when fast mode is automatic. [77012f9](https://github.com/openclaw/openclaw/commit/77012f9807851c662e064d05097497a25ab13505) Thanks [@vincentkoc](https://github.com/vincentkoc). - Codex-backed conversations now return to normal routing after automatic fast mode is cleared, preventing later turns or model changes from reusing a stale priority tier. [8afc1f7](https://github.com/openclaw/openclaw/commit/8afc1f770bbef30a4d2d9957ef26a685c508448c) - Fallback agent runs now honor each model's configured automatic fast-mode cutoff even when fast mode is overridden for the run, keeping fallback behavior aligned with the selected model policy. [efd3172](https://github.com/openclaw/openclaw/commit/efd3172662ce023eb8d6568b689361536edf06dd) - Live model-switch retries now preserve the original fast-mode cutoff for long-running sessions, while explicit fast mode avoids misleading automatic-cutoff progress messages. [d990115](https://github.com/openclaw/openclaw/commit/d990115d1972fdf4361884a29bbf8396f33e5cba) Thanks [@vincentkoc](https://github.com/vincentkoc). - Embedded agent runs now keep automatic fast mode working consistently through retries and progress updates without confusing it with a manually selected fast-mode setting. [cf1b6fe](https://github.com/openclaw/openclaw/commit/cf1b6fef4403bee7c206299efc4385a7fcb74375) Thanks [@vincentkoc](https://github.com/vincentkoc). - Fast-mode runs now keep their speed setting through model fallback retries and show the configured automatic threshold in status, avoiding inconsistent retry behavior and an unhelpful generic label. [aa3797c](https://github.com/openclaw/openclaw/commit/aa3797c8d0d74b4502d24852ce6baa70286f2f06) Thanks [@vincentkoc](https://github.com/vincentkoc). - Agent replies and scheduled cron runs now handle fast-mode fallback retries more reliably, keeping the state needed for the final attempt to finish or report progress correctly. [14e448e](https://github.com/openclaw/openclaw/commit/14e448e0e13db9f194ea16bb98e0f846a67769fd) Thanks [@vincentkoc](https://github.com/vincentkoc). - Users no longer see a fast-mode reset notice while model fallback attempts are still running; it appears only when the run reaches its final fallback attempt. [6eb72a8](https://github.com/openclaw/openclaw/commit/6eb72a830ece3e2b4c6c85e5a9c2b72b59e0dae9) - Users and operators now get clearer handling when a configured live model becomes unavailable because OpenClaw recognizes the provider's "selected model was not found" response as a model-not-found failure instead of a generic error. [2405d02](https://github.com/openclaw/openclaw/commit/2405d029d437ee58ab94da800a5b213bc6bf4628) Thanks [@vincentkoc](https://github.com/vincentkoc). - Qwen and vLLM now preserve existing chat-template settings consistently when thinking is switched on or off, and provider plugins can use the same tested helper. [2ba9d6e](https://github.com/openclaw/openclaw/commit/2ba9d6eabef9427a950bacc47f077200446cb865) Thanks [@vincentkoc](https://github.com/vincentkoc). - OpenAI-compatible proxy providers can handle thinking levels and legacy `reasoning_effort` fields more consistently, with plugin developers and provider maintainers using one documented normalization helper across OpenRouter, Kilocode, and the SDK. [35bafea](https://github.com/openclaw/openclaw/commit/35bafea757fab0386292951a3dc2a2d3514f370e) - Browser and Vite builds can now load the OpenAI ChatGPT Responses provider without a server-only dependency breaking the bundle, while WebSocket failures still appear normally. [8c8eb86](https://github.com/openclaw/openclaw/commit/8c8eb86fff6e843bd391808ceee249ac8c7f5fa5) Thanks [@vincentkoc](https://github.com/vincentkoc). - OpenRouter model scans now accept the same larger valid catalogs as runtime discovery while still rejecting oversized responses before they can consume unbounded memory. [ad3b2f4](https://github.com/openclaw/openclaw/commit/ad3b2f4b8827cd73b4c1a6c8288569c0966276fe) Thanks [@vincentkoc](https://github.com/vincentkoc). - OpenAI Responses users, including affected Bedrock Mantle GPT-5.x reasoning setups, now get one clean final answer with aligned saved transcripts and replay context instead of dozens of repeated cumulative copies. [#92399](https://github.com/openclaw/openclaw/pull/92399) Related [#91959](https://github.com/openclaw/openclaw/issues/91959). Thanks [@amersheeny](https://github.com/amersheeny), [@daimingnj](https://github.com/daimingnj), [@phoenixyy](https://github.com/phoenixyy), [@pigfoot](https://github.com/pigfoot). - Scheduled jobs and isolated sessions using opencode-go models now move stalled requests into configured timeout or fallback handling instead of hanging for minutes before ending with a generic `LLM request failed` error. [#93965](https://github.com/openclaw/openclaw/pull/93965) Related [#93610](https://github.com/openclaw/openclaw/issues/93610). Thanks [@forceconstant](https://github.com/forceconstant), [@zhangguiping-xydt](https://github.com/zhangguiping-xydt). ##### Session, memory, and trust continuity [Sessions](https://docs.openclaw.ai/concepts/session), [compaction](https://docs.openclaw.ai/concepts/compaction), [memory](https://docs.openclaw.ai/concepts/memory), [QMD-backed memory](https://docs.openclaw.ai/concepts/memory-qmd), and [Tool Search](https://docs.openclaw.ai/tools/tool-search) retain useful state more consistently, while [Matrix](https://docs.openclaw.ai/channels/matrix) recovery, [tool policies](https://docs.openclaw.ai/gateway/sandbox-vs-tool-policy-vs-elevated), and [approvals](https://docs.openclaw.ai/cli/approvals) stay attached to the intended trust boundary. - Affected agent conversations using OpenAI Responses can now recover and keep replying after a visible channel response leaves their saved history incomplete, instead of every later turn failing before a reply appears. [#84708](https://github.com/openclaw/openclaw/pull/84708) Thanks [@anyech](https://github.com/anyech). - When a Codex-backed agent produces unusually large tool output, saved and replayed conversations now keep its text within the usual size limit while leaving non-text content unchanged. [#87912](https://github.com/openclaw/openclaw/pull/87912) Thanks [@adrianip0204](https://github.com/adrianip0204). - Control UI conversations now stay visible and continue in the same session after a sleep, network drop, or Gateway reconnect instead of disappearing when the next message is sent. [#89017](https://github.com/openclaw/openclaw/pull/89017) Related [#87700](https://github.com/openclaw/openclaw/issues/87700). Thanks [@zhangguiping-xydt](https://github.com/zhangguiping-xydt), [@asicoe](https://github.com/asicoe). - Bundled Codex and Copilot integrations now keep mirrored chat history and transcript updates tied to the correct OpenClaw session as storage evolves, while existing file-backed active transcripts continue working during the migration. [#89518](https://github.com/openclaw/openclaw/pull/89518) Thanks [@jalehman](https://github.com/jalehman). - WebChat's current-session status now matches the conversation you are actually using, so the session identity, thinking level, token context, and cost details no longer come from the fallback `main` session. [#89800](https://github.com/openclaw/openclaw/pull/89800) Related [#89773](https://github.com/openclaw/openclaw/issues/89773). Thanks [@killo3967](https://github.com/killo3967), [@sweetcornna](https://github.com/sweetcornna). - Your conversation is less likely to lose its context after you press stop during automatic compaction because the compaction request is now cancelled too. [#89886](https://github.com/openclaw/openclaw/pull/89886) Related [#89868](https://github.com/openclaw/openclaw/issues/89868). Thanks [@lykeion-dev](https://github.com/lykeion-dev), [@openperf](https://github.com/openperf), [@vincentkoc](https://github.com/vincentkoc). - When cross-agent session access is blocked, OpenClaw now lists all required visibility, agent-to-agent, and allow-list settings, helping operators correct policy configuration instead of chasing a nonexistent agent failure. [#90489](https://github.com/openclaw/openclaw/pull/90489) Related [#90443](https://github.com/openclaw/openclaw/issues/90443). Thanks [@ramitrkar-hash](https://github.com/ramitrkar-hash), [@sahibzada-allahyar](https://github.com/sahibzada-allahyar), [@vincentkoc](https://github.com/vincentkoc). - `openclaw memory status` now shows an active light or REM dreaming phase instead of incorrectly reporting `Dreaming: off`, so operators can see that valid memory configurations are enabled. [#93113](https://github.com/openclaw/openclaw/pull/93113) Related [#67868](https://github.com/openclaw/openclaw/issues/67868). Thanks [@agentarclab](https://github.com/agentarclab), [@mrossit](https://github.com/mrossit). - Timed-out QMD memory searches now stop their background work when the agent moves on, preventing abandoned processes from continuing to consume CPU and memory. [#93394](https://github.com/openclaw/openclaw/pull/93394) Thanks [@alix-007](https://github.com/alix-007). - Repeated instructions sent after compaction now remain in the conversation, preventing lost turns, orphaned replies, and malformed history that some providers reject. [#94328](https://github.com/openclaw/openclaw/pull/94328) Thanks [@vincentkoc](https://github.com/vincentkoc), [@yetval](https://github.com/yetval). - Memory Wiki's Stale Pages report now leaves durable concept and synthesis pages out of freshness warnings, keeping attention on source and entity pages that may actually need review. [#94369](https://github.com/openclaw/openclaw/pull/94369) Thanks [@sunnyshu0925](https://github.com/sunnyshu0925), [@vincentkoc](https://github.com/vincentkoc). - Long embedded runs with recent progress are now less likely to be interrupted by stale-session recovery, while genuinely stalled runs can still be cleared so queued work continues. [#94701](https://github.com/openclaw/openclaw/pull/94701) Thanks [@imadal1n](https://github.com/imadal1n), [@mrclawfield](https://github.com/mrclawfield). - Ollama memory search now respects a configured smaller embedding dimension and keeps indexes for different dimensions separate, avoiding incompatible vectors being mixed together. [#94811](https://github.com/openclaw/openclaw/pull/94811) Thanks [@mushuiyu886](https://github.com/mushuiyu886). - Memory searches and targeted refreshes now stay connected to the correct OpenClaw session even when transcript filenames change or QMD exports use a different name. [#95087](https://github.com/openclaw/openclaw/pull/95087) Thanks [@jalehman](https://github.com/jalehman). - Long-running conversations with screenshots or other images now keep their continuity more consistently when OpenClaw makes room for new messages, instead of repeatedly filling up without moving the retained conversation forward. [#95128](https://github.com/openclaw/openclaw/pull/95128) Thanks [@yetval](https://github.com/yetval). - Windows users can now run QMD-backed memory indexing and search through configured absolute `memory.qmd.command` paths, including drive-letter and UNC locations, without OpenClaw stripping the path separators before launch. [#95274](https://github.com/openclaw/openclaw/pull/95274) Related [#92302](https://github.com/openclaw/openclaw/issues/92302). Thanks [@ardooken](https://github.com/ardooken), [@ly85206559](https://github.com/ly85206559). - Usage footers selected with `/usage full` or `/usage tokens` now remain visible after daily or idle session rollover, so users do not have to turn them on again. [#95322](https://github.com/openclaw/openclaw/pull/95322) Thanks [@litang9](https://github.com/litang9). - Follow-up replies, reactions, threaded messages, and status checks stay with the chat they belong to after webchat or system activity, while real channel switches still clear outdated routing details. [#95467](https://github.com/openclaw/openclaw/pull/95467) Thanks [@yetval](https://github.com/yetval). - Long-running main conversations now keep their prior context when users return after an overnight or delayed follow-up, rather than silently starting over after an otherwise normal completion. [#95472](https://github.com/openclaw/openclaw/pull/95472) Thanks [@xydt-tanshanshan](https://github.com/xydt-tanshanshan). - People with large session histories can list, preview, and find sessions without multi-second freezes, while older mixed-case session keys are still migrated at startup. [#95699](https://github.com/openclaw/openclaw/pull/95699) Thanks [@jalehman](https://github.com/jalehman), [@jzakirov](https://github.com/jzakirov). - Fixes delivered replies sometimes being saved to the wrong conversation history, or omitted from it, when operators use a custom or per-agent `session.store`, improving continuity and auditability for the intended session. [#95782](https://github.com/openclaw/openclaw/pull/95782) Related [#95781](https://github.com/openclaw/openclaw/issues/95781). Thanks [@youngting520](https://github.com/youngting520). - Saved session-memory summaries now leave out raw model tokens, tool-call blocks, media placeholders, role tags, and stale `NO_REPLY` markers so future conversations keep useful context. [#95791](https://github.com/openclaw/openclaw/pull/95791) Thanks [@sweetsophia](https://github.com/sweetsophia), [@vincentkoc](https://github.com/vincentkoc), [@yb0y](https://github.com/yb0y). - Long-running OpenAI sessions using Codex/ChatGPT OAuth can now compact without a separate API key, whether `/compact` is run manually or triggered automatically. [#95831](https://github.com/openclaw/openclaw/pull/95831) Related [#95693](https://github.com/openclaw/openclaw/issues/95693). Thanks [@sallyom](https://github.com/sallyom), [@yui-tien](https://github.com/yui-tien). - Long, tool-heavy sessions now compact oversized conversations instead of getting stuck when a large tool result appears at the end. [#95860](https://github.com/openclaw/openclaw/pull/95860) Related [#78478](https://github.com/openclaw/openclaw/issues/78478). Thanks [@jw8957](https://github.com/jw8957), [@wzhgba](https://github.com/wzhgba), [@yetval](https://github.com/yetval). - When `memory_search` is unavailable because the Node runtime lacks `node:sqlite`, OpenClaw now points users to a compatible runtime instead of sending them through unrelated embedding-provider troubleshooting. [#95916](https://github.com/openclaw/openclaw/pull/95916) Thanks [@rrrrrredy](https://github.com/rrrrrredy), [@vincentkoc](https://github.com/vincentkoc). - Developers and operators inspecting a compacted Copilot session now get its summary, before-and-after token counts, and session details instead of an incomplete result. [#96049](https://github.com/openclaw/openclaw/pull/96049) Thanks [@vincentkoc](https://github.com/vincentkoc). - The `/stop` and abort commands now keep stopping active runs, clearing queued followups, and ending related subagents promptly even when session keys need canonicalizing or abort metadata cannot be saved. [#96201](https://github.com/openclaw/openclaw/pull/96201) Thanks [@jalehman](https://github.com/jalehman). - Voice Wake upgrades now keep existing trigger phrases and routing rules working as OpenClaw moves them from retired settings files into the shared state database. [bdf81a8](https://github.com/openclaw/openclaw/commit/bdf81a825fa3ef66ad2c535c1eeb0bb4e31b6d1b) - Upgrades from older OpenClaw state layouts now preserve update notifications, check throttling, available-version records, and automatic-update attempt history as that state moves into SQLite. [eb00d49](https://github.com/openclaw/openclaw/commit/eb00d499d16feea600fceef92d575fa30f005649) Thanks [@vincentkoc](https://github.com/vincentkoc). - Plugin-channel conversations keep their intended session more reliably through startup, doctor checks, and state repairs, with older binding records migrated into OpenClaw's shared database. [9f888d9](https://github.com/openclaw/openclaw/commit/9f888d95e082d50380a66db18ee2e32683e688e0) - Windows memory-backed session syncing now keeps using the intended transcript file even when path formatting differs. [b3b5b08](https://github.com/openclaw/openclaw/commit/b3b5b08e67a26efd648c7c7d879e5487223cd796) Thanks [@vincentkoc](https://github.com/vincentkoc). - Embedded agent runs with a missing or blank session key now stay attached to the intended session instead of being sent through inconsistent session routing. [911f853](https://github.com/openclaw/openclaw/commit/911f853b7fc4d819e2175b001662a01eba30453d) Thanks [@vincentkoc](https://github.com/vincentkoc). - When a model guesses the wrong tool name, Tool Search and Code Mode now show how to find and retry the correct tool, reducing the risk that long-running sessions get stuck or lose durable memory during compaction. [#93374](https://github.com/openclaw/openclaw/pull/93374) Related [#92273](https://github.com/openclaw/openclaw/issues/92273). Thanks [@mushuiyu886](https://github.com/mushuiyu886), [@poison](https://github.com/poison), [@vincentkoc](https://github.com/vincentkoc). - Fixes assistant replies disappearing from webchat, Control UI, Feishu, and other embedded conversations after compaction, keeping refreshed chats readable and follow-up requests separate. [#95484](https://github.com/openclaw/openclaw/pull/95484) Related [#76729](https://github.com/openclaw/openclaw/issues/76729). Thanks [@maweibin](https://github.com/maweibin), [@njuboy11](https://github.com/njuboy11), [@vincentkoc](https://github.com/vincentkoc). - OpenClaw memory features now keep active, reset, and deleted transcript coverage aligned with configured session stores and agent ownership, making dreaming, QMD exports, indexing, and sync less likely to miss or misattribute conversation history. [#96162](https://github.com/openclaw/openclaw/pull/96162) Thanks [@jalehman](https://github.com/jalehman). - Gateway TLS setup now rejects blank certificate or key paths clearly or uses OpenClaw's defaults, avoiding confusing startup and certificate-generation failures while preserving valid paths. [#94054](https://github.com/openclaw/openclaw/pull/94054) Thanks [@miorbnli](https://github.com/miorbnli). - Configured plugin policies keep blocking or rewriting sensitive tool calls after Gateway registry changes, reloads, or later hook initialization instead of being silently skipped. [#94545](https://github.com/openclaw/openclaw/pull/94545) Thanks [@jesse-merhi](https://github.com/jesse-merhi). - Mobile operators with `operator.approvals` can now see and resolve chat-triggered exec approvals on the iOS device that started the request, including while the app is open, without relying only on push notifications. [#95175](https://github.com/openclaw/openclaw/pull/95175) Thanks [@joshavant](https://github.com/joshavant). - Control UI users now get the patched DOMPurify release, reducing exposure to the GHSA-cmwh-pvxp-8882 sanitizer vulnerability without changing how the interface behaves. [#95691](https://github.com/openclaw/openclaw/pull/95691) Thanks [@vincentkoc](https://github.com/vincentkoc). - "Always allow" approvals for plugin conversation bindings now carry over from the old settings file and are less likely to be lost or overwritten when multiple OpenClaw processes are running. [ae41b00](https://github.com/openclaw/openclaw/commit/ae41b009224b0a8e3a990912503258d4478fb4d0) Thanks [@vincentkoc](https://github.com/vincentkoc). - Matrix users now see that the active recovery key is required before a forced cross-signing reset can proceed, preventing a second reset from leaving encryption recovery and room-key backups unusable. [#95720](https://github.com/openclaw/openclaw/pull/95720) Related [#78396](https://github.com/openclaw/openclaw/issues/78396). Thanks [@jteddy](https://github.com/jteddy), [@vincentkoc](https://github.com/vincentkoc), [@xialonglee](https://github.com/xialonglee). ##### Slack router relay mode [Slack router relay mode](https://docs.openclaw.ai/channels/slack) gives managed and multi-gateway deployments a supported way to centralize incoming Slack traffic while preserving gateway ownership of mentions, threads, and replies. - Managed Slack deployments can now use a central router to send mentions and ongoing threads to the right OpenClaw gateway while replies still appear through Slack. [#94707](https://github.com/openclaw/openclaw/pull/94707) Thanks [@pash-openai](https://github.com/pash-openai), [@sjf-oa](https://github.com/sjf-oa). ##### Raft External Agent wake bridge The [Raft channel](https://docs.openclaw.ai/channels/raft) and [Raft plugin](https://docs.openclaw.ai/plugins/reference/raft) now support the local CLI wake path for External Agents. - Raft External Agent operators can now wake an OpenClaw agent when a workspace has pending work through the supported local CLI bridge, with named profiles and checks for missing CLI prerequisites. [#95497](https://github.com/openclaw/openclaw/pull/95497) Thanks [@vincentkoc](https://github.com/vincentkoc). ##### Official plugin installation and repair [Plugin management](https://docs.openclaw.ai/plugins/manage-plugins) and the [plugin inventory](https://docs.openclaw.ai/plugins/plugin-inventory) now cover more official integrations through normal installation, update, and repair workflows. - When `plugins.allow` uses a channel or package name instead of the real plugin id, startup guidance now identifies the unmatched entry and shows the discovered plugin ids needed to correct the configuration. [#68389](https://github.com/openclaw/openclaw/pull/68389) Related [#68352](https://github.com/openclaw/openclaw/issues/68352). Thanks [@aym9999](https://github.com/aym9999), [@jirboy](https://github.com/jirboy), [@lyfuci](https://github.com/lyfuci), [@pahuchi-joe](https://github.com/pahuchi-joe), [@zmxccxy](https://github.com/zmxccxy). - Plugin trust warnings for first-time or fresh installs now include a ready-to-copy `plugins.allow` example and commands to list or inspect plugin ids, so users can resolve the warning before trusting or reinstalling plugin code. [#78105](https://github.com/openclaw/openclaw/pull/78105) Related [#68780](https://github.com/openclaw/openclaw/issues/68780). Thanks [@jirboy](https://github.com/jirboy), [@pahuchi-joe](https://github.com/pahuchi-joe). - Codex migrations now work with standard global plugin installs because `openclaw migrate` can find the installed provider instead of failing with `Unknown migration provider`. [#89612](https://github.com/openclaw/openclaw/pull/89612) Related [#89609](https://github.com/openclaw/openclaw/issues/89609). Thanks [@mugabuga](https://github.com/mugabuga), [@zerone0x](https://github.com/zerone0x). - Plugin installs and updates recover from stale OpenClaw-managed dependency pins instead of failing with `npm EOVERRIDE`, without later synchronization downgrading or removing packages users installed explicitly. [#91786](https://github.com/openclaw/openclaw/pull/91786) Related [#91772](https://github.com/openclaw/openclaw/issues/91772). Thanks [@amknight](https://github.com/amknight), [@mkdelta221](https://github.com/mkdelta221). - Channel plugin developers can now carry native sender and conversation identifiers through hooks and selected exec workflows, giving integrations more precise routing without breaking existing sender and chat fields. [#91903](https://github.com/openclaw/openclaw/pull/91903) Thanks [@lanzhi-lee](https://github.com/lanzhi-lee), [@vincentkoc](https://github.com/vincentkoc). - Plugin discovery now repeats fewer blocking filesystem checks during startup, reducing avoidable cold-start work for bundled plugin trees, especially on slower Windows filesystems, without changing bundle discovery behavior. [#93919](https://github.com/openclaw/openclaw/pull/93919) Related [#76209](https://github.com/openclaw/openclaw/issues/76209). Thanks [@ml12580](https://github.com/ml12580), [@shenhonglong456-ai](https://github.com/shenhonglong456-ai). - Plugin Gateway methods now work through `openclaw gateway call` after registration, so plugin authors can use them from scripts and cron jobs instead of hitting an `unknown method` error. [#94154](https://github.com/openclaw/openclaw/pull/94154) Related [#94127](https://github.com/openclaw/openclaw/issues/94127). Thanks [@brycemurray](https://github.com/brycemurray), [@pick-cat](https://github.com/pick-cat), [@vincentkoc](https://github.com/vincentkoc). - ClawHub skill discovery and install checks are less likely to stall or crash OpenClaw because oversized or stalled marketplace responses are now stopped before they can exhaust memory. [#95226](https://github.com/openclaw/openclaw/pull/95226) Thanks [@alix-007](https://github.com/alix-007). - Pinned official plugins no longer stay on an old release when operators follow the repair advice from `openclaw doctor` or deep gateway status after an upgrade. [#95541](https://github.com/openclaw/openclaw/pull/95541) Thanks [@ooiuuii](https://github.com/ooiuuii), [@vincentkoc](https://github.com/vincentkoc). - Managed npm plugin updates are less likely to break work on a running gateway with missing-module errors, because the older plugin files remain available until a later gateway start cleans them up. [#95589](https://github.com/openclaw/openclaw/pull/95589) Thanks [@ooiuuii](https://github.com/ooiuuii), [@vincentkoc](https://github.com/vincentkoc). - Official plugin cards for supported brands now show recognizable icons in ClawHub and other catalogs, and plugin authors can provide marketplace artwork through the documented manifest field. [#95845](https://github.com/openclaw/openclaw/pull/95845) Thanks [@patrick-erichsen](https://github.com/patrick-erichsen). - Official plugin icons in ClawHub and other catalogs are no longer forced into the same hard-coded color, allowing Simple Icons to use its default artwork instead. [#95987](https://github.com/openclaw/openclaw/pull/95987) Thanks [@patrick-erichsen](https://github.com/patrick-erichsen). - Docker users now have an official `openclaw/openclaw` Docker Hub mirror alongside GHCR, with versioned beta releases kept from moving the stable `latest` and `main` aliases. [#97122](https://github.com/openclaw/openclaw/pull/97122) Thanks [@vincentkoc](https://github.com/vincentkoc). - Git-based OpenClaw installs now use the repository's pinned pnpm version even when another global pnpm or surrounding project package manager is present, so setup commands no longer run against the wrong package-manager environment. [bd74a62](https://github.com/openclaw/openclaw/commit/bd74a62118aa4774706359d9494116ded8c1f6e3) Thanks [@vincentkoc](https://github.com/vincentkoc). - ClawHub skill-card and update requests now complete or time out predictably even when they receive an unusually large timeout value. [8cd0c11](https://github.com/openclaw/openclaw/commit/8cd0c11227f6f4096d089cd6108d6f2ae31252b7) Thanks [@vincentkoc](https://github.com/vincentkoc). - Windows users can complete source installs without a llama.cpp setup step blocking or slowing them, and the installer restores their existing shell setting afterward. [ea9065b](https://github.com/openclaw/openclaw/commit/ea9065bc68dd4ff94495b85a7dcb4491cf41b67a) Thanks [@vincentkoc](https://github.com/vincentkoc). - More official channel, provider, and web-search plugins can now be installed or repaired through normal external package catalogs while still being recognized from their existing credentials. [#95683](https://github.com/openclaw/openclaw/pull/95683) Thanks [@vincentkoc](https://github.com/vincentkoc). ##### Channels and Messaging ##### Additional channel fixes Additional [Telegram](https://docs.openclaw.ai/channels/telegram) and channel configuration fixes cover narrower delivery and setup problems. - Telegram reply chains keep cached replies attached after context changes instead of failing when those cached replies are reused. [#82909](https://github.com/openclaw/openclaw/pull/82909) Thanks [@lidge-jun](https://github.com/lidge-jun). - Fixes Discord dropping an entire long reply with fenced code blocks when a closing code fence lands near the 2,000-character message limit. [#95661](https://github.com/openclaw/openclaw/pull/95661) Thanks [@ly-wang19](https://github.com/ly-wang19). - Slack operators can now store tokens and signing secrets as supported SecretRef inputs, while reads, writes, allowlist and target lookups, and setup checks use the resolved credentials instead of rejecting or misreading the references. [7da955f](https://github.com/openclaw/openclaw/commit/7da955fae4ca2083599aa33a1f93dbfff53cb187) Thanks [@vincentkoc](https://github.com/vincentkoc). - Channel capability checks now return a clear timeout when an integration stops responding, keeping troubleshooting from hanging in a terminal or automation run. [8ecdb97](https://github.com/openclaw/openclaw/commit/8ecdb97b636e4c3fcc6d142d217327404ae06581) Thanks [@vincentkoc](https://github.com/vincentkoc). ##### Providers and Models ##### Additional provider and model fixes Additional [model configuration](https://docs.openclaw.ai/providers/models) fixes improve selection, usage reporting, status output, and streaming. - After changing the default model, starting a fresh channel session with `/new` or `/reset` now uses the new default instead of silently reusing the previous cached model, while explicit `/model` overrides remain unchanged. [#77339](https://github.com/openclaw/openclaw/pull/77339) Related [#77322](https://github.com/openclaw/openclaw/issues/77322). Thanks [@mjamiv](https://github.com/mjamiv), [@zaynl](https://github.com/zaynl). - Behind HTTP or HTTPS proxies, Codex/OpenAI usage and quota checks in `openclaw status --usage --json` and the Control UI now retrieve usage windows instead of failing when chatgpt.com is unreachable directly. [#93943](https://github.com/openclaw/openclaw/pull/93943) Related [#78714](https://github.com/openclaw/openclaw/issues/78714). Thanks [@tnzgit](https://github.com/tnzgit), [@turbotheturtle](https://github.com/turbotheturtle). - `/status` now keeps the active model and how to clear a pinned choice on one compact line, so Discord and other chat users can scan model status without a multi-line explanation. [#95797](https://github.com/openclaw/openclaw/pull/95797) Thanks [@solvely-colin](https://github.com/solvely-colin). - Anthropic streaming responses now keep interleaved text, thinking, and tool-call updates …

openclaw-barnacle Bot added docs Improvements or additions to documentation channel: telegram Channel integration: telegram size: S triage: needs-pr-context Candidate: external PR body lacks required problem context or evidence. labels Jun 20, 2026

openclaw-barnacle Bot removed the triage: needs-pr-context Candidate: external PR body lacks required problem context or evidence. label Jun 20, 2026

snowzlmbot mentioned this pull request Jun 20, 2026

fix(telegram): render progress draft rows as plain readable text #95007

Merged

clawsweeper Bot mentioned this pull request Jun 20, 2026

Show Telegram progress placeholder when progress-mode answer drafts are suppressed #95344

Closed

snowzlmbot force-pushed the fix/telegram-preview-placeholder-95004 branch from 209955b to 1ab0ba3 Compare June 21, 2026 09:01

snowzlmbot force-pushed the fix/telegram-preview-placeholder-95004 branch from 1ab0ba3 to 1e6af44 Compare June 21, 2026 11:57

snowzlmbot and others added 5 commits June 21, 2026 07:17

fix(telegram): materialize streaming progress placeholders

7dabe25

fix(telegram): cancel delayed progress drafts before final

a1f9a4c

fix(telegram): satisfy progress placeholder lint

917a7e5

fix(telegram): cancel delayed draft preview on clear

f953287

refactor(telegram): simplify delayed preview flush

1c1c068

obviyus force-pushed the fix/telegram-preview-placeholder-95004 branch from d584cbe to 1c1c068 Compare June 21, 2026 14:17

obviyus merged commit 6441e56 into openclaw:main Jun 21, 2026
30 checks passed

snowzlmbot mentioned this pull request Jun 21, 2026

feat(telegram): unify progress fallback with assistant preview lane #95573

Closed

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

📡 Upstream Digest — 2026-06-21 15:46 UTC curtismercier/openclaw-mods#1123

Open

This was referenced Jun 21, 2026

feat(mcp): opt-in injectCallerContext for bundle MCP remote servers #75118

Open

docs: add missing breakPreference field to blockStreamingChunk config example #76094

Closed

fix(telegram): keep tool progress after non-final commentary #90997

Closed

github-actions Bot mentioned this pull request Jul 1, 2026

chore: bump openclaw/openclaw version from v2026.6.10 to v2026.6.11 Docker-Hub-sirmark/docker-openclaw#35

Merged

clawsweeper Bot mentioned this pull request Jul 2, 2026

fix(telegram): distinguish and render streamed reasoning/commentary progress lanes #98907

Merged

github-actions Bot mentioned this pull request Jul 6, 2026

chore(openclaw): bump pinned version v2026.5.28 → v2026.6.11 Evans-Software-Solutions-Limited/axel-saas#121

Open

clawsweeper Bot mentioned this pull request Jul 13, 2026

Feature: Processing indicator message for Telegram (send ⌛️ while thinking, delete on reply) #6946

Closed

Uh oh!

Uh oh!

Conversation

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

Uh oh!

What Problem This Solves

Related Work / Scope Boundary

Summary

Product decision encoded

Latest timer cleanup fix evidence

Live Telegram Bot API timer cleanup proof

Evidence

Native Telegram Bot API proof

Telegram draft lifecycle proof

Uh oh!

snowzlmbot commented Jun 20, 2026

Uh oh!

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

Uh oh!

Uh oh!

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

Uh oh!

Uh oh!

snowzlmbot commented Jun 20, 2026

Uh oh!

snowzlmbot commented Jun 20, 2026

Uh oh!

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

Uh oh!

Uh oh!

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

Uh oh!

Uh oh!

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

Uh oh!

Uh oh!

snowzlmbot commented Jun 20, 2026

Uh oh!

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

Uh oh!

Uh oh!

chatgpt-codex-connector Bot commented Jun 20, 2026

Uh oh!

snowzlmbot commented Jun 20, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jun 20, 2026

Uh oh!

snowzlmbot commented Jun 21, 2026

Uh oh!

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

Uh oh!

Uh oh!

snowzlmbot commented Jun 21, 2026

Uh oh!

snowzlmbot commented Jun 21, 2026

Uh oh!

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

Uh oh!

Uh oh!

Uh oh!

obviyus commented Jun 21, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

snowzlmbot commented Jun 20, 2026 •

edited

Loading

clawsweeper Bot commented Jun 20, 2026 •

edited

Loading

clawsweeper Bot commented Jun 20, 2026 •

edited

Loading

clawsweeper Bot commented Jun 20, 2026 •

edited

Loading

snowzlmbot commented Jun 20, 2026 •

edited

Loading

clawsweeper Bot commented Jun 20, 2026 •

edited

Loading

snowzlmbot commented Jun 20, 2026 •

edited

Loading

clawsweeper Bot commented Jun 21, 2026 •

edited

Loading

clawsweeper Bot commented Jun 21, 2026 •

edited

Loading