OpenClaw 2026.5.6 Release Notes: Codex OAuth Route Recovery and Fetch Fixes
OpenClaw v2026.5.6 was released on May 6, 2026. The official GitHub release is short, but it addresses a concrete regression introduced in OpenClaw 2026.5.5.
The headline fix is a rollback of a doctor --fix repair that could rewrite valid openai-codex/* routes to openai/*. According to the official release notes, that could break OAuth-only GPT-5.5 setups or move users onto the direct OpenAI API-key route unintentionally.
The Main Fix: Recovering OpenAI Codex OAuth Routing
The May 6 release notes state that OpenClaw reverted the 2026.5.5 route rewrite for ChatGPT/Codex OAuth users. This is important because OpenClaw treats openai/* and openai-codex/* as different provider and authentication paths.
The official OpenAI provider documentation explains the distinction clearly:
openai/*is the direct OpenAI API-key route unless you explicitly force the Codex app-server harness.openai-codex/*is the Codex subscription route for ChatGPT/Codex OAuth usage.
That means the 2026.5.6 fix is not cosmetic. It restores the expected routing model for users who rely on subscription authentication rather than API keys.
OpenClaw also published a recovery command in the release notes:
openclaw models set openai-codex/gpt-5.5
openclaw config validate
The release notes point users to the official recovery documentation at docs.openclaw.ai/providers/openai#check-and-recover-codex-oauth-routing.
Runtime Fetch and Debug Proxy Fixes
The rest of the release focuses on request handling and fetch cleanup.
According to the official release notes, OpenClaw now drops third-party symbol metadata from plain request header dictionaries before passing them into native fetch or Headers. The same normalization was applied to the debug proxy so replayed requests do not fail for the same reason.
The release also says guarded dispatcher cleanup is now bounded after request timeouts. The stated goal is that timed-out web fetches return tool errors instead of leaving Gateway tool lanes active.
These are low-level changes, but they matter if you use plugins or proxy-heavy workflows. They reduce the chance that valid requests fail because of header-object contamination or that timed-out requests leave follow-on work in a bad state.
Why OpenClaw 2026.5.6 Matters
This release is best understood as a targeted recovery patch. If you use OpenClaw with Codex OAuth, it is materially more important than its small changelog suggests.
The sequence is straightforward:
- OpenClaw 2026.5.5 introduced a
doctor --fixbehavior that could rewrite valid Codex OAuth routes. - OpenClaw 2026.5.6, released later on May 6, 2026, reverted that rewrite.
- The official docs provide a specific recovery path for users already affected.
If your setup depends on OpenAI subscription authentication inside OpenClaw, this is the update to read before making additional config changes.