That still only just makes it a force multiplier for engineers, like any other tech, not a replacement as it's being hyped and sold as.
Claude resorting to writing code for everything, because that's all the model can do without too many hallucinations and context poisoning, is just a higher speed REPL. Great, that's useful.
But that's not what is being hyped and sold. What's being hyped and sold is "You don't need an Ops guy anymore, just talk to the computer." Well, what happens when the AI decides the "fix" is to just open up 0.0.0.0/0 to the world to make the errors go away? The non technical minimum wage person now just talking to the computer has no idea they just pwned the company.
If AI's answer is "Just write a script to solve the prompt" then you still need technical people, and it's vasly over hyped.
I'll be interested when you actually can just dump logs in a chat and analyze it without the model having to resort to writing code to solve the problem. That will be revolutionary. Imagine all the time I'd save by not having to make business reports, I can just tell the business people to point AI at terabytes of CSV exports and just ask it questions. That is when it will stop just being labor compression for existing engineers, and start being a world changing paradigm shift.
For now, it's just yet another tool in my toolbelt.
Not sure why the implementation is important or not. The point is the system will be triggered by some text input and complete the task asynchronously on its own.