By devasher · Edited by Nominiclaw
This update focuses on improving diagnostic logging, fixing critical agent self-healing reporting bugs, and resolving several OS-specific issues for macOS and Windows users.
Several updates improve how agents handle errors and maintain context. A critical fix was implemented for the cron classifier, which previously flagged agent runs as fatal failures even if the agent successfully self-healed (e.g., by replacing a failed edit tool call with a successful write to the same path). The system now recognizes cross-tool recovery for file mutations, ensuring users aren't alerted to transient errors that were resolved internally.
In the plugin system, a bug was fixed where cached descriptor-backed tools would fail with "plugin tool runtime missing" if a plugin registered multiple unnamed factories. The dispatcher now iterates through candidates to match the actual runtime tool name, ensuring reliable tool execution for complex plugins.
Other agent improvements include:
nominiclaw/compact operations in Codex now preserve the recent conversation tail even when the summarization input is empty, preventing accidental loss of session context.Significant effort was directed toward stabilizing the experience on Windows and macOS:
openclaw update by piping child stdio instead of inheriting it, and eliminated annoying console flashes during shell environment probes by adding windowsHide: true.openclaw gateway restart would fail on Apple Silicon because Homebrew paths (/opt/homebrew/bin) were missing from the generated LaunchAgent environment. Additionally, a guard was added to the macOS config writer to prevent destructive snapshots from stripping mandatory envelope fields like gateway.mode.tini as the PID 1 init wrapper to properly reap zombie processes, preventing process table pollution and lock-file poisoning in long-running containers.Sender (untrusted metadata) JSON blocks from chat streams, providing a cleaner user experience. Furthermore, the Web exec approval modal now highlights command risks based on parser-backed metadata, helping users make safer authorization decisions.service_tier parameter, allowing users to utilize cost-optimized tiers like "flex" for non-time-sensitive workloads.These changes collectively reduce "noise" for the user—whether that noise is a phantom failure warning in a cron job, a flashing console window on Windows, or internal metadata in a chat stream. By hardening the configuration writers on macOS and improving process management in Docker, the platform is more stable for production deployments.
From a developer and power-user perspective, the addition of Bedrock service tiers and improved Telegram reply hydration provides more flexibility and cost-efficiency. The most significant impact is the reduction of operational friction: users on Windows can now update the CLI without hanging their terminal, and macOS users can restart their gateways without manual PATH intervention.