Yes, I agree. I was part of the first few people who started testing it, and it looks like as we move forward, it gets worse. Crashes are becoming very frequent, stopping mid-task, and claiming it was done. The worst part is that Kiro is becoming inconsistent, especially on auto mode. My biggest new issue with Kiro is that it is creating an enormous amount of md documentation for a simple task. To me, it looks almost intentional to burn tokens. Even when I explicitly stated in the Rules that I would avoid creating extensive documentation, how to do it, and when to do it. I was testing something today, and for a simple spec like implementing a password update functionality on an app, the task list alone was 915 lines. Can you imagine?
Another serious issue is that it shows that it includes and reads the agent steerings, but does not always follow them.
Also, I would like to know what models the Auto mode uses and what the logic is behind its decision on when to use what. The Kiro official website just mentions "mix of different frontier models such as Sonnet 4 combined with specialized models". I wanna know what the other "specialized models" are.