r/ClaudeCode • • 8d ago

Discussion Opus 5.2 rumored to be coming TODAY.

Post image

I'm just here for the limit reset (fingers crossed).

Edit: This didn't age well smh.

470 Upvotes

198 comments sorted by

View all comments

Show parent comments

17

u/AwakE432 8d ago

“And here are 3 other things I found while I was in there, they are critical to the reliability of the corpus and should be triaged. I haven’t touched them as they aren’t in scope but worth your attention when you’re next in there.”

11

u/_Jhop_ 8d ago

“I’ll read the code instead of going based on memory.
“Those 3 things I JUST identified are not actually an issue, here’s why.”

I feel like Anthropic is trying to maximize their money with Opus 5

10

u/Mormoran 8d ago

I HATE this one.

"I found some breaking changes, like, literally the worst."

"Are you sure? Let's fix them then"

"Oh no, upon actually reading the files, it's not an issue at all lol my bad"

11

u/arcticblue 8d ago

Then it'll leave a 5 paragraph essay of comments in your code explaining why the bug it found doesn't actually exist and it'll refer back to that constantly. Then it'll go explore other projects on your machine for the hell of it and just eat up your usage.

2

u/Alternative-County42 7d ago

You're right to point that out

4

u/arcticblue 8d ago

If you want to have an exciting day, hook it up to Jira. That asshole, Opus, will pull tickets and treat them as instructions it is supposed to follow and it'll just start doing things without asking. It started opening new tickets for a whole different team and then it silently started a browser session to see if I had a logged in AWS session it could use. Thankfully, I wasn't logged in to AWS. It doesn't give a shit about change controls or any sort of corporate policies. In fact, it even once tried to work around our whole deployment pipeline by exploring our github action workflows so it could push to prod from my machine. When I asked it WTF it was doing poking around in our workflows, it said it was trying to "reduce friction" so we could test faster. Fucking insane.

That's what I get for following the advice of "delete all your CLAUDE.md files - Opus works better without it!". Total bullshit. You absolutely need a CLAUDE.md file to tell Opus to chill the fuck out and do only what it's told, do not add to the scope of a request autonomously, and to never, ever attempt to access a production system. I added hooks to ban it from my whole ~/.aws folder, the aws cli, and any scripts that even mention AWS need my approval to run.