OpenClaw Task Registry Observable State, Android Assistant Bugs Fixed, and Managed Child Execution Architecture Explained

Tools

PR #64749: Observable Worker State Snapshot Added to Task Registry

This PR wires a lightweight worker-state.json file out of the task registry observer layer, giving you a clean way to inspect runtime worker and task state without poking SQLite internals. It is a small but foundational step toward real operational visibility for anyone running OpenClaw agents in production.

Managed Child Task Execution Lands in TaskFlow Substrate

This is the first real execution layer on top of the restored TaskFlow substrate: managed flows can now spawn child tasks, and cancel propagates sticky so parent jobs stop scheduling new work immediately and let active children wind down cleanly. If you are orchestrating multi-step agent workflows, this is the PR that makes TaskFlow actually useful rather than just durable state in a database.

News

Android Assistant Entrypoints Merged with P1 Manifest Bug Addressed

The PR adds Google Assistant App Actions and ACTION_ASSIST routing into OpenClaw's chat composer, but shipped with a P1 shortcuts meta-data placement bug that would have silently killed App Actions on all devices. The fix landed before merge, so if you are on the Android companion app this should work correctly now.

Analysis

Stack Observer Breakdown: What Task Flow Restoration Means for Production DevOps Teams

Good technical writeup on the 4.2 Task Flow changes with a focus on the managed vs mirrored sync modes and the new openclaw flows inspection commands. Worth reading if you want the operational angle rather than the plugin developer angle.

OpenClaw 4.2 Operator Perspective: Task Flows, Security Hardening, and Two Breaking Config Migrations

The Playbook blog gives a practitioner take on 4.2 with concrete details on the xAI and Firecrawl config path migrations that will break your setup if you do not run openclaw doctor --fix before relying on those tools. The security hardening section on insecure TLS override blocking is worth reading if you are running OpenClaw on shared infrastructure.