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

In our last post, we described how three engineers and a crew of agents merged 1,000 pull requests in one week. The most common question we got back was how we keep that from breaking everything. But ...

This release adds Windows system-wide installers for x64 and ARM64 devices. It also brings drag-and-drop file attachments to chat without holding Shift, and framed Mermaid diagrams that stay readable ...

Spec-driven development (SDD) is changing how large teams build software. Instead of relying on a prompt alone, you author a specification that guides an AI coding agent through design, tasks, and ...

Starting on November 1, we’re changing how the Kiro free trial works. If you upgrade to Pro for the first time, the rest of that month is on us. You also get 500 ...

Claude Opus 5.5 and GPT-5.6 Sol are generally available with full Kiro support. Expanded capacity supports more dependable access for production workloads. Their current plans, regions, surfaces, ...

Kiro Web can now keep a short recap for each session and separates agent settings from account settings. Workflows now ask for input during planning and review. Schedule replaces Automations, and ...

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

This release adds a faster way to reconnect when an IAM Identity Center or AWS Builder ID session expires, without choosing a sign-in method or re-entering your Start URL. Markdown Review now lets you ...

Cloud sessions appear in the rail ordered by recent activity, with the same status indicators as local sessions. From a session's context menu you can: Pin Session to keep it at the top of the section ...

In CLI 2.x, tool permissions were managed through CLI flags, slash commands, and per-tool settings in agent config. In V3, per-tool settings are replaced by structured permissions.yaml files; the ...

At the center is the unified agent harness, which handles everything an agent run involves: orchestrating the conversation, executing tools, managing context, evaluating permissions, and talking to ...