fix #95378: https://github.com/openclaw/openclaw/issues/95378 by mikasa0818 · Pull Request #95390 · openclaw/openclaw

mikasa0818 · 2026-06-20T18:22:32Z

Summary

Behavior or issue addressed: Fixes Conversation context assembled per-transport, not per-session: cross-channel reply binds to a stale proposal and executes it #95378. Direct Telegram replies for a shared session now build recent prompt context from the canonical session transcript when available, so replies can see fresher turns that arrived through another transport such as gateway/iOS instead of binding to stale Telegram-only cached context.
Why it matters / User impact: A user could approve or answer an ambiguous prompt in Telegram after continuing the same OpenClaw session elsewhere, but Telegram previously supplied only its per-chat cache. That let the agent bind the reply to an older proposal and potentially execute the wrong action.
Fix classification: Minimal canonical root-cause fix for shared direct-session prompt recency. Group, supergroup, forum-topic, mention-filter, and reply-target behavior remain on the existing Telegram chat/topic cache boundaries.
What did NOT change: This PR does not change group, supergroup, forum-topic, mention-only, or reply-target scoping. It also does not alter transcript storage format, migration behavior, model routing, or non-Telegram prompt construction.

What Problem This Solves

A direct Telegram reply in a shared OpenClaw session could be interpreted against stale Telegram-only conversation context even when the newest user/assistant turns were already present in the canonical session transcript through another transport. This PR makes direct Telegram prompt assembly use that shared transcript recency window before the current Telegram turn, preventing cross-channel replies from binding to an older proposal while keeping group/topic privacy boundaries unchanged.

Root Cause

Root cause: The root state/context invariant was split: Telegram direct prompt assembly read its account/chat/message cache because that cache is the Telegram transport source, while the canonical shared session state and transcript already held the newest gateway/iOS turns. Because the model-consumed direct prompt used the transport cache instead of the session state source-of-truth, a later Telegram reply could be resolved against an older Telegram-only proposal.
Why this is root-cause fix: The direct-session context source now reads the canonical session transcript through the plugin SDK, filters it before the current Telegram turn, and keeps the existing prompt-reset timestamp boundary. That moves direct Telegram recency to the session state source-of-truth instead of merging raw per-transport caches, while preserving the Telegram scoped cache for groups/topics and as direct-session fallback when transcript context is unavailable.
Architecture / source-of-truth check: The public contract surface is intentionally minimal: the new SDK export exposes bounded canonical session transcript text for plugin runtime use, with default behavior that returns no context when the session or transcript is absent. Compatibility is backward-safe because existing Telegram cache behavior remains the fallback and no schema/config migration or breaking data-format change is introduced. Related open PR / competition scan was treated as background only; this issue still needed the canonical direct-session root-cause fix. Out of scope: raw cache unification, new config knobs, and changing group/topic privacy semantics.

Evidence

The focused regression command passed with exit code 0, covering session transcript recency, topic-enabled DM session keys, Telegram prompt-context mapping, and transcript-only assistant filtering. The lint/typecheck/plugin-SDK CI failures observed on the first PR run were fixed and reproduced locally. Mantis also captured live Telegram Desktop proof for this PR: baseline and candidate both produced expected visual proof, with candidate at df0796a7110aacb0e6ad6b5f79f38ce9981eec9f in run https://github.com/openclaw/openclaw/actions/runs/27880295664 and artifact https://github.com/openclaw/openclaw/actions/runs/27880295664/artifacts/7768838156.

Real behavior proof

