OpenClaw 2026.7.1: Control UI overhaul, GPT-5.6 compatibility, Gateway crash-loop fix
Stable 2026.7.1 release of the OpenClaw harness, drawing 3,063 contributions from 532 contributors across 2,018 credited PRs. Headline work is a Control UI and onboarding rebuild, substantial iOS/Android/macOS app updates, broader model and provider coverage including GPT-5.6, Tencent Hy3 and Meta Muse Spark 1.1, and Gateways that stop restarting forever when they fail.
PUBLISHED2026-07-13
OBSERVED2026-08-11
AGE29d
SOURCES1
- Control UI: side-by-side conversations, live Tasks, usage and cost views, files, downloads, pairing, approvals and Gateway health surfaced next to the conversation
- Guided setup checks connections before saving and preserves earlier choices if interrupted
- Official apps: iOS/iPadOS, Android and macOS updated across setup, navigation, chat, voice, permissions, localization, files, scheduled work, offline reading, queued sends, connection recovery, native session controls
- Models/providers: improved GPT-5.6 compatibility on supported OpenAI and Codex routes, complete Tencent Hy3 setup path, Meta Model API adds Muse Spark 1.1, plus Claude, Ollama, ClawRouter and LongCat work
- Coding agents:
openclaw attachgrants Claude Code temporary access to a selected session; Codex delegation and native subagents return tracked results more reliably; Copilot gains broader provider choices - Channels: substantial Telegram, Slack, Discord and Apple Messages work on threads, progress, media, identity, retries and duplicate prevention
- Gateway crash loops now leave a stable repair path instead of restarting indefinitely
- Scheduled work can wake only on change; selected signed-in browser tabs pair remotely and save completed downloads; guarded terminals on web, iOS and Android
- Hardening: fewer secrets in logs, sensitive controls limited to approved users, earlier blocking of unsafe downloads, files and network requests
- Full notes: https://docs.openclaw.ai/releases/2026.7.1
COMMUNITY
No curated reactions recorded for this event. Facts and takes are kept in separate layers — community context is added by hand, never blended into the record above.