fix(memory-core): keep QMD JSON search one-shot by TurboTheTurtle · Pull Request #91837 · openclaw/openclaw

TurboTheTurtle · 2026-06-10T04:35:40Z

Summary

openclaw memory search <query> --json could print valid JSON with the QMD backend and then stay alive because the one-shot QMD CLI manager could still schedule session-start/search sync work. withManager() closes the manager after JSON output, and close() waits for pending QMD update/embed work, so a background sync can keep the CLI process alive after the result has already been written.

This keeps the repair in the QMD lifecycle boundary: CLI-mode QMD managers still initialize without watchers or boot timers, and now also skip session/search-triggered sync scheduling during one-shot searches. JSON output remains prompt; best-effort recall tracking is not moved into the blocking JSON path.

Verification

node scripts/run-vitest.mjs extensions/memory-core/src/cli.test.ts extensions/memory-core/src/memory/qmd-manager.test.ts — 192 passed
pnpm exec oxfmt --check --threads=1 extensions/memory-core/src/cli.runtime.ts extensions/memory-core/src/cli.test.ts extensions/memory-core/src/memory/qmd-manager.ts extensions/memory-core/src/memory/qmd-manager.test.ts — clean
git diff --check — clean
git log --format='%h %an <%ae> %s' upstream/main..HEAD — 4137a2ab05 Andy Ye <[email protected]> fix(memory-core): keep qmd json search one-shot

Real behavior proof

Behavior addressed: QMD-backed memory search --json exits after printing successful JSON even when sync settings would otherwise trigger session/search update work. The proof uses a stub qmd binary that returns valid search JSON and intentionally never exits for qmd update/qmd embed; if the CLI schedules the old background update path, the command times out.

Real environment tested: macOS source checkout /Users/andy/openclaw-91821-memory-json-exit, Node 24.15.0, rebuilt local dist/index.js, temporary OPENCLAW_CONFIG_PATH, temporary OPENCLAW_STATE_DIR, QMD backend enabled, memorySearch.sync.onSessionStart=true, memorySearch.sync.onSearch=true, fake qmd command on PATH logging every invocation.

Exact steps or command run after this patch:

node dist/index.js memory search "QMD proof token" --json

Evidence after fix:

{
  "proof": "PR91837_QMD_JSON_EXIT_STUB",
  "command": "node dist/index.js memory search \"QMD proof token\" --json",
  "config": {
    "backend": "qmd",
    "sync": {
      "onSessionStart": true,
      "onSearch": true
    },
    "qmdUpdateStubWouldHang": true
  },
  "exit": {
    "code": 0,
    "signal": null
  },
  "timedOut": false,
  "durationMs": 4020,
  "stdout": "{\n  \"results\": [\n    {\n      \"path\": \"memory/proof.md\",\n      \"startLine\": 1,\n      \"endLine\": 1,\n      \"score\": 0.91,\n      \"snippet\": \"@@ -1,1\\nQMD proof token from stub\",\n      \"source\": \"memory\"\n    }\n  ]\n}",
  "stderr": "[memory] qmd manager initialized for agent \"main\" mode=cli collections=1 durationMs=210\n[memory] failed to read qmd index stats: Error: unable to open database file",
  "qmdCalls": [
    ["collection", "list", "--json"],
    ["collection", "add", "<temp-workspace>", "--name", "workspace-main", "--mask", "**/*.md"],
    ["search", "QMD proof token", "--json", "-n", "4", "-c", "workspace-main"]
  ],
  "backgroundUpdateCallCount": 0
}

Observed result after fix: the CLI printed a valid JSON result and exited with status 0 before the 7s proof timeout. The QMD invocation log shows collection setup and search only; no qmd update or qmd embed command was spawned, so the intentionally hanging update path was not reached.

What was not tested: a live installed QMD binary and real QMD index. The proof is a faithful process-lifecycle stub for the reported exit hang: it exercises the OpenClaw CLI, config loading, QMD manager creation, QMD collection/search subprocess calls, JSON output, and process exit behavior.

clawsweeper · 2026-06-10T04:38:02Z

Codex review: needs maintainer review before merge. Reviewed June 10, 2026, 1:21 AM ET / 05:21 UTC.

