Claude, change the “Add to Cart” button to blue

The behavior is congruent with my experience in abstract, in that all models will regularly do things you didn't ask for, will regularly go "above and beyond" by their training I expect, will regularly make changes that are entirely orthogonal to the change you asked for.

I've worked with Opus and Sonnet daily, and they are pretty great at generating functions and modules and components that have clear boundaries of concern, but I've recently been working some research tasks into our infrastructure and code and it seems impossible to coerce Sonnet into making only specific changes to a document you are working on.

It also blatantly ignores instructions as a rule. "Don't disassemble java class files, just ask me to pull in the source code" worked less than half the time. The Intellij Copilot plugin just doesn't use the AGENTS.md and similar files, and there doesn't seem to be any meaningful activity in the bug reports of same. "Don't modify code unless I tell you to" had bad adherence as well.

It also will read documentation and inform you that it says the opposite. This problem happened to me across models, across model updates, across months of real time. There's a specific example that I will not mention to avoid having it be trained on specifically. A distinct but similar problem is that it will take bad documentation and just pretend it has a good understanding. Claude gave me absurdly wrong descriptions for Splunk alert settings with absolute confidence.

I don't think any agent can reliably figure out "I don't know"

> "Everything is variable reward. Is everything gambling?"

well, no. If you work overtime and get paid overtime, you are not gambling and that is not a variable reward.

Humans engage more with rewards that are intermittent and variable. Like Futurama's scene from 'The Scary Door' where the character says "A casino where I'm winning, I must be in heaven! A casino where I always win, that's boring, I must really be IN HELL!". A constant predictable reward is boring, less engaging. So if you know you get no overtime, but sometimes your boss rewards you with $5 coffee voucher, sometimes a free pizza dinner, sometimes double-time pay for the time worked or a half-day off, now you might be gambling 1hr overtime for an intermittent variable reward.

> "Drive to work, traffic might be good or might be bad."

Good traffic is not a "reward" for driving to work(!) and you have to drive to work regardless so you are not risking anything [you might be risking your life, but you are not making a choice which can reward you with good traffic]. You might say that going a different route is a choice and a gamble which could reward you with good traffic, but traffic engineering does not work that way because if there was a consistently low-traffic route, everyone else would take that route until it was no faster than any other route. Traffic will generally be the predictable and similar every day, plus 'arriving at work early' is not much of a reward.

I wanted to reply this to your other comment but it works here as well.

If I get frustrated by it because it just would not "listen", I discontinue its use!

People do both. Some choices aren't worth the time and effort of detailed analysis and contemplation and some are basically instinctual, but there are plenty of times that choices are carefully considered and well reasoned before being made and acted on.

"Plus rigorously ensuring backwards compatibility for a project that is 2 hours old and has zero users."

That is exactly how the slop accretes and you get a pile of crap. Claude somehow assumes that said 2 hour old userless app is some dusty enterprise app with millions of users and billions of dollars at stake for a 1 second outage.

I have to constantly have these things "take a deep breath, step back and look at the entire thing and do this change holistically. please restate what i'm asking you to do and why it's important"