Kiro

October 5, 2026 Switch to 3.0 from Classic, Category-Based Hook Matching, and Steadier V3 Sessions 2.28.0 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. Improvements Fixes { PREVIOUS } Connect more MCP servers, relocate ~/.kiro, and remap the TUI { NEXT } Workflow Delegation, Live Steering Context, and Saved Prompt Commands

October 1, 2026 Workflow Delegation, Live Steering Context, and Saved Prompt Commands 2.27.0 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. Learn more -> Include live context in Steering 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

September 30, 2026 Workflows, Classic Migration Guidance, and V3 Approval Safeguards 2.26.0 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. Run multi-step Workflows 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 -> Move from Classic to the terminal UI 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 -> Improvements Fixes Patches

Introducing Workflows in Kiro Web 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. Learn more -> Follow and guide each step

September 30, 2026 Workflows, Safer Untrusted Workspaces, and Enterprise Sign-In Controls 1.2.4 Run reusable multi-agent Workflows in the background, apply stronger safeguards to Kiro configuration, and manage enterprise sign-in options. 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. Run multi-agent Workflows in the background 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 -> Protect Kiro configuration and Workflow recipes

September 28, 2026 Power Management, V3 Output Styles, and Fullscreen Scroll Speed 2.25.0 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. Install and uninstall Powers 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 -> Choose a V3 output style 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 ->

September 24, 2026 Live Settings, Durable Work, and Broader Pull Request Watches 0.7.0 Kiro Crew 0.7.0 makes day-to-day work more durable and easier to control. Most settings apply as soon as you save them, accepted background work survives Gateway restarts, and updates wait for active work to finish. Long chats gain a turn minimap, clearer tool-call titles, and direct model and reasoning controls, while pull request watches expand to GitLab, Bitbucket Cloud, and Azure DevOps Services. Windows gets isolated pods and a faster Gateway start, and Preview users can choose more agent backends, let Jev route individual turns, or run remote crews on AWS Fargate. Settings That Apply While You Work Most settings now reach the running Gateway as soon as you save config.json or change a value in Settings. Fields that still need a restart identify themselves in the UI; the Slack slash-command field is the current boot-only setting and carries a Changes need a restart badge. Learn more -> Chat That Keeps Up With You

September 24, 2026 Live Settings, Durable Work, and Broader Pull Request Watches 0.7.0 Kiro Crew 0.7.0 makes day-to-day work more durable and easier to control. Most settings apply as soon as you save them, accepted background work survives Gateway restarts, and updates wait for active work to finish. Long chats gain a turn minimap, clearer tool-call titles, and direct model and reasoning controls, while pull request watches expand to GitLab, Bitbucket Cloud, and Azure DevOps Services. Windows gets isolated pods and a faster Gateway start, and Preview users can choose more agent backends, let Jev route individual turns, or run remote crews on AWS Fargate. Settings That Apply While You Work Most settings now reach the running Gateway as soon as you save config.json or change a value in Settings. Fields that still need a restart identify themselves in the UI; the Slack slash-command field is the current boot-only setting and carries a Changes need a restart badge. Learn more -> Chat That Keeps Up With You

September 21, 2026 Reasoning Controls and Cloud Sessions 2.23.0 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. Reasoning controls in /model 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 -> Cloud sessions before repository connection (V3)