Skip to content

fix(android): avoid dataSync FGS for persistent node#80082

Merged
obviyus merged 2 commits into
openclaw:mainfrom
davelutztx:fix-android-node-connected-device-fgs
Jun 8, 2026
Merged

fix(android): avoid dataSync FGS for persistent node#80082
obviyus merged 2 commits into
openclaw:mainfrom
davelutztx:fix-android-node-connected-device-fgs

Conversation

@davelutztx

@davelutztx davelutztx commented May 10, 2026

Copy link
Copy Markdown

Summary

  • switches the persistent Android node foreground service from dataSync to connectedDevice
  • declares FOREGROUND_SERVICE_CONNECTED_DEVICE and the required normal CHANGE_NETWORK_STATE companion permission
  • keeps microphone as an additive foreground-service type only when talk mode is active
  • updates the node foreground-service unit test expectations

Why

Android 15 applies a time budget to foreground services of type dataSync. The OpenClaw node service is a long-lived device connection to the gateway, not a bounded sync job, so dataSync can be exhausted and Android can then crash or deny service restarts with errors like:

  • ForegroundServiceDidNotStopInTimeException
  • ForegroundServiceStartNotAllowedException: Time limit already exhausted for foreground service type dataSync

connectedDevice better matches the service's purpose: keeping the Android device connected as an OpenClaw node. Android requires a connected-device foreground service to declare at least one qualifying capability permission; this PR uses CHANGE_NETWORK_STATE, a normal permission, so no new runtime permission prompt is introduced.

Real behavior proof

  • Behavior addressed: Android OpenClaw node foreground service no longer crashes/restarts immediately after the dataSync foreground-service budget is exhausted. Before this change, adb/logcat showed NodeForegroundService crashes from ForegroundServiceDidNotStopInTimeException and ForegroundServiceStartNotAllowedException: Time limit already exhausted for foreground service type dataSync.
  • Real environment tested: Samsung Galaxy Z Fold7 (SM-F966U1) running the OpenClaw Android node app with targetSdk=36, connected to a live OpenClaw gateway over the normal Android node websocket route.
  • Exact steps or command run after fix: Built a debug APK with this change; installed it with adb install -r; force-stopped ai.openclaw.app; cleared logcat; launched the app with adb shell monkey -p ai.openclaw.app -c android.intent.category.LAUNCHER 1; checked openclaw nodes status; filtered adb logcat for AndroidRuntime, ForegroundServiceStartNotAllowedException, ForegroundServiceDidNotStopInTimeException, and NodeForegroundService.
  • Observed result after fix: The Android node process stayed alive after launch, the Fold7 node reconnected to the gateway, and the crash filter had no new OpenClaw AndroidRuntime/FGS crash entries after the final connected-device build.
  • What was not tested: Long-duration 6+ hour soak on multiple Android OEMs was not run in this PR. The failure mode was reproduced and cleared on a real Samsung targetSdk 36 device, and unit/build/APK manifest checks were run locally.
  • Evidence after fix: adb/logcat before fix showed Process: ai.openclaw.app, ForegroundServiceDidNotStopInTimeException: A foreground service of type dataSync did not stop within its timeout, and ForegroundServiceStartNotAllowedException: Time limit already exhausted for foreground service type dataSync at NodeForegroundService.startForegroundWithTypes(NodeForegroundService.kt:187). After the fix, live command output showed Performing Streamed Install, Success, versionName=2026.5.5, pid=28121, Known: 2 · Paired: 2 · Connected: 1, Dave's Z Fold7 ... openclaw-android/node ... paired · connected (just now), and logcat only reported ActivityManager: Background started FGS: Allowed [callingPackage: ai.openclaw.app; ... targetSdkVersion:36] with no new AndroidRuntime, ForegroundServiceStartNotAllowedException, or ForegroundServiceDidNotStopInTimeException entries for ai.openclaw.app after final launch.

Validation

  • ./gradlew :app:testPlayDebugUnitTest :app:assemblePlayDebug
  • inspected the built APK manifest with aapt:
    • includes android.permission.FOREGROUND_SERVICE_CONNECTED_DEVICE
    • includes android.permission.CHANGE_NETWORK_STATE
    • no longer includes android.permission.FOREGROUND_SERVICE_DATA_SYNC
    • NodeForegroundService has foreground service type 0x90 (connectedDevice | microphone)

