Earlier quoted context omitted.
[flagged]
[flagged]
[flagged]
Kiro: A new agentic IDE
321–330 of 498 posts
Re: Kiro: A new agentic IDE
#322So I'm glad there are more agentic dev tools coming out, but can we please stop making entirely new IDEs and start integrating as plugins to well-established (and some already paid for) IDEs we already use? Webstorm/other Jetbrains, VS Code, etc. It is a huge hassle to match my existing settings, which I've spent countless hours tweaking over the years, with a new editor that can't import them. :(
Shameless plug but our co is building a AI plugin for JetBrains that has next edit autocomplete + a strong coding agent (sweep dev)
Isn't that competing directly with JetBrains themselves?
Re: Kiro: A new agentic IDE
#323Why does it feel like all tech companies are the same these days? It wasn’t always like this right?
It's a new category of tool and they're all competing for it
Re: Kiro: A new agentic IDE
#324> 2. Technical design based on requirements > Kiro then generates a design document by analyzing your codebase and approved spec requirements. It creates data flow diagrams, TypeScript interfaces, database schemas, and API endpoints—like the Review interfaces for our review system. This eliminates the lengthy back-and-forth on requirements clarity that typically slows development. This is nice for documentation but r…
Kiro takes the requirements and the existing code to create a spec.
Otherwise the spec may cover requirements that are already met in the existing code and needs to understand integration points it needs to include in the spec.
Having used Kiro myself I think it does what you expect.
Re: Kiro: A new agentic IDE
#325Hello 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 pr…
Does it work for Swift development and can it compile to test for compilation errors?
Re: Kiro: A new agentic IDE
#326Really impressed with what Amazon is doing with Kiro. The emphasis on "spec-driven development" to get beyond "vibe coding" and into production-ready software is a crucial step.
Re: Kiro: A new agentic IDE
#327Earlier quoted context omitted.
> I get paid a fuck load of money to write C. Your point is? My point is there aren't many of you, are there? All things considered, keeping up with the industry trends is generally a more reliable career path.
Correct but we are never fungible. That’s the trick for a reliable career. I’ve survived every single layoff season since 1995.
Ironically, Claude Code has me working in lower-level languages with more low-level tools than ever before, simply because of how powerful it is, particularly as a terminal tool. I've always been more of a GUI person, but now the editor I use most often is Helix.
If I've atrophied in certain aspects of my thinking, I honestly think I've more than made up for it in learning how to engineer the context and requirements for Claude Code more effectively and to quickly dive in to fix things without taking my hands off the keyboard and leaving the terminal.
Re: Kiro: A new agentic IDE
#328Earlier quoted context omitted.
I don't know if this is feedback for Kiro per se or more feedback for this category of applications as a whole, but I've personally noticed that the biggest barrier holding me back from giving an earnest look at new coding agents are the custom rules I've set up w/ my existing agents. I have extensively used Copilot, Continue, Cursor, Cline, Aider, Roo Code, and Claude Code. I've just finished porting my rules over t…
Agents.md is at least used by both codex and GitHub copilot. VSCode has its own thing for instruction files and Claude.md is also its own thing :(
and opencode
Re: Kiro: A new agentic IDE
#329Earlier quoted context omitted.
Actually yes! I saw this post some months ago, and thought to myself: "Wow this is really close to what we've been building". Kiro uses three files though: requirements, design, and then tasks. The requirements doc is a bunch of statements that define all the edge cases you might not have originally thought of. Design looks at what is currently in the code, how the code implementation differs from the requirements, a…
That's a compelling three file format. Have you considered a fourth file for Implemented such that Spec = Implemented + Design? It would serve both as a check that nothing is missing from Design, and can also be an index for where to find things in the code, what architecture / patterns exist that should be reused where possible. And what about coding standards / style guide? Where does that go?
That is interesting. So far we are just using the task list to keep track of the list of implemented tasks. In the long run I expect there will be an even more rigorous mapping between the actual requirements and the specific lines of code that implement the requirements. So there might be a fourth file one day!
Coding standards / style guide are both part of the "steering" files: https://kiro.dev/docs/steering/index
Re: Kiro: A new agentic IDE
#330My 2c-TLDR; after doing some battle testing over the few weeks (so keep in mind some of this was on pre-release versions):
The good: It's great to see they've baked in the concept of setup -> plan -> act into the tool with the use of specs If you're someone who currently only has Copilot / Q dev, this is a good step in the right direction - if you don't mind changing your IDE. I love that it has a command / task queuing system. Hooks = good.
Goes either way: Even though it uses Q under the bonnet, it does seem somewhat better than Q although I think most of that is down to the use of plan -> act workflows
The not good: There's no reason at all for it to be a VSCode fork and running multiple IDEs for every vendor that wants me to use their products is a PITA. It seems to massively over-complicate solutions, for things that could be quite simple even if the tasks are well defined it likes to create many files and go down very extensive and complex implementation patterns. This has to be something to do with the app itself as Sonnet 4 does not do this with Cline/Roo Code so hopefully it can be fixed (but maybe it suits the kind of folks that write big java apps!). It doesn't seem to have any integrated web browser capabilities to allow the model to run up and explore the app while inspecting the js console browser side like Cline / Roo have. My installation has mysteriously become 'corrupted' and needed reinstalling several times. There's no global rules, you have to keep a note of them somewhere and copy paste them into each project. GH Issue #25
The bad: It's slower than Cline / Roo Code, it just takes a lot longer to get things done. It's very easy to hit the rate limits and be blocked for an undefined amount of time before you can continue working. There's lots of MCP bugs mainly relating to it still not supporting the standard streamableHTTP or SSE modes and breaks all MCPs without any warning or logs if you try to add one. GH Issue #23 The version of VSCode it's built from is quite out of date already, which rings alarm bells for how well such a large, complex application will be maintained and rolled out at speed over time.