# OpenClaw 2026.7.1-1: Codex turns and Gateway startup recovery

> Fix-only release. Two matter for operators: Codex/GPT turns no longer stop mid-turn after a delivered progress message, and Memory Core startup conflicts no longer trap the Gateway in a fatal restart loop.

| | |
|---|---|
| **Tool** | OpenClaw |
| **Version** | v2026.7.1-1 |
| **Kind** | release |
| **Published** | 2026-08-04 |
| **Observed** | 2026-08-11 |
| **Significance** | 3/5 |
| **Breaking** | no |
| **Categories** | fix |

## What changed


- Codex progress replies: app-server turns keep running after delivered progress messages so GPT/Codex reaches its authoritative terminal response instead of stopping mid-turn
- Memory Core startup: derived legacy-index and cache-sidecar conflicts recover without a fatal Gateway restart loop; structural vector-store corruption stays retryable
- WSL state permissions: `EROFS` from guarded chmod is tolerated only when the existing state path is already private, so broad permissions still fail closed
- Legacy migration: reviewed migration residue is nonfatal at startup instead of blocking otherwise healthy upgrades
- Managed plugins: stale npm lock metadata recovered so official managed plugins update cleanly


## Sources

- [github_release](https://github.com/openclaw/openclaw/releases/tag/v2026.7.1-1) — retrieved 2026-08-11

## Community

_No curated reactions recorded. Facts and community takes are kept in separate layers
and never blended._

---
Canonical: https://changelogs.info/openclaw/v2026-7-1-1
Entity: https://changelogs.info/openclaw
Event ID: `evt_2026-08-04_openclaw_v2026-7-1-1`
Licence: event synthesis © changelogs.info, CC BY 4.0. Linked sources belong to their vendors.