@openclaw-barnacle openclaw-barnacle Bot added app: android App: android size: XS triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. proof: supplied External PR includes structured after-fix real behavior proof. and removed triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. labels May 10, 2026
@clawsweeper

clawsweeper Bot commented May 10, 2026

Copy link
Copy Markdown
Contributor

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

Summary
The branch switches Android NodeForegroundService from dataSync to connectedDevice, updates companion manifest permissions, unit expectations, and the Android platform docs.

PR surface: Docs 0, Other -15. Total -15 across 4 files.

Reproducibility: yes. The linked issue provides the dataSync foreground-service timeout stack trace, current main still uses dataSync, and Android's docs describe the same Android 15+ timeout and exception path; I did not run a live Android repro in this read-only review.

Review metrics: 1 noteworthy metric.

  • Android FGS contract changed: 2 permissions added/replaced, 1 permission removed, 1 service type changed. The manifest permission and foreground-service type contract is enforced by Android at runtime, so maintainers should notice the OS-facing compatibility surface before merge.

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

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

Risk before merge

  • [P1] This changes an OS-enforced Android foreground-service contract; the supplied proof is strong for one Samsung targetSdk 36 device, but it is not a long multi-OEM soak.

Maintainer options:

  1. Accept the focused Android FGS change (recommended)
    Land the current connected-device repair with the supplied Samsung/logcat proof and normal checks, while accepting the residual multi-OEM soak gap.
  2. Require broader Android proof
    Ask for an additional OEM or longer soak before merge if maintainers want stronger runtime compatibility evidence for the OS-facing manifest change.
  3. Pause for a different Android strategy
    Pause this PR only if maintainers prefer a different foreground-service type or lifecycle design for the persistent node.

Next step before merge

  • [P2] No repair lane is needed; the remaining action is maintainer review and land/close handling for the proof-positive Android crash fix.

Security
Cleared: The diff changes Android manifest permissions but uses the normal CHANGE_NETWORK_STATE companion permission required by the connected-device FGS contract, with no dependency, CI, secret, or code-execution surface changed.

Review details

Best possible solution:

Land this focused connected-device foreground-service repair, or an equivalent maintainer-approved Android fix, and close the linked crash issue after main no longer uses dataSync for the long-lived node service.

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

Yes. The linked issue provides the dataSync foreground-service timeout stack trace, current main still uses dataSync, and Android's docs describe the same Android 15+ timeout and exception path; I did not run a live Android repro in this read-only review.

Is this the best way to solve the issue?

Yes. Switching the persistent node service to connectedDevice with the required companion permission is the narrowest maintainable fix for a long-lived device connection, and the PR now updates runtime, manifest, test expectations, and docs together.

AGENTS.md: found and applied where relevant.

Codex review notes: model gpt-5.5, reasoning high; reviewed against 9a82b60024b5.

Label changes

Label changes:

  • add merge-risk: 🚨 compatibility: The diff changes Android foreground-service type and manifest permissions, which are runtime-enforced platform compatibility contracts across Android versions and OEMs.
  • add rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🦞 diamond lobster and patch quality is 🦞 diamond lobster.
  • remove rating: 🐚 platinum hermit: Current PR rating is rating: 🦞 diamond lobster, so this older rating label is no longer current.

Label justifications:

  • P1: The PR fixes a linked Android node crash/restart loop that can break the real device connection workflow for affected users.
  • merge-risk: 🚨 compatibility: The diff changes Android foreground-service type and manifest permissions, which are runtime-enforced platform compatibility contracts across Android versions and OEMs.
  • rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🦞 diamond lobster and patch quality is 🦞 diamond lobster.
  • status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (logs): The PR body includes after-fix real-device adb/logcat and node-status output showing a Samsung targetSdk 36 Android node stayed connected with no new FGS crash signatures.
  • proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes after-fix real-device adb/logcat and node-status output showing a Samsung targetSdk 36 Android node stayed connected with no new FGS crash signatures.
Evidence reviewed

PR surface:

Docs 0, Other -15. Total -15 across 4 files.

View PR surface stats
Area Files Added Removed Net
Source 0 0 0 0
Tests 0 0 0 0
Docs 1 1 1 0
Config 0 0 0 0
Generated 0 0 0 0
Other 3 7 22 -15
Total 4 8 23 -15