Summary
This PR records QMD manager mode, skips session-start and dirty-search sync scheduling in CLI mode, and adds a regression test for one-shot CLI search with QMD sync triggers enabled.

PR surface: Source +8, Tests +49. Total +57 across 2 files.

Reproducibility: yes. I did not run the failing current-main command, but the source path is clear: CLI search can schedule QMD sync work and manager close waits for pending update/embed work, matching the linked report and the PR's after-fix terminal proof.

Review metrics: none identified.

Merge readiness
Overall: 🐚 platinum hermit
Proof: 🐚 platinum hermit
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:

none.

Risk before merge

[P1] The proof uses a real OpenClaw CLI command with a qmd subprocess stub rather than a live installed QMD index; this is sufficient for the lifecycle bug, but a maintainer may still want a live-QMD smoke before landing.

Maintainer options:

Decide the mitigation before merge
Land the lifecycle-bound QMD fix after normal maintainer review and CI, keeping explicit memory index commands as the path for blocking QMD refresh work.
Pause or close
Do not merge this PR until maintainers decide whether the risk is worth taking.

Next step before merge

No repair lane is needed because there are no actionable review findings; the remaining action is normal maintainer review and CI.

Security
Cleared: The diff only changes QMD manager lifecycle branching and a colocated test, with no new dependency, secret, workflow, package, install, or code-download surface.

Review details

Best possible solution:

Land the lifecycle-bound QMD fix after normal maintainer review and CI, keeping explicit memory index commands as the path for blocking QMD refresh work.

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

Yes. I did not run the failing current-main command, but the source path is clear: CLI search can schedule QMD sync work and manager close waits for pending update/embed work, matching the linked report and the PR's after-fix terminal proof.

Is this the best way to solve the issue?

Yes. Fixing the QMD manager's CLI lifecycle is more maintainable than adding process.exit() after JSON output because it prevents the background work that keeps close() alive while preserving normal explicit sync commands.

AGENTS.md: found and applied where relevant.

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

Label changes

Label changes:

add proof: sufficient: Contributor real behavior proof is sufficient. The PR body supplies after-fix terminal proof from a rebuilt OpenClaw CLI showing JSON output, exit code 0, and no update/embed subprocess calls on the hang-triggering path.
add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🐚 platinum hermit.
add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (terminal): The PR body supplies after-fix terminal proof from a rebuilt OpenClaw CLI showing JSON output, exit code 0, and no update/embed subprocess calls on the hang-triggering path.
remove rating: 🌊 off-meta tidepool: Current PR rating is rating: 🐚 platinum hermit, so this older rating label is no longer current.
remove merge-risk: 🚨 availability: Current PR review selected no merge-risk labels.

Label justifications:

P2: The PR addresses a bounded memory-core CLI bug where successful QMD JSON search can keep the process alive until upstream callers time out.
rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit 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 supplies after-fix terminal proof from a rebuilt OpenClaw CLI showing JSON output, exit code 0, and no update/embed subprocess calls on the hang-triggering path.
proof: sufficient: Contributor real behavior proof is sufficient. The PR body supplies after-fix terminal proof from a rebuilt OpenClaw CLI showing JSON output, exit code 0, and no update/embed subprocess calls on the hang-triggering path.

Evidence reviewed

PR surface:

Source +8, Tests +49. Total +57 across 2 files.

View PR surface stats

Area	Files	Added	Net
Source	1	8	+8
Tests	1	49	+49
Docs	0	0	0
Config	0	0	0
Generated	0	0	0
Other	0	0	0
Total	2	57	+57

What I checked:

