Changelog

GPT-5.6 Sol, Terra, and Luna now support a 1M token context window, up from 272K, in the Kiro IDE, CLI, and Web. Entire codebases, long-form documents, and extended multi-turn agent histories fit in a single request, so repository-scale refactors, end-to-end debugging, and long-horizon agentic tasks run without chunking or losing earlier context. Credit multipliers for the GPT-5.6 family are updated with this launch and follow the two-tier context model OpenAI and Amazon Bedrock use: requests up to 272K tokens bill at the short context rate (Sol 4.4x, Terra 2.2x, Luna 1.1x), and requests above 272K tokens bill at double that rate. 1M context is rolling out gradually with experimental support to Kiro Pro, Pro+, Pro Max, and Power customers. Restart your IDE or CLI, or refresh Kiro Web, to see the updated models. Learn more ->

IDE 1.1 lets agents produce durable artifacts you can review and return to, adds native ARM64 builds for Windows and Linux, and updates the editor foundation to Code OSS 1.131. Compacted conversations retain the right context, MCP failures are clearer, Hooks are more reliable, and enterprise profiles route requests to the selected region.

Kiro can turn documents, diagrams, code, images, and other agent outputs into durable artifacts instead of leaving them buried in the chat transcript. Open a compact preview from the conversation, review the full artifact beside the chat in Agent Focus, or return to it from the Agent Focus context panel. Learn more ->

Install native ARM64 builds for Windows and Linux instead of relying on x64 emulation. Choose the ARM64 download for your platform from the Kiro downloads page.

These capabilities shipped earlier in the IDE 1.0 release line and are included here for context.

• Cloud Configuration and synced Powers (1.0.437): Access supported personal configuration across IDE surfaces and try cloud-synced Powers from the installed list. Release notes ->
• Permission improvements and configured Windows shells (1.0.337): Keep ignored files out of search, apply filesystem and command permission rules more accurately, and run agent commands in your configured Windows terminal profile. Release notes ->
• Cloud Sessions and Agent Focus upgrades (1.0.293): Start Cloud Sessions from Agent Focus, collapse the session rail for more chat space, answer attention cards in place, and move back or forward between views. Release notes ->
• Agent Plugin support and session pinning (1.0.288): Use Agent Plugins through Powers and pin important Agent Focus sessions. Release notes ->

This version lets you choose what session search covers, adds a flag that selects the V2 agent harness for a single run, and gives every settings menu the same keyboard behavior.

In V3, /sessions search indexes session titles, your prompts, and agent responses, so you can find a session by what Kiro answered rather than only by what you asked. Open /settings and choose Session search to switch between Prompts only and Prompts and agent responses. Tool output is not indexed in either mode. If your local index currently covers prompts only, /sessions asks once before rebuilding it. Learn more ->

Pass --v2 to run one session on the V2 agent harness. It works on both kiro-cli and kiro-cli chat, and it takes precedence over a saved chat.agentEngine value without overwriting it, so your default stays as you set it. Learn more ->

Kiro Crew 0.6.0 lets you choose the harness behind a session, start work on a connected remote crew, and let crew members dispatch workers of their own. Chat is quieter and easier to resume, long-running work gets more room to finish, and Apps adds a Launchpad for the tools you install. Python 3.12 is now the minimum supported version.

A few changes need your attention before updating:

• Python 3.12 is now required. Hosts on Python 3.10 or 3.11 must upgrade before installing or updating. The installer provisions its own pinned Python when needed; pass --system-python only when you deliberately want to use your system interpreter.
• Keep the sandbox enabled if you rely on the command gate. Credential-path protection no longer relies on command-text inspection. Check that agent.sandbox in config.json is not off.
• Unattended auto-run plans stop after two hours by default. Raise orchestrator.max_plan_duration_seconds in config.json, or set it to 0 to remove the ceiling. Stage-gated plans are not cut off.
• Crew Members is now a preview opt-in. Turn on Settings > Developer > Feature Previews > Crew Members and Crew Mode to show the Crew Members entry and the new-crew-chat action.
• Automatic knowledge folders are removed. Add and confirm a folder before it appears in the Library. Older folders that were registered automatically remain pending until you confirm them.
• Developing an app UI outside its install root now requires the terminal. Use kirocrew app dev <name> --confirm-out-of-install-root. The dashboard and API no longer grant this access.

Choose Claude Code, Codex, or KAS for a session from Settings > Developer > Agent Backend after enabling Developer Mode. Crew shows whether each option is ready, missing on this machine, or waiting for a Gateway restart, while monitor loops and follow-up cards work across supported backends. Learn more ->

Start a chat on a connected crew without leaving your sidebar. Turn on instances.enabled and Settings > Developer > Feature Previews > Chat on a crew, then select a peer from New chat on crew. The transcript stays local, the remote crew runs each turn, and its name and server badge identify where the work happens. Learn more ->

Diffs now start folded into a file chip, with Settings > Chat > Plain diffs available when you prefer raw patch text. The composer can attach a sketch, show the project branch and changed-file count, and collapse when you need the transcript back. You can also share an assistant reply as a branded image or start a social post from it. Learn more ->

Agents can start, revise, and stop their own monitoring loop from the dashboard, Slack, or Discord, then wake when the work they watch changes. Crew members can dispatch workers from their own threads on Claude and KAS, inheriting the creator's trust posture. Session control is now on by default, and agent.session_control lets you disable it globally when needed. Learn more ->

A chat turn can now run for up to four hours through agent.chat_turn_timeout_secs, whose default rises to 14400. Subagents can run for three hours with agent.subagent_timeout_secs at 10800, and agent.subagent_max_turns supports up to 1000 tool calls. The monitor-loop goal chip also shows its cycle cap before the backstop is reached. Learn more ->

Give a crew member a customized ghost avatar or upload a picture from Agent Capabilities > Agents > Avatar > Customize. The new Expressions pane lets you set a reacting face and sound for working, done, and failed states. The Crew Members page also shows activity, patrols, schedules, webhooks, and roster filters for finding the right member. Learn more ->

Installed apps now appear as an Apps > Library Launchpad grid, where you can open, pin, update, disable, or uninstall each one. App manifests can declare background jobs with permissions.jobs, Command Bar entries with contributes.commands, and up to two live composer controls with contributes.sessionControls. Create Folders From Project also turns selected packages into nested sidebar folders. Learn more ->

AWS Control now opens on an Overview of account health, drive use, month-to-date spend, share links, and backup status. Its Files view opens common file types in a preview dialog, searches by name or path, renames from the item menu, and keeps upload, move, and delete actions close to the files they affect. Backup progress survives navigation, and disconnecting an account removes only Crew's local registry and consent records. Learn more ->

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 ->