What I checked:

  • Repository policy read: Read the full root AGENTS.md and the scoped docs/AGENTS.md; the review applied the OpenClaw requirement to inspect source, tests, docs, dependency contract, current behavior, and history before verdict. (AGENTS.md:1, 9a82b60024b5)
  • Current main manifest still uses dataSync: Current main declares FOREGROUND_SERVICE_DATA_SYNC and android:foregroundServiceType="dataSync|microphone" for NodeForegroundService, so the central change is not already on main. (apps/android/app/src/main/AndroidManifest.xml:5, 9a82b60024b5)
  • Current main runtime still uses DATA_SYNC: foregroundServiceTypesForVoiceMode currently uses ServiceInfo.FOREGROUND_SERVICE_TYPE_DATA_SYNC as the base type and adds microphone only for Talk Mode. (apps/android/app/src/main/java/ai/openclaw/app/NodeForegroundService.kt:237, 9a82b60024b5)
  • PR diff targets the implicated Android path: The PR diff changes the manifest to connectedDevice|microphone, replaces the data-sync permission with FOREGROUND_SERVICE_CONNECTED_DEVICE, adds CHANGE_NETWORK_STATE, and changes runtime/test expectations to FOREGROUND_SERVICE_TYPE_CONNECTED_DEVICE. (apps/android/app/src/main/AndroidManifest.xml:1, 136bfd8d214b)
  • Docs blocker is resolved in the PR diff: The current PR diff updates docs/platforms/android.md from dataSync/dataSync|microphone to connectedDevice/connectedDevice|microphone and mentions the connected-device companion permission. (docs/platforms/android.md:218, 136bfd8d214b)
  • Android dependency contract checked: Android's official foreground-service docs state that Android 15+ limits dataSync foreground services to 6 hours per 24 hours and can throw ForegroundServiceStartNotAllowedException with Time limit already exhausted for foreground service type dataSync; the same docs list connectedDevice, FOREGROUND_SERVICE_CONNECTED_DEVICE, and CHANGE_NETWORK_STATE as a qualifying manifest permission path.

Likely related people:

  • @obviyus: Ayaan Zaidi appears in the merged Android foreground-service history, authored related service/runtime changes, is assigned on this PR, and force-pushed the latest head commit for the connected-device repair. (role: feature-history owner and current assignee; confidence: high; commits: 5568b393a86d, 46145fde1988, 136bfd8d214b; files: apps/android/app/src/main/java/ai/openclaw/app/NodeForegroundService.kt, apps/android/app/src/test/java/ai/openclaw/app/NodeForegroundServiceTest.kt, apps/android/app/src/main/AndroidManifest.xml)
  • @steipete: Peter Steinberger authored the merged Talk Mode exposure and recent Android service/doc comment work that touches the same foreground-service and voice capture surface. (role: Android Talk and foreground-service area contributor; confidence: medium; commits: 86d897cfaa6a, 0ef6702af379, 85beee613c64; files: apps/android/app/src/main/java/ai/openclaw/app/NodeForegroundService.kt, apps/android/app/src/main/AndroidManifest.xml, docs/platforms/android.md)
  • @joshavant: Josh Avant has several recent merged commits in NodeRuntime.kt, the caller/callee side that drives NodeForegroundService.setVoiceCaptureMode for Talk and Mic state. (role: recent Android runtime contributor; confidence: medium; commits: 72b387ad488c, 53e50ec12747, 81f4fe6c113b; files: apps/android/app/src/main/java/ai/openclaw/app/NodeRuntime.kt)
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.

@RomneyDa

Copy link
Copy Markdown
Member

Heads up: this PR needs to be updated against current main before the new required Dependency Guard check can pass.

