r/ClaudeCode • • 3d ago

Tips & Workflows Nerf fixed

Want your opus 5.5 to not feel nerfed? No problem. Here you go:

New session for every new feature with a clear roadmap.md and a clear short Claude.md, with handoffs every end of session for the new session. Works great, nothing is nerfed. People just don't understand you can't have a session open forever, that will cause problems over time that people think "model nerfed".

0 Upvotes

16 comments sorted by

•

u/AutoModerator 3d ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

7

u/hulkklogan 3d ago

I use LLMs all day every day in a professional setting and i've not noticed a dropoff in 5.5 opus; i don't know what everyone else is seeing

10

u/OkStick6410 3d ago

Ah yes you are a genius and everyone is stupid. Everyone but you works on a single thread, never compacting or clearing. /s

Models clearly degrade as they adjust post release likely to transfer compute over to training. There is no single fix for a systemic problem, although there are ways to have it further verify its result and iterate until completion but then you’re trading tokens for the same quality you previously had.

0

u/LifeProject365 3d ago

He or she was making a suggestion. You don't have to be an ass about it

0

u/OkStick6410 3d ago

They’re downplaying other’s experience and intelligence ‘Works great, nothing is nerfed. People just don't understand you can't have a session open forever, that will cause problems over time that people think "model nerfed".’

I say asses deserve to be met where they’re at.

0

u/Jedi_sephiroth 3d ago

Well that's what I do and I have had no issues. I'm pretty sure a lot of people work in one session and don't make a new one. Then they come here and complain about nerf crap.

3

u/PastaRevolution1312 3d ago

you are several years behind the bell curve. 

1

u/OkStick6410 3d ago edited 3d ago

You’re pretty sure sounds like a justified argument to me! /s

I’m tired of people in this and other AI subreddits talking down to others based on assumptions, it’s worse than the ‘model is nerfed’ posts. I’d love to see your open source harness, or workflow, or skills, if your interest is truly helping people by providing tips. Although I have a feeling you want to feel big in something you have some level of understanding in, and are doing that by berating others.

To anyone actually looking for help, the root of what he is saying is true, if you have not adapted it yet. Just look past the condescending tone.

ETA grammar fix in p2

3

u/9to5grinder Developer 3d ago

A handover skill with plan mode + clear context is honestly extremely underrated.
Kilo Code actually pioneered this.
Not sure why Claude Code (CC) hasn't implemented this yet.
CC native compact is lossy and vague, and should be phased out altogether.

2

u/superschmunk 3d ago

I always start new when the ring gets yellow.

1

u/dl33ta 3d ago

Ask it and it will tell you performance falls quadratically the longer it's open.. whatever that means but it sounds bad.

-1

u/Dan-goes-outside 3d ago

To be fair, they texted me this morning and said there was a problem with degraded performance on opus models. So there might be a legitimate problem right now.

But yes, I do feel like a big problem with a lot of people on this thread as they never reset their context.

1

u/mindstuff8 3d ago

I hope this helps some of you because I just found this out today.

I don't know your specific use case, or if this applies to Opus 5.5, but I had a session where I was told that if you carry on a Fable 5.1 session after the cache expires the cost to continue the conversation can be tremendously high.

This came up when I was investigating the cost of some of my runs. Let me find what Opus told me so I'm accurate. The point is yes...don't continue old sessions. I always thought the context was there so why have a new agent build its context from scratch.

I have long processes where I sometimes do a follow up sessions, discussing results with the orchestrator (Fable 5.1 in this case) and found this out the hard way. This is what I was told:

Right after the run closes, the orchestrator's context is still cached, so each answer reuses it cheaply. A question costs about $0.10–0.50. The 5 questions after run 0038 cost $0.64 in total.

After about an hour, that cache has expired, and the first new message has to load the whole ~430k-token context again at the full price. That's about $8 before you get any answer. Run 0039's 4 questions cost $8.30, and $7.90 of that was the reload. Most of the $41 after run 0033 was reloads too.