This release shows a startup prompt inviting you to switch to V3 as part of a gradual rollout. It also adds V3 model fallback notices, keeps more of your V2 agent access when you upgrade agents to V3, ...
Use the local command sandbox and autonomous mode in V3, load MCP tools on demand, and keep V3 configuration under KIRO_HOME. This release makes the local command sandbox and local autonomous mode ...
Limit what agent-run shell commands can reach, start saved Workflows from chat, and see live session status on editor tabs. This release lets you limit what agent-run shell commands can reach and ...
Kiro Web now lets you choose a fallback model and change the model a workflow step runs on. Reopened sessions show their conversation while the sandbox starts. You can also recover a workflow loop ...
Until now, there was no way to control how enterprise users sign in to Kiro on managed devices. Even if your organization requires IAM Identity Center, users can still sign in to Kiro with a personal ...
How global and project settings combine When the global policy is active, a project file can only tighten it. A project cannot set enabled to false, choose a more open network mode, or turn off MCP ...
Kiro is now in scope for FedRAMP Class C in the US East (N. Virginia) Region. US government agencies, contractors, and other organizations whose workloads are subject to FedRAMP Class C requirements ...
You must have an instance of IAM Identity Center (IdC) set up in your AWS account, with the identities of the users you want to subscribe to Kiro. Your IAM Identity Center instance must be in a ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results