There is also a lot of other work that it can do really well.
I was asked to create a little one page process flow chart for some stuff my team maintains. We had all the documentation for everything as handfuls of markdown files in each code repository. The thing is not complex. I could have opened Visio and created a nice looking chart in probably 1/2 an hour to an hour.
Instead I told Claude to do it. It was done in seconds, took be me about five min to look it over and conclude there were no major errors, incorrect over simplifications, or serious omissions. Another few min to propose some minor edits and then it was done.
Now we have nice executive level one pager to quickly explain to anyone business side roughly how the system works, rather than a collection of technical documents i have sit in a meeting with them and go over. No it can't do everything. Yes there are serious problems when it comes to authoring code etc that will quickly become serious problems with any project where the person doing the vibe code does not have real experience and understanding as far as software development.
That does not mean this stuff isn't really useful and valuable. My advice to the people screaming claude/codex/etc are not good tools is rethink that or you're going to get left behind by someone who probably isn't half as skilled as you are but isn't refusing to use tools that make the job better. You're that guy inserting assert()s and printf()s into code every other line and doing 25 build-run-test turns while the rest of your team has moved on to an debugger and and IDE that will let them step thru. Seriously that is who you are right now.