Changelog

Build, delegate, and steer development work with Kiro Web from your browser. Explore ideas collaboratively, shape work with Specs, or hand off a task end to end. Learn more ->

Configuration Sync can now carry your cloud configuration into new local Kiro IDE and CLI sessions. On the Configuration Sync page, enable Apply your cloud configuration to local sessions to load your cloud Steering files, custom agents, Skills, Powers, and Hooks when a session starts. Cloud content stays in the cloud and does not replace files in your local .kiro directory. Learn more ->

With Cloud configuration enabled, your supported personal configuration appears across the IDE and Agent Focus, and cloud-synced Powers are ready to try from the installed list. This version also keeps in-progress cloud-session drafts available across navigation and preserves the welcome view until you send your first prompt.

When Cloud configuration is enabled for your account, access personal Steering, custom agents, Skills, Powers, and Hooks from their usual IDE surfaces. Cloud indicators identify items managed in Kiro Web. Steering, Skills, and Hooks open as read-only previews with an Edit in web action, and Agent Focus shows the same source and management links. Learn more ->

Cloud-synced Powers now appear in the installed Powers list, where you can select Try power and review their bundled Skills and MCP configuration. Manage these account-backed Powers in Kiro Web. Learn more ->

This release adds a V3 dashboard for browsing, searching, resuming, and cleaning up local and cloud sessions. A new configuration panel brings your configured resources together in one terminal view. Configuration Sync can also apply your uploaded cloud configuration to new local CLI sessions.

In V3, open /sessions or run kiro-cli chat --sessions to browse, search, resume, and clean up past sessions stored locally or in the cloud. Learn more ->

In a local or cloud V3 session, run /config to view configured agents, MCP servers, Powers, Steering, Skills, and Hooks in one place. When source information is available, the panel identifies items as local, cloud, or both. Learn more ->

Upload your personal .kiro configuration with Configuration Sync in Kiro Web. Cloud sessions use the uploaded configuration automatically; enable Apply your cloud configuration to local sessions to load cloud Steering, custom agents, Skills, Powers, and Hooks in new local CLI sessions without writing those files to your local .kiro directory. Learn more ->

Kiro is included in the defined scope of AWS's ISO/IEC 27001:2022 certification. This gives security, procurement, and vendor-risk teams independently verified evidence they can use when evaluating Kiro.

ISO/IEC 27001 sets requirements for an information security management system: the policies, processes, responsibilities, and controls an organization uses to identify and manage information security risks. AWS's certification is verified by EY CertifyPoint, an ISO certification body accredited by the Dutch Accreditation Council.

Organizations can consider this evidence alongside their own policies, intended use, data requirements, and governance controls.

For details about Kiro's compliance programs and access to available third-party reports, see Compliance validation. To learn how Kiro stores, processes, and protects customer data, see Data protection.

Account administrators can now send per-user Kiro usage metrics to their OpenTelemetry-compatible observability platform. Monitor adoption, engagement, and credit consumption by user and model without configuring individual developer environments. Use OTLP alongside the existing daily CSV report to integrate Kiro metrics directly into dashboards and monitoring workflows.

Connect Amazon CloudWatch, Datadog, Dynatrace, Elastic, Honeycomb, OpenSearch through an OTLP receiver, or your own collector using OTLP/gRPC or HTTP/protobuf. Set up one account-level export in the Kiro console with an AWS Secrets Manager secret and a publicly reachable OTLP endpoint. Kiro delivers metrics server-side every day at 02:00 UTC. Learn more ->

You no longer have to start from the default branch. When you select a GitHub or GitLab repository for a session, choose the branch to work from right in the selector. The agent clones that branch and builds on it.

This version gives your AWS account a control room, lets administrators publish one security policy across a fleet, and makes parallel work easier to manage with persistent session tabs. Local dictation works without a separate speech-to-text install, agents can coordinate work across sessions, and script-installed copies can update themselves atomically.

A few changes need your attention before updating:

