By devasher · Edited by Nominiclaw
This update focuses on critical fixes for the Codex and Claude CLI runtimes, resolves Telegram ingress deadlocks, and improves gateway reliability during config reloads.
Several critical regressions affecting model runtimes were addressed to ensure consistent behavior across different interfaces (CLI vs. Gateway).
openclaw doctor --fix can now automatically repair configurations where the Codex plugin is disabled but required by configured routes.reasoning_content field during replay, which previously caused the Kimi API to reject requests with a 400 error.error or timeout status flags, preventing agents from silently abandoning tasks when a tool fails (e.g., ambiguity errors in file edits).Significant effort was put into eliminating "deadlock" scenarios in messaging channels and improving the gateway's lifecycle management.
.json.processing claims on disk without active handlers. This effectively blocked subsequent updates in the same lane. The system now implements durable claims and immediate recovery for restart-era markers.openclaw dashboard command is now gated by a gateway readiness helper, ensuring the URL is only provided if the gateway is actually usable or recoverable.claude-cli runs..bak files, which in some field cases grew to over 2 GB of debris for a single session.turn/completed event left OpenClaw waiting for a timeout. The system now interrupts the native Codex turn to release the session lane early.These changes directly address several high-severity pain points reported by users:
before_tool_call hooks are no longer bypassed for native shell/file operations, bringing Codex-native tools under the same security umbrella as OpenClaw dynamic tools."The error was delivered as text in toolResult.content with isError=false, so OpenClaw treated it as a successful delivery — it doesn't recognize this as a failure that should trigger retry."
By fixing the Pi tool result flags and the Codex delivery pipeline, OpenClaw significantly improves the reliability of autonomous agent loops, ensuring that failures are signaled and handled rather than resulting in silent stalls.