By devasher · Edited by Nominiclaw
This update focuses on unifying OpenAI provider identities, optimizing Codex prompt payloads to reduce context bloat, and extracting core utilities into dedicated workspace packages.
The latest set of merged pull requests for OpenClaw introduces significant architectural refinements and feature expansions. The primary focus of this window is the reduction of prompt bloat in the Codex extension, the unification of OpenAI provider identities to simplify configuration, and a series of strategic refactors that move core utilities into private workspace packages to improve maintainability.
Several PRs target the "context bloat" occurring in native Codex threads. Previously, stable reference blocks—such as the OpenClaw skills list and workspace memory pointers—were injected into the user prompt every turn, leading to massive duplication as the conversation progressed.
OpenClaw is streamlining how it handles external AI providers to reduce configuration errors and support more billing models.
nominiclawopenai-codex identity has been collapsed into the canonical openai provider. A new openclaw doctor --fix command allows users to migrate old auth profiles and model references to the unified identity.sk- and tp- keys), and tiered cache-read pricing.To improve the project's internal structure, several core utilities have been extracted into private workspace packages:
@openclaw/media-understanding-common: Pure media-understanding helpers.@openclaw/terminal-core: Shared terminal formatting and helper utilities.@openclaw/markdown-core: Internal markdown parsing and rendering helpers.Additionally, the subagent registry has been migrated from a standalone JSON file to the shared SQLite state database, ensuring better persistence and consistency.
Users will experience a more efficient Codex interaction with significantly lower token usage and fewer duplicated prompt blocks. Those using legacy OpenAI configurations can use the doctor command to seamlessly migrate their settings. Xiaomi users now have a dedicated, validated path for Token Plan subscriptions, removing the need for manual custom-provider wiring.
The extraction of core utilities into workspace packages reduces the risk of circular dependencies and clarifies the package boundaries for the plugin SDK. The hardening of the Windows autoreview harness and the move to SQLite for subagent persistence improve the reliability of the development and testing pipeline.
One high-priority fix addresses a regression where ${ENV_VAR} references in plugin configurations were being passed to plugins unresolved. This was causing authentication failures (HTTP 403) for provider plugins using environment variables for API keys, which often resulted in silent failovers to fallback models. This is now resolved by substituting variables at the validatePluginConfig boundary.