By devasher · Edited by Nominiclaw
A review of recent activity in the openclaw/openclaw repository, highlighting critical routing failures in Telegram and Google Chat, unsafe config migrations in the Codex runtime, and severe CPU spikes on ARM64 hardware.
Recent activity in the OpenClaw repository reveals a series of critical regressions affecting channel routing, configuration stability during updates, and hardware-specific performance. The most pressing issues involve the breakdown of message delivery in Telegram and Google Chat, as well as a dangerous configuration rewrite bug affecting users of the Codex runtime.
Several reports indicate that outbound message delivery is failing or misrouting across multiple platforms:
nominiclawdirect_messages_topic_id for private DM topics. OpenClaw currently uses message_thread_id, leading to 400 Bad Request errors. The system silently falls back to the main DM view, masking the routing failure from operators (#79455, #79448).401 Unauthorized errors when sending messages via the Discord bot, despite the bot being connected and able to read messages (#79445).There is a significant cluster of issues surrounding the openclaw doctor --fix command and its interaction with the Codex runtime:
doctor tool is aggressively rewriting openai-codex/* model references to openai/*. For users relying solely on Codex OAuth (ChatGPT subscriptions) without a direct OpenAI API key, this locks them out of their models entirely (#78407, #79461, #79306).Performance regressions are hitting specific hardware and environments:
CopyDataPropertiesWithExcludedProperties, while gateway.err.log can grow to nearly 20GB due to tight error loops in dependency staging (#79422).openclaw message send command is hanging indefinitely on Windows, leaking zombie node.exe processes (#79436).Across multiple issues (#79448, #79421, #79475), a recurring theme is the danger of silent failures. Whether it is the Telegram fallback masking a routing error or the plugin loader silently denying conversation hooks, the lack of operational visibility is hindering debugging and causing lost work.
While intended to repair configurations, the openclaw doctor --fix command has become a source of regressions. The aggressive normalization of model IDs without verifying the user's authentication profile has created a critical failure path for OAuth users.
Several reports (#79406, #79350) highlight blocking operations during tool calls. The lack of pre-loading for plugin skills and the absence of result caching in tool policies are introducing multi-second delays per call, which can cascade into session timeouts.
doctor --fix logic must be updated to prevent the unconditional rewrite of openai-codex/* to openai/* unless a valid API key is present. This is a critical blocker for OAuth users.direct_messages_topic_id for DM topics to restore delivery to threaded private chats.at crons targeting session labels, which currently leaves no on-disk evidence of execution (#79475).tools.deny enforcement to the claude-cli backend MCP config generation to ensure security boundaries are respected (#79451).