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

> 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.

- URL: https://acceptallhq.com/diff/2026-11-02-kiro-auto-upgrades-v2-agents-by-default/
- Section: The Diff
- Published: 2026-11-02T15:04:00-05:00
- Author: MK (https://acceptallhq.com/about/)
- Tool: Kiro
- Source: https://kiro.dev/changelog/cli/2-37/

## 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.
