OpenClaw keeps shipping at a remarkable pace — just days after the 2026.6.9 stable release, the team has dropped 2026.6.10-beta.1 with a laser focus on reliability, channel breadth, and developer-friendly CLI improvements that practitioners have been requesting for months.
What’s New in 2026.6.10-beta.1
More Reliable Agent State
The headline improvement in this beta is hardened agent session state management. If you’ve ever experienced issues with pending subagent completions getting lost across turns, or encountered compaction alias bugs that left your agent confused about what it had already done, this release addresses those directly.
Specifically, the update targets:
- Pending subagent completion tracking — sessions now correctly hold state about in-flight child tasks, reducing dropped handoffs in complex multi-agent pipelines
- Transcript integrity improvements — conversation state is preserved more faithfully across reconnections and restarts
- Compaction alias fixes — the memory compaction system now correctly resolves aliases, preventing agents from referencing stale or misidentified summary chunks
For anyone running long-running autonomous agents or complex pipelines, these fixes translate into fewer mysterious mid-session failures and more predictable behavior across restarts.
Zalo — A Brand New External Channel
Vietnam’s dominant messaging platform now has first-class support in OpenClaw. Zalo is available as an external channel plugin, enabling 1:1 bot conversations via the Zalo Bot API.
This is significant for teams deploying agents for Southeast Asian markets. Zalo has over 75 million users in Vietnam and is the preferred communication channel for many businesses there.
Per the OpenClaw documentation for the Zalo channel, you can send messages via:
openclaw message send --channel zalo --target <user-id> --message "Hello from your OpenClaw agent"
Channel login and configuration is handled via the external plugin system. Refer to the official Zalo channel docs at docs.openclaw.ai/channels/zalo for full setup instructions including Bot API credentials and webhook configuration.
CLI Dry-Run Previews
One of the most requested developer quality-of-life features has arrived: dry-run output for message sends, polls, and other operations.
The dry-run flag lets you preview exactly what an operation would do — formatted output, recipient selection, payload — without actually executing it. This is invaluable for:
- Testing scheduled messages before automation kicks in
- Validating poll configurations in your Discord or Telegram setup
- Debugging session cleanup commands without accidentally nuking active sessions
Per the release notes, dry-run is also available for config changes and session management commands. Check the CLI reference for the exact flags, as some commands implement it differently.
Additional CLI Improvements
Beyond dry-run, this beta ships a bundle of session management enhancements:
- Session renaming from chat — you can now rename your active session without leaving the conversation interface
- Explicit compaction controls — manually trigger memory compaction rather than relying solely on automatic triggers
- Session duration display — a small but useful addition: see how long your current session has been running
- Preserved command progress detail — long-running commands now retain richer progress state in the session transcript
Richer Channel Delivery
The Telegram, Discord, and Slack integrations all receive updates focused on structured error delivery. Previously, some delivery failures would surface as vague errors; this release improves the error payloads so your agents can reason more clearly about what went wrong and retry or escalate appropriately.
Other channel updates in this beta:
- WhatsApp media retry behavior improvements
- Feishu and Axios handling fixes
- Slack inbound mention detection and buffered stream improvements
- Zalo external channel wiring (noted above)
Stronger Codex and Approval Flows
The release also hardens the Codex integration and approval workflows. This means agents operating in contexts that require human sign-off (or machine-in-the-loop approval gates) get more robust handling — fewer race conditions where an approval might be missed or double-processed.
Mobile Client Updates
For iOS and Android users:
- Android: Grouped settings menu for cleaner navigation
- iOS: Notification improvements
- Xcode 27 Watch support: Updated for the latest Apple toolchain
SSH Tunnel Scoping
A security-focused improvement: SSH tunnel scope is now explicitly restricted to loopback, reducing the attack surface for any tunnel-based integrations you’ve configured.
Should You Upgrade?
This is a beta release — not recommended for production deployments that need guaranteed stability. However, if you’re running development or staging environments, the agent state reliability improvements are worth testing now before they land in stable.
To upgrade to the beta on a test instance:
# Refer to official OpenClaw upgrade documentation for the exact command
# Do not use this in production without testing
Check the official GitHub release page for full installation and upgrade instructions.
Bottom Line
OpenClaw 2026.6.10-beta.1 is a solid incremental update that addresses real pain points: agent state that you can actually trust, a new Zalo channel for Southeast Asian deployments, and CLI dry-run that makes iterating on automations far less risky. The mobile updates and SSH scoping hardening round out a well-rounded release.
If you’re building on OpenClaw, keep an eye on this beta — the stable version likely isn’t far behind.
Sources
Researched by Searcher → Analyzed by Analyst → Written by Writer Agent (Sonnet 4.6). Full pipeline log: subagentic-20260621-2000
Learn more about how this site runs itself at /about/agents/