Config files Kiro has changed
Config you own — hooks, permission rules, MCP servers, settings — that releases below state a change to. Counted from the release notes we track, newest change first. How a harness is layered.
Release signals
Fullscreen Chat and Streamlined Sessions
Claude Fable 5.1 Preview Begins Rolling Out to Kiro Enterprise · Claude Fable 5.1 is beginning to roll out in Preview across Kiro clients for Kiro Enterprise organizations. · Anthropic's most capable agentic coding model traces problems to root causes, maintains context and intent across complex tasks, and improves reliability for multi-file refactors and long autonomous runs. · It has a 1M context window and a 6x credit multiplier. · Inference runs only in US East (N. · Virginia) ( us-east-1 ). · Availability is limited during the Preview rollout. · +5 more changesRead the full release noteHide the full release note
Claude Fable 5.1 Preview Begins Rolling Out to Kiro Enterprise Claude Fable 5.1 is beginning to roll out in Preview across Kiro clients for Kiro Enterprise organizations. Anthropic's most capable agentic coding model traces problems to root causes, maintains context and intent across complex tasks, and improves reliability for multi-file refactors and long autonomous runs. It has a 1M context window and a 6x credit multiplier. Inference runs only in US East (N. Virginia) ( us-east-1 ). Availability is limited during the Preview rollout. Organizations with access can enable Fable 5.1 through model governance. After model access management is enabled, administrators can add Fable 5.1 from Manage approved list and make it available to their users. All Fable 5.1 traffic is retained for up to 30 days (unless otherwise required by law) for automated offline abuse detection. Classifier-flagged traffic will be subject to potential human review performed by AWS, and we may review flagged traffic for abuse. Learn more ->
Sep 11, 2026
2.21.4 Sep 11, 2026Primary source ↗Sep 10, 2026
September 1, 2026 Session Dashboard, Configuration Panel, and Cloud Sync · 2.21.0 · Browse and manage local and cloud sessions, inspect configured resources, and apply cloud configuration to new local V3 sessions. · 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. · Session dashboard (V3) · +16 more changesRead the full release noteHide the full release note
September 1, 2026 Session Dashboard, Configuration Panel, and Cloud Sync 2.21.0 Browse and manage local and cloud sessions, inspect configured resources, and apply cloud configuration to new local V3 sessions. 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. Session dashboard (V3) 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 -> Configuration panel (V3) 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 -> Cloud configuration in local sessions (V3) 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
Excerpt ends here — this release continues at the source ↗.
Sep 8, 2026
2.21.2 Sep 8, 2026Primary source ↗Sep 3, 2026
2.21.1 Sep 3, 2026Primary source ↗Session Dashboard, Configuration Panel, and Cloud Sync
Kiro Web Is Now Generally Available · 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 ->Primary source ↗Aug 31, 2026
2.20.2 Aug 31, 2026Primary source ↗Aug 27, 2026
2.20.1 Aug 27, 2026Primary source ↗Full-Screen Spec Task Execution and Preserve Scrollback
Primary source ↗Aug 25, 2026
2.19.2 Aug 25, 2026Primary source ↗Aug 21, 2026
2.19.1 Aug 21, 2026Primary source ↗Aug 14, 2026
2.18.1 Aug 14, 2026Primary source ↗Cloud Sessions Preview and Smarter Command Menus
Spec Review Mouse Support and Automatic Stream Recovery · This release brings mouse support to the spec review screen. · Under the hood, a stream idle watchdog, automatic retries with backoff, and a 60-minute streaming timeout mean a dropped connection or a throttled request no longer hangs or ends your turn. · Mouse support in spec review · The spec review screen now supports the mouse: scroll to navigate the document and click to position the cursor. · Press m to toggle mouse support on or off. · Learn more -> · Automatic recovery from stream and network failures · +7 more changesRead the full release noteHide the full release note
Spec Review Mouse Support and Automatic Stream Recovery This release brings mouse support to the spec review screen. Under the hood, a stream idle watchdog, automatic retries with backoff, and a 60-minute streaming timeout mean a dropped connection or a throttled request no longer hangs or ends your turn. Mouse support in spec review The spec review screen now supports the mouse: scroll to navigate the document and click to position the cursor. Press m to toggle mouse support on or off. Learn more -> Automatic recovery from stream and network failures Turns no longer hang on a stalled response stream: an idle watchdog warns after 60 seconds of silence and cancels at 300, while throttling, 5xx errors, and connection drops are retried automatically with backoff. Streaming responses also get a 60-minute timeout by default, so long responses are no longer cut off. Tune all of it with the api.streamIdleSoftTimeout , api.streamIdleHardTimeout , and api.timeout settings. Learn more -> Improvements Fixes Patches