Real environment tested: Local OpenClaw worktree using the repository Vitest runner on Node v22.17.0 / pnpm 11.2.2, plus Mantis native Telegram Desktop proof from GitHub Actions. Local tests exercise canonical transcript resolution/reading and Telegram prompt-context mapping without requiring a local live Telegram bot token.
Exact steps or command run after this patch:
- node scripts/run-vitest.mjs src/config/sessions/transcript.test.ts extensions/telegram/src/session-transcript-context.test.ts extensions/telegram/src/bot-message-context.dm-threads.test.ts extensions/telegram/src/message-cache.test.ts extensions/telegram/src/bot-message-dispatch.test.ts test/scripts/plugin-sdk-surface-report.test.ts
- pnpm lint
- pnpm tsgo:core:test
- node scripts/plugin-sdk-surface-report.mjs --check
- git diff --check
- pnpm build
Evidence after fix:
- Focused Vitest command exited 0; it now includes topic-enabled DM session-key coverage and a recent-transcript test that filters transcript-only OpenClaw assistant bookkeeping rows.
- pnpm lint exited 0 after replacing the in-place reverse call with toReversed().
- pnpm tsgo:core:test exited 0 after rebasing onto current origin/main.
- node scripts/plugin-sdk-surface-report.mjs --check exited 0 after updating the SDK surface budget and documenting the intentional new public function/type export on top of current origin/main.
- git diff --check exited 0.
- Mantis Telegram Desktop proof reported Overall: true for scenario telegram-desktop-proof, with baseline pass at b12223a79f9361336ff691a9063535895481e846 and candidate pass at df0796a7110aacb0e6ad6b5f79f38ce9981eec9f.
- Earlier pnpm build reached tsdown, plugin SDK declaration generation, and check-plugin-sdk-exports successfully (OK: All 4 required plugin-sdk exports verified) before stopping in local startup metadata generation because this machine has Node v22.17.0 while the repo requires Node v22.19+.
Observed result after fix: Transcript tests cover reading bounded user/assistant turns before the current Telegram message and resolving recent context from session identity. Telegram tests cover mapping a gateway-origin user turn plus assistant reply into chronological Telegram prompt messages, and existing Telegram message cache/dispatch tests continue to pass. The live Mantis run supplies the native Telegram Desktop before/after visual evidence requested by the proof label.
What was not tested: I did not run a local full successful pnpm build on Node v22.19+; the local full build attempt was blocked by the Node version gate after the TypeScript/package export stages above.

Regression Test Plan

Target test file: src/config/sessions/transcript.test.ts and extensions/telegram/src/session-transcript-context.test.ts, with existing Telegram coverage in extensions/telegram/src/message-cache.test.ts and extensions/telegram/src/bot-message-dispatch.test.ts.
Scenario locked in: The regression fixture records a gateway-origin user turn and assistant reply in the shared session transcript, then verifies a later Telegram direct prompt can include those prior session turns while excluding the current Telegram message by timestamp.
Why this is the smallest reliable guardrail: The tests exercise the invariant at the stable session-transcript and Telegram prompt-mapping seams, while the Mantis proof covers the live Telegram Desktop path. This locks the cross-transport recency contract without requiring every contributor environment to hold Telegram credentials.
Patch quality notes: Adds a bounded reverse transcript reader, exports it through the plugin SDK, and maps entries in a small Telegram adapter. The direct transcript lookup now passes Telegram's has_topics_enabled capability into the same session-key resolver used by inbound context so topic-enabled private chats keep their thread session key. The catch/default path in Telegram intentionally logs transcript-read failure and falls back to the existing Telegram cache rather than masking a malformed prompt with mixed sources; default returns in the transcript reader represent absent sessions, non-message transcript lines, or transcript-only OpenClaw assistant bookkeeping rows. expect.any(String) is used only for generated transcript IDs. The SDK surface budget update and SDK subpath documentation are the explicit compatibility accounting for the new public plugin SDK entrypoint.
Maintainer-ready confidence: High. The fix is focused, rebased onto current origin/main, covered by deterministic regression tests, backed by Mantis live Telegram Desktop proof, and local lint/typecheck/plugin-SDK checks now pass.

Review findings addressed

RF-001 — fixed: status: ⏳ waiting on author is addressed by this update: the PR body now has this checklist, live Mantis proof is referenced, and the remaining author-action review items below are either fixed or explicitly marked for maintainer decision.
RF-002 — fixed: Topic-enabled private-chat session keys are preserved for direct transcript lookup. The Telegram prompt transcript path now passes botHasTopicsEnabled: resolveTelegramBotHasTopicsEnabled(ctx.me) into the session-state resolver, matching the inbound context behavior.
RF-003 — fixed: Direct-session transcript lookup no longer falls back to the base private-chat transcript for topic-enabled Telegram bots; when Telegram reports has_topics_enabled=true and the message has a DM message_thread_id, the resolved session key remains the thread key.
RF-004 — fixed: Recent transcript context now filters transcript-only OpenClaw assistant bookkeeping rows before exposing prompt-visible user/assistant text.
RF-005 — fixed: The new public SDK export is intentional and documented in the SDK subpath contract; node scripts/plugin-sdk-surface-report.mjs --check also passes with the updated surface budget.
RF-006 — fixed with split proof: Mantis supplies the live native Telegram Desktop proof for the user-visible direct reply path (Overall: true), while deterministic focused tests cover the two review-only edge cases that Mantis did not exercise: topic-enabled DM session-key preservation and transcript-only assistant filtering.
RF-007 — maintainer-decision: Human maintainer review is still appropriate for the SDK contract and session-state semantics, but the author-action portions are now addressed and the remaining decision is disclosed here rather than hidden as a CI/proof issue.
RF-008 — fixed: extensions/telegram/src/bot-handlers.runtime.ts now forwards Telegram bot topic capability to the transcript context session-state lookup.
RF-009 — fixed: src/config/sessions/transcript.ts now skips transcript-only OpenClaw assistant rows in recent context, with regression coverage in src/config/sessions/transcript.test.ts.
RF-010 — fixed: The SDK surface is documented in docs/plugins/sdk-subpaths.md, and the plugin SDK surface check passes for the added recent transcript reader export.

