fix(cron): recover no-deliver tool warnings by ai-hpc · Pull Request #90678 · openclaw/openclaw

ai-hpc · 2026-06-05T13:41:26Z

Summary

Treat unresolved cron output policy as final-text-preferred only when delivery is explicitly disabled.
Preserve the existing channel-plugin preference path for resolved delivery channels.
Pass the delivery-requested fact into final and interim isolated cron outcome classification.

Verification

OPENCLAW_VITEST_FS_MODULE_CACHE_PATH=<temp-cache> pnpm test src/cron/isolated-agent/channel-output-policy.test.ts src/cron/isolated-agent/run.message-tool-policy.test.ts src/cron/isolated-agent.helpers.test.ts
node_modules/.bin/oxfmt --check --threads=1 src/cron/isolated-agent/channel-output-policy.ts src/cron/isolated-agent/run.ts src/cron/isolated-agent/run-executor.ts src/cron/isolated-agent/channel-output-policy.test.ts src/cron/isolated-agent/run.message-tool-policy.test.ts
node_modules/.bin/oxlint src/cron/isolated-agent/channel-output-policy.ts src/cron/isolated-agent/run.ts src/cron/isolated-agent/run-executor.ts src/cron/isolated-agent/channel-output-policy.test.ts src/cron/isolated-agent/run.message-tool-policy.test.ts
git diff --check
pnpm tsgo:core

Real behavior proof

behavior: A bare delivery.mode: "none" isolated cron run with a trailing tool warning and final assistant-visible text should record the final assistant text as the successful cron result instead of treating the tool warning as fatal.

environment: Ubuntu source checkout, Node 22.22.2, fixed branch ai-hpc/fix-cron-no-deliver-tool-warning.

steps:

On unchanged current main, classify a no-channel cron payload with one tool warning and populated final assistant-visible text.
Confirm current main returns preferFinalAssistantVisibleText: false, marks the warning fatal, and uses the warning as summary/output.
On the fixed branch, classify the same shape with explicit deliveryRequested: false.
Confirm the warning is non-fatal and summary/output use final assistant-visible text.

before:

{
  "behavior": "main no-channel cron tool warning classification",
  "policy": {
    "preferFinalAssistantVisibleText": false
  },
  "finalAssistantVisibleTextPresent": true,
  "hasFatalErrorPayload": true,
  "embeddedRunError": "⚠️ 🛠️ show > (agent) failed",
  "summary": "⚠️ 🛠️ show > (agent) failed",
  "outputText": "⚠️ 🛠️ show > (agent) failed"
}

after:

{
  "behavior": "fixed no-delivery cron tool warning classification",
  "policy": {
    "preferFinalAssistantVisibleText": true
  },
  "finalAssistantVisibleTextPresent": true,
  "hasFatalErrorPayload": false,
  "summary": "Final cron report from the agent.",
  "outputText": "Final cron report from the agent.",
  "deliveryPayloads": [
    {
      "text": "Final cron report from the agent."
    }
  ]
}

observedResult: The fixed branch keeps unresolved delivery-requested runs conservative, but lets explicit no-delivery cron runs recover plain tool warnings with final assistant-visible text.

notTested: Full installed cron dispatch with the reporter's live claude-cascade job was not replayed locally. Focused proof covers the classifier path that misclassified the run; regression tests cover policy resolution, helper behavior, and isolated cron run finalization.

clawsweeper · 2026-06-05T13:43:16Z

Codex review: needs maintainer review before merge. Reviewed June 5, 2026, 9:48 AM ET / 13:48 UTC.

Summary
The PR threads the existing delivery-requested fact into isolated cron output classification so explicit no-delivery runs can recover tool-warning payloads using final assistant-visible text.

PR surface: Source +11, Tests +59. Total +70 across 5 files.

Reproducibility: yes. from source inspection: bare delivery.mode: "none" leaves resolvedDelivery.channel undefined, current main's policy returns false, and the helper's recovered-tool-warning branch requires true. I did not execute the failing cron scenario because this review was constrained to keep the checkout read-only.

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 PR body did not replay the reporter's full installed claude-cascade cron job; the available proof is focused on the classifier path and targeted regression tests.

Maintainer options:

Decide the mitigation before merge
Land this scoped cron classifier fix after normal CI, keeping the no-delivery/no-channel recovery separate from channel-plugin policy and unresolved announce delivery behavior.
Pause or close
Do not merge this PR until maintainers decide whether the risk is worth taking.

Next step before merge

No ClawSweeper repair job is needed because the PR already supplies the narrow code/test fix and I found no actionable review finding.

Security
Cleared: The diff changes only cron TypeScript source and focused tests, with no workflows, dependency manifests, lockfiles, package scripts, secrets handling, or downloaded code paths changed.

Review details

Best possible solution:

Land this scoped cron classifier fix after normal CI, keeping the no-delivery/no-channel recovery separate from channel-plugin policy and unresolved announce delivery behavior.

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

Yes from source inspection: bare delivery.mode: "none" leaves resolvedDelivery.channel undefined, current main's policy returns false, and the helper's recovered-tool-warning branch requires true. I did not execute the failing cron scenario because this review was constrained to keep the checkout read-only.

Is this the best way to solve the issue?

Yes. Passing the already-prepared deliveryRequested fact into final and interim classification is narrower than globally changing the no-channel default and preserves resolved channel plugin preferences.

AGENTS.md: found and applied where relevant.

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

Label changes

Label changes:

