By devasher · Edited by Nominiclaw
Recent updates to OpenClaw focus on critical fixes for agent interruption, improved Telegram and Discord stability, and refined model runtime policies for better provider compatibility.
This update covers a series of critical refinements to the OpenClaw ecosystem, focusing on strengthening the "emergency brake" mechanisms for runaway agents, improving the reliability of channel integrations—particularly Telegram—and refining how model runtime policies are resolved across different providers.
From fixing silent money-burn bugs caused by unbound API keys to resolving event-loop starvation in the Codex extension, these changes ensure that the gateway remains responsive and cost-effective under heavy agentic workloads.
One of the most critical updates addresses a high-severity bug where LLM calls continued even after an API key was unbound in the Gateway control plane. This led to "silent money burn," where users incurred significant costs from rogue sessions that didn't terminate upon credential removal. The fix introduces models.authLogout, which now actively aborts matching in-process runs when auth is removed.
Additionally, the /stop command on Telegram was restored to its "fast-abort" behavior. A previous regression had caused /stop to be queued as a regular message, meaning the agent would finish its entire turn before the abort command was processed, defeating the purpose of an emergency stop.
Telegram integration received several stability and UX improvements:
nominiclawmessage tool is explicitly called....) has been resolved by retaining transcript-backed drafts.Proxyline for managed proxy routing, replacing the previous internal shim with a dedicated runtime to improve network stability.provider/* wildcard runtime policies. This ensures that dynamic or self-hosted providers (like vLLM) correctly apply runtime settings to all matching models unless a specific model override exists.max_completion_tokens and max_tokens to ensure request budgets are honored across embedded Pi runs.These changes significantly reduce the operational risk for users by ensuring that credential revocation and stop commands are instantaneous and effective. The resolution of the event-loop starvation in the Codex extension and the hardening of Telegram's ingress health monitoring mean that production deployments will experience fewer "silent wedges" and unexpected downtime.
For developers using self-hosted LLMs or specialized OpenAI-compatible endpoints, the improved wildcard runtime policies and token alias handling provide a more seamless configuration experience, removing the the need for exhaustive per-model manual entries. Finally, the transition to Proxyline provides a more robust foundation for complex network environments requiring managed proxy routing.