← Back to Blogs
GH PRs

OpenClaw Update: Native Codex Support, Realtime Voice Upgrades, and System Stability

18:30–00:30 UTC May 7, 2026

OpenClaw Update: Native Codex Support, Realtime Voice Upgrades, and System Stability

The latest set of merges for OpenClaw focuses on deepening the integration with the Codex harness, enhancing real-time voice capabilities, and hardening the system's resilience against provider failures. A significant architectural shift is also underway to move toward a "prepared runtime" foundation, reducing redundant lookups during request processing.

Merged PRs

  • feat(codex): enable native plugin app support Original PR
  • fix(openai): use GA realtime bridge for gpt-realtime-2 Original PR
  • Defer Codex dynamic tools behind search Original PR
  • fix: keep gateway watch sync tracing opt-in Original PR
  • feat(agents): implement state-aware failover and lane suspension Original PR
  • fix: share plugin runtime helpers Original PR
  • fix: bound skills watcher traversal Original PR
  • refactor(runtime): add prepared runtime foundation Original PR
  • fix: print resolved installer follow-up command Original PR
  • Implement ACP bridge lifecycle handlers Original PR
  • fix(channels): surface missing external plugin repairs Original PR
  • docs: document Docker CLI DNS override Original PR

Key Changes

Codex Integration and Optimization

OpenClaw has significantly evolved its Codex mode. The platform now supports native plugin app support, allowing migrated Codex plugins to be exposed as native capabilities within the same harness thread. This removes the latency and complexity associated with the old bridge shape.

To optimize token usage, OpenClaw now defers dynamic tools behind search. Previously, the full integration tool catalog was loaded at the start of every thread. Now, tools are marked as deferred under the openclaw namespace, and the model uses tool_search to load them on demand. This has resulted in a massive reduction in upfront tokens—up to 75% in some scenarios (e.g., saving over 5,000 tokens for Telegram and Discord source replies).

Realtime Voice and Connectivity

The OpenAI realtime voice default has been switched to gpt-realtime-2. The backend WebSocket bridge has been migrated to the GA session shape, dropping the beta header to ensure compatibility with the latest OpenAI standards. Additionally, the ACP (Agent Client Protocol) bridge now includes stable lifecycle handlers for session listing, resuming, and closing, providing a more robust interface for external schedulers.

System Resilience and Stability

To combat the "infinite retry loop" problem during provider quota exhaustion, OpenClaw has implemented state-aware failover and lane suspension. When a provider returns a rate limit or billing error, the affected lane is suspended (concurrency set to 0) with a TTL-based auto-resume. Upon resumption, a recovery briefing is injected to the fallback model to ensure a seamless handoff without duplicating work.

Other stability fixes include:

  • Skills Watcher Bounds: Traversal is now capped to prevent EMFILE (too many open files) errors when users have large non-skill trees (like venv or node_modules) in their workspace.
  • Plugin Runtime Consolidation: Shared SDK surfaces for JSON Schema validation and MIME detection have been introduced to remove redundant local dependencies across plugins.
  • Channel Repair Hints: Users will now see actionable repair hints in openclaw status when official external channel plugins (like WhatsApp or Feishu) are missing after an upgrade.

Impact

For developers and power users, the most immediate impact is a leaner, faster Codex experience with significantly lower token overhead. The transition to gpt-realtime-2 ensures that voice interactions remain current with OpenAI's latest GA releases.

From an operational standpoint, the introduction of lane suspension and state-aware failover transforms how OpenClaw handles API instability. Instead of wasting credits on failing providers, the system now intelligently pauses and briefs the fallback model, maintaining agent continuity. Finally, the improved installer follow-up commands and Docker DNS documentation resolve critical friction points for users setting up the environment on diverse OS distributions.

References

Pull Requests