Select Language:
If you’re wondering where to send feedback, feel free to ask me. I want to share my experience with the Kiro CLI and a few suggestions on how it could improve.
I’ve been using the Kiro CLI for a while now. Before that, I frequently used Claude Code and OpenCode. My goal isn’t to criticize Kiro, as it’s not a bad tool. However, I’ve noticed it lags quite a bit behind OpenCode, especially in terms of features and user experience. It’s really commendable that Kiro supports custom agents and agent skills, which are essential and very useful. Yet, there are a couple of key areas where OpenCode and Claude Code excel that I believe could enhance Kiro CLI:
First, supporting custom commands would make Kiro more flexible and better suited for different workflows. Second, the overall user and developer experience could be improved significantly.
Some examples of features that improve usability include partial or fuzzy matching when tagging resources, queuing messages while the agent is “thinking,” and having a command window accessible with ctrl+p. These small but impactful features make a big difference in how smooth and efficient the experience feels.
OpenCode offers a level of user and developer experience that feels much more intuitive and fluid. If Kiro CLI took some inspiration from OpenCode’s design and features, it could reach a whole new level.
Plus, an even better solution would be for Amazon to contribute directly to OpenCode, adding support for Amazon Q Pro subscriptions. This way, there wouldn’t be a need to build everything from scratch. Improving Kiro by leveraging existing tools like OpenCode could save time and bring a more polished, user-friendly experience to everyone.





