[_kidlike]

they all suck, because at the end of the day, these tools are just automating multiple prompts to one of the same codegen LLMs that everyone is using already.

The loop is: it identifies which files need to change, creates an action plan, then proceeds with a prompt per file for codegen.

In my experience, the parts up to the codegen are how these tools differ, with Junie being insanely good at identifying which parts of a codebase need change (at least for Java, on a ~250k loc project that I tried it on).

But the actual codegen part is as horrible as when you do it yourself.

Of course I'm not talking about hello world usages of codegen.

I suppose these tools would allow moving the goalpost a bit further down the line for small "from scratch" ideas, compared to not using them.