OpenClaw Releases v2026.4.20, Default Model for Moonshot Set to Kimi K2.6

robot
Abstract generation in progress

According to monitoring by Dongcha Beating, the open-source AI Agent platform OpenClaw has released v2026.4.20, with core changes focusing on default model switching, plugin contract rollback, and gateway storage governance. The default model for the built-in Moonshot channel, web search, and multimodal understanding has been changed to kimi-k2.6, while kimi-k2.5 remains compatible. Moonshot only allows thinking.keep = “all” on kimi-k2.6; other Moonshot models or requests with fixed tool_choice will automatically strip this field. The cost estimation now includes a tiered pricing structure, with built-in unit prices for Kimi K2.6/K2.5, and token usage reports can be directly billed. A key fix is the rollback of the strict id contract introduced in version 2026.4.14. Previously, this contract required the plugin info.id to equal the registered slot id, resulting in third-party context engine plugins like lossless-claw being rejected in every round. The default timeout for BlueBubbles text outbound has been increased from 10 seconds to 30 seconds, and on macOS 26 Tahoe, even without enabling the Private API, it will prioritize using the Private API to avoid previous silent message losses. Two structural adjustments have been made on the operations side. Cron has separated the runtime execution status from jobs.json into jobs-state.json, allowing jobs.json to only retain task definitions suitable for git management; Sessions storage now defaults to enable entry limits and time trimming, cutting off excessive storage at startup to prevent cron/executor backlog from overwhelming gateway memory. The onboarding installation wizard has revamped security instructions, changing from plain text to a yellow warning banner with a segmented list. The initial model directory loading now includes a loading animation, and the API key input box has a placeholder. Security measures have also tightened around Gateway WebSocket broadcasting, device pairing permissions, and the injection blocking of OPENCLAW_* keys in the workspace .env.

This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • Comment
  • Repost
  • Share
Comment
Add a comment
Add a comment
No comments
  • Pin