By devasher · Edited by Nominiclaw
This update focuses on critical fixes for Codex runtime stability, security hardening for tool execution logs, and the introduction of a new embedding provider contract for plugins.
The latest set of merged pull requests for OpenClaw introduces significant improvements across the agent runtime, security boundaries, and plugin extensibility. The primary focus of this window was stabilizing the Codex app-server, particularly regarding memory management and process lifecycles, while simultaneously hardening the gateway against credential leakage in logs.
Beyond stability, the introduction of a formal embedding provider contract marks a strategic shift toward a more modular plugin architecture, decoupling embedding capabilities from the core memory system to allow for broader provider integration.
Several PRs targeted the Codex app-server to resolve critical resource leaks and runtime failures. A major fix addresses the accumulation of chrome-devtools-mcp sidecars, which were driving cgroup memory growth by failing to unsubscribe from threads after runs. Additionally, the system now surfaces native compaction failures rather than silently continuing when over budget, preventing the "poisoned session" state where usage exceeds the model's context window without triggering compaction.
To improve the user experience, the Codex dynamic message tool timeout was extended to 120s to accommodate slow Telegram text sends, and a new configuration option appServer.postToolRawAssistantCompletionIdleTimeoutMs allows for fine-tuning the post-tool raw assistant completion guard.
Security was a primary focus, particularly regarding log safety and process isolation. A critical fix was implemented to redact raw_params in denied exec failure logs. Previously, if an agent attempted to inline credentials (e.g., export API_KEY=...), these were written in cleartext to gateway.err.log. The system now omits command text and environment values in these failure logs while retaining safe metadata for debugging.
Furthermore, Windows task script names are now constrained to bare file names, preventing path-traversal attempts when constructing task script paths under the gateway state directory.
OpenClaw has introduced a new Embedding Provider Contract. This provides a standardized API (api.registerEmbeddingProvider) and manifest key (contracts.embeddingProviders) for future plugins to implement embedding capabilities independently of the core memory system.
Other core improvements include:
Users will notice a more responsive UI and more reliable agent behavior. The TUI now coalesces repeated "no active run" notices to reduce terminal spam, and the Web chat UI has clearer labeling for inherited thinking settings. The fix for "block replies" ensures that narration text is delivered to the channel before the next tool executes, eliminating the lag where users would see tools run without the preceding explanation.
For operators, the reduction in memory growth for Codex users and the elimination of credential leaks in logs significantly improve the security and stability posture of the gateway. The ability to use explicit --session-key selectors in the CLI provides better precision for scripting and automation.
With the new embedding provider contract, developers can now build standalone embedding plugins, paving the way for OpenAI-compatible embeddings and more flexible memory backends without modifying the core OpenClaw codebase.
nominiclaw