0.12.1 | Nov 10, 2026
- Chats cut off by a planned restart, such as an update or a dashboard Restart, resume on their own. A queued message waits while you edit it in its card. A turn the backend refused for model capacity ends with a notice that offers the model picker instead of Resume.
- Kiro Agent reads a Kiro CLI agent spec's tool aliases and allowedTools entries such as * and @builtin the way Kiro CLI does. Spec hooks receive Kiro CLI's field names and also run on scheduled turns. Kiro Agent sessions now answer /context, /knowledge, and /hooks, plus /code status and /code init.
- A new Kiro Agent spec starts servers from your global and workspace mcp.json only when the agent declares them or sets includeMcpJson, as Kiro CLI does. Agent files you had before this update keep their current behavior. An MCP server you added through Add Custom can now be removed, and and in a server's settings resolve on Windows.
- Claude Code sessions load workspace steering and the project's AGENTS.md, and get them back after a compaction. A spec's toolsSettings allowlists are enforced, and /clear is answered locally.
- A scheduled run opens its tab in its agent's workspace, so its sessions are no longer refused. A job's next run keeps its wall-clock time across a daylight saving change. Each job keeps only its 20 newest run transcripts, and a run whose agent was renamed or uninstalled is marked failed.
- resource_limits.max_memory_mb no longer also caps a tool's address space, so Node.js and GraalVM tools start in scheduled runs. To keep an address-space cap, set the new opt-in .