Changelog

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.

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.

Learn more ->

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.

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.

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.

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

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.

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.

Learn more ->

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.

Learn more ->

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.

Learn more ->

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.

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.

Learn more ->

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.

Learn more ->

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.

Learn more ->

IDE 1.2 introduces Workflows, strengthens safeguards for untrusted workspaces, and adds enterprise controls for sign-in methods. This release also reworks session details, keeps enterprise traffic in your profile's Region, and fixes authentication, debugging, and reliability issues.

Ask Kiro to run a reusable, multi-step plan while you continue in the parent chat. Each step runs in its own agent session. Use the Workflows area above the chat to inspect progress, open a step, and pause, resume, or stop the run. Workflows are off by default: turn on Workflows in Workspace Configuration in Agent Focus, or set kiroAgent.workflows.enabled in Settings, then start a new chat session. Learn more ->

Kiro asks before the agent changes agent, Hook, or Power files, or the Workflow recipes in .kiro/workflows/ that define your Workflows, even when broader file permissions allow the write. In an untrusted workspace, Kiro also asks before changing any other Kiro configuration and before each command runs, even when you previously allowed it. Workflow recipes in an untrusted workspace are not loaded until you trust the workspace. Learn more ->

Kiro CLI 2.26.0 adds opt-in Workflows for reusable, multi-step tasks and helps Classic users identify what to change before moving to the terminal UI. V3 also tightens approval checks for Hook and Language Server Protocol (LSP) file writes, for MCP tools and shell commands in untrusted workspaces, and for approvals that change while an action waits.

In a V3 session, open /settings, choose Features, and enable Workflows, then restart Kiro CLI to apply the change. Then ask Kiro to create a Workflow from the outcome you want, or launch a recipe with /workflow run, and use the /workflow commands to inspect and manage runs.

Learn more ->

Classic sessions now show a deprecation notice. If a flag, environment variable, or saved setting launched Classic, the notice identifies it and points to guidance for switching to the terminal UI.

Learn more ->

Claude Opus 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). Anthropic reports stronger performance on long, complex coding tasks and clearer communication than prior models. Claude Opus 5.5 includes a 1M-token context window and has a 2.0x 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 ->

This release lets you manage Powers from a local V3 session or without starting chat, customize how V3 responds, and tune fullscreen scrolling. V3 also adds a SessionEnd Hook, while model notices, session loading, terminal rendering, authentication, and security receive reliability updates.

In a local V3 session, run /powers install <name|path> to add a Power from the catalog or a local directory, and /powers uninstall <name> to remove one. Kiro refreshes the available Powers immediately so the current session can use the updated set. To manage Powers without starting chat, run kiro-cli powers install <name|path> or kiro-cli powers uninstall <name>.

Learn more ->

Open /settings in a V3 session to choose how Kiro formats its responses. The available choices include output styles supplied by upgraded agents, so each agent can offer styles suited to its work.

Learn more ->

Open /settings display, select Full Screen, and set Scroll speed to move the transcript by 1, 2, or 3 rows per mouse-wheel event. The default is 2 rows. The new Full Screen screen also contains the existing Start fullscreen setting.

Learn more ->

Use the new SessionEnd trigger to run a Hook when a V3 session shuts down. This gives your session-level automation a reliable teardown event for cleanup and other end-of-session tasks.

Learn more ->