The outcome

Get into the official Kiro experience with the right account and a setup you understand.

Kiro is a agentic integrated development environment from AWS. Turning feature ideas into requirements, design, tasks, and implementation while preserving repository guidance and explicit review of agent changes. This guide narrows that broad capability into one repeatable outcome, with checkpoints that keep the source material and your judgment in the loop.

Before you begin

Set the boundary before the tool starts.

Choose one real task, identify who will use the result, and decide what evidence or test will make the result acceptable. Gather only the source material needed for that task. If the work contains confidential, personal, regulated, or client-owned information, confirm that the platform and account are approved before sharing it.

Troiana principle

AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.

Step by step

A workflow you can repeat.

  1. 01

    Start at https://kiro.dev/ and confirm the domain before entering account or payment information.

  2. 02

    For desktop use, follow the official download link. Current availability: Kiro is a standalone agentic IDE with structured specs, steering files, hooks, agentic chat, MCP integrations, supervised review, and autopilot workflows..

  3. 03

    A supported desktop system, a Kiro account, an authorized repository, and reviewed identity, extension, model, command, and optional AWS access.

  4. 04

    Sign in with the account you intend to keep using, then review plan, data, notification, and permission settings.

  5. 05

    Run one low-risk test task before connecting sensitive files, repositories, or workspace data.

Working standard

What good use looks like.

  • Use official download pages.
  • Review permissions during setup.
  • Keep installers and applications updated.

Supervised and Autopilot modes have similar underlying file and command access; supervised mode adds a review-and-revert workflow rather than a stronger sandbox. Use repository-scoped authentication, temporary AWS credentials, carefully bounded trusted-command prefixes, protected paths, reviewed extensions and MCP servers, human-approved specs, checkpoints, and independent tests. Never use a universal command trust pattern on untrusted content.

Official references

Check the current product documentation.

Features, plan limits, availability, and data controls change. These official pages are the starting points used for this collection.