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/T…
Kiro: A new agentic IDE
71–80 of 498 posts
Re: Kiro: A new agentic IDE
#72Re: Kiro: A new agentic IDE
#73Re: Kiro: A new agentic IDE
#74Re: Kiro: A new agentic IDE
#75I am a heavy Jetbrains user, I never liked the idea of Cursor. I embraced Claude Code immediately when it came out.
Re: Kiro: A new agentic IDE
#76Here 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/T…
Every 6 months? It's turning into every two weeks. Sticking with claude code. Its working beautifully for us.
I think it is entirely possible to build a fantastic CLI tool for coding, and the CLI tools for coding already work well enough, but there is just more context info available inside of an IDE, therefore the ceiling is higher when working with an agent that runs inside of the IDE. Context is king for LLM results, and IDE's just have more context.
Over time I'm sure we'll see tools like Claude Code support everything that an IDE can do, but for now if you want to reach the same ceiling you still have to glue together a very custom setup with MCP tool use, and that has the downside of introducing additional tool use latency, compared to an IDE that is able to source context directly from the IDE's internal API, and provide that to the LLM nearly instantly.
Re: Kiro: A new agentic IDE
#77With my experience with Amazon Q in the AWS console (100% useless, worse than a Google search), I can only assume that this Kiro product will suck and not be a market leader. As a customer I have no incentive to try it. I think that reputation is 100% Amazon’s fault. When all you do is ship half-baked rushed products your customers will assume your next big thing sucks because that’s the reputation you built for your…
Re: Kiro: A new agentic IDE
#78Earlier quoted context omitted.
Hello! What is the connection with AWS? Do you work for AWS? Is this going to be some official AWS product, backed by Amazon Q or Bedrock?
Kiro is created by an AWS team, and originates from AWS expertise. We are using Kiro internally as one of our recommended tools for development within AWS (and Amazon). So Kiro is an official AWS product, however, we are also keeping it slightly separated from the rest of core AWS. For example, you can use Kiro without having any AWS account at all. Kiro has social login through Google and GitHub. Basically, Kiro is…
Re: Kiro: A new agentic IDE
#79Earlier quoted context omitted.
Unfortunately aider is showing its age. It is great for what it does, but better LLMs + "agentic" have shown that you can get more in the swe domain. There was a paper recently where they had an LLM evolve tool harnesses and got ~20% more than w/ aider on the benchmark they used, so it's pretty clear that the models + tools (+better harness) are better than just aider.
1) You can plug in any model into aider 2) It can be quite agentic > evolve tool harnesses Claude code & Gemini cli etc. don't do this either
As for 1), I agree but you force the model to work within aider's constraints. Claude4 for example excels at the agentic flow and it's better at that than providing the diffs that aider expects.
As for the last sentence, I disagree. They are evolving the stack, and more importantly they are evolving both at the same time, stack + LLM. That's the main reason they all subsidise use atm, they are gathering data to improve both. If I were to place a bet right now, I'd say that provider_tool + provider_LLM > 3rd party tool + same model in the short, medium and long term.