the diff / Kiro

Kiro changes

Every Diff about Kiro: the model, pricing, limit and feature changes that alter how you ship with an agent, newest first, each with its official source. 9 notes so far; the newest is from November 11, 2026. Written by MK.

Also: Kiro pricing · RSS for every Diff

Kiro adds Grok 4.7 with experimental support in the IDE, CLI, Crew and Web. 500K context, 2.7x credits for requests up to 200K tokens, 5.4x over that.

score credits past 200K tokens: 5.4x

  • Kiro changelog, dated November 10: Grok 4.7 is available with experimental support
  • Works in the Kiro IDE, CLI, Crew and Web
  • 500K token context window
  • 2.7x credits for requests up to 200K tokens, 5.4x over 200K
  • Affects Kiro Pro, Pro+, Pro Max and Power customers

open the article →

What changed

Kiro's changelog, dated November 10, adds Grok 4.7 with experimental support in the Kiro IDE, CLI, Crew and Web for Pro, Pro+, Pro Max and Power customers. The context window is 500K tokens. Requests up to 200K tokens are billed at a 2.7x credit multiplier; requests over 200K tokens, 5.4x. To see it in the model list, restart the IDE or CLI, run kirocrew restart for Crew, or refresh Kiro Web.

Why it matters if you ship with an agent

Credits past 200K tokens: 5.4x. The multiplier doubles at the line, and a long agent session crosses it without announcing itself. If you try it, watch the context size and compact before 200K. It is labelled experimental, so do not make it a team default yet.

sources: kiro.dev

open the article →

Kiro previews Enterprise Management: one AWS console policy for the IDE, CLI, Web and Crew LTS. On new us-east-1 profiles, models and API keys are denied until a rule allows them.

score regions in the preview: 1

  • Kiro changelog, dated November 10: Enterprise Management is in preview for newly created profiles in us-east-1
  • One policy applies in Kiro IDE 1.4.154 or later, CLI 3.1.0 or later, Kiro Web and Kiro Crew LTS
  • Models, API keys, and Crew messaging and network access are denied until a rule allows them
  • Files, shell, web, MCP and Crew scheduled jobs keep Kiro's defaults until a rule names them
  • Affects admins creating new Kiro profiles in us-east-1; existing and European profiles come later

open the article →

What changed

Kiro's changelog, dated November 10, puts Enterprise Management in preview for newly created profiles in US East (N. Virginia). Admins write one policy in the AWS console and it applies in the IDE (1.4.154 or later), the CLI (3.1.0 or later), Kiro Web and the new Kiro Crew LTS. Rules allow, deny or ask for models, shell commands, files, web search and MCP tools, for everyone, one group or one user. Models, API keys, and Crew messaging and network access are denied until a rule allows them. Files, shell, web, MCP and Crew scheduled jobs keep Kiro's defaults until a rule names them. Existing and European profiles come later.

Why it matters if you ship with an agent

Regions in the preview: 1. If your admin creates a new profile there, expect no models until a rule allows one. Update the IDE and CLI before you file the bug.

sources: kiro.dev

open the article →

Kiro IDE 1.4.154 adds Approve for me to chat. The Autopilot toggle becomes a three-mode menu, Autopilot is renamed Accept file changes, and a model can answer the prompts your rules leave open.

score modes in the menu: 3

  • Kiro IDE 1.4.154, dated November 10, adds Approve for me to chat
  • Where it is available the Autopilot toggle becomes a menu of Supervised, Accept file changes (formerly Autopilot) and Approve for me
  • Deny, ask and allow rules decide first, then a model approves, blocks or asks
  • Off by default, with a switch and a command to make it the default for new chats
  • Affects Kiro IDE users, and Kiro Web users, who got the same option on November 6

open the article →

What changed

Kiro IDE 1.4.154, dated November 10, adds Approve for me to chat. Where it is available, the Autopilot toggle becomes a permission mode menu: Supervised, Accept file changes (the old Autopilot) and Approve for me. Your deny, ask and allow rules decide first. For an action no rule covers, a model approves it if it judges it safe, blocks it if not, and asks when unsure. Each pass is marked Approved for you. The docs say it is off by default; "Use Approve for me by default" in What's new, or the command Kiro: Enable Approve For Me (User), turns it on for new chats. Kiro Web got the same option on November 6, under Agent Config, Tool approvals.

Why it matters if you ship with an agent

Modes in the menu: 3. Autopilot is gone by name, so update your team docs. Before making the third mode your default, write deny rules for push, deploy and secrets. Those still win.

sources: kiro.dev

open the article →

Kiro CLI 3.0 starts new interactive sessions and --trust-all-tools scripts on V3, retires the Classic interface, the desktop app and five commands.

score commands retired: "5"

  • Kiro CLI 3.0.0, dated November 3, makes V3 the default.
  • New interactive sessions start on V3; existing V2 users are asked first.
  • The scripts flip quietly: a CI job that passes --trust-all-tools now runs on V3, and scripts are not asked first.

open the article →

What changed