Repository policy applied: Read the full root AGENTS.md plus the scoped extensions/AGENTS.md; the OpenClaw PR review, proof, dependency, plugin-boundary, and changed-surface guidance applied to this memory-core review. (AGENTS.md:1, 54c400a97571)
Current main manager path: Current main creates QMD managers with an optional mode and already returns early from initialize() for CLI mode before watchers and timers are started, but it does not persist that mode for later search-time decisions. (extensions/memory-core/src/memory/qmd-manager.ts:318, 54c400a97571)
Current main search/close interaction: Current main search() calls maybeWarmSession(), maybeSyncDirtySearchState(), and waitForPendingUpdateBeforeSearch(); close() then waits for pendingUpdate and queuedForcedUpdate, which is the hang-prone lifecycle described by the linked issue. (extensions/memory-core/src/memory/qmd-manager.ts:1190, 54c400a97571)
Current main sync scheduling source: maybeWarmSession() schedules a session-start sync when onSessionStart is enabled, and maybeSyncDirtySearchState() can await a search sync when onSearch and dirty are true; neither function has a CLI-mode guard on current main. (extensions/memory-core/src/memory/qmd-manager.ts:1731, 54c400a97571)
PR runtime change: The PR adds a private mode field, assigns it during initialize(), and returns early from both search-time sync helpers when the manager mode is cli. (extensions/memory-core/src/memory/qmd-manager.ts:379, 4137a2ab0575)
Regression coverage: The new test enables onSessionStart and onSearch for a CLI-mode QMD manager, performs a search with a CLI session key, closes the manager, and asserts no update/embed subprocess was spawned while the search subprocess did run. (extensions/memory-core/src/memory/qmd-manager.test.ts:706, 4137a2ab0575)

Likely related people:

Dallin Romney: Current-main blame for initialize(), CLI-mode setup, search-time sync helpers, and the CLI manager close wrapper points to the imported memory-core implementation in commit a2dd821. (role: current implementation provenance; confidence: medium; commits: a2dd8219087a; files: extensions/memory-core/src/memory/qmd-manager.ts, extensions/memory-core/src/cli.runtime.ts)
Vincent Koc: Git history shows QMD sync parity hooks and the latest stable release prep touching the same memory-core QMD manager surface. (role: QMD sync feature history contributor; confidence: medium; commits: d26d7c797b65, 5181e4f7c82b; files: extensions/memory-core/src/memory/qmd-manager.ts, docs/reference/memory-config.md)
Peter Steinberger: Recent history includes the move of the memory engine into the memory plugin and later QMD sync/runtime refactors on the same files and adjacent host SDK paths. (role: recent memory-core refactor contributor; confidence: medium; commits: cad83db8b2f7, 30c686423f12; files: extensions/memory-core/src/memory/qmd-manager.ts, extensions/memory-core/src/memory/search-manager.ts, extensions/memory-core/src/cli.runtime.ts)

What the crustacean ranks mean

🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

TurboTheTurtle · 2026-06-10T04:51:04Z

@clawsweeper re-review

clawsweeper · 2026-06-10T04:51:06Z

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

TurboTheTurtle · 2026-06-10T04:52:42Z

@clawsweeper re-review

clawsweeper · 2026-06-10T04:52:45Z

🦞👀
ClawSweeper picked this up.

Command router queued. I will update this comment with the next step.

Re-review progress:

State: Failed
Detail: The targeted re-review did not finish cleanly. Check the workflow run for details.
Run: https://github.com/openclaw/clawsweeper/actions/runs/27254088532
Updated: 2026-06-10T04:54:30.399Z

TurboTheTurtle · 2026-06-10T04:54:46Z

@clawsweeper re-review

clawsweeper · 2026-06-10T04:54:48Z

🦞🧹
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: Complete
Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
Run: https://github.com/openclaw/clawsweeper/actions/runs/27254747777
Updated: 2026-06-10T05:22:45.368Z

vincentkoc · 2026-06-10T07:30:27Z

Landed after maintainer verification:

Reviewed the full QMD manager lifecycle and the CLI/full manager split.
Structured autoreview: clean; no accepted/actionable findings.
Focused proof: node scripts/run-vitest.mjs extensions/memory-core/src/memory/qmd-manager.test.ts — 124 tests passed.
GitHub checks were green at merge time.
Compared with fix(memory-core): force exit after memory search --json output #91864: this PR fixes lifecycle ownership at the manager boundary instead of forcing process.exit(), preserving normal cleanup and best-effort recall behavior.

Proof gap: no live qmd binary is installed in this checkout, so live-QMD smoke was not repeated locally. The contributor's subprocess lifecycle proof and focused regression cover the reported hang.

Landed commit: 9408380

