This release shows a startup prompt inviting you to switch to V3 as part of a gradual rollout. It also adds V3 model fallback notices, keeps more of your V2 agent access when you upgrade agents to V3, and fixes screen reader, tmux, and knowledge search issues.
Switch to V3 when you start a chat
The startup prompt is rolling out gradually before V3 becomes the default with CLI 3.0 at the end of October, so you may not see it right away. When it appears, choose Switch to V3 and upgrade my configs to save V3 as your default harness, enable automatic agent upgrades, and start migrating your custom agent configurations. You can also try V3 anytime with kiro-cli --v3. Read the Kiro CLI V3 rollout announcement for details.
See when a V3 turn moves to another model
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. You can tell that a different model continued the turn instead of wondering why a reply changed. Learn about model fallback notices.
Kiro is now in scope for FedRAMP Class C in the US East (N. Virginia) Region. US government agencies, contractors, and other organizations whose workloads are subject to FedRAMP Class C requirements can now use Kiro for AI-assisted software development.
FedRAMP is a US government-wide program that delivers a standard approach to security assessment, certification, and continuous monitoring for cloud products and services. See AWS services in scope by compliance program for current Kiro scope details, AWS compliance resources for program details, and FedRAMP on AWS for background on the FedRAMP program itself.
Claude Opus 5.5 is available in the Kiro IDE and CLI across both AWS GovCloud (US) Regions.
Claude Opus 5.5, Anthropic's most capable Opus model yet, is now available in the Kiro IDE and CLI across AWS GovCloud (US-East) and AWS GovCloud (US-West). It improves on Opus 5 for long-running agentic coding work and thinks adaptively on every request, deciding how much effort each task needs. It includes a 1M-token context window with a 2.0x credit multiplier, down from Opus 5's 2.2x. Update to the latest IDE or CLI version, then restart it to access the model from the model selector. Learn more ->
Claude Sonnet 5.5 is available in the Kiro IDE and CLI across both AWS GovCloud (US) Regions.
Claude Sonnet 5.5 is now available in the Kiro IDE and CLI across AWS GovCloud (US-East) and AWS GovCloud (US-West). It is Anthropic's fastest Sonnet model to date and a natural upgrade for teams already using Sonnet 5: output is more than 30% faster, real-world coding and knowledge work approaches Opus 5.5 performance, and writing is clearer. It is available with a 1M-token context window and a 1.3x credit multiplier. Update to the latest IDE or CLI version, then restart it to access the model from the model selector. Learn more ->
In local V3 sessions, Kiro can learn useful context from your work and recall it in later chat sessions, with controls for memory access and automatic updates.
Kiro CLI 2.29.0 introduces Memory for local V3 sessions, so Kiro can carry useful context from your work, such as a repository's commands and conventions, into later chat sessions instead of asking you to restate it.
Carry context across chat sessions with Memory
Kiro can now learn useful context from your work and recall it when a later session needs it. For example, if Kiro learns while debugging that a repository's integration tests fail until the local database is seeded, a later session can seed it first instead of rediscovering the cause. When Kiro uses a memory, the chat shows a Memory entry with command=get and the memory's title while Kiro is still working.
In a local V3 session, type /memories and select config to choose read & write, read only, or off. The read only option says "Use existing memories. No changes or automatic updates." off stops Kiro from using or changing memories. Access changes apply in your next session. With read & write, Automatic memory updates lets Kiro create and refine memories, including after a session ends; changes to that setting apply immediately. In a workspace you have not trusted, Kiro can read memories but cannot add, change, or delete them.
Select list to search, preview, and open stored memories. The list is read-only; to fix or delete a memory, ask Kiro in the chat.
This release adds a feedback link for Workflows, fixes several chat, terminal, and source control issues, and improves workflow reliability, spec-only commands, and Hook matching.
Switch an interactive Classic session to 3.0, match V3 Hooks by tool category, and improve reliability in long V3 sessions.
Kiro CLI 2.28.0 offers Classic users a path to switch to 3.0 without leaving their terminal, lets V3 Hooks match tool categories, and makes long V3 chats more reliable.
Switch to 3.0 from an interactive Classic session
When you start an interactive Classic session on a host that can run 3.0, Kiro now offers to switch: choose Switch to 3.0 and upgrade my agent configs to save 3.0 as your default, upgrade your agent configurations, and rerun your command in 3.0. Decline, and Kiro reminds you again about once a week.
Match Hooks by tool category in V3
In V3 sessions, Hooks that run before or after a tool can now match by category, such as shell, read, write, or a specific MCP server or tool, instead of only by internal tool ID.
Claude Sonnet 5.5 is now available with experimental support across the Kiro IDE, CLI, Crew, and Web for Pro, Pro+, Pro Max, and Power customers in us-east-1 (IAD) and eu-central-1 (FRA). It's Anthropic's fastest Sonnet model to date and a clear upgrade over Sonnet 5: output is more than 30% faster, real-world knowledge work approaches Opus 5.5 performance, and clearer writing makes it a stronger collaborator. Claude Sonnet 5.5 includes a 1M-token context window, adaptive thinking on by default, and a 1.3x credit multiplier. To load the latest model list, restart the IDE or CLI, run kirocrew restart for Crew, or refresh Web in your browser. Learn more ->
Choose how V3 delegates with Workflows, include live file and folder context in Steering, and invoke saved prompts as slash commands.
Kiro CLI 2.27.0 adds control over how V3 delegates when Workflows are enabled, expands Steering with live file and folder context, and exposes saved prompts as slash commands. It also tightens access to local Kiro state and improves terminal rendering and tool reliability.
Choose how chat delegates with Workflows
When Workflows are enabled, the new Workflows: sub-agent tool setting is on by default, so the main chat can delegate directly to sub-agents or through Workflows. Turn it off under /settings features to limit main-chat delegation to Workflows; sub-agents remain available inside workflow steps when their agent configuration permits them.
Whole-file #[[file:...]] references work across surfaces. CLI V3 adds one-line and line-range selectors plus #[[folder:...]] references for a one-level directory listing. In CLI V3, referenced content resolves when the Steering document loads, subject to the session's file-read policy.
V3 exposes workspace, global, and MCP prompts as slash commands. Completion shows argument hints, and invoking a prompt resolves its file template or MCP content before sending the expanded text to the model.
Run reusable, multi-step agent plans in Kiro Web cloud sessions, inspect and guide every step, and keep working in the parent conversation.
Workflows are now available as an opt-in feature in Kiro Web cloud sessions. They run reusable, multi-step agent plans in the background while you continue working in the parent conversation.
Start a Workflow from the conversation
Describe the outcome and how much structure or review you want. Kiro proposes a Workflow, names its steps, agents, and effort, and launches it in the background. Ask Kiro to investigate a codebase for risks, deliver a feature with independent reviewers, or make a failing build green. Each step runs in its own agent session, which you open from the Workflows panel; it sees only what earlier steps hand it, and the run pauses when a step needs your input.
Start with one of three bundled recipes: investigate for read-only investigation, feature-pipeline for staged feature delivery, or publish-pr for opening a pull request and handling review feedback.
Once a Workflow is running, open Workflows from the side panel in the parent conversation and select a run to inspect its nested steps. Select a step to see its status, elapsed time, agent, model, effort, and tool activity. You can Answer this step when it pauses, Steer the agent while it runs, or Message this step's agent for other guidance. You can also pause, resume, or stop a run. After a failure, you can retry the failed steps. Summary, Files, and Artifacts also share the side panel to keep outcomes and evidence in the session.
Open Settings > Workflows and turn on Enable workflows. Use Upload workflow for one .workflow.json, .workflow.yaml, or .workflow.yml recipe, or use Configuration Sync to import a complete .kiro/workflows/ folder. Turning Workflows off hides its surfaces and prevents new launches.