OpenClaw Observable State Snapshot, Sticky Cancel Semantics, and What PR #64749 Still Needs Before Merge

Tools

PR #64749: Observable Worker State Snapshot Adds Runtime Visibility Without Touching SQLite

This PR writes a lightweight worker-state.json from the task registry observer layer so you can inspect runtime state without scraping the database. It is a small but meaningful step toward operability for anyone running OpenClaw as persistent infrastructure rather than a chat tool.

Analysis

Managed Child Task Execution: How Sticky Cancel Intent Works in the TaskFlow Substrate

The cancelRequestedAt stamp-before-shutdown pattern means a parent flow signals stop intent immediately and children wind down asynchronously, which prevents orphaned tasks after a cancel. If you are building multi-step automation on top of OpenClaw, this is the cancellation contract you are working with.

before_agent_reply Hook and api.runtime.taskFlow: The Two 4.2 Plugin Seams Worth Building On

The before_agent_reply hook lets plugins short-circuit the LLM entirely and return synthetic replies, which is a real cost-reduction lever for high-traffic channels handling repetitive requests. Combined with first-class Task Flow access from plugin code, 4.2 gives plugin authors two new primitives that did not exist in 4.1.

Security

Android Assistant PR Merged With a P1 Shortcuts Bug and a Medium-Severity Intent Spoofing Finding

The shortcuts meta-data was placed outside the launcher activity element, meaning App Actions and static shortcuts would silently not register on any device. The Aisle security bot also flagged that any third-party app can spoof an assistant intent and pre-fill the chat composer with arbitrary text, which is a real prompt injection vector.

News

Task Flow Config Migration: What Moving xAI and Firecrawl to Plugin-Owned Paths Actually Changes

The move from tools.web.x_search. and tools.web.fetch.firecrawl. to plugin-owned namespaces is the right call architecturally, but it will silently break existing configs if you skip the doctor --fix step. Run the migration command before assuming your search or fetch tools still work after updating.