OpenClaw has released v2026.3.7, and the core change in this update is the official introduction of the ContextEngine plugin interface. The official adds full lifecycle hooks and plug-in slots for context management, allowing developers to customize the connection between context assembly, compression and sub-agents without changing the core compression logic. The LegacyContextEngine wrapper layer is also preserved to ensure that the default behavior remains the same when the plugin is not configured.
The second main line is persistent binding and multi-terminal synergy enhancement. Persistent binding storage and routing resolution for Discord channels and Telegram topics have been officially added, allowing ACP thread targets to continue to work after restarting. The Telegram side also expands the topic-level agentId override, thread binding, and approval button interaction. For teams that rely on long-term threaded sessions and cross-end collaboration, this release significantly improves operability and stability.
In addition, v2026.3.7 also completes a number of deployment and ecological capabilities, including new Spanish language support for Control UI, structured search for Perplexity Search API, SecretRef support for gateway.auth.token, Docker multi-stage build, and first-line model support for Google Gemini 3.1 Flash-Lite. It's important to note that there is a breaking change in this upgrade: when the token is configured at the same time as the password, gateway.auth.mode must be explicitly set, otherwise it may affect the boot and pairing process.
FAQs
Q: What are the most important capabilities in this update?
A: It is the ContextEngine plugin interface, which allows context management to be extended by plugins.
Q: What is the direct impact on Telegram and Discord users?
A: Channel and topic binding becomes persistence, and the routing relationship can be retained after restarting.
Q: What are the changes in search and model support?
A: Added Perplexity Search API structured search capabilities and added Gemini 3.1 Flash-Lite support.
Q: Are there any compatibility issues that I must be aware of in this upgrade?
A: Yes, gateway.auth.mode must be explicitly set when configuring both token and password.
Q: Which users are more suitable for upgrading first?
A: It is suitable for users who rely on multi-terminal collaboration, plug-in expansion, container deployment, and production environment stability.
