←back to thread

Kiro: A new agentic IDE

(kiro.dev)
1015 points QuinnyPig | 1 comments | 14 Jul 25 14:24 UTC | HN request time: 2.056s | source
Show context
suralind ◴[14 Jul 25 15:39 UTC] No.44561441[source]▶
Here my problem with this: I don't want to be jumping an editor/IDE every 6 months, learning new key bindings and even more importantly, getting used to a completely new look.

In a space that moves as quickly as "AI" does, it is inevitable that a better and cheaper solution will pop up at some point. We kinda already see it with Cursor and Windsurf. I guess Claude Code is all the rage now and I personally think CLI/TUI is the way to go for anyone that has a similar view.

That said, I'm sure there's a very big user base (probably bigger than terminal group) that will enjoy using this and other GUI apps.

replies(17): >>44561462 #>>44561479 #>>44561494 #>>44561503 #>>44561512 #>>44561592 #>>44561678 #>>44561889 #>>44562034 #>>44562091 #>>44563075 #>>44563576 #>>44564212 #>>44566667 #>>44569070 #>>44569580 #>>44569595 #
TimMeade ◴[14 Jul 25 15:43 UTC] No.44561503[source]▶
Every 6 months? It's turning into every two weeks. Sticking with claude code. Its working beautifully for us.
replies(2): >>44561522 #>>44561949 #
MuffinFlavored ◴[14 Jul 25 15:45 UTC] No.44561522[source]▶
I have a question. I do not like the concept of "agent mode" for AI. I'm a control freak and I want to control every line that gets committed because I am responsible for it and need to understand/visualize/memorize every part of codebases I work on.

Is Claude Code good for the "ask" flow? No, right?

The old flow before agent mode got added. Select some code, ask questions about it or give an instruction on editing it and then choose to accept the change.

As I understand (I could be wrong), with agent mode, it edits the file for you, no way for you to accept before it does, so you have to manually check the diff, roll back parts you don't want, etc.

Am I right?

replies(6): >>44561579 #>>44561587 #>>44561648 #>>44561661 #>>44561726 #>>44563237 #
1. cmrdporcupine ◴[14 Jul 25 15:55 UTC] No.44561648[source]▶
It could be better. I think the PMs and investors and decision makers at these companies are running with a "we want to replace / automate developers" philosophy, while these tools are actually best at augmenting developers. And so they're sorta builing with this "I'll do everything and ask you for confirmation" (and basically encourage you to give me blanket permission).

In reality these tools would be best if they took a more socratic method, a more interactive pair programming approach. So instead of giving you a blanket diff to accept or refuse or "No, and here's some changes" -- it should be more dialog oriented.

Of all of them so far though, I think Claude Code is closest to this. IF you prompt it right you can have a much more interactive workflow, and I find that most productive.