This release draws Mermaid diagrams directly in chat. It also makes saved settings work in headless V3 runs. Other fixes improve copied prompts, blocked panes, model fallback, compaction, Windows setup, release notes, AWS sign-in, and workflow output.
2.31.1CLI
2.31.0CLI
Use the local command sandbox and autonomous mode in V3, load MCP tools on demand, and keep V3 configuration under KIRO_HOME.
This release makes the local command sandbox and local autonomous mode available to every V3 user. It also loads MCP tools on demand, extends KIRO_HOME across V3 configuration and state, and fixes image, service, MCP, cloud-session, and sign-in issues.
Run /sandbox to place agent shell commands and their child processes inside an operating-system sandbox. Choose whether outbound network access is blocked, limited to common development hosts, or open. You can also run local stdio MCP servers inside the same sandbox.
The agent, built-in file tools, and remote MCP servers stay outside the sandbox. Permission rules still govern agent actions. The sandbox reduces risk but cannot guarantee complete isolation, so keep reviewing proposed commands. Learn more ->
Run /autonomous on in a local V3 session when you want Kiro to work through a task without asking you to approve each shell command. Kiro switches to the Default agent and turns on the local command sandbox first. Learn more ->
2.30.0CLI
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.
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.
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.
2.29.0CLI
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.
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.
2.28.0CLI
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.
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.
2.27.0CLI
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.
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.
2.26.0CLI
Run reusable, multi-step Workflows in V3, get clear guidance when Classic sessions start, and use stricter approval checks for files, tools, and shells.
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.
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.
2.25.0CLI
Install and uninstall Powers from chat or the command line, choose V3 output styles, tune fullscreen scrolling, and automate session teardown with a new Hook.
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>.
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.
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.
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.
2.24.0CLI
Use session-wide tool approval in V3, combine session dashboard filters, and control which environment variables your chats and tools inherit.
This release adds session-wide tool approval to V3 and makes /sessions controls easier to discover and combine. Project .env files no longer load automatically into chat sessions, MCP servers, or tools. In V2, image handling now recovers when images exceed supported dimensions. Terminal rendering, settings, and agent config upgrades also receive reliability updates.
Run /tools trust-all to automatically approve tool calls for the rest of the current V3 session. By default, Kiro shows a safety warning and asks you to confirm before enabling it, so enable trust-all only in an environment you trust. Learn more ->
In /sessions, open the Filter, Sort, or Group control to see its options inline. You can combine the current workspace, main sessions, and bookmarked filters; includes empty reveals empty sessions, which are hidden by default. Learn more ->
Project .env files no longer load automatically into chat sessions, MCP servers, or tools. Kiro starts with the environment inherited from your terminal. If your workflow relies on variables from a project .env, export them in your shell before starting Kiro. For MCP servers, reference the exported values in the server configuration. Learn more ->
In V2, Kiro resizes images that exceed supported dimensions while preserving their aspect ratio, and scales down oversized images in saved history when a session loads. If the model provider still rejects an image, Kiro retries automatically, then replaces the rejected images with a placeholder and shows a notice so the conversation can continue. Learn more ->
2.23.0CLI
Configure thinking and effort from /model and start V3 cloud sessions before connecting a repository.
This release brings reasoning controls into /model and lets V3 cloud sessions start before you connect a repository. Improvements add clearer live progress, smoother streaming, and more efficient fullscreen scrolling. Reliability fixes cover models, sessions, tools, and non-interactive runs.
Open /model to switch models and configure the selected model's thinking and effort in one place. The panel shows only the options supported by that model and saves your choices for future sessions. /model is now the primary interface for reasoning settings. In V2, bare /effort is a legacy command: it shows a deprecation warning and opens the Effort setting in /model; /effort <level> remains supported. In V3, /effort continues to open its own picker. Learn more ->
You can start a cloud session before connecting a repository. Run /repo when you're ready to attach one. If no source provider is connected, Kiro opens the connection screen, where the repository is marked as optional. Learn more ->