OpenClaw Digest: Enhancing Observability, Agent Reliability, and OS Integration

Merged PRs

• fix(fetch-timeout): pass operation and url context at omitting call sites (Original PR)
• fix(agents): self-heal cross-tool file-mutation in cron classifier (Original PR)
• fix: separate Current time from Reference UTC (Original PR)
• Harden Telegram QA live harness (Original PR)
• test: cover download parent symlink race (Original PR)
• fix(cli): canonicalize infer model refs safely (Original PR)
• fix(daemon): include Homebrew paths in LaunchAgent env (Original PR)
• fix(macos): guard config writer fallback (Original PR)
• fix(ui): hide sender metadata in control chat (Original PR)
• [codex] Preserve recent tail for empty manual compact (Original PR)
• feat(docker): integrate tini as PID 1 init wrapper to reap zombie processes (Original PR)
• Hydrate Telegram reply chains (Original PR)
• feat(amazon-bedrock): support service_tier parameter for Bedrock models (Original PR)
• [AI-assisted] Fix cached plugin tool wrapper bug - iterate through candidates to match by actual runtime tool name (Original PR)
• perf(agents): skip idle wait on abort to release session lock synchronously (Original PR)
• fix(browser): keep user tabs open when SSRF guard rejects read-only ops (Original PR)
• Keep OpenAI Codex migrations on automatic runtime routing (Original PR)
• fix(update): pipe post-core child stdio on Windows to prevent terminal hang (Original PR)
• fix(shell-env): hide Windows login shell probe (Original PR)
• Highlight exec command risks in Web approvals (Original PR)

Key Changes

Agent Reliability and Tooling

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:

• Performance: Aborted agent runs now skip idle waits to release session locks synchronously, reducing blocking for subsequent messages.
• Context Preservation: Manual /compact operations in Codex now preserve the recent conversation tail even when the summarization input is empty, preventing accidental loss of session context.

OS and Infrastructure Integration

Significant effort was directed toward stabilizing the experience on Windows and macOS:

• Windows: Resolved a terminal hang during openclaw update by piping child stdio instead of inheriting it, and eliminated annoying console flashes during shell environment probes by adding windowsHide: true.
• macOS: Fixed a critical issue where 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.
• Docker: Integrated tini as the PID 1 init wrapper to properly reap zombie processes, preventing process table pollution and lock-file poisoning in long-running containers.

User Interface and Experience

• Web UI: The Control UI now strips internal 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.
• Browser Plugin: Read-only browser operations (like snapshots) that are rejected by the SSRF guard no longer silently close the user's tab, reducing the risk of data loss for users attached to their own Chrome profiles.

Provider and Integration Updates

• Amazon Bedrock: Now supports the service_tier parameter, allowing users to utilize cost-optimized tiers like "flex" for non-time-sensitive workloads.
• Telegram: Enhanced the Telegram integration by hydrating reply chains from persisted parent messages, providing the agent with better conversational context.

Impact

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.