This release brings Output details to everyone: choose in /settings how much detail tool calls show, from one line per call to the full output. It also fixes sign-in on Linux hosts with no graphical session and with Identity Center flags, keeps /model fallback settings working, and fixes workflow, spec, Skills, file search, permissions, and session reload issues.
This release adds a full-screen viewer for Mermaid diagrams that are too wide for your terminal, and signs you in to more MCP servers with no OAuth configuration. It also lets you run one more iteration or finish a workflow loop that used all its iterations, tells you when workflows are not available in autonomous mode, asks before a V2 shell command sets XDG_CONFIG_HOME or HOME, and fixes file search, custom agent, workflow, spec, Hook, clipboard, help text, and session issues.
When an otherwise supported Mermaid diagram in an agent reply is too wide for your terminal, Kiro now shows the source with a notice and an entry above the prompt. Press Ctrl+] or run /diagram to open the newest wide diagram on its own screen, laid out at full width. Use the arrow keys or the mouse wheel to move around it, press Tab to step to older diagrams, and press Esc to return to the chat with your draft intact. Change the key with chat.keybindings.viewDiagram. Learn more ->
Some MCP servers, such as Tableau's hosted MCP, support Client ID Metadata Documents but offer no dynamic client registration. Kiro now signs in to them with its own hosted client metadata document, so you add the server and sign in with no oauth block in your configuration. Servers that offer dynamic client registration keep using it, and a configured clientId or clientMetadataUrl still takes priority. Learn more ->
This release adds PreCompact and PostCompact Hooks that run around conversation compaction, and shows the credits a session has used so far in /usage, the status line, and workflow step rows. It also lets you ship default settings for an environment, adds an opt-in session recap, lets sub-agents read their parent's memories, groups notifications into one row, and fixes rendering, sub-agent, workflow, and headless issues.
In CLI V3 sessions, PreCompact Hooks run before manual or automatic compaction and can refuse it, while PostCompact Hooks run afterward and receive the summary. Use these lifecycle points to save a copy of the conversation before older history is summarized, or archive and review the summary after compaction finishes. Learn more ->
/usage now shows the credits your session has used so far. Turn on the optional Session credits segment under /settings display to keep that total in the status line while you work. In the workflow monitor, each step row shows the credits that step used, so you can see where a run spends. Learn more ->
This release makes V3 the default agent harness for interactive Kiro CLI sessions on hosts that can run it. Existing V2 users are asked before the default applies, and Kiro upgrades custom agents still in the V2 format unless you turn that off. Kiro CLI is now a single standalone kiro-cli binary that retires the Classic interface, the desktop app, and inline autocomplete.
V3 brings capabilities V2 does not have. Cloud sessions let you disconnect and resume later from /sessions. Memory, once enabled, carries repository context forward. Approve for me, once enabled, approves routine actions, blocks unsafe ones, and asks about the rest while your deny, ask, and allow rules still decide first. /sandbox isolates shell commands, /autonomous on runs tasks without per-command approval with sandboxing on, and Workflows show their plan before starting. Turn on Workflows under /settings > Features.
- Classic interface: The Classic (V1) interactive experience no longer runs. If your command, alias, or settings still select it, Kiro offers Continue with V3 when you start a chat, and scripts ignore the selection. To keep the V2 agent, run
kiro-cli --v2. Learn more -> - Desktop app: Kiro CLI no longer ships the desktop app. Existing macOS desktop app installs switch to the standalone
kiro-clion their next update check. To reinstall or change how Kiro CLI is installed, see Moving from the Kiro CLI desktop app. - Autocomplete and inline suggestions: Inline shell autocomplete and inline suggestions are retired with the desktop app and have no standalone replacement. The
autocomplete,inline,translate,theme, anddashboardcommands are unavailable; remove them from your scripts. Runningkiro-cli doctornow directs you tokiro-cli diagnosticorkiro-cli issue.
V3 is now the default. You no longer need --v3.
- Interactive: New sessions start on V3. If you already use V2, you'll be asked first.
- Headless: By default, scripts using
--trust-all-toolsstart on V3. Other scripts stay on V2. - ACP: By default, new clients start on V3. Existing clients stay on V2 unless already supported.
This release turns on automatic V2 agent upgrades by default when a V3 session starts and lets ACP clients that declare terminal authentication sign in to Kiro from a terminal. Custom agents built for V2 keep working on V3 without a manual upgrade run, and a capable client opens a terminal sign-in flow. It also draws Mermaid node shapes and nested subgraphs, adds a KIRO_RUNTIME_DIR override for the bundled runtime, and tidies V3 approval prompts. Fixes cover fullscreen scrolling, click targeting in fullscreen, and the Homebrew upgrade hint.
Kiro CLI can upgrade V2-format agents to the V3 format when a V3 session starts. That upgrade now runs unless you turned it off: an unset chat.enableAutoAgentUpgrade preference enables launch migration, while an explicit false stays off. It covers your workspace and global agent directories, or the KIRO_AGENT_CONFIG_DIR directory when set, and rewrites each agent file in place after saving a .json.bak backup. To keep agents in V2, run kiro-cli settings chat.enableAutoAgentUpgrade false; interactive V3 launches then show a notice naming how many agents still need upgrading. Learn more ->
If kiro-cli acp starts while you are signed out, ACP clients that declare terminal authentication now offer a Log in to Kiro method that runs kiro-cli login in a terminal. Complete the sign-in and reconnect, and the agent starts with your credentials. If your client does not declare terminal authentication, Kiro asks you to run kiro-cli login. Until you sign in, every other request returns an authentication-required error. Learn more ->
This release adds Approve for me to interactive V3 sessions. Kiro approves routine actions for you, blocks risky ones, and asks when unsure, so work no longer stops at every routine prompt. Existing deny, ask, and allow rules decide first; Approve for me handles only unsettled actions and marks each action it approves Approved for you. Turn it on under /permissions when available.
In an interactive V3 session, run /permissions and choose Policies. When the page offers approve for me, choose it. The choice you make here is stored per workspace: Kiro adds the approve-for-me policy preset to the workspace permissions file, so it stays with that repository and does not follow you to others. When the page says instead that Approve for me is unavailable in your session, Kiro keeps asking. Choose ask for approval to go back to prompts for every action your rules do not cover. Learn more
This release warns you when Kiro CLI starts as root or Administrator and makes V3 sessions follow your organization's MCP and web tools settings. It also lets you jump back to the prompt from a long answer in fullscreen, shows which MCP servers your registry hid in V3, and fixes model fallback, session resume, dictation, and MCP connection issues.
Kiro CLI now warns you when a session starts as root on macOS and Linux or as Administrator on Windows. Tools, shell commands, Hooks, and MCP servers can run with those privileges and create root-owned files or change system settings. The warning does not block anything. If you intentionally run Kiro CLI with elevated privileges, turn the warning off with kiro-cli settings app.warnOnElevatedPrivileges false. Learn more
V3 sessions now turn MCP servers and the web_search and web_fetch tools on or off according to your organization's Kiro settings. Learn more
This release lets V3 MCP tools ask for input, gives you more control over Workflows, and lets you delete memories from /memories. It also adds a model picker editor and improves workflow recovery, headless MCP sign-in, saved sessions, accessibility, and more.
In local V3 sessions, MCP tools can now pause and show a form or link when they need more information. Enter the requested details, complete an action on another page, or decline the request. The tool continues without restarting its call. Learn more
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.
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.