OpenClaw published v2026.7.1-beta.1 on July 2nd, the first July beta after the stable v2026.6.11 line.
The release is broad, but it has a clear theme: OpenClaw is tightening the paths where users move between models, mobile clients, external coding harnesses, messaging channels, and scheduled automation.
That makes this beta less about one isolated headline and more about connected operator workflows. A user can select newer OpenAI preview models, attach an external harness to a Gateway session, steer Codex from Telegram, run cron jobs from exit events, and use refreshed native apps with fewer rough edges.
The Headline Changes
The release notes call out seven highlights:
- GPT-5.6 family recognition across model catalogs and runtime selection
openclaw attachfor launching an external harness against an existing Gateway session- Telegram Codex pairing, steering, and final-reply recovery improvements
on-exitcron schedules plus detached session-targeted runs- Native iOS and Android app refreshes and localization work
- iMessage poll creation, reading, and voting
- Scoped conversation capability profiles for future per-conversation boundaries
Several of those areas were already visible in late June and early July pull requests, but the beta matters because it bundles them into an installable channel with release evidence and manifests.
Better Model and Harness Routes
The model work is led by PR #98333, which adds GPT-5.6 Sol, Terra, and Luna support for users with preview access. The release notes also mention Nemotron Super's 1M context window and preservation of explicit OpenRouter authentication headers.
The harness story comes from PR #96454, which added openclaw attach. That command mints a temporary Gateway grant, writes a Claude Code MCP config, launches the external harness, and revokes the grant on exit.
Together, those two changes show where OpenClaw's control-plane work is headed: model selection and external tool access need to be explicit, inspectable, and scoped rather than hidden behind one broad runtime default.
Cron and Messaging Keep Getting Attention
Cron remains one of the busiest parts of OpenClaw. This beta includes the new on-exit schedule kind from PR #92037, detached session-targeted run work from PR #98755, and a set of fixes around timeout model preservation, catch-up deferrals, action-required output, thinking overrides, and daily reset sessions.
Messaging also gets a substantial pass. Telegram reliability fixes cover stalled ingress claims, restart-dropped media, transient polling errors, poison updates, forwarded rich text, plugin callbacks, and rejected rich final replies. iMessage gains poll creation, reading, and voting. Slack, WeChat, Nostr, and other channel paths pick up routing and delivery corrections.
These are not flashy changes in isolation, but they are exactly the kind of work that determines whether an always-on personal agent feels dependable after weeks of use.
Native Apps Move Forward
The release notes describe a native app refresh across iOS and Android. iOS gets newer navigation, settings, Chat, Talk, and onboarding flows, while localization expands across Apple and Android surfaces.
That matters because OpenClaw's mobile story is now part of the main product, not a side experiment. Earlier docs updates moved the apps out of pre-release language, and this beta continues the shift toward treating mobile as a first-class control surface.
Validation
The release includes downloadable evidence artifacts, a release manifest, postpublish evidence, and checksums. The notes also link to the full release CI report, release publish workflow, npm preflight, validation workflow, plugin publishing, and Windows Hub promotion evidence.
For a beta with this many surfaces, that evidence trail is important. It gives operators more than a changelog: it gives them a way to trace what was built, published, and verified.
Bottom Line
OpenClaw v2026.7.1-beta.1 is a platform beta. GPT-5.6 support and openclaw attach are the most obvious developer-facing changes, but the release is just as much about cron correctness, messaging durability, and native app polish.
If you run OpenClaw as a personal operating layer rather than a single terminal tool, this is the kind of beta worth watching closely.