←back to thread

1013 points QuinnyPig | 1 comments | | HN request time: 0.001s | source
Show context
NathanKP ◴[] No.44561071[source]
Hello folks! I've been working on Kiro for nearly a year now. Happy to chat about some of the things that make it unique in the IDE space. We've added a few powerful things that I think make it a bit different from other similar AI editors.

In specific, I'm really proud of "spec driven development", which is based on the internal processes that software development teams at Amazon use to build very large technical projects. Kiro can take your basic "vibe coding" prompt, and expand it into deep technical requirements, a design document (with diagrams), and a task list to break down large projects into smaller, more realistic chunks of work.

I've had a ton of fun not just working on Kiro, but also coding with Kiro. I've also published a sample project I built while working on Kiro. It's a fairly extensive codebase for an infinite crafting game, almost 95% AI coded, thanks to the power of Kiro: https://github.com/kirodotdev/spirit-of-kiro

replies(27): >>44561401 #>>44561480 #>>44561505 #>>44561508 #>>44561540 #>>44561643 #>>44562248 #>>44562738 #>>44562815 #>>44562867 #>>44562880 #>>44563346 #>>44563915 #>>44563941 #>>44563988 #>>44563992 #>>44564153 #>>44564270 #>>44564551 #>>44565359 #>>44565453 #>>44565634 #>>44565909 #>>44566659 #>>44567132 #>>44568049 #>>44570644 #
ActorNightly ◴[] No.44562880[source]
While I like the product, implementation could be better. Kiro is sitting idle with Helper Plugin using a shitload of CPU for no reason.
replies(2): >>44562994 #>>44563028 #
NathanKP ◴[] No.44563028[source]
A few things:

1) It's normal for Kiro (and almost every AI editor) to use a lot more CPU when you first start it up, because it is indexing your codebase in the background, for faster and more accurate results when you prompt. That indexing should complete at some point

2) On initial setup of Kiro it will import and install your plugins from VS Code. If you have a large number of plugins this continues in the background, and can be quite CPU heavy as it extracts and runs the installs for each plugin. This is a one time performance hit though.

3) If your computer is truly idle, most modern CPU's get throttled back to save power. When the CPU is throttled, even a tiny amount of CPU utilization can show up as a large percentage of the CPU, but that's just because the CPU has been throttled back to a very slow clock speed.

In my setup (minimal plugins, medium sized codebase, computer set to never idle the processor clock) I rarely see Kiro helper go above .4% CPU utilization, so if you are seeing high CPU it is likely for one of the above reasons.

replies(1): >>44563252 #
ActorNightly ◴[] No.44563252[source]
Thanks for the reply. It was the indexing.

Is there any way to control this? I have my files.watcherExclude setting, does it respect that?

replies(1): >>44563303 #
NathanKP ◴[] No.44563303[source]
I believe that the file indexing exclusion is based on .gitignore, not files.watcherExclude, but let me check on that and confirm.
replies(1): >>44563432 #
ActorNightly ◴[] No.44563432[source]
I tried with a small project, it worked fine, no high CPU usage.

However with a large project, it seems that it indexed, then dropped CPU, then I started opening up files and working with them, then the CPU spiked again.

replies(1): >>44563643 #
NathanKP ◴[] No.44563643[source]
I'll look into this. Kiro is supposed to be doing progressive reindexing. When you make a change it should only have to reindex the files that changed. If you have any logs or other data you are willing to share, to help the team investigate you can use the "report a bug / suggest an idea" link at the bottom, or open an issue at: https://github.com/kirodotdev/Kiro/issues
replies(1): >>44574458 #
1. ActorNightly ◴[] No.44574458[source]
I ironically don't have a github account (use my own personal gittea). However I don't think its the indexing. I left Kiro open for a day, and CPU usage is still high.