Kiro CLI 3.0.0, dated November 3, makes V3 the default. New interactive sessions start on V3; existing V2 users are asked first. Headless scripts using --trust-all-tools start on V3, other scripts stay on V2, and new ACP clients start on V3. The Classic (V1) interface no longer runs: a command or setting that still selects it gets a "Continue with V3" offer. The desktop app is gone, and macOS installs switch to the standalone kiro-cli on their next update check. The autocomplete, inline, translate, theme and dashboard commands are unavailable. kiro-cli --v2 keeps the V2 agent.

Why it matters if you ship with an agent

The scripts flip quietly: a CI job that passes --trust-all-tools now runs on V3, and scripts are not asked first. Run it once by hand, or pass --v2 until you have. Grep your dotfiles for the five retired commands. Inline shell autocomplete ended with the desktop app and has no replacement.

sources: kiro.dev

open the article →

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.

score backups per agent: 1

  • 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.
  • Your agent files change the first time V3 starts, global ones included.

open the article →

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.

sources: kiro.dev

open the article →

Kiro CLI 2.36.0 adds Approve for me to local V3 sessions. A classifier approves actions your deny, ask and allow rules leave open. Per workspace, off until you pick it.

score who approves: Sonnet 4.6

  • Kiro CLI 2.36.0, dated October 29, adds Approve for me to interactive local V3 sessions.
  • Run /permissions, choose Policies, then approve for me.
  • Who approves: Sonnet 4.6.

open the article →

What changed

Kiro CLI 2.36.0, dated October 29, adds Approve for me to interactive local V3 sessions. Run /permissions, choose Policies, then approve for me. Kiro approves actions it judges safe, blocks ones it judges unsafe and asks when unsure. Your deny, ask and allow rules decide first; the policy only handles what they leave open, and each action it passes is marked Approved for you. The docs say a Claude Sonnet 4.6 classifier makes the call, and the preset allows workspace reads, writes and read-only shell commands outright. It is stored per workspace, so other repos keep asking. The same release adds a subcommand match tier for shell rules, such as git stash *.

Why it matters if you ship with an agent

Who approves: Sonnet 4.6. Keep deny rules for push, deploy and anything touching secrets, since those still win. Then read the Approved for you labels after the session, not during it.

sources: kiro.dev

open the article →

Kiro CLI 2.32.0 lets you allow a whole folder when a V3 session asks to write a file, runs cloud sessions non-interactively and previews workflow plans.

score files per yes: a folder

  • Kiro CLI 2.32.0, dated October 15: when a V3 session asks to write a file, you can now allow the whole folder instead of that one file.
  • V3 cloud sessions run from non-interactive commands.
  • The write prompt now has a bigger answer.

open the article →

What changed

Kiro CLI 2.32.0, dated October 15: when a V3 session asks to write a file, you can now allow the whole folder instead of that one file. V3 cloud sessions run from non-interactive commands. A workflow shows its plan before any step runs. The release also adds three V3 output styles and gives selected workflow steps access to Powers and MCP servers. Fixes cover non-interactive runs, model fallback, MCP sign-in and workflows.

Why it matters if you ship with an agent

The write prompt now has a bigger answer. Allowing a folder saves a tap per file, and it also means every later write under it goes through unchanged. Pick the narrowest folder that does the job, not the repo root, and keep anything with secrets or deploy config outside it. Workflow previews are the quieter win: read the plan before the first step, which is the one moment where saying no costs nothing.

sources: kiro.dev

open the article →

Kiro retired Claude Sonnet 4 on October 14, 2026. Kiro does not switch your selected model for you, and requests to a removed model fail.

score models switched for you: 0

  • Kiro's changelog says Claude Sonnet 4 reached end of life in Kiro as of October 14, 2026, and that if your work depends on it you should choose another available model before continuing.
  • Claude Sonnet 5.5 is the latest Sonnet model.
  • If a Kiro agent, workflow or teammate's setup still picks Sonnet 4, nothing migrates it for you.

open the article →

What changed

Kiro's changelog says Claude Sonnet 4 reached end of life in Kiro as of October 14, 2026, and that if your work depends on it you should choose another available model before continuing. Claude Sonnet 5.5 is the latest Sonnet model. Kiro's model lifecycle page lists the same date for Claude Sonnet 4.0, marks EOL models [EOL] in the model picker, and says that after Kiro removes a model, requests to it fail. Kiro does not switch your selected model automatically.

Why it matters if you ship with an agent

If a Kiro agent, workflow or teammate's setup still picks Sonnet 4, nothing migrates it for you. Open the model picker and look for the [EOL] tag, then pick a model whose status is Active. Sonnet 5.5 is still listed as Experimental in Kiro and carries a 1.3x credit multiplier, so check the lifecycle page before you move everything there.

sources: kiro.dev

open the article →

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.

  • 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.
  • The prompt migrates your custom agents in one tap, and the default flips in about three weeks either way.

open the article →

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.

sources: kiro.dev

open the article →

other tools: v0 · Claude · Claude Code · OpenAI Agents API · OpenAI API · Claude API · Gemini API · Jules · GitHub Copilot · DeepSeek API · Codex · Anthropic · opencode · Lovable