@davelutztx davelutztx force-pushed the fix-android-node-connected-device-fgs branch from 8434940 to ec81366 Compare May 29, 2026 18:36
@openclaw-barnacle openclaw-barnacle Bot removed the proof: sufficient ClawSweeper judged the real behavior proof convincing. label May 29, 2026
@clawsweeper clawsweeper Bot added proof: sufficient ClawSweeper judged the real behavior proof convincing. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. P1 High-priority user-facing bug, regression, or broken workflow. labels May 29, 2026
@obviyus obviyus self-assigned this Jun 8, 2026
@obviyus obviyus force-pushed the fix-android-node-connected-device-fgs branch from ec81366 to 136bfd8 Compare June 8, 2026 13:33
@openclaw-barnacle openclaw-barnacle Bot added the docs Improvements or additions to documentation label Jun 8, 2026
@clawsweeper clawsweeper Bot added rating: 🦞 diamond lobster Very strong PR readiness with only minor maintainer review expected. merge-risk: 🚨 compatibility 🚨 May break existing users, config, migrations, defaults, or upgrade paths. and removed rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. labels Jun 8, 2026
@obviyus obviyus merged commit 6d7eb9b into openclaw:main Jun 8, 2026
58 of 64 checks passed
@obviyus

obviyus commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Landed via rebase onto main.

  • Scoped tests: git diff --check; pnpm docs:list; ./gradlew :app:testPlayDebugUnitTest --tests ai.openclaw.app.NodeForegroundServiceTest; .agents/skills/autoreview/scripts/autoreview --mode branch --base origin/main
  • GitHub checks: android-build-play, android-test-play, android-test-third-party, check-docs, Real behavior proof, dependency-guard, preflight, security-fast all passed on the pushed head.
  • Changelog: not updated; release generation owns CHANGELOG.md for normal PRs.
  • PR branch head before merge: 136bfd8d214b20806148b43578c2e1b906a7cef5
  • Main commits: 7d357a75fd (runtime/manifest/test), 6d7eb9bb84 (distill/docs cleanup)
  • Merge commit: 6d7eb9bb8483b590a1c60322c5ea4fda733ed8ad

Thanks @davelutztx!

