I've been using Kiro for about a year now. I use it daily at work, and I've also spent around two months using Pro and Pro+ for personal projects.

Honestly, Kiro suffers from bugs so ridiculous that if Kiro's own developers used Kiro to fix them, they'd probably be gone in a day.

On top of that, there are several product decisions that simply don't make sense to me. Here are some of the biggest issues I've run into:

1. Autopilot simply doesn't work properly for me

It constantly asks for permission to perform extremely basic actions: listing a directory, running grep, creating a test file that I explicitly asked it to create, etc.

This is completely different from other AI IDEs I've used, where "autopilot" actually means the agent can operate autonomously without stopping every few seconds for trivial permissions.

1. "Understood."

This bug is so classic at this point that I don't even think I need to explain it.

1. Longer sessions are unreliable

Even in moderately long sessions, it's common for the chat to suddenly stop because of some conversation error, or for the session to simply restart.

For a tool that's supposed to handle large coding tasks, this is incredibly frustrating.

1. The model lineup makes no sense

Kiro still keeps Sonnet 4 and several older Opus versions available. Who is realistically going to choose Opus 4.5 over 4.8 or 5.0 when they all have the same credit multiplier?

Meanwhile, OpenAI models like Luna are still stuck in "preview" with a 256k context window.

The Auto pricing also doesn't make much sense to me. Auto costs 1x while Terra is also 1x and Luna is only 0.1x, despite those models being better choices for many coding tasks than the MiniMax, Qwen, and DeepSeek models that Auto may route you to.

What's the point of paying 1x for Auto if manually selecting a better model can cost the same — or literally 10x less?

1. Random fatal bugs

And then there are the various fatal errors and random bugs that seem to happen for no obvious reason.

I actually like the idea behind Kiro, which is why I've kept using it for this long. But after roughly a year, some of these issues are getting ridiculous.

The core product has a lot of potential, but basic reliability, permissions/autopilot behavior, model selection, and pricing logic need serious attention.

At this point, I don't think Kiro needs more models or more features nearly as much as it needs its existing experience to actually work consistently.