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.