eleboucher pushed a commit to eleboucher/homelab that referenced this pull request Jun 12, 2026
…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. ([#&#8203;91529](openclaw/openclaw#91529), [#&#8203;91618](openclaw/openclaw#91618), [#&#8203;91615](openclaw/openclaw#91615), [#&#8203;91619](openclaw/openclaw#91619), [#&#8203;91741](openclaw/openclaw#91741), [#&#8203;91745](openclaw/openclaw#91745), [#&#8203;91746](openclaw/openclaw#91746), [#&#8203;91748](openclaw/openclaw#91748), [#&#8203;91749](openclaw/openclaw#91749), [#&#8203;91750](openclaw/openclaw#91750), [#&#8203;91751](openclaw/openclaw#91751), [#&#8203;91752](openclaw/openclaw#91752), [#&#8203;91763](openclaw/openclaw#91763), [#&#8203;89938](openclaw/openclaw#89938)) Thanks [@&#8203;joshavant](https://github.com/joshavant), [@&#8203;pgondhi987](https://github.com/pgondhi987), [@&#8203;mmaps](https://github.com/mmaps), [@&#8203;eleqtrizit](https://github.com/eleqtrizit), [@&#8203;shakkernerd](https://github.com/shakkernerd), and [@&#8203;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. ([#&#8203;91189](openclaw/openclaw#91189), [#&#8203;88682](openclaw/openclaw#88682), [#&#8203;89588](openclaw/openclaw#89588), [#&#8203;90212](openclaw/openclaw#90212), [#&#8203;91876](openclaw/openclaw#91876), [#&#8203;91874](openclaw/openclaw#91874), [#&#8203;91904](openclaw/openclaw#91904), [#&#8203;91478](openclaw/openclaw#91478), [#&#8203;91915](openclaw/openclaw#91915)) Thanks [@&#8203;codysai001](https://github.com/codysai001), [@&#8203;alexzhu0](https://github.com/alexzhu0), [@&#8203;joelnishanth](https://github.com/joelnishanth), [@&#8203;snowzlm](https://github.com/snowzlm), [@&#8203;obviyus](https://github.com/obviyus), and [@&#8203;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. ([#&#8203;91335](openclaw/openclaw#91335), [#&#8203;91449](openclaw/openclaw#91449), [#&#8203;88969](openclaw/openclaw#88969), [#&#8203;88530](openclaw/openclaw#88530), [#&#8203;91783](openclaw/openclaw#91783), [#&#8203;91785](openclaw/openclaw#91785)) Thanks [@&#8203;omarshahine](https://github.com/omarshahine), [@&#8203;jmissig](https://github.com/jmissig), and [@&#8203;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. ([#&#8203;91422](openclaw/openclaw#91422), [#&#8203;89851](openclaw/openclaw#89851), [#&#8203;91736](openclaw/openclaw#91736), [#&#8203;91747](openclaw/openclaw#91747), [#&#8203;91451](openclaw/openclaw#91451), [#&#8203;80143](openclaw/openclaw#80143)) Thanks [@&#8203;pgondhi987](https://github.com/pgondhi987), [@&#8203;anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia), [@&#8203;lifuyue](https://github.com/lifuyue), [@&#8203;eleqtrizit](https://github.com/eleqtrizit), [@&#8203;LiuwqGit](https://github.com/LiuwqGit), and [@&#8203;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. ([#&#8203;91531](openclaw/openclaw#91531), [#&#8203;91538](openclaw/openclaw#91538), [#&#8203;91568](openclaw/openclaw#91568), [#&#8203;91583](openclaw/openclaw#91583), [#&#8203;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. ([#&#8203;91830](openclaw/openclaw#91830), [#&#8203;91882](openclaw/openclaw#91882), [#&#8203;91590](openclaw/openclaw#91590), [#&#8203;88630](openclaw/openclaw#88630), [#&#8203;88768](openclaw/openclaw#88768), [#&#8203;91696](openclaw/openclaw#91696)) Thanks [@&#8203;Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@&#8203;joshavant](https://github.com/joshavant), [@&#8203;bdjben](https://github.com/bdjben), and [@&#8203;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. ([#&#8203;89834](openclaw/openclaw#89834), [#&#8203;90883](openclaw/openclaw#90883)) Thanks [@&#8203;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. ([#&#8203;91256](openclaw/openclaw#91256), [#&#8203;91568](openclaw/openclaw#91568), [#&#8203;91583](openclaw/openclaw#91583)) Thanks [@&#8203;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. ([#&#8203;91574](openclaw/openclaw#91574), [#&#8203;91591](openclaw/openclaw#91591), [#&#8203;90004](openclaw/openclaw#90004), [#&#8203;90927](openclaw/openclaw#90927), [#&#8203;90838](openclaw/openclaw#90838)) Thanks [@&#8203;Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@&#8203;brokemac79](https://github.com/brokemac79), and [@&#8203;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. ([#&#8203;91324](openclaw/openclaw#91324), [#&#8203;89138](openclaw/openclaw#89138), [#&#8203;90457](openclaw/openclaw#90457), [#&#8203;91837](openclaw/openclaw#91837), [#&#8203;91851](openclaw/openclaw#91851)) Thanks [@&#8203;osolmaz](https://github.com/osolmaz), [@&#8203;mushuiyu886](https://github.com/mushuiyu886), [@&#8203;ai-hpc](https://github.com/ai-hpc), and [@&#8203;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. ([#&#8203;91423](openclaw/openclaw#91423), [#&#8203;91557](openclaw/openclaw#91557), [#&#8203;89909](openclaw/openclaw#89909)) Thanks [@&#8203;cxyhhhhh](https://github.com/cxyhhhhh), [@&#8203;Solvely-Colin](https://github.com/Solvely-Colin), and [@&#8203;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. ([#&#8203;90782](openclaw/openclaw#90782), [#&#8203;89978](openclaw/openclaw#89978), [#&#8203;91580](openclaw/openclaw#91580), [#&#8203;91531](openclaw/openclaw#91531)) Thanks [@&#8203;RomneyDa](https://github.com/RomneyDa) and [@&#8203;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. ([#&#8203;85679](openclaw/openclaw#85679), [#&#8203;91450](openclaw/openclaw#91450), [#&#8203;91566](openclaw/openclaw#91566), [#&#8203;91840](openclaw/openclaw#91840), [#&#8203;91590](openclaw/openclaw#91590), [#&#8203;91361](openclaw/openclaw#91361), [#&#8203;91895](openclaw/openclaw#91895)) Thanks [@&#8203;openperf](https://github.com/openperf), [@&#8203;yetval](https://github.com/yetval), [@&#8203;joshavant](https://github.com/joshavant), [@&#8203;wangmiao0668000666](https://github.com/wangmiao0668000666), and [@&#8203;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. ([#&#8203;89151](openclaw/openclaw#89151), [#&#8203;91422](openclaw/openclaw#91422), [#&#8203;91425](openclaw/openclaw#91425), [#&#8203;91529](openclaw/openclaw#91529), [#&#8203;90212](openclaw/openclaw#90212)) Thanks [@&#8203;joelnishanth](https://github.com/joelnishanth), [@&#8203;pgondhi987](https://github.com/pgondhi987), [@&#8203;joshavant](https://github.com/joshavant), and [@&#8203;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. ([#&#8203;85823](openclaw/openclaw#85823), [#&#8203;89659](openclaw/openclaw#89659), [#&#8203;91684](openclaw/openclaw#91684), [#&#8203;91649](openclaw/openclaw#91649), [#&#8203;90263](openclaw/openclaw#90263), [#&#8203;91686](openclaw/openclaw#91686), [#&#8203;90426](openclaw/openclaw#90426)) Thanks [@&#8203;itsuzef](https://github.com/itsuzef), [@&#8203;ladygege](https://github.com/ladygege), [@&#8203;jacobtomlinson](https://github.com/jacobtomlinson), [@&#8203;fuller-stack-dev](https://github.com/fuller-stack-dev), and [@&#8203;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. ([#&#8203;90666](openclaw/openclaw#90666), [#&#8203;90678](openclaw/openclaw#90678)) Thanks [@&#8203;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. ([#&#8203;87105](openclaw/openclaw#87105), [#&#8203;91551](openclaw/openclaw#91551), [#&#8203;91219](openclaw/openclaw#91219), [#&#8203;91614](openclaw/openclaw#91614), [#&#8203;91740](openclaw/openclaw#91740), [#&#8203;91978](openclaw/openclaw#91978)) Thanks [@&#8203;fuller-stack-dev](https://github.com/fuller-stack-dev) and [@&#8203;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. ([#&#8203;91390](openclaw/openclaw#91390), [#&#8203;91709](openclaw/openclaw#91709), [#&#8203;91507](openclaw/openclaw#91507), [#&#8203;91567](openclaw/openclaw#91567), [#&#8203;88630](openclaw/openclaw#88630), [#&#8203;91696](openclaw/openclaw#91696)) Thanks [@&#8203;hxy91819](https://github.com/hxy91819), [@&#8203;brokemac79](https://github.com/brokemac79), [@&#8203;RomneyDa](https://github.com/RomneyDa), [@&#8203;joshavant](https://github.com/joshavant), and [@&#8203;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. ([#&#8203;91581](openclaw/openclaw#91581), [#&#8203;91599](openclaw/openclaw#91599), [#&#8203;91547](openclaw/openclaw#91547), [#&#8203;91591](openclaw/openclaw#91591)) Thanks [@&#8203;fuller-stack-dev](https://github.com/fuller-stack-dev), [@&#8203;sallyom](https://github.com/sallyom), and [@&#8203;Patrick-Erichsen](https://github.com/Patrick-Erichsen).
- UI: require explicit user intent before opening chat sessions and drain restored chat queues after session switches. ([#&#8203;91480](openclaw/openclaw#91480)) Thanks [@&#8203;TurboTheTurtle](https://github.com/TurboTheTurtle).
- Android: avoid the `dataSync` foreground-service type for persistent nodes. ([#&#8203;80082](openclaw/openclaw#80082)) Thanks [@&#8203;davelutztx](https://github.com/davelutztx).
- Native hooks: bound relay lifetimes so abandoned native hook connections cannot linger indefinitely. ([#&#8203;91550](openclaw/openclaw#91550)) Thanks [@&#8203;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.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xMDEuMSIsInVwZGF0ZWRJblZlciI6IjQzLjEwMS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZS9jb250YWluZXIiLCJ0eXBlL3BhdGNoIl19-->

Reviewed-on: https://git.erwanleboucher.dev/eleboucher/homelab/pulls/1040
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

app: android App: android docs Improvements or additions to documentation merge-risk: 🚨 compatibility 🚨 May break existing users, config, migrations, defaults, or upgrade paths. P1 High-priority user-facing bug, regression, or broken workflow. proof: sufficient ClawSweeper judged the real behavior proof convincing. proof: supplied External PR includes structured after-fix real behavior proof. rating: 🦞 diamond lobster Very strong PR readiness with only minor maintainer review expected. size: XS status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants