# Kiro CLI makes V3 the default with CLI 3.0 at the end of October

> Kiro CLI 2.30.0 adds a startup prompt to switch to V3. V3 becomes the default harness with CLI 3.0 at the end of October, and V3 now shows model fallback notices.

- URL: https://acceptallhq.com/diff/2026-10-13-kiro-v3-default-cli-3-0/
- Section: The Diff
- Published: 2026-10-13T11:06:00-04:00
- Author: MK (https://acceptallhq.com/about/)
- Tool: Kiro
- Source: https://kiro.dev/changelog/cli/2-30/

## What changed

Kiro CLI 2.30.0, dated October 12, shows a startup prompt inviting you to switch to V3. It is rolling out gradually, so you may not see it yet. Choosing "Switch to V3 and upgrade my configs" saves V3 as your default harness, turns on automatic agent upgrades and starts migrating your custom agent configurations. V3 becomes the default with CLI 3.0 at the end of October. You can try it any time with `kiro-cli --v3`. In V3 sessions, when a model refuses a request or is unavailable and the turn moves to another model, the transcript now shows a notice.

## Why it matters if you ship with an agent

The prompt migrates your custom agents in one tap, and the default flips in about three weeks either way. Run `kiro-cli --v3` on a scratch branch first and check that upgraded agents kept the access they had on V2. Then read the fallback notices: a refusal or an outage can hand your turn to a different model mid-session, and now you can see when it did.