…26.6.6) (#1040) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ghcr.io/openclaw/openclaw](https://openclaw.ai) ([source](https://github.com/openclaw/openclaw)) | patch | `2026.6.5` → `2026.6.6` | --- ### Release Notes <details> <summary>openclaw/openclaw (ghcr.io/openclaw/openclaw)</summary> ### [`v2026.6.6`](https://github.com/openclaw/openclaw/blob/HEAD/CHANGELOG.md#202666) [Compare Source](openclaw/openclaw@v2026.6.5...v2026.6.6) ##### Highlights - Security boundaries are substantially tighter across transcripts, sandbox binds, host environment inheritance, MCP stdio, Codex HTTP access, native search policy, elevated sender checks, deleted-agent ACP bypasses, loopback tools, Discord moderation, and Teams group actions; exec approvals now fail closed on timeout. ([#91529](openclaw/openclaw#91529), [#91618](openclaw/openclaw#91618), [#91615](openclaw/openclaw#91615), [#91619](openclaw/openclaw#91619), [#91741](openclaw/openclaw#91741), [#91745](openclaw/openclaw#91745), [#91746](openclaw/openclaw#91746), [#91748](openclaw/openclaw#91748), [#91749](openclaw/openclaw#91749), [#91750](openclaw/openclaw#91750), [#91751](openclaw/openclaw#91751), [#91752](openclaw/openclaw#91752), [#91763](openclaw/openclaw#91763), [#89938](openclaw/openclaw#89938)) Thanks [@joshavant](https://github.com/joshavant), [@pgondhi987](https://github.com/pgondhi987), [@mmaps](https://github.com/mmaps), [@eleqtrizit](https://github.com/eleqtrizit), [@shakkernerd](https://github.com/shakkernerd), and [@drobison00](https://github.com/drobison00). - Telegram delivery is safer and more coherent: account-scoped topics route to the right agent, streamed text survives tool calls, `/compact` works on generic ingress, callback handling uses concrete APIs, draft chunking is shared, durable dispatch dedupe moved into the SDK, and unauthorized DM text stays out of cache and prompt context. ([#91189](openclaw/openclaw#91189), [#88682](openclaw/openclaw#88682), [#89588](openclaw/openclaw#89588), [#90212](openclaw/openclaw#90212), [#91876](openclaw/openclaw#91876), [#91874](openclaw/openclaw#91874), [#91904](openclaw/openclaw#91904), [#91478](openclaw/openclaw#91478), [#91915](openclaw/openclaw#91915)) Thanks [@codysai001](https://github.com/codysai001), [@alexzhu0](https://github.com/alexzhu0), [@joelnishanth](https://github.com/joelnishanth), [@snowzlm](https://github.com/snowzlm), [@obviyus](https://github.com/obviyus), and [@sallyom](https://github.com/sallyom). - iMessage recovery and delivery now cover always-on inbound restart, durable echo markers, block streaming, idle approval discovery, hardened outbound transport, and actionable inbound startup diagnostics. ([#91335](openclaw/openclaw#91335), [#91449](openclaw/openclaw#91449), [#88969](openclaw/openclaw#88969), [#88530](openclaw/openclaw#88530), [#91783](openclaw/openclaw#91783), [#91785](openclaw/openclaw#91785)) Thanks [@omarshahine](https://github.com/omarshahine), [@jmissig](https://github.com/jmissig), and [@colmbrogan](https://github.com/colmbrogan). - Browser and MCP connectivity gained existing-session CDP support, discovered WebSocket validation, default-profile `cdpUrl` handling, safer browser-output boundaries, Streamable HTTP loopback transport, corrected OAuth/SSE authorization handling, and broader schema compatibility. ([#91422](openclaw/openclaw#91422), [#89851](openclaw/openclaw#89851), [#91736](openclaw/openclaw#91736), [#91747](openclaw/openclaw#91747), [#91451](openclaw/openclaw#91451), [#80143](openclaw/openclaw#80143)) Thanks [@pgondhi987](https://github.com/pgondhi987), [@anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia), [@lifuyue](https://github.com/lifuyue), [@eleqtrizit](https://github.com/eleqtrizit), [@LiuwqGit](https://github.com/LiuwqGit), and [@HemantSudarshan](https://github.com/HemantSudarshan). - Control UI startup and first-reply latency are lower through cached model metadata, removal of the startup catalog wait, lazy slash-command loading, and first-event tracing with slow-reply diagnostics. ([#91531](openclaw/openclaw#91531), [#91538](openclaw/openclaw#91538), [#91568](openclaw/openclaw#91568), [#91583](openclaw/openclaw#91583), [#91598](openclaw/openclaw#91598)) - Provider support expands with OpenRouter OAuth onboarding and Claude Fable 5 adaptive thinking, while Codex sessions keep correct compaction ownership, local models skip guardian review, dynamic tool progress normalizes cleanly, and Gemma 4 reasoning replay is preserved. ([#91830](openclaw/openclaw#91830), [#91882](openclaw/openclaw#91882), [#91590](openclaw/openclaw#91590), [#88630](openclaw/openclaw#88630), [#88768](openclaw/openclaw#88768), [#91696](openclaw/openclaw#91696)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@joshavant](https://github.com/joshavant), [@bdjben](https://github.com/bdjben), and [@Coder-Wangyankun](https://github.com/Coder-Wangyankun). ##### Changes - CLI progress: emit Claude CLI commentary progress events and bridge inter-tool commentary into channel progress without exposing internal protocol scaffolding. ([#89834](openclaw/openclaw#89834), [#90883](openclaw/openclaw#90883)) Thanks [@anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia). - Observability: allow trusted diagnostics channels to capture tool input/output content, add first-assistant-event traces, and warn on slow initial replies. ([#91256](openclaw/openclaw#91256), [#91568](openclaw/openclaw#91568), [#91583](openclaw/openclaw#91583)) Thanks [@amknight](https://github.com/amknight). - Plugins/ClawHub: dogfood reusable package publishing, let dry runs skip publish approval, allow declared installed trusted hooks, report managed plugin version drift, and warn instead of failing on retired Skill Workshop configuration. ([#91574](openclaw/openclaw#91574), [#91591](openclaw/openclaw#91591), [#90004](openclaw/openclaw#90004), [#90927](openclaw/openclaw#90927), [#90838](openclaw/openclaw#90838)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@brokemac79](https://github.com/brokemac79), and [@lonexreb](https://github.com/lonexreb). - Memory/providers: move the local llama.cpp runtime into its provider plugin, batch embeddings across files, persist the agent model catalog cache, and keep QMD JSON search one-shot while filtering stale REM recall previews. ([#91324](openclaw/openclaw#91324), [#89138](openclaw/openclaw#89138), [#90457](openclaw/openclaw#90457), [#91837](openclaw/openclaw#91837), [#91851](openclaw/openclaw#91851)) Thanks [@osolmaz](https://github.com/osolmaz), [@mushuiyu886](https://github.com/mushuiyu886), [@ai-hpc](https://github.com/ai-hpc), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Channels/mobile: add the QQBot group mention toggle, improve iPad and iPhone control surfaces, and expose the active connection host in the TUI footer. ([#91423](openclaw/openclaw#91423), [#91557](openclaw/openclaw#91557), [#89909](openclaw/openclaw#89909)) Thanks [@cxyhhhhh](https://github.com/cxyhhhhh), [@Solvely-Colin](https://github.com/Solvely-Colin), and [@baskduf](https://github.com/baskduf). - Performance: prewarm TUI runtime plugins, deduplicate plugin auto-enable fanout, trim dense text-delta snapshots, and reuse prepared startup model metadata. ([#90782](openclaw/openclaw#90782), [#89978](openclaw/openclaw#89978), [#91580](openclaw/openclaw#91580), [#91531](openclaw/openclaw#91531)) Thanks [@RomneyDa](https://github.com/RomneyDa) and [@ai-hpc](https://github.com/ai-hpc). ##### Fixes - Agent/session recovery: drop stale approval follow-ups after session rebind, remove drained reply-queue items by identity, recover stale main and visible replies, preserve Codex context-engine compaction ownership, lower the default compaction timeout to 180 seconds while respecting explicit configuration, and keep provider-failure terminal lifecycle state correct. ([#85679](openclaw/openclaw#85679), [#91450](openclaw/openclaw#91450), [#91566](openclaw/openclaw#91566), [#91840](openclaw/openclaw#91840), [#91590](openclaw/openclaw#91590), [#91361](openclaw/openclaw#91361), [#91895](openclaw/openclaw#91895)) Thanks [@openperf](https://github.com/openperf), [@yetval](https://github.com/yetval), [@joshavant](https://github.com/joshavant), [@wangmiao0668000666](https://github.com/wangmiao0668000666), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - User-visible content boundaries: suppress Codex/Harmony protocol artifacts, neutralize browser and LanceDB memory media directives, redact transcript images, and preserve native `/compact` replies through source suppression. ([#89151](openclaw/openclaw#89151), [#91422](openclaw/openclaw#91422), [#91425](openclaw/openclaw#91425), [#91529](openclaw/openclaw#91529), [#90212](openclaw/openclaw#90212)) Thanks [@joelnishanth](https://github.com/joelnishanth), [@pgondhi987](https://github.com/pgondhi987), [@joshavant](https://github.com/joshavant), and [@snowzlm](https://github.com/snowzlm). - Channel delivery: keep WhatsApp captured replies attached to the successor controller after restart, retry Feishu rate limits, preserve Mattermost thread replies, canonicalize LINE webhook paths, restore Discord reply hydration and runtime timeout exports, and show OpenAI Realtime WebRTC assistant transcripts. ([#85823](openclaw/openclaw#85823), [#89659](openclaw/openclaw#89659), [#91684](openclaw/openclaw#91684), [#91649](openclaw/openclaw#91649), [#90263](openclaw/openclaw#90263), [#91686](openclaw/openclaw#91686), [#90426](openclaw/openclaw#90426)) Thanks [@itsuzef](https://github.com/itsuzef), [@ladygege](https://github.com/ladygege), [@jacobtomlinson](https://github.com/jacobtomlinson), [@fuller-stack-dev](https://github.com/fuller-stack-dev), and [@shushushv](https://github.com/shushushv). - Cron: cancel active task runs cleanly, preserve terminal timeout/cancel state, and recover no-deliver tool warnings instead of silently losing the outcome. ([#90666](openclaw/openclaw#90666), [#90678](openclaw/openclaw#90678)) Thanks [@ai-hpc](https://github.com/ai-hpc). - Gateway/config/auth: share the approval runtime socket token, replace arrays explicitly in `config.patch`, skip the deleted-agent guard only for valid ACP harness sessions, surface headless LaunchAgent state, verify SQLite auth migration before cleanup, and arm QMD startup maintenance. ([#87105](openclaw/openclaw#87105), [#91551](openclaw/openclaw#91551), [#91219](openclaw/openclaw#91219), [#91614](openclaw/openclaw#91614), [#91740](openclaw/openclaw#91740), [#91978](openclaw/openclaw#91978)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev) and [@scotthuang](https://github.com/scotthuang). - Providers/Codex: clarify quota errors, restore the Codex synthetic usage line, canonicalize Codex protocol assets, require API-key auth for realtime voice, normalize ACP model refs, preserve Gemma 4 `reasoning_content`, and avoid guardian review for local models. ([#91390](openclaw/openclaw#91390), [#91709](openclaw/openclaw#91709), [#91507](openclaw/openclaw#91507), [#91567](openclaw/openclaw#91567), [#88630](openclaw/openclaw#88630), [#91696](openclaw/openclaw#91696)) Thanks [@hxy91819](https://github.com/hxy91819), [@brokemac79](https://github.com/brokemac79), [@RomneyDa](https://github.com/RomneyDa), [@joshavant](https://github.com/joshavant), and [@Coder-Wangyankun](https://github.com/Coder-Wangyankun). - Updates/builds: recover package Gateway restarts after refresh failure, expose plugin convergence repair, fall back to Corepack in PATH-less pnpm environments, seed the correct Docker store packages, and keep ClawHub dry-run and publish paths reusable. ([#91581](openclaw/openclaw#91581), [#91599](openclaw/openclaw#91599), [#91547](openclaw/openclaw#91547), [#91591](openclaw/openclaw#91591)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev), [@sallyom](https://github.com/sallyom), and [@Patrick-Erichsen](https://github.com/Patrick-Erichsen). - UI: require explicit user intent before opening chat sessions and drain restored chat queues after session switches. ([#91480](openclaw/openclaw#91480)) Thanks [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Android: avoid the `dataSync` foreground-service type for persistent nodes. ([#80082](openclaw/openclaw#80082)) Thanks [@davelutztx](https://github.com/davelutztx). - Native hooks: bound relay lifetimes so abandoned native hook connections cannot linger indefinitely. ([#91550](openclaw/openclaw#91550)) Thanks [@joshavant](https://github.com/joshavant). </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.erwanleboucher.dev/eleboucher/homelab/pulls/1040

openclaw-barnacle Bot added extensions: memory-core Extension: memory-core size: XS triage: mock-only-proof Candidate: PR proof only shows tests, mocks, snapshots, lint, typecheck, or CI. labels Jun 10, 2026

TurboTheTurtle force-pushed the fix/91821-memory-json-qmd-exit branch from 11a832b to 28deb04 Compare June 10, 2026 04:50

openclaw-barnacle Bot added size: S and removed size: XS labels Jun 10, 2026

TurboTheTurtle changed the title ~~fix(memory-core): settle json search cleanup~~ fix(memory-core): keep QMD JSON search one-shot Jun 10, 2026

openclaw-barnacle Bot added the proof: supplied External PR includes structured after-fix real behavior proof. label Jun 10, 2026

fix(memory-core): keep qmd json search one-shot

4137a2a

TurboTheTurtle force-pushed the fix/91821-memory-json-qmd-exit branch from 28deb04 to 4137a2a Compare June 10, 2026 04:54

clawsweeper Bot added status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. and removed merge-risk: 🚨 availability 🚨 May cause crashes, hangs, restart loops, stalls, or process outages. labels Jun 10, 2026

vincentkoc self-assigned this Jun 10, 2026

vincentkoc merged commit 9408380 into openclaw:main Jun 10, 2026
189 of 200 checks passed

vincentkoc mentioned this pull request Jun 10, 2026

fix(memory-core): force exit after memory search --json output #91864

Closed

TurboTheTurtle deleted the fix/91821-memory-json-qmd-exit branch June 10, 2026 07:36

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

📡 Upstream Digest — 2026-06-10 08:01 UTC curtismercier/openclaw-mods#1051

Open

github-actions Bot pushed a commit to Desicool/openclaw that referenced this pull request Jun 11, 2026

fix(memory-core): keep qmd json search one-shot (openclaw#91837)

aea2ca1

clawsweeper Bot mentioned this pull request Jun 18, 2026

fix(memory-core): bound zero-hit forced sync so memory_search can't hang the whole deadline #94564

Closed

badgerbees pushed a commit to badgerbees/openclaw that referenced this pull request Jul 8, 2026

fix(memory-core): keep qmd json search one-shot (openclaw#91837)

db3e972

clawsweeper Bot mentioned this pull request Jul 14, 2026

fix(memory): preserve UTF-8 when qmd output splits across pipe chunks #107263

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

fix(memory-core): keep QMD JSON search one-shot#91837

fix(memory-core): keep QMD JSON search one-shot#91837
vincentkoc merged 1 commit into
openclaw:mainfrom
TurboTheTurtle:fix/91821-memory-json-qmd-exit

TurboTheTurtle commented Jun 10, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented Jun 10, 2026 •

edited

Loading

Uh oh!

TurboTheTurtle commented Jun 10, 2026

Uh oh!

clawsweeper Bot commented Jun 10, 2026 •

edited

Loading

Uh oh!

TurboTheTurtle commented Jun 10, 2026

Uh oh!

clawsweeper Bot commented Jun 10, 2026 •

edited

Loading

Uh oh!

TurboTheTurtle commented Jun 10, 2026

Uh oh!

clawsweeper Bot commented Jun 10, 2026 •

edited

Loading

Uh oh!

Uh oh!

vincentkoc commented Jun 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Uh oh!

Conversation

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

Uh oh!

Summary

Verification

Real behavior proof

Uh oh!

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

Uh oh!

Uh oh!

TurboTheTurtle commented Jun 10, 2026

Uh oh!

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

Uh oh!

Uh oh!

TurboTheTurtle commented Jun 10, 2026

Uh oh!

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

Uh oh!

Uh oh!

TurboTheTurtle commented Jun 10, 2026

Uh oh!

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

Uh oh!

Uh oh!

Uh oh!

vincentkoc commented Jun 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

TurboTheTurtle commented Jun 10, 2026 •

edited

Loading

clawsweeper Bot commented Jun 10, 2026 •

edited

Loading

clawsweeper Bot commented Jun 10, 2026 •

edited

Loading

clawsweeper Bot commented Jun 10, 2026 •

edited

Loading

clawsweeper Bot commented Jun 10, 2026 •

edited

Loading