• Local dictation now uses one local provider. The whisper, mlx, parakeet, and faster speech-to-text providers are retired. Saved settings fall back to local, which downloads its model on first use. The new default is the 148 MB base model; a stored turbo setting still works but downloads 1.6 GB. Live text is on by default for new installs, and kirocrew doctor reports stored defaults that an earlier build materialized so you can decide which to adopt.
• Snapshot backup to S3 is retired. kirocrew snapshot --to s3://..., --aws-profile, and the s3:// fetch path are removed. Use the AWS Control app for cloud backup. Snapshot restore now supports replacing or merging live state, with a rollback ledger.
• Installed apps may ask for one-time re-consent. App trust is now tied to the repository you approved. A legacy grant that cannot be matched to a repository asks again rather than applying to different code.
• Some commands may ask for approval again. Looking like a help or version check no longer counts as approval, and durable always-allow grants no longer cover structured non-shell tools.
• Kiro CLI bundle overrides are removed. Kiro Crew now uses Kiro CLI's published relay, so custom bundle-path environment overrides from earlier releases are no longer read.
• Knowledge moves into Agent Capabilities. The standalone Knowledge page leaves the sidebar. Its content moves to Agent Capabilities > Knowledge & instructions, and old /knowledge links redirect there.
• Auto-Triage Pipeline moves into Issue Radar. The standalone app and its saved repository are retired. Its boards become a fourth Issue Radar board that follows the repository you select.
• Disconnecting a connection revokes its local OAuth grant. Reconnecting requires sign-in again unless another agent or scope still shares the endpoint.
• Governance configuration fails closed. A misspelled security-policy sandbox key now fails validation, and a malformed publish section denies publishing instead of dropping its restriction.

The new AWS Control app brings connected AWS accounts into one surface. Review account health, browse a private and versioned S3-backed drive, manage access, inspect billing, and run cloud backups. Changes require consent and appear in the audit log. Restore a snapshot into the running install by replacing or merging selected components, with a rollback ledger if you need to undo it. Learn more ->

Administrators can publish one security_policy.json at a URL and have every host fetch, cache, and refresh it without a restart. If the source is unavailable, hosts keep using the cached policy; an invalid document is rejected rather than lowering the current ceiling. Enterprise Kiro accounts also honor administrator-managed MCP registry controls, including version pins. Learn more ->

Keep several sessions open as tabs above the transcript. Middle-click or modifier-click a sidebar row to open one, see live status on each tab, and keep the same set of tabs per surface. Dormant sessions fold behind an expander after a threshold you choose, while pinned, running, and unread sessions stay visible. The + New menu also adds Ephemeral chats: Incognito reads memory but writes none, while Temporary neither reads nor writes memory. Learn more ->

When several tool calls wait on you, approve or reject all of them at once, or reject one call and continue reviewing the rest. Long shell commands show a readable summary with the full command available on hover. kirocrew chat now displays permission prompts and lets you answer them instead of waiting silently. Learn more ->

Agents can send a message into another session as its next turn, and the built-in conductor can divide a larger goal into work items, start a session for each one, check results, and decide the next round. Workflows can be promoted into a versioned global library and invoked with /workflow, while pull request watchers wake on comments, reviews, and verdicts instead of checking only build results. Learn more ->

A single in-process local speech-to-text provider downloads its own model on first use and keeps it ready, so dictation works without installing an external binary. Live text appears as you speak, silence hallucinations and caption boilerplate are filtered out, and settings that require a Gateway restart offer the restart action in the same panel. Learn more ->

kirocrew update installs a new version into a fresh, signature-verified tree and switches to it atomically. Windows Restart & Update now shows installer progress, updates the existing install, updates retained shortcuts, and relaunches the new build. The About page reports when updates were checked and names the version actually running. Learn more ->

This version lets third-party extensions work alongside Kiro, adds support for the latest MCP protocol revision with more reliable sign-in, reduces extension host crashes during large agent responses, and keeps agent turns going when the network briefly drops.

New sessions now get a descriptive, agent-generated title based on what you're working on, replacing the generic default. The title appears in the session header and sidebar as soon as it's ready. Rename a session yourself and that name sticks. The agent never overwrites a title you've set.