the diff / Kiro / November 2, 2026

Kiro CLI 2.37.0 rewrites V2 agents to V3 by default at launch

score backups per agent: 1

Kiro CLI 2.37.0 upgrades V2 agent files to V3 when a V3 session starts unless you turn it off. Each file is rewritten in place after a .json.bak backup.

What changed

Kiro CLI 2.37.0, dated October 30, upgrades V2-format custom agents to V3 when a V3 session starts. It runs unless you turn it off: an unset chat.enableAutoAgentUpgrade preference counts as on, and only an explicit false keeps it off. It covers your workspace and global agent directories, or the directory in KIRO_AGENT_CONFIG_DIR if you set one. Each agent file is rewritten in place after Kiro saves a .json.bak backup. To keep V2 agents, run kiro-cli settings chat.enableAutoAgentUpgrade false; interactive V3 launches then show a notice counting the agents still waiting. The same release lets ACP clients that support terminal authentication sign in from a terminal.

Why it matters if you ship with an agent

Your agent files change the first time V3 starts, global ones included. Diff each .json against its .json.bak before you trust the session. If the configs live in git, commit first, and set the preference to false on machines where the migration should land as a reviewed change.

By MK · Source: https://kiro.dev/changelog/cli/2-37/

more Kiro changes: Kiro adds Grok 4.7 at 2.7x credits, experimental · Kiro previews Enterprise Management: one policy, every client · Kiro IDE 1.4.154 adds Approve for me and renames Autopilot · Kiro CLI 3.0 defaults to V3, retires Classic and the desktop app · Kiro CLI 2.36.0 adds Approve for me, a model that answers the prompt · all

keep handy: AI coding tool pricing tracker · vibe coding vs AI coding · agent fail hall of fame


The Diff is Accept All's short note on changes that alter how you ship with an agent. Newer: Claude Code 2.1.317 asks before a tool call sends your email. Older: Kiro CLI 2.36.0 adds Approve for me, a model that answers the prompt.