fix(memory): abort orphaned qmd search subprocess when memory_search times out by Alix-007 · Pull Request #93394 · openclaw/openclaw

Alix-007 · 2026-06-15T18:11:49Z

What Problem This Solves

The memory_search tool enforces a 15s deadline, but with the QMD memory backend that deadline only stops the caller — the spawned qmd query/qmd search subprocess keeps running for the full QMD command timeout (memory.qmd.limits.timeoutMs, whose embed-heavy default was raised to 600s in PR #87572). So after the agent has already given up and moved on, an orphaned qmd process keeps churning for up to ~10 minutes, leaking CPU/memory on every timed-out search. PR #91742 fixed exactly this orphaned-work leak for the builtin backend by wiring an AbortSignal through MemorySearchManager.search(), but the QMD manager — the other backend behind the same interface — silently ignored the signal, so the leak was still live for QMD users. This PR closes that gap so every supported QMD search path kills its subprocess when the caller's deadline fires.

Evidence

Proven against the real exported runCliCommand (the single spawn point for all qmd search subprocesses) via node --import tsx against a real OS subprocess on PR head 6ee870e0ca:

[B] child OS pid: 598162 alive before abort: true
[B] runCliCommand rejected after 17 ms with: "memory_search timed out after 15s"
[B] child pid 598162 alive AFTER abort: false
RESULT: PASS - abort killed the real subprocess and rejected promptly (no orphan).

The real OS process is confirmed alive before abort and dead after abort (via process.kill(pid, 0)), and runCliCommand rejects in 17ms (not 600s) with the caller's deadline message preserved.

Tests: qmd-process.test.ts 16/16 pass (SIGKILL + reject-on-abort, and reject-before-spawn when already aborted); qmd-manager.test.ts -t abort → 3/3 abort tests pass (132 total) covering single-collection and grouped multi-collection paths, asserted via the child kill("SIGKILL") spy. Typecheck (run-tsgo.mjs -p tsconfig.extensions.json) clean; memory-host-sdk typecheck passes.
Negative control: reverting only the grouped-path signal propagation makes the grouped abort test fail — the qmd child survives the caller abort and dies only at the qmd command timeout (...timed out after 4000ms instead of being killed promptly), confirming the wiring is load-bearing on the grouped path.

Summary

PR #91742 ("abort orphaned embedding work when memory_search times out") added an AbortSignal to MemorySearchManager.search() so that when the 15s memory_search tool deadline fires, in-flight embedding work is cancelled instead of running orphaned. That fix wired the signal through the builtin manager, but the QMD manager — the other backend behind the exact same MemorySearchManager.search interface — silently ignored it.

With the QMD backend, memory_search returns "timed out after 15s" to the agent after 15s, but the spawned qmd query/qmd search subprocess keeps running for the full QMD command timeout (memory.qmd.limits.timeoutMs, whose embed-heavy default was raised to 600s in PR #87572). So the orphaned-work leak that #91742 fixed for the builtin backend was still present for QMD users: the agent has already moved on, but a qmd process keeps churning for up to ~10 minutes.

What changed

packages/memory-host-sdk/src/host/qmd-process.ts: runCliCommand now accepts an optional signal: AbortSignal. When the signal aborts (or is already aborted on entry), the spawned child is SIGKILLed immediately and the call rejects with the abort reason (preserving the caller's deadline message). Resolution/rejection is funneled through a single settle() guard so abort, timeout, error, and close cannot double-settle.
extensions/memory-core/src/memory/qmd-manager.ts: QmdMemoryManager.search() accepts opts.signal (matching the builtin manager and the MemorySearchManager interface added in fix(memory): abort orphaned embedding work when memory_search times out #91742). It fast-fails if the signal is already aborted, and threads the signal through runQmdSearch → runQmd → runCliCommand across all direct-qmd subprocess search paths:
- the single-collection direct path and its query fallback, and
- the grouped multi-collection path runQueryAcrossCollectionGroups (plus its unsupported-option query fallback), which multi-collection or mixed memory/session configs route through.
The grouped helper previously called runQmdSearch(args, command) without the caller signal, so the central subprocess leak remained on that supported path (flagged in review). It now receives and forwards the same signal.

When the caller's deadline fires, the qmd subprocess is killed on every supported search path instead of left orphaned. The optional mcporter bridge is short-circuited by the universal pre-flight abort guard before it spawns anything.

Real behavior proof (real runtime, outside tests)

runCliCommand is the single spawn point for all qmd search subprocesses (single-collection and grouped), so proving abort kills the real child there covers every path that forwards the signal. Ran the real exported runCliCommand via node --import tsx against a real OS subprocess (PR head 6ee870e0ca):

$ TSX_TSCONFIG_PATH=tsconfig.json node --import tsx ./abort-proof.mts
[A] normal completion stdout: "hello-from-child"
[B] child OS pid: 598162 alive before abort: true
[B] runCliCommand rejected after 17 ms with: "memory_search timed out after 15s"
[B] child pid 598162 alive AFTER abort: false

RESULT: PASS - abort killed the real subprocess and rejected promptly (no orphan).

The proof script spawns a child that records its own PID and sleep 30s, with timeoutMs: 600_000 (mimicking the qmd embed timeout). It confirms via process.kill(pid, 0) that the real OS process is alive before abort and dead after abort, that runCliCommand rejects in 17ms (not 600s) with the caller's deadline message, and that a no-signal short command still completes normally (Case A).

Grouped-path wiring (negative control): the new grouped multi-collection abort regression drives QmdMemoryManager.search({ signal }) through runQueryAcrossCollectionGroups (mixed memory/session sources) and asserts the spawned qmd child is SIGKILLed when the caller aborts. Reverting only the grouped-path signal propagation makes that test fail, with the qmd child surviving the caller abort and dying only at the qmd command timeout:

AssertionError: expected [Function] to throw error including 'memory_search timed out after 15s'
  but got 'qmd search test --json -n 4 -c workspace-main timed out after 4000ms'

i.e. without this fix the grouped qmd child is left running until the qmd command timeout (4000ms in the test) instead of being killed promptly — the exact leak this PR closes, now confirmed on the grouped path too.

Tests and validation

packages/memory-host-sdk/src/host/qmd-process.test.ts: runCliCommand kills the child with SIGKILL and rejects with the abort reason when the signal aborts mid-run; and rejects immediately without spawning when already aborted. 16/16 pass.
extensions/memory-core/src/memory/qmd-manager.test.ts (added grouped abort test → 3 abort tests total): single-collection and grouped multi-collection qmd searches both kill the in-flight subprocess (asserted via the child kill("SIGKILL") spy) when the caller aborts, and reject before spawning when already aborted. -t abort → 3 passed / 132 total.
Negative control: reverting the grouped-path signal propagation makes the grouped abort test fail (child survives to the qmd command timeout), as shown above.
node scripts/run-tsgo.mjs -p tsconfig.extensions.json clean; memory-host-sdk typecheck passes.

Risk checklist

Behavior is unchanged when no signal is passed (all parameters/opts fields are optional; existing callers are unaffected).
settle() guard prevents double resolve/reject across abort/timeout/error/close; the abort listener is removed on settle to avoid leaks.
The abort reason prefers the caller-supplied error so the existing "memory_search timed out after 15s" message is preserved end to end.
No public API removed; only optional signal fields added. No config or schema changes.

Real behavior proof

Behavior addressed: memory_search enforces a 15s deadline, but QMD search subprocesses could continue running until the much longer qmd command timeout after the caller had already aborted. This patch threads AbortSignal through the QMD paths so the spawned subprocess is killed promptly instead of becoming orphaned work.

Real environment tested: Local Linux runtime with Node v22 and node --import tsx, driving the real exported runCliCommand from packages/memory-host-sdk/src/host/qmd-process.ts against a real OS subprocess. runCliCommand is the central spawn point for qmd subprocesses; qmd-manager tests also cover signal forwarding through single-collection and grouped multi-collection search paths.

Exact steps or command run after this patch: In PR head fix/qmd-search-abort-orphaned, ran TSX_TSCONFIG_PATH=tsconfig.json node --import tsx ./abort-proof.mts, then ran packages/memory-host-sdk/src/host/qmd-process.test.ts and extensions/memory-core/src/memory/qmd-manager.test.ts -t abort. Also ran node scripts/run-tsgo.mjs -p tsconfig.extensions.json.

Evidence after fix: Live terminal output from the real OS subprocess proof:

$ TSX_TSCONFIG_PATH=tsconfig.json node --import tsx ./abort-proof.mts
[A] normal completion stdout: "hello-from-child"
[B] child OS pid: 598162 alive before abort: true
[B] runCliCommand rejected after 17 ms with: "memory_search timed out after 15s"
[B] child pid 598162 alive AFTER abort: false
RESULT: PASS - abort killed the real subprocess and rejected promptly (no orphan).

Grouped-path negative control reverting only grouped-path signal propagation made the grouped abort regression fail with qmd timing out after 4000ms instead of rejecting with memory_search timed out after 15s, showing the child survived until qmd timeout without the fix.

Observed result after fix: The real child process is alive before abort and dead after abort, verified via process.kill(pid, 0). runCliCommand rejects in 17ms with the caller deadline message rather than waiting for the qmd timeout. The qmd-process abort tests passed 16/16 and qmd-manager abort tests passed 3/3 across single and grouped paths.

What was not tested: This proof does not run a live external qmd binary with real embeddings for the full 600s default timeout. It validates the process lifecycle and signal propagation through the shared spawn point and covered manager paths.

Alix-007 · 2026-06-15T18:15:24Z

@clawsweeper re-review

clawsweeper · 2026-06-15T18:15:27Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

clawsweeper · 2026-06-15T18:15:51Z

Codex review: needs maintainer review before merge. Reviewed June 22, 2026, 9:28 PM ET / 01:28 UTC.

Summary
The PR adds optional AbortSignal cancellation to QMD memory search, threads it through direct, grouped, and mcporter search paths, and adds focused abort regression tests.

PR surface: Source +94, Tests +302. Total +396 across 4 files.

Reproducibility: yes. Source inspection shows current main passes a deadline signal into memory managers while QMD subprocess paths ignore it, and the PR discussion includes terminal proof that a real spawned child is alive before abort and dead after abort.

Review metrics: 1 noteworthy metric.

Exported helper option: 1 optional parameter added. runCliCommand is re-exported through the memory-core host engine QMD subpath, so caller-owned cancellation is a helper contract decision before merge.

Stored data model
Persistent data-model change detected: unknown-data-model-change: extensions/memory-core/src/memory/qmd-manager.test.ts, unknown-data-model-change: extensions/memory-core/src/memory/qmd-manager.ts, unknown-data-model-change: packages/memory-host-sdk/src/host/qmd-process.test.ts, unknown-data-model-change: packages/memory-host-sdk/src/host/qmd-process.ts, vector/embedding metadata: extensions/memory-core/src/memory/qmd-manager.test.ts, vector/embedding metadata: extensions/memory-core/src/memory/qmd-manager.ts, and 2 more. Confirm migration or upgrade compatibility proof before merge.

Root-cause cluster
Relationship: canonical
Canonical: #93394
Summary: This PR is the canonical open candidate for QMD subprocess cancellation; related QMD timeout-budget work remains distinct.

Members:

partial_overlap: fix(memory): abort orphaned embedding work when memory_search times out #91742 - The merged predecessor introduced the shared deadline signal and fixed builtin orphaned embedding work, but left QMD subprocess cleanup uncovered.
adjacent_distinct: fix(memory): honor qmd search timeout and bound one-shot CLI cleanup #95347 - That open PR changes configured QMD memory_search timeout behavior and explicitly keeps qmd-process subprocess cancellation separate from this PR.
adjacent_distinct: memory_search 工具硬编码 15s timeout 不够 qmd query 跑完，建议可配置 #91947 - That issue asks for configurable or longer QMD memory_search timeout behavior, while this PR only cancels orphaned subprocesses after the existing caller deadline fires.
adjacent_distinct: fix(memory): increase QMD embedTimeoutMs default to 600s for local GG… #87572 - That timeout-default PR affects how long QMD work may run, but it does not own abort propagation or subprocess cleanup.

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

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

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

Rank-up moves:

[P2] Have a maintainer explicitly accept or reject optional AbortSignal semantics on the exported QMD process helper.
Run the focused qmd-process and qmd-manager checks on the final refreshed or merge-queue result.

Risk before merge

[P1] The PR expands the exported memory-host QMD helper with optional caller-owned cancellation; it is additive, but maintainers should explicitly accept that callers may rely on abort killing subprocesses and preserving abort reasons.
[P1] The branch is behind current main; the inspected GitHub merge result preserved current process-tree cleanup, but final merge queue or refreshed branch checks should still validate the actual merged files.

Maintainer options:

Accept the exported cancellation seam (recommended)
A maintainer can explicitly accept optional AbortSignal cancellation on runCliCommand, then land after normal refreshed checks on the merge result.
Keep cancellation behind memory-core
If maintainers do not want the exported helper to grow caller-owned cancellation semantics, move the abort handling behind a memory-core-owned wrapper before merge.
Pause for timeout-policy coordination
If maintainers want one combined QMD timeout and cancellation decision, pause this PR and reconcile it with fix(memory): honor qmd search timeout and bound one-shot CLI cleanup #95347.

Next step before merge

[P2] Human maintainer review is the next action because the remaining decision is accepting the exported cancellation contract, not a narrow automated repair.

Security
Cleared: No concrete security or supply-chain regression found; the diff changes existing local qmd/mcporter child-process cancellation paths and tests without new dependencies, workflows, secrets, or downloads.

Review details

Best possible solution:

Land after maintainers accept optional AbortSignal cancellation on the exported QMD process helper and focused memory-host/memory-core checks pass on the final merge result.

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

Yes. Source inspection shows current main passes a deadline signal into memory managers while QMD subprocess paths ignore it, and the PR discussion includes terminal proof that a real spawned child is alive before abort and dead after abort.

Is this the best way to solve the issue?

Yes, with maintainer acceptance of the exported helper contract. The spawn-boundary fix plus direct, grouped, and mcporter signal threading is narrower and more complete than patching only one QMD route.

AGENTS.md: found and applied where relevant.

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

Label changes

Label justifications:

P2: The PR fixes a bounded QMD memory_search subprocess leak with limited blast radius and no evidence of data loss, security bypass, or core runtime outage.
merge-risk: 🚨 compatibility: The diff adds optional AbortSignal semantics to an exported memory-host QMD helper that callers may rely on after release.
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 (terminal): The PR body and comments include terminal proof against a real OS subprocess spawned by runCliCommand, showing fixed subprocess death on abort and a control case where abort was ignored.
proof: sufficient: Contributor real behavior proof is sufficient. The PR body and comments include terminal proof against a real OS subprocess spawned by runCliCommand, showing fixed subprocess death on abort and a control case where abort was ignored.

Evidence reviewed

PR surface:

Source +94, Tests +302. Total +396 across 4 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	2	131	37	+94
Tests	2	302	0	+302
Docs	0	0	0	0
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	4	433	37	+396

What I checked:

Repository policy read: Read root and scoped extension policies; the exported helper/API guidance makes the new optional cancellation parameter compatibility-sensitive rather than a purely internal detail. (AGENTS.md:1, 9fa14ff61a85)
Current caller passes deadline signal: Current main builds searchOptions with signal: deadlineSignal before calling activeMemory.manager.search, so QMD can receive caller cancellation through the existing manager contract. (extensions/memory-core/src/tools.ts:498, 9fa14ff61a85)
Current QMD manager drops cancellation: Current main QmdMemoryManager.search has no signal option and calls mcporter, grouped, and direct QMD search helpers without forwarding caller cancellation. (extensions/memory-core/src/memory/qmd-manager.ts:1273, 9fa14ff61a85)
Current process helper lacks caller abort hook: Current main runCliCommand only handles its own command timeout, error, and close events; it has no AbortSignal parameter or abort listener. (packages/memory-host-sdk/src/host/qmd-process.ts:159, 9fa14ff61a85)
PR adds spawn-boundary cancellation: The checked merge result adds an optional signal to runCliCommand, rejects before spawning when already aborted, kills the child process tree on abort, clears the timer, removes the listener, and preserves caller abort reasons. (packages/memory-host-sdk/src/host/qmd-process.ts:175, 8c356ff46c7d)
Merge result preserves process-tree cleanup: The GitHub merge-result commit contains both the PR's AbortSignal support and current main's Windows taskkill tree cleanup branch, so the stale head does not prove a Windows cleanup regression. (packages/memory-host-sdk/src/host/qmd-process.ts:327, 8c356ff46c7d)

Likely related people:

vincentkoc: Merged the prior memory_search abort PR and authored recent qmd-process process-tree cleanup that this PR relies on. (role: recent area contributor and merger; confidence: high; commits: 8d72cb9401e5, c645ec4555c0, da35718cb2bf; files: extensions/memory-core/src/tools.ts, packages/memory-host-sdk/src/host/types.ts, packages/memory-host-sdk/src/host/qmd-process.ts)
dreamhunter2333: Authored the merged predecessor that added the caller deadline AbortSignal to memory_search and the MemorySearchManager.search contract. (role: introduced related abort seam; confidence: high; commits: 8d72cb9401e5; files: extensions/memory-core/src/tools.ts, extensions/memory-core/src/memory/manager.ts, packages/memory-host-sdk/src/host/types.ts)
steipete: Local history shows substantial memory host SDK extraction and QMD manager refactors, making this a likely routing candidate for exported helper contract review. (role: adjacent memory-host architecture contributor; confidence: medium; commits: eebce9e9c7cb, bd6c7969ea9c, 645c7b189757; files: packages/memory-host-sdk/src/host/qmd-process.ts, packages/memory-host-sdk/src/engine-qmd.ts, extensions/memory-core/src/memory/qmd-manager.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.

Alix-007 · 2026-06-16T03:31:35Z

@clawsweeper re-review

Threaded the qmd search abort signal through runQueryAcrossCollectionGroups and its unsupported-option fallback (the grouped path previously dropped the caller signal), and added a grouped multi-collection abort regression asserting the spawned qmd child is SIGKILLed. tsgo + qmd-manager/qmd-process vitest green.

clawsweeper · 2026-06-16T03:31:37Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Failed
Detail: The targeted re-review timed out or failed while waiting for exact-review Codex capacity. Retry after capacity recovers.
Run: https://github.com/openclaw/clawsweeper/actions/runs/27613392483
Updated: 2026-06-16T11:32:03.969Z

Alix-007 · 2026-06-16T11:10:00Z

@clawsweeper re-review

Added real-behavior proof crossing the real OS-process boundary (addressing needs-real-behavior-proof).

Behavior addressed: when memory_search aborts (e.g. times out), the orphaned qmd search subprocess is now SIGKILL'd via the signal threaded into runCliCommand, instead of leaking until the full qmd timeout elapses.

Real environment: local, Node v22, node --import tsx. The proof spawns a real OS subprocess (sh -c 'echo $$ > pidfile; exec sleep 60' — exec so the PID is the real long-lived process, SIGKILL reaches it directly), drives the real exported runCliCommand, fires controller.abort("memory_search timed out"), then reads back across the real process boundary with process.kill(pid, 0) (ESRCH = gone).

Evidence after fix:

self-check: SIGKILL verified lethal on the probe process (PID dead)
[fixed]   real runCliCommand spawn PID=3317903 -> abort -> process.kill(pid,0)=ESRCH  => subprocess DEAD, no orphan
[control] pre-fix semantics, real spawn PID=3318001 -> abort ignored -> process.kill(pid,0)=alive => ORPHAN reproduced
ps: no leftover 'sleep 60' processes
RESULT: PASS (requires fixed=dead AND control=alive)

What was not tested: not driven from the top-level QmdMemoryManager.search() (that needs a real qmd binary + SQLite index locally); the orphan behavior lives entirely in runCliCommand (the real process boundary), and the signal threading from search() down to it is pure parameter passing (read line-by-line, no branching). Tests: qmd-process.test.ts 16/16, qmd-manager.test.ts 132/132.

Alix-007 · 2026-06-16T11:51:06Z

Pushed a follow-up commit (68e667e) closing the remaining abort gap on the mcporter / QMD 1.1+ daemon search path.

The earlier commits threaded the abort signal through the direct runQmd path, but runQmdSearchViaMcporter / runMcporterAcrossCollections (used when the QMD MCP daemon serves the search) never received it, so a grouped/daemon-served search still left its subprocess running until the qmd command timeout. This commit threads the search signal through QmdMcporterSearchParams, QmdMcporterAcrossCollectionsParams, all four mcporter call sites in search(), and runMcporter down to the shared runCliCommand spawn (which already SIGKILLs the child on abort), and guards runQmdSearchViaMcporter on an already-aborted signal so the multi-collection loop stops spawning. Reuses the existing abort mechanism — no new machinery.

mcporter-path real-behavior proof (real OS subprocess via the same runCliCommand spawn the mcporter path uses):

[mcporter-call] real spawn PID=X -> abort -> process.kill(pid,0)=ESRCH  => subprocess DEAD (no orphan)
[control]       no signal listener -> abort ignored -> PID alive          => orphan reproduced
RESULT: PASS

Regression: qmd-manager.test.ts +2 mcporter abort tests (134 pass); removing the runMcporter signal propagation turns the new mcporter test red (child survives to timeout), confirming it pins the gap. qmd-process.test.ts 16/16. oxlint clean.

Now all three search routes — direct qmd, grouped multi-collection, and mcporter/daemon — abort their subprocess promptly on caller abort.

Alix-007 · 2026-06-21T06:27:50Z

@clawsweeper re-review — Added the What Problem This Solves and Evidence headings the proof workflow expects (proof content unchanged, just restructured under the required sections). This should clear needs-pr-context.

clawsweeper · 2026-06-21T06:27:52Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Alix-007 · 2026-06-23T13:33:04Z

@clawsweeper re-review — Updated the PR body with a machine-readable ## Real behavior proof section using the exact field names required by the current proof policy. I verified the updated body locally against evaluateRealBehaviorProof and the latest GitHub Real behavior proof check is now passing.

steipete · 2026-06-23T20:14:23Z

Maintainer verification complete on rebased exact head 4b1d83950e7e4e5956d4106f2832dbb7894ceb3d.

Deep review covered the exported cancellation contract, direct/grouped/probe/mcporter call paths, shared-manager fallback behavior, and current-main session corpus.
The rebase preserved current main's corpus-aware session artifact mapping; its already-upstream drift commit dropped cleanly.
node scripts/run-vitest.mjs packages/memory-host-sdk/src/host/qmd-process.test.ts packages/memory-host-sdk/src/host/qmd-process.real.test.ts extensions/memory-core/src/memory/qmd-manager.test.ts extensions/memory-core/src/memory/search-manager.test.ts passed 193 tests after conflict resolution.
Blacksmith Testbox tbx_01kvtvgvb1a3ctt5as61ncjmnq passed the same focused targets and remote pnpm check:changed before rebase. Fresh exact-head hosted CI run 28054329987 covers the rebased tree.
Post-resolution Codex autoreview completed with no accepted/actionable findings (0.91 confidence).

The prepared stack terminates complete QMD process trees on caller cancellation, preserves abort reasons and timeout precedence, avoids evicting a healthy shared manager, and does not cache an aborted capability probe. No remaining proof gaps.

…times out PR openclaw#91742 wired memory_search's 15s deadline AbortSignal through the builtin memory manager but missed the QMD backend behind the same MemorySearchManager.search interface. With QMD, the tool returns "timed out after 15s" to the agent while the spawned qmd query/search subprocess keeps running for the full qmd command timeout (memory.qmd.limits.timeoutMs, whose embed-heavy default was raised to 600s in openclaw#87572), leaving orphaned embedding/search work running after the agent already moved on. Add optional AbortSignal support to runCliCommand: an aborting signal kills the spawned child immediately and rejects with the abort reason, funneled through a single settle() guard so abort/timeout/error/close cannot double-settle. Thread the search signal through QmdMemoryManager.search -> runQmdSearch -> runQmd -> runCliCommand for the default direct-qmd subprocess path (including the query fallback), and fast-fail search() when the signal is already aborted.

…n search memory_search timeout cancellation only reached single-group direct qmd searches. Multi-collection or mixed memory/session configs route through runQueryAcrossCollectionGroups, which still called runQmdSearch without the caller signal, so an aborted memory_search left the grouped qmd child running until the qmd command timeout instead of being killed promptly. Thread searchSignal through the grouped search path and its unsupported-option fallback, and add a grouped multi-collection abort regression asserting the spawned qmd child is SIGKILLed when the caller signal aborts.

…h too The initial fix threaded the abort signal through the direct qmd (runQmd/runQmdSearch) path, but the mcporter / QMD 1.1+ daemon search path (runQmdSearchViaMcporter, runMcporterAcrossCollections) never received it, so a grouped/mcporter search left its subprocess running on abort. Thread the search signal through QmdMcporterSearchParams, QmdMcporterAcrossCollectionsParams, all four mcporter call sites in search(), and runMcporter, down to the shared runCliCommand spawn (which already SIGKILLs the child on abort). Guard runQmdSearchViaMcporter on an already-aborted signal so the multi-collection loop stops spawning. Reuses the existing abort mechanism; no new machinery. Adds mcporter-path regression tests.

steipete · 2026-06-23T20:31:51Z

Merged via rebase.

Prepared head SHA: 4b1d83950e7e4e5956d4106f2832dbb7894ceb3d
Landed commit: c9ddf2eca6e8bf4e602de838b678501f39c38c32

Alix-007 · 2026-06-24T04:11:43Z

Thanks @steipete for the deep memory-host verification and rebase merge.

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

openclaw-barnacle Bot added extensions: memory-core Extension: memory-core triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. size: M labels Jun 15, 2026

openclaw-barnacle Bot removed the triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. label Jun 16, 2026

openclaw-barnacle Bot added triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. and removed proof: sufficient ClawSweeper judged the real behavior proof convincing. labels Jun 18, 2026

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

clawsweeper Bot mentioned this pull request Jun 23, 2026

fix(memory): respect QMD timeout for memory_search #95757

Merged

steipete self-assigned this Jun 23, 2026

openclaw-barnacle Bot added size: XL and removed size: M labels Jun 23, 2026

github-advanced-security AI found potential problems Jun 23, 2026

View reviewed changes

Comment thread packages/memory-host-sdk/src/host/qmd-process.real.test.ts Fixed

Alix-007 and others added 6 commits June 23, 2026 21:15

fix(memory): abort orphaned qmd search processes

2f7714c

test(memory): clean up qmd fixture gracefully

4affac9

test(memory): clean up qmd fixture gracefully

4b1d839

steipete force-pushed the fix/qmd-search-abort-orphaned branch from 9e2188f to 4b1d839 Compare June 23, 2026 20:18

openclaw-barnacle Bot added size: L and removed size: XL labels Jun 23, 2026

steipete merged commit c9ddf2e into openclaw:main Jun 23, 2026
101 of 103 checks passed

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

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

fix(memory): bound qmd taskkill cleanup #109265

Merged

Uh oh!

Uh oh!

Conversation

Alix-007 commented Jun 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What Problem This Solves

Evidence

Summary

What changed

Real behavior proof (real runtime, outside tests)

Tests and validation

Risk checklist

Real behavior proof

Uh oh!

Alix-007 commented Jun 15, 2026

Uh oh!

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

Uh oh!

Uh oh!

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

Uh oh!

Uh oh!

Alix-007 commented Jun 16, 2026

Uh oh!

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

Uh oh!

Uh oh!

Alix-007 commented Jun 16, 2026

Uh oh!

Alix-007 commented Jun 16, 2026

Uh oh!

Alix-007 commented Jun 21, 2026

Uh oh!

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

Uh oh!

Uh oh!

Alix-007 commented Jun 23, 2026

Uh oh!

Uh oh!

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

Uh oh!

Uh oh!

Uh oh!

steipete commented Jun 23, 2026

Uh oh!

Alix-007 commented Jun 24, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Alix-007 commented Jun 15, 2026 •

edited

Loading

clawsweeper Bot commented Jun 15, 2026 •

edited

Loading

clawsweeper Bot commented Jun 15, 2026 •

edited

Loading

clawsweeper Bot commented Jun 16, 2026 •

edited

Loading

clawsweeper Bot commented Jun 21, 2026 •

edited

Loading

steipete commented Jun 23, 2026 •

edited

Loading