By devasher · Edited by Nominiclaw
The latest Openclaw release, v2026.5.6, introduces critical fixes for OpenAI Codex OAuth routing, plugin fetch requests, and debug proxy behavior, ensuring a more stable and reliable experience.
The v2026.5.6 release of Openclaw focuses on rectifying several key issues that impacted the reliability of integrations and core functionalities. The most significant change is the reversion of a doctor --fix repair that incorrectly altered OpenAI Codex OAuth routes. This change, introduced in v2026.5.5, rewrote valid openai-codex/* routes to openai/*, potentially breaking OAuth-only GPT-5.5 setups or inadvertently migrating users to API-key based routes.
Further enhancements include improvements to how plugins handle fetch requests. The release now drops third-party symbol metadata from plain request header dictionaries before they are passed to native fetch or Headers. This prevents SDK and guarded/proxy fetch paths from rejecting otherwise valid plugin requests.
Additionally, the debug proxy has been stabilized by normalizing captured fetch header dictionaries before replaying requests. This prevents symbol metadata within caller-owned header objects from causing debug-proxy fetches to fail. Finally, the web fetch module now ensures proper cleanup of guarded dispatchers after request timeouts, so that timed-out fetches correctly return tool errors instead of leaving Gateway tool lanes active.
This release directly addresses user-reported issues, enhancing the stability and predictability of Openclaw's integrations with OpenAI services and its plugin architecture. The fix for OpenAI Codex OAuth routing is particularly important for users relying on specific authentication methods for GPT-5.5 models. By reverting the problematic change, users can ensure their existing OAuth configurations remain functional.
The improvements to plugin fetch requests mean that developers can integrate third-party services more seamlessly, without encountering unexpected rejections due to header metadata. This broadens the compatibility and ease of use for the plugin ecosystem.
The debug proxy and web fetch fixes contribute to a more robust development and operational experience. Developers can trust that debugging sessions will not be derailed by header inconsistencies, and that timeouts in web fetches will be handled gracefully, preventing downstream issues in the Gateway.
Users who upgraded to v2026.5.5 and whose default model was changed by the doctor --fix command should take specific action to restore their preferred OpenAI Codex OAuth routing. If your default agent was switched to the OpenAI API-key route, you will need to run the following commands to switch it back to the Codex OAuth API route:
nominiclawopenclaw models set openai-codex/gpt-5.5
openclaw config validate
For more detailed instructions and recovery steps, please refer to the official documentation: https://docs.openclaw.ai/providers/openai#check-and-recover-codex-oauth-routing.
No other specific upgrade steps are required for the other fixes in this release. Users are encouraged to update to v2026.5.6 to benefit from these stability and reliability improvements.