CLI tool
kirodotdev/Kiro avatar
kirodotdev/Kiro

Kiro: an agentic IDE you cannot read, only file issues about

Kiro is an agentic IDE that works alongside you from prototype to production.

4,473 stars335 forksTypeScriptLicense varies

At a glance

What is it?
The kirodotdev/Kiro repository holds no product code. It is the public issue and feedback tracker for an Amazon agentic development platform whose real source lives elsewhere, so anyone evaluating Kiro has to judge it from its documentation rather than its commits.
Who is it for?
Adopt Kiro if your team wants spec-first agent work with steering, hooks and permissions carried across an IDE, a CLI and cloud sandboxes, and if losing the ability to read or fork the agent harness is an acceptable trade. Do not adopt it if you need an auditable, forkable agent runtime, because the harness behind these five surfaces is deliberately absent from this repository, and cloud sessions are still marked Preview.
Can I use it commercially?
Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
Is it still maintained?
Yes. The repository last received commits 10 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • kirodotdev/Kiro4,473 ★ · +171
Star history
Repository2026-09-162026-11-15
kirodotdev/Kiro4.3k4.5k

171 Stars in the last 60 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Kiro's GitHub repository holds the issue tracker, not the IDE

Everything a developer can audit here is process, not product. The repository says so directly: it is the public issue and feedback tracker for Kiro, and the product source code is not hosted here. What sits at the top level is a `.kiro/` directory, `docs/`, `scripts/`, `assets/`, a code of conduct and a contributing guide. That shape matters for anyone doing a dependency review or a licence audit before adoption, because there is no package manifest, no build file and no vendored code to read. Primary language is listed as TypeScript, which reflects the triage automation rather than an editor. The last push was on 2026-10-18 and the repository is not archived, so issue triage is still moving, but the churn you see is issue plumbing. Security reports deliberately do not come here either; the README routes them to the AWS vulnerability reporting page and asks people not to open a public GitHub issue for them.

One agent harness behind IDE, CLI, Web, Mobile and Crew

The design bet is portability of project context rather than a single strong editor. A single agent harness powers every Kiro surface, which is the stated reason your specs, steering, permissions, hooks, MCP servers and custom agents can follow a project as you move between surfaces. The table the README prints maps each surface to a job: the IDE for local editing with chat, specs and hooks, the CLI for terminal-native and headless CI work, Web for delegating multi-repository tasks into isolated cloud sandboxes, Mobile for monitoring and pull request review, and Crew for a persistent open-source workspace with memory, scheduling and multi-channel access. Only Crew is described as persistent, and it lives in a different repository, KiroCrew. That is the real architectural claim here, and it is also the hardest to verify from outside, since the harness is exactly what this repository does not contain.

Requirements Analysis runs before the first line of code

Specs are the entry point, and the first automated step is adversarial rather than generative. You structure requirements, design decisions and implementation tasks as specs, then run Requirements Analysis to find contradictions, ambiguities and gaps before coding begins. Correctness checking follows the same pattern: requirements become executable properties, exercised against generated inputs that example-based tests would miss. The interesting consequence for a reviewer is that the quality gate is placed upstream of the code, not after it. A spec that contains an unresolved contradiction surfaces while the fix is still a paragraph, not a refactor. The README does not say which model produces the analysis, how long it takes on a large codebase, or how the findings are presented for a human to accept or dismiss, so the granularity of that review is not something you can predict from these pages.

Steering, .kiroignore, hooks and permissions bound agent reach

The control surface is unusually explicit for an agent tool, and it is split across four separate mechanisms that do different jobs. Steering holds project conventions that guide custom agents, Agent Skills package reusable expertise, and custom agents themselves carry focused instructions and a tool set. Hooks react to agent events so you can run your own automation when something happens. Powers add on-demand tools and knowledge, while MCP connects external systems. Then there are the boundaries: permissions set what an agent may access, `.kiroignore` keeps sensitive paths out of context, and checkpoints with rewind let you inspect or undo changes. Read those together and the model is containment by layers rather than a single allowlist. Whether `.kiroignore` patterns are gitignore-style, and how rewind interacts with checkpoints taken mid-generation, is not something these pages answer.

Five setup paths, none of them a command in this repository

There is no install command here to copy, so this section stays prose. The README routes installation to a separate documentation page, and the per-surface entry points are distinct: Download Kiro for the IDE, CLI setup for terminal use, Kiro Web setup for the cloud sandbox surface, and a Mobile preview. Getting past installation means authenticating and then building a first project, both of which are separate documentation links. The CLI surface is the one worth planning around, because it is the only entry point aimed at headless automation and CI/CD, and its setup documentation lives at kiro.dev rather than in this repository. The practical consequence: anyone evaluating Kiro on a build server has to leave the codebase entirely and read hosted documentation, and any pinned, offline or air-gapped install story is not answered by anything in this repository.

What the repository does contain: issue triage automation

The one piece of real software in the tree is aimed at maintainers, not users. The repository includes automation used to triage and manage its own GitHub issues, and it ships two issue templates you can fill in directly: a bug report form and a feature request form. Bug reports and ideas are handled through standard GitHub issue forms, so filing one does not require an account anywhere else. Community support is routed to a Discord server instead of the tracker, and billing questions go to Kiro account settings. That split is worth naming before you commit: bugs and ideas go to the tracker, while questions and community help go to a chat server.

Cloud sessions are Preview and enterprise rollout is a separate path

Two parts of the roadmap carry an explicit maturity marker. Cloud sessions, the feature that starts work in a managed sandbox and lets it continue while you are away, are stated as currently in Preview. For teams, the enterprise path covers identity connection, subscription management, organization-wide governance controls and usage monitoring, but each of those is documented outside this repository too. Governance decides whether Kiro is usable in a regulated environment, and the privacy and security documentation is linked rather than reproduced here. If your decision hinges on where prompts and code are stored, or on what an administrator can lock down, these pages point at kiro.dev and stop. The governance controls are named precisely and described in no detail.

Editorial conclusion

Adopt Kiro if your team wants spec-first agent work with steering, hooks and permissions carried across an IDE, a CLI and cloud sandboxes, and if losing the ability to read or fork the agent harness is an acceptable trade. Do not adopt it if you need an auditable, forkable agent runtime, because the harness behind these five surfaces is deliberately absent from this repository, and cloud sessions are still marked Preview. Before signing up, open the repository and confirm that a bug report template and a Discord support server are the level of public accountability you are happy working with, then read the CLI setup page for the pinned build server story, because neither is answered anywhere in this repository.

Frequently asked questions

What company is Kiro?

Amazon. The README closes with a copyright line for Amazon.com, Inc. or its affiliates, and billing and account questions are directed to Kiro account settings.

Is Kiro from AWS?

The support contacts point that way: security issues are reported to AWS/Amazon Security through the AWS vulnerability reporting page, and suspended Kiro accounts are routed to Kiro support on support.aws.amazon.com. The repository itself follows the Amazon Open Source Code of Conduct.

How do I use Kiro?

Pick the surface for the job, then follow its setup page: Download Kiro for the IDE, CLI setup for terminal and CI work, Kiro Web setup for cloud sandboxes. After installation you authenticate and build a first project, then work through specs, steering and custom agents.

Official sources

  1. Issues
  2. kirodotdev/Kiro on GitHub
  3. Project website
  4. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/kirodotdev-kiro.svg)](https://hysenlabs.com/projects/kirodotdev-kiro)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/kirodotdev-kiro.svg)](https://hysenlabs.com/projects/kirodotdev-kiro)

Was this useful?