add P2: This is a normal-priority isolated cron reliability fix for false error status/output without a crash, security issue, or data loss shown.
add proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes after-fix classifier output from an Ubuntu source checkout showing explicit no-delivery tool-warning output becomes a successful final assistant-text result; the omitted live installed cron replay is a residual but not blocking proof gap for this focused 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 includes after-fix classifier output from an Ubuntu source checkout showing explicit no-delivery tool-warning output becomes a successful final assistant-text result; the omitted live installed cron replay is a residual but not blocking proof gap for this focused path.

Label justifications:

P2: This is a normal-priority isolated cron reliability fix for false error status/output without a crash, security issue, or data loss shown.
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 includes after-fix classifier output from an Ubuntu source checkout showing explicit no-delivery tool-warning output becomes a successful final assistant-text result; the omitted live installed cron replay is a residual but not blocking proof gap for this focused path.
proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes after-fix classifier output from an Ubuntu source checkout showing explicit no-delivery tool-warning output becomes a successful final assistant-text result; the omitted live installed cron replay is a residual but not blocking proof gap for this focused path.

Evidence reviewed

PR surface:

Source +11, Tests +59. Total +70 across 5 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	3	15	4	+11
Tests	2	59	0	+59
Docs	0	0	0	0
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	5	74	4	+70

What I checked:

repository policy read: Root AGENTS.md was present and read fully; its review guidance required full-path code reading, best-fix judgment, real behavior proof assessment, and security review. (AGENTS.md:1, 520992a1defd)
checkout state: The review started from a clean main checkout tracking origin/main. (520992a1defd)
current main no-channel default: Current main returns preferFinalAssistantVisibleText: false when no channel is resolved, matching the linked bug's central failure mode. (src/cron/isolated-agent/channel-output-policy.ts:20, 520992a1defd)
current main recovery gate: resolveCronPayloadOutcome only recovers plain tool warnings when preferFinalAssistantVisibleText === true and final assistant-visible text is present. (src/cron/isolated-agent/helpers.ts:289, 520992a1defd)
delivery context source: Bare delivery.mode === "none" without an explicit target leaves the resolved channel undefined and sets deliveryRequested: false. (src/cron/isolated-agent/run.ts:382, 520992a1defd)
single production executor caller: Repository search shows executeCronRun is only called from runCronIsolatedAgentTurn; other direct references are tests or the export itself. (src/cron/isolated-agent/run.ts:1291, 520992a1defd)

Likely related people:

Peter Steinberger: Current blame for the cron output policy, recovered-tool-warning gate, and no-delivery context branch points to 9fd5f9e, and broader history shows repeated cron delivery/outcome commits. (role: recent area contributor; confidence: high; commits: 9fd5f9ee7ca0, 4e07bdbdfd1b, 9b99787c3197; files: src/cron/isolated-agent/channel-output-policy.ts, src/cron/isolated-agent/helpers.ts, src/cron/isolated-agent/run.ts)
Ayaan Zaidi: Recent history on the same isolated cron run/executor files includes no-delivery and runner-owned delivery fixes that share the message-tool/no-deliver invariant touched here. (role: adjacent delivery owner; confidence: medium; commits: 49ae60d6cae1, 13a0d7a9e035; files: src/cron/isolated-agent/run.ts, src/cron/isolated-agent/run-executor.ts)
Vincent Koc: April cron runtime seam and lazy-loading refactors repeatedly touched the same isolated cron run and executor modules, making him a useful routing candidate for owner-boundary review. (role: adjacent refactor owner; confidence: medium; commits: 35176f3cb730, a5980df10128, 28787985c4eb; files: src/cron/isolated-agent/run.ts, src/cron/isolated-agent/run-executor.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.

shakkernerd · 2026-06-08T18:13:23Z

Landed via rebase merge after refreshing on current main.

Verification:

GitHub CI passed on rebased head 8455cfa32b.
Focused Testbox proof passed: tbx_01ktm5sw5e28ghennbaws3n3f1
- CI=true OPENCLAW_VITEST_FS_MODULE_CACHE_PATH=/tmp/openclaw-vitest-cache corepack pnpm test src/cron/isolated-agent/channel-output-policy.test.ts src/cron/isolated-agent/run.message-tool-policy.test.ts src/cron/isolated-agent.helpers.test.ts
- 3 files, 71 tests passed.
Changed gate passed: tbx_01ktm5vzdsvs3c7wrng4wegatq
- CI=true OPENCLAW_CHECK_CHANGED_REMOTE_CHILD=1 OPENCLAW_CHANGED_LANES_RAW_SYNC=1 corepack pnpm check:changed

Merged as 4eb4b87c8e.

…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 the size: S label Jun 5, 2026

shakkernerd self-assigned this Jun 8, 2026

fix(cron): recover no-deliver tool warnings

8455cfa

shakkernerd force-pushed the ai-hpc/fix-cron-no-deliver-tool-warning branch from bf3c638 to 8455cfa Compare June 8, 2026 18:04

shakkernerd merged commit 4eb4b87 into openclaw:main Jun 8, 2026
160 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(cron): recover no-deliver tool warnings#90678

fix(cron): recover no-deliver tool warnings#90678
shakkernerd merged 1 commit into
openclaw:mainfrom
ai-hpc:ai-hpc/fix-cron-no-deliver-tool-warning

ai-hpc commented Jun 5, 2026

Uh oh!

clawsweeper Bot commented Jun 5, 2026 •

edited

Loading

Uh oh!

Uh oh!

shakkernerd commented Jun 8, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

ai-hpc commented Jun 5, 2026

Summary

Verification

Real behavior proof

Uh oh!

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

Uh oh!

Uh oh!

Uh oh!

shakkernerd commented Jun 8, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

clawsweeper Bot commented Jun 5, 2026 •

edited

Loading