This release changes how V3 Workflows start: turning the feature on no longer kicks off a workflow by itself, so one runs only when you ask for it. The fixes improve screen reader output, MCP setup, and V2-to-V3 session resume.
2.33.1CLI
2.33.0CLI
This release adds workspace trust to interactive V3 sessions: Kiro CLI asks you to trust a folder before it loads that folder's hooks, agents, MCP servers, steering, workflows, or language server configuration. A cloned repository can no longer change how the agent behaves until you say so.
The first time you start an interactive V3 session in a folder, Kiro CLI shows a Trust this workspace? screen before it loads the folder's hooks, agents, MCP servers, steering, workflows, or language server configuration. Choose Trust, continue or Don't trust, exit. Kiro saves your answer per workspace root under ~/.kiro/workspace-roots/, so the screen appears once per folder. Trust for your home directory is never saved, so Kiro asks again at each launch there. To change your answer, remove workspaceTrusted from the per-workspace file the screen names. Learn more
V3 sessions can set model fallback again. The /model settings pane and the /model fallback commands save fallback configuration when the agent supports it. A saved choice applies to the current session and persists for later sessions. Open /model to confirm your fallback choice.
2.32.0CLI
This release lets you allow a whole folder when a V3 session asks to write a file. V3 cloud sessions now run from non-interactive commands, and a workflow shows its plan before any step runs. It 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.
2.31.1CLI
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.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.