That's not what the grandparent poster was saying, but sure. They have been steadily improving across those metrics, as Opus 4.6 / 4.7 / Mythos demonstrate. They're certainly not perfect, and I understand your fatigue (it is certainly fatiguing to follow, even if interested!), but each new release pushes it that bit further, and the improvements percolate downwards to the cheaper models.

right on. I certainly empathize with your frustrations about "AGI". but rest assurred, I'm firmly in the camp of "not in my lifetime" and even further in the camp of "not without at least 3 more massive breakthroughs about things we currently do not understand at all". so sorry if it sounded like I was asking "what about when local llms get SUPER GOOD", or something. that's not at all what I meant. All I was asking was - "Claude Code can currently be pointed to a directory and then be chatted with about what it needs to do in that directory to make a full code project. That ability is already available on local machines through a ton of convoluted setup, but it's almost certainly going to be a packaged solution within a year (and possibly within the next few months/weeks/days). So when that packaged solution arrives and the choices are 'use the llm for scaffolding which takes 3 hours of unattended time' or 'build the scaffolding myself which takes 6 hours of deep focus time', what will still be objectionable about choosing the former?"

and, to be clear, it's an earnest question. like I've said elsewhere, I have concerns about over-reliance on the tech, but once it all moves local, a lot of those concerns become much more trivial. so I'm curious if other people have concerns that remain pressing and practical.

ETA: I'm aware that Claude wouldn't take 3 hours to do this, while using its massive warehouses of GPUS. I'm estimating what I think is a reasonable time for a single-gpu device to produce something workable.