Skip to main content

Changelog

Stay up to date with the latest updates and improvements to Kiro. Also, follow us on X, Bluesky, LinkedIn, or Discord.

1.4.236IDE

This release lets you install powers and skills from GitLab, answer permission prompts with a script, and sign in once to your organization's MCP servers. It also lets you move chats between the Side Bar and Editor Area and choose Memory settings from the Memories view.

Install powers and skills from GitLab

Paste a public GitLab URL to install a custom power or import a skill, the same way you do from GitHub. To use a self-hosted GitLab instance, add its host to the kiroAgent.powers.trustedGitLabHosts setting first. Learn more ->

Answer permission prompts with a script

Create a Permission Request Hook in the Hook editor to run a command just before Kiro would ask you to approve a tool call, so a script can answer routine prompts in a session nobody is watching. Pre Tool Use Hooks can also replace a tool call's input before it runs, and any approval prompt shows the final arguments. Learn more ->

Sign in once to your organization's MCP servers

Eligible HTTP MCP servers can share one sign-in through your organization's identity provider, instead of asking you to sign in to each server. Add the identity provider your administrator gives you to your user MCP configuration, then select Sign in on the Organization sign-in row in the MCP Servers view. Learn more ->

3.5.0CLI

This release adds organization sign-in for MCP servers in V3 sessions and a configurable portal for kiro-cli login. One sign-in through your organization's identity provider now covers every server set to use it, and you or your administrator choose where browser sign-in starts.

Sign in to MCP servers through your organization

In a V3 session, every MCP server you set to organization sign-in shares one sign-in through your organization's identity provider instead of a separate browser flow per server. Run kiro-cli mcp idp setup with your provider's issuer and client ID, then open /mcp and press Enter to sign in once; those servers stay disconnected until you do. For an HTTP server whose owner issued Kiro a client ID, use the --oauth-client-id <client-id> flag on kiro-cli mcp add, except when your organization's registry manages that server's OAuth. Learn more ->

Choose the sign-in portal kiro-cli login opens

Set auth.portalUrl and kiro-cli login opens that portal in your browser instead of the default one. Administrators can set the portal for their users through the AuthPortalUrl policy or auth_portal_url in managed-settings.json. If Kiro cannot use that value, it falls back to the default portal. Learn more ->

General

Enterprise administrators can now set local sandbox controls for Kiro IDE and Kiro CLI. In Controls, require sandboxing for commands and local stdio MCP servers, and choose file and network defaults. Developers cannot turn off a required sandbox through client settings or change organization-set modes. Their allow rules cannot override organization deny rules, and tool permissions still decide which commands may run. Credential stores stay closed by default, but a file allow rule that covers them can open them.

Enterprise Management is in preview in US East (N. Virginia) (us-east-1) for profiles using IAM Identity Center or an external identity provider. Developers need Kiro CLI 3.4.0 or later or Kiro IDE 1.4.215 or later.

Learn more ->

General

Enterprise administrators can now move existing Kiro profiles to Enterprise Management. The preview covers US East (N. Virginia) (us-east-1). Profiles can use IAM Identity Center or an external identity provider.

When Settings offers Migrate to the new experience, preview the mapping. Kiro copies your current settings to Controls. Overages, the encryption key, and member account subscriptions stay on Settings. The move is one-way.

Learn more ->

Web

You can now run commands in your session's workspace right in Kiro Web. Open a terminal beside the conversation or below it to run builds and tests, check output, or try a command yourself. Learn more ->

Loading image...Kiro Web session with the terminal docked on the right beside the conversation. The terminal shows pwd, node --version, python3 --version and git --version run in /projects/sandbox, printing Node v24.21.0, Python 3.11.15 and git 2.50.1.
1.4.215IDE

This release lets you fork a chat from any turn, so you can try a different prompt from the same point without losing the original. It also shows the credits a workflow run reports, gives the Memory levels clearer names, and lets chats that use a custom agent or Plan run at the same time as other chats. Kiro profiles in Europe (Frankfurt) can also use cloud sessions from the IDE.

3.4.0CLI

This release adds hooks that rewrite a tool call's inputs before it runs or answer its permission prompt, so a script can apply your team's rules to every tool call in V3 sessions instead of waiting on you to approve each one. It also offers four /memories choices, resumes and lists cloud sessions in more places, and fixes headless, context window, MCP, search, /tangent, /rewind, and display issues.

Rewrite a tool call or answer its permission prompt from a hook

In a V3 session, a PreToolUse hook can now return updatedInput to replace a tool call's inputs before the tool runs, alongside its allow, ask, or deny decision. A new PermissionRequest hook runs when a tool call would ask you for permission and can answer with allow or deny, so a script grants or refuses a call that would otherwise wait on you. A deny from any hook wins over an allow, and a hook's permission answer applies to that one tool call only. Learn more ->

General

Kiro Enterprise administrators can now send richer activity data to their observability tools. Stream each LLM request and completed tool call as a real-time OpenTelemetry event, or use daily CSV reports and OpenTelemetry metrics for reconciled trends. Track credits, models, conversations, response times, tool outcomes, client versions, and agent modes. Real-time events and private connectivity are available for Kiro profiles in US East (N. Virginia) and Europe (Frankfurt).

Loading image...Kiro sends real-time events and daily metrics through the public internet, AWS PrivateLink, or Amazon VPC Lattice to an OTLP collector and dashboards.

Daily metrics move to 00:30 UTC on November 26, 2026. Until then, Dynatrace and Grafana Cloud reject them as too old. The CSV report stays at 02:00 UTC.

Choose public delivery, AWS PrivateLink, or Amazon VPC Lattice for OpenTelemetry. Private connections never fall back to public delivery. Exports include usage data and user identifiers. They exclude prompts, responses, code, and files. Turn on and test each export in the Kiro console.

Learn more ->

Web
Mobile

Kiro Mobile is now available on Google Play, so you can work in Kiro cloud sessions from your Android phone. Your laptop doesn't need to stay on. Sign in with your Kiro account, and your sessions, connected repositories, and model choices are already there. Kiro Mobile requires a Pro, Pro+, Pro Max, or Power plan.

Follow, Steer, and Review Sessions from Your Phone

Loading image...Kiro Mobile new chat screen on Android. Under the Let's build heading, Connect repositories shows 2 repositories and Build with spec is off. The composer holds a prompt, with Auto and Autonomous on selected.
Loading image...Kiro Mobile session list on Android. Each session shows its title, repositories, age, and pull request status, such as 1 merged or 3 open.

Start a cloud session, or pick up one you started in Kiro Web, the IDE, or the CLI. Choose your repositories and a model, and turn on Build with spec to plan first. In Autonomous mode, the model selector shows Auto and cannot be changed. Follow replies and tool activity live, attach images, answer the agent's questions, or stop a run. Each edited file appears as a phone-sized diff card, and each session shows its pull request status. You review and merge in your Git provider. Learn more ->