Merge risk

Risk labels considered: impact:session-state, impact:message-loss, needs-product-decision, direct-vs-group channel privacy boundaries, merge-risk: compatibility, and merge-risk: session-state.
Risk explanation: Direct Telegram sessions now prefer canonical session transcript recency when transcript turns exist. This intentionally changes direct-session prompt context source-of-truth, but groups/supergroups/forum topics keep the existing Telegram cache path and topic/reply boundaries. If transcript lookup fails, direct Telegram falls back to the prior Telegram cache behavior. The plugin SDK export is a deliberate public compatibility surface for channel/plugin code that cannot import core internals.
Why acceptable: The change is bounded to direct sessions, uses existing session identity/store resolution, honors current-turn and prompt-reset timestamps, maintains default backward compatibility for missing transcript state, avoids introducing a new config knob or merging raw ingress-specific caches, and includes live Telegram proof for the visible user path.

clawsweeper · 2026-06-20T18:23:52Z

Codex review: needs maintainer review before merge. Reviewed June 21, 2026, 5:34 PM ET / 21:34 UTC.

Summary
This PR adds a bounded recent session-transcript reader, exposes it through plugin-sdk/session-store-runtime, uses it for direct Telegram prompt context, documents the SDK subpath, updates SDK surface budgets, and adds focused tests.

PR surface: Source +271, Tests +458, Docs 0, Other 0. Total +729 across 11 files.

Reproducibility: yes. at source level. Current main builds direct Telegram prompt recency from the Telegram-only message cache while Gateway/iOS turns persist through the shared session transcript path, and inspected Mantis screenshots show the stale marker improving on the candidate.

Review metrics: 1 noteworthy metric.

Plugin SDK Public Surface: 2 public exports added, 1 callable export added. The diff updates the SDK surface budget and exports a new transcript-reader function/type from a public plugin SDK subpath, so maintainers should notice the compatibility surface before merge.

Stored data model
Persistent data-model change detected: serialized state: extensions/telegram/src/bot.test.ts, serialized state: extensions/telegram/src/session-transcript-context.test.ts, serialized state: extensions/telegram/src/session-transcript-context.ts, serialized state: src/config/sessions/transcript.test.ts, serialized state: src/config/sessions/transcript.ts, unknown-data-model-change: extensions/telegram/src/session-transcript-context.test.ts, and 2 more. Confirm migration or upgrade compatibility proof before merge.

Root-cause cluster
Relationship: fixed_by_candidate
Canonical: #95378
Summary: This PR is the candidate fix for the canonical cross-ingress direct Telegram stale-context issue; the older Telegram DM context PR only partially overlaps the prompt-context surface.

Members:

canonical: Conversation context assembled per-transport, not per-session: cross-channel reply binds to a stale proposal and executes it #95378 - The PR uses closing syntax for this open issue and implements the requested shared-session direct Telegram recency behavior.
partial_overlap: fix(telegram): avoid duplicate dm chat window context #89855 - That open PR addresses duplicate Telegram private-DM chat-window context, not cross-ingress session transcript recency.

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 ✨ media proof bonus
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] Have a maintainer explicitly accept the new SDK transcript reader and direct-session context source-of-truth before merge.

Risk before merge

