Product briefing
What it is and how it fits a coding workflow
Kiro is an agentic development environment organized around one harness that is available through several clients. The IDE adds editor integration and specification-driven planning; the CLI supports terminal and headless work; Kiro Web runs repository tasks in a managed sandbox and can prepare pull requests; mobile is for following sessions and reviewing work. AWS documents Kiro CLI as the next update of Amazon Q Developer CLI and provides a migration path. Existing users can continue using the old `q` commands, so treat Kiro as the recommended successor path rather than an unrelated second CLI agent or an instantaneous removal of Q CLI. The `.kiro` project configuration carries guidance such as steering rules, custom agents, hooks, MCP servers and skills across surfaces, while each client has different permissions and execution location. That makes Kiro a useful option for teams that want structured requirements and a continuous handoff from local planning to cloud implementation. It is not an open-source, provider-neutral runtime: model selection follows the product’s current catalog and account or enterprise geography policies. Pay attention to where a session runs—local IDE/CLI work can touch the developer machine, whereas web sessions operate in a cloud sandbox connected to selected repositories. The cloud interface can open a PR, but documentation says changes are reviewed before reaching the default branch. Before enabling it for a company repository, validate identity setup, data residency, repository grants, audit requirements and how secrets are handled. Compare Kiro with an IDE-only agent when local control is more important than shared cross-surface sessions.