代理框架
OpenClaw 2026.8.1 Moves Agent Sessions to Cross-Device Execution and Tracks Progress with Persistent State
The new OpenClaw release can dispatch workspaces and agent sessions to paired devices or cloud workers while preserving progress, branches, and sharing permissions after reconnection. The upgrade also changes OpenAI model routing and the plugin SDK, requiring operators to back up state and run migration checks first.
OpenClaw 2026.8.1 expands agent sessions, previously centralized in a single Gateway, into portable execution units. According to the [official release notes](https://github.com/openclaw/openclaw/releases/tag/v2026.8.1), tasks can be dispatched to paired devices or cloud workers and moved together with their workspaces. Warm machines and project seeds can also be reused later. The release additionally introduces `openclaw agent exec`, which can start headless execution in a specified directory, use ephemeral or persistent state, configure model fallbacks, and return machine-readable results.
State management has also been further decoupled from chat history. The new `progress_card` stores up to fifty steps and short descriptions in the Gateway. When a browser reloads or a client reconnects, it reads the latest revision directly instead of reconstructing it from tool events. The official [tool documentation](https://docs.openclaw.ai/tools/progress-card) states that each update replaces the entire card, making it the single source of truth. Web and native clients can display subagent activity and accumulated changes, while administrators can configure the owner and visibility of shared sessions, as well as permissions to view, suggest, or participate.
For long-running coding agents, this decouples the “model turn” from the “execution location” and reduces observability gaps caused by page refreshes, Gateway restarts, or device switching. Conversations can now branch from or rewind to saved user messages, but rewinding changes only the chat context; it does not undo files already written or other tool side effects. Engineering teams must still use version control or transactional tools for a true rollback.
The upgrade is not frictionless. The bundled OpenProse plugin and `/prose` command have been removed, while `codex/*` and `openai-codex/*` models and automation routes must migrate to `openai/*`. Several plugin SDK subpaths will also reach their removal deadline on September 1. Production environments should first back up their configuration and SQLite state, then run `openclaw doctor --fix` and revalidate that sharing permissions, credential proxy destinations, and automation approvals still comply with existing policies.