alt Hacker NewsBased on my experience with these tools so far, this seems exactly the kind of subtle but extremely severe bug that sneaks in when you start piling up layers of AI generated patches to a codebase without caring too much about the code.
Replies
Yep, especially with long contexts (and moreso if the last thing you were working on in the same context involved telemetry too). AI sneaks in weird conditions like this and then does the entire "You're absolutely right" thing if you're paying enough attention to catch it.
I used to actively use Msty for local models because it just worked and had a lot of nice advanced features. A few months ago they released their beta version of a Claw-like UI and mentioned using a version of it to develop Msty itself. Well, that was around the time I stopped using Msty because every update started breaking things and two updates in a row included bugs which wiped all my configs, chats, and history.
It seems to be exactly the opposite, a "fully human error":
https://news.ycombinator.com/item?id=49815363
Nothing to do with AI patches at all, nor was it a bug. It was intentional human behavior, a temporary rollout setting, that seems to have made sense.
But I guess that doesn't fit the "narrative".
Except that, and this I find slightly amusing, is a situation where they definitely don't want to publicly blame the ai model when there are mistakes.
"extremely severe" - aren't we laying it on a bit thick here? The whole impact seems to be that users who have telemetry turned off got this feature ~2 days later, when the bug was noticed.