$ the-wire · showcase
OpenClaw fixes premature approval expiry, embedding readiness, and startup integrity proofs
By RepoJournal · Filed · About OpenClaw · Composed from the cited sources · methodology
![openclaw-docs-sync[bot]](https://avatars.githubusercontent.com/u/13697529?v=4)
Gateway node approvals no longer expire after the operator already said yes, managed Ollama and LM Studio embeddings stop eating memory_search's deadline, and a background integrity scan now keeps its proof across startup admission.
fix(gateway): preserve live node approval handoffs openclaw/openclaw
A stale second clock in the gateway let an operator's allow-once or allow-always decision expire mid-dispatch; on a paired CLI node with a two-second approval window, both decisions were rejected about 2.1 seconds after resolution and the run never happened. The fix preserves the live node approval handoff, so an approved system.run request is no longer dropped when dispatch crosses the prompt ...
fix(memory): report managed local-service readiness from the Ollama and LM Studio embedding providers openclaw/openclaw
Managed Ollama and LM Studio embedding startup used to consume memory_search's 30-second deadline even though startup has its own localService.readyTimeoutMs budget. Both adapters now report readiness waits to the existing memory deadline owner, matching the shared OpenAI-compatible adapter, while warm and unmanaged services and post-readiness embedding deadlines stay as they were.
fix(state): retain integrity proof across startup admission openclaw/openclaw
An integrity scan that finished before the agent's startup preparation admitted ordinary writes could lose its proof, forcing another full integrity and foreign-key scan after the next clean shutdown. Verification now waits on that same startup admission and keeps the receipt through the original writer, and failed preparation still reports the original failure.
improve: show useful Telegram and Discord progress by default openclaw/openclaw
Long-running Telegram and Discord requests could look idle because Discord defaults to no preview and quiet progress shows only "Working" even with a delegated task active. Progress is now on by default for both surfaces, a maintainer-directed change that treats Discord's omitted-setting default as intentional while explicit off still wins.
fix(ui): CI automation toggles lag and shift the popover openclaw/openclaw
CI automation toggles no longer jump back or make the popover look like it reloads on every click, and other options stay usable during a save. "Next check" details and automation links are gone while genuine errors, blockers, and GitHub check and job links remain; the docs mirror also picked up five syncs from openclaw/openclaw.