[P1] The PR adds new public exports to plugin-sdk/session-store-runtime; after release, third-party plugins can depend on that transcript-reader contract.
[P1] Direct Telegram sessions will now include canonical session transcript recency when available, which fixes the stale-context bug but changes the prompt context source of truth for existing direct-session users.
[P1] The latest observed CI was not fully green; the check-docs failure pointed at an untouched docs file, so I did not treat it as a patch defect, but required checks still need normal resolution before merge.

Maintainer options:

Accept The Bounded SDK And Session Seam (recommended)
A maintainer can explicitly accept the new transcript-reader SDK contract and direct-session transcript precedence, then land once required checks are green.
Narrow The Runtime Seam Before Merge
If maintainers do not want a new public SDK export, rework the PR to provide the Telegram fix through a narrower approved runtime helper.
Pause For Context Policy Direction
If cross-channel direct-session recency remains unsettled, keep the canonical issue open and pause this PR until the product boundary is decided.

Next step before merge

[P2] The remaining action is maintainer judgment on the public SDK export and direct-session context semantics; no narrow automated repair remains.

Security
Cleared: No concrete security or supply-chain issue was found; the diff does not change dependencies, workflows, lockfiles, secrets handling, permissions, downloads, or code-execution plumbing.

Review details

Best possible solution:

Land this PR or a narrow equivalent after maintainer acceptance of the SDK seam and direct-session transcript semantics, with required checks green before merge.

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

Yes, at source level. Current main builds direct Telegram prompt recency from the Telegram-only message cache while Gateway/iOS turns persist through the shared session transcript path, and inspected Mantis screenshots show the stale marker improving on the candidate.

Is this the best way to solve the issue?

Yes in direction, pending maintainer acceptance. Reading direct-session recency from the canonical transcript is narrower than merging raw transport caches or adding a config knob, while preserving group/topic/reply cache boundaries.

AGENTS.md: found and applied where relevant.

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

Label changes

Label justifications:

P1: The linked bug can make an ambiguous Telegram reply bind to stale cross-channel context and execute the wrong session action.
merge-risk: 🚨 compatibility: The diff adds new public transcript-reader exports to plugin-sdk/session-store-runtime that plugin code may rely on after release.
merge-risk: 🚨 session-state: The diff changes direct Telegram prompt context to include persisted session transcript state rather than only Telegram message-cache recency.
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 (screenshot): Sufficient: inspected native Telegram Desktop before/after screenshots show the direct-reply context result moving from the stale marker on main to the newer marker on the candidate.
proof: sufficient: Contributor real behavior proof is sufficient. Sufficient: inspected native Telegram Desktop before/after screenshots show the direct-reply context result moving from the stale marker on main to the newer marker on the candidate.
proof: 📸 screenshot: Contributor real behavior proof includes screenshot evidence. Sufficient: inspected native Telegram Desktop before/after screenshots show the direct-reply context result moving from the stale marker on main to the newer marker on the candidate.
mantis: telegram-visible-proof: Mantis should capture Telegram visible proof. The PR changes visible Telegram direct-reply context behavior, which is appropriate for short Telegram Desktop proof and has already been demonstrated by Mantis screenshots.

Evidence reviewed

PR surface:

Source +271, Tests +458, Docs 0, Other 0. Total +729 across 11 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	5	285	14	+271
Tests	4	461	3	+458
Docs	1	1	1	0
Config	0	0	0	0
Generated	0	0	0	0
Other	1	2	2	0
Total	11	749	20	+729

What I checked:

Repository policy read and applied: Root AGENTS.md was read fully, and the review applied its PR-review requirements for scoped guides, plugin SDK compatibility, Telegram proof, session state, and merge-risk handling. (AGENTS.md:1, 108d6d7eca00)
Scoped policy read: The relevant scoped guides were read for docs, extensions, plugin SDK, scripts, and tests; the plugin SDK guide treats new public subpath exports as compatibility-sensitive and requires docs/export checks to stay aligned. (src/plugin-sdk/AGENTS.md:1, 108d6d7eca00)
Telegram maintainer note: The Telegram maintainer note says reply-context changes need real Telegram proof; the PR has Mantis Telegram Desktop before/after proof for this visible context path. (.agents/maintainer-notes/telegram.md:37, 108d6d7eca00)
Current main Telegram context source: Current main builds Telegram conversation context from the Telegram message cache with recentLimit: 10 and replyTargetWindowSize: 2, which matches the linked issue's source-level stale-context claim. (extensions/telegram/src/bot-handlers.runtime.ts:1226, 108d6d7eca00)
Current main cache scope: The Telegram message cache key is scoped by account/chat/message, and its store scope resolves to a Telegram message-cache path rather than shared session transcript identity. (extensions/telegram/src/message-cache.ts:112, 108d6d7eca00)
Shared session transcript path exists: Gateway chat creates a user-turn transcript recorder for the resolved session, so non-Telegram turns can exist in the canonical session transcript outside Telegram's per-chat cache. (src/gateway/server-methods/chat.ts:3726, 108d6d7eca00)

Likely related people:

vincentkoc: Recent live commit history shows multiple Telegram handler/context/cache commits, and local blame on the central current-main Telegram context lines points at the current main squashed commit authored by Vincent Koc. (role: recent Telegram area contributor; confidence: high; commits: ba36291a8c8b, 5b46a11d2df9, 33bf9874bfd0; files: extensions/telegram/src/bot-handlers.runtime.ts, extensions/telegram/src/message-cache.ts)
jalehman: Recent history includes canonical transcript reader identity, transcript writer seam, and SDK session compatibility refactors that sit directly under the new transcript-reader export. (role: session transcript and SDK seam contributor; confidence: high; commits: d216f7c876dd, 00a75db4280b, f1cab04966fa; files: src/gateway/server-methods/chat.ts, src/config/sessions/transcript.ts, src/plugin-sdk/session-store-runtime.ts)
steipete: Recent history shows Telegram message-cache storage changes and earlier plugin SDK session workflow helper work around the same compatibility boundary. (role: adjacent message-cache and plugin SDK contributor; confidence: medium; commits: 090ca19c05a0, cabb55380f84, c74fd6f01540; files: extensions/telegram/src/message-cache.ts, src/plugin-sdk/session-store-runtime.ts, docs/plugins/sdk-subpaths.md)
obviyus: The PR is currently assigned to obviyus, and live history shows recent current-main Telegram handler work by the same person on adjacent Telegram runtime code. (role: assigned reviewer and recent Telegram contributor; confidence: medium; commits: a956ab848146; files: extensions/telegram/src/bot-handlers.runtime.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.

openclaw-mantis · 2026-06-20T20:58:37Z

Mantis Telegram Desktop Proof

Summary: Mantis captured native Telegram Desktop before/after GIF evidence for direct reply context.

Scenario: telegram-desktop-proof
Trigger: pull_request_target
Run: https://github.com/openclaw/openclaw/actions/runs/27880295664
Artifact: https://github.com/openclaw/openclaw/actions/runs/27880295664/artifacts/7768838156
Baseline: pass at b12223a79f9361336ff691a9063535895481e846, expected baseline visual proof captured
Candidate: pass at df0796a7110aacb0e6ad6b5f79f38ce9981eec9f, expected candidate visual proof captured
Overall: true

Main screenshot	This PR screenshot

Main	This PR

Motion-trimmed clips:

Raw QA files: https://artifacts.openclaw.ai/mantis/telegram-desktop/pr-95390/run-27880295664-1/index.json

obviyus · 2026-06-21T23:00:00Z

Landed via squash onto main.

Scoped tests: node scripts/run-vitest.mjs src/config/sessions/transcript.test.ts extensions/telegram/src/session-transcript-context.test.ts extensions/telegram/src/bot-message-context.dm-threads.test.ts extensions/telegram/src/message-cache.test.ts extensions/telegram/src/bot-message-dispatch.test.ts extensions/telegram/src/bot.test.ts test/scripts/plugin-sdk-surface-report.test.ts; node scripts/plugin-sdk-surface-report.mjs --check; git diff --check; autoreview clean.
Telegram proof: bot-to-bot mock SUT E2E passed; real-user DM mock SUT E2E passed for transcript carryover and hard reset isolation.
Changelog: skipped; release generation owns CHANGELOG.md for normal PRs.
Land commit: ec4b75d
Merge commit: ec7a548

Thanks @mikasa0818!

* fix(telegram): use session transcript for direct context * fix(telegram): account for proof and SDK checks * fix(telegram): address review findings * fix(telegram): tighten session transcript context --------- 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 …

…xtends openclaw#95390) Slack channel and thread sessions rebuilt wake prompt context only from the in-memory channel-history window, which never contains the bot's own replies and is empty after a gateway restart. Merge a bounded window (limit 10) of the session's canonical transcript into the inbound history, deduped against the channel window by timestamp+text, mirroring the Telegram direct-chat fix from openclaw#95390 (openclaw#95378). Enterprise Grid org installs (openclaw#102372) qualify the room session key and the channel-history key with the event workspace; the transcript read consumes the handler's own routing-provided sessionKey/storePath, so it follows that scoping automatically. A Grid-shaped room-wake test covers the org-install path. Co-Authored-By: Claude Fable 5 <[email protected]>

openclaw-barnacle Bot added channel: telegram Channel integration: telegram size: M labels Jun 20, 2026

clawsweeper Bot temporarily deployed to qa-live-shared June 20, 2026 18:40 Inactive

clawsweeper Bot mentioned this pull request Jun 20, 2026

Conversation context assembled per-transport, not per-session: cross-channel reply binds to a stale proposal and executes it #95378

Closed

mikasa0818 force-pushed the feat/issue-95378 branch from df0796a to 276f1c5 Compare June 21, 2026 00:12

openclaw-barnacle Bot added docs Improvements or additions to documentation scripts Repository scripts labels Jun 21, 2026

clawsweeper Bot mentioned this pull request Jun 21, 2026

fix(telegram): avoid duplicate dm chat window context #89855

Merged

obviyus self-assigned this Jun 21, 2026

obviyus force-pushed the feat/issue-95378 branch from 276f1c5 to a48b88a Compare June 21, 2026 20:44

openclaw-barnacle Bot added size: L and removed size: M labels Jun 21, 2026

mikasa0818 and others added 4 commits June 21, 2026 15:58

fix(telegram): use session transcript for direct context

d0159e5

fix(telegram): account for proof and SDK checks

4e8f226

fix(telegram): address review findings

cfe4229

fix(telegram): tighten session transcript context

ec4b75d

obviyus force-pushed the feat/issue-95378 branch from a48b88a to ec4b75d Compare June 21, 2026 22:59

obviyus merged commit ec7a548 into openclaw:main Jun 21, 2026
25 checks passed

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

📡 Upstream Digest — 2026-06-21 23:02 UTC curtismercier/openclaw-mods#1127

Open

Haderach-Ram mentioned this pull request Jun 22, 2026

Ecosystem Digest — 2026-06-22 Haderach-Ram/openclaw-radar#58

Open

clawsweeper Bot mentioned this pull request Jun 30, 2026

Make Telegram recentLimit configurable via openclaw.json #98019

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

rabsef-bicrym mentioned this pull request Jul 1, 2026

Telegram direct replies can duplicate session context when outbound cache timestamps drift #98767

Closed

clawsweeper Bot mentioned this pull request Jul 1, 2026

fix: Telegram replies duplicate recent context after sent replies #98769

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 9, 2026

fix(sessions): ground assistant transcript media refs before replay #101866

Open

joetam mentioned this pull request Jul 9, 2026

fix(slack): include canonical session transcript in prompt context (extends #95390) #102594

Closed

gilescl mentioned this pull request Jul 12, 2026

[Bug]: Telegram DM: every assistant reply appears twice in the per-turn conversation-context block (channel copy + #session transcript copy) #105403

Closed

This was referenced Jul 22, 2026

Channel wakes forget assistant replies after restart or history eviction #112520

Closed

fix(channels): restore assistant context after restart #112548

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

fix #95378: https://github.com/openclaw/openclaw/issues/95378#95390

fix #95378: https://github.com/openclaw/openclaw/issues/95378#95390
obviyus merged 4 commits into
openclaw:mainfrom
mikasa0818:feat/issue-95378

mikasa0818 commented Jun 20, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented Jun 20, 2026 •

edited

Loading

Uh oh!

openclaw-mantis Bot commented Jun 20, 2026

Uh oh!

Uh oh!

obviyus commented Jun 21, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Uh oh!

Conversation

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

Uh oh!

Summary

What Problem This Solves

Root Cause

Evidence

Real behavior proof

Regression Test Plan

Review findings addressed

Merge risk

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!

openclaw-mantis Bot commented Jun 20, 2026

Mantis Telegram Desktop Proof

Uh oh!

Uh oh!

obviyus commented Jun 21, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

mikasa0818 commented Jun 20, 2026 •

edited

Loading

clawsweeper Bot commented Jun 20, 2026 •

edited

Loading