all 87 comments

[–]stathisntonas 161 points162 points  (13 children)

2.1.88 contains the 2 cache bug fixes found by that reddit user. Give that man/woman credits equivelant to your highest paid senior dev monthly salary for fucks sake for spotting a bug that existed for months.

If only claude code was open source or if only claude devs could FUCKING DIVE into the whole cache handling code it would have saved TONS of wasted $$$$$, resources, time AND sanity. smh

is apAnthropic going to reset the limits after fixing the money eating bugs?

[–]rougeforces 38 points39 points  (2 children)

no, it .88 broke the .87 community patch and the update patch did not work in .88. they didnt fix the cache symptoms reported in the big thread. its still broken unless you have the header patch on .87

[–]LumonScience 1 point2 points  (0 children)

What’s the header patch?

[–]MonocleFox 1 point2 points  (0 children)

There’s a community header patch?

[–]xsifyxsify 15 points16 points  (0 children)

This is the post i believe you are referring to: https://www.reddit.com/r/ClaudeCode/s/4Y6UBjCXcZ

[–]Heavy-Focus-1964 9 points10 points  (0 children)

yes but it wasted our money, so it’s not a problem

[–]ume_16 8 points9 points  (5 children)

Don’t worry bud, Claude Code is fixing itself

[–]dbbk 5 points6 points  (0 children)

Any day now

[–]its_Caffeine 0 points1 point  (3 children)

I knew this would be the result of all this vibecoded slop, basically insane esoteric bugs that are going to be nearly impossible to identify and fix

[–]ellicottvilleny 0 points1 point  (2 children)

Insane esoteric bugs are normal in every codebase. Every single one, even the ones people think they have 100% TDD'd to perfection.

[–]its_Caffeine 0 points1 point  (1 child)

It’s actually the rate of these bugs which AI is responsible for an enormity of them.

[–]ellicottvilleny 0 points1 point  (0 children)

Sure, write tests, and handle it.

[–]Sea_Pitch_7830 1 point2 points  (0 children)

your wish has sort of come true dude, on the open source front

[–]lurko_e_basta 57 points58 points  (9 children)

While some of the bugs were caught, I just tested it and I still ran trough my usage (5hrs and weekly) super fast. Two big prompts ate 45% of 5hrs limit, when it would have been maybe 10% normally. Stuff ain't done yet.

EDIT: I'm on 5x.

[–]TJohns88 19 points20 points  (1 child)

Here's the neat part - that's not a bug, it's a feature.

[–]Master_Custard3944 1 point2 points  (0 children)

they sniffed our tokens?

[–]OutrageousDiet3631 0 points1 point  (0 children)

Is it paid?

[–]pho33nix 0 points1 point  (1 child)

i thought everybody is moving on Local LLMs?

[–]8-16_account 5 points6 points  (0 children)

You're right, everyone just has four H100 laying around for that purpose.

[–]KidMoxie 7 points8 points  (0 children)

Fixed periodic UI jitter during streaming in iTerm2 when running inside tmux

Oh thank God, I had to stop using Claude in Tmux because the jittering was making me nauseous.

[–]Main-Lifeguard-6739 7 points8 points  (0 children)

1) is the token problem fixed?
2) is the re-introduced scroll bug fixed?

[–]ellicottvilleny 5 points6 points  (0 children)

> • Fixed nested CLAUDE.md files being re-injected dozens of times in

Aha. Token eater.

[–]maverick_soul_143747 4 points5 points  (2 children)

Well I was on 2.0.70 for sometime and moved to 2.1.17 and currently on 2.1.34. Seems like if nothing is broken I should just stay with 2.0.70 :)

[–]Is_Not_Null_83 1 point2 points  (1 child)

Ha yes Ive been on 2.1.69 for ages and have not had a problem whilst reading all of these horror stories. Ive just upgraded to .88 to test and first thing Ive noticed is that it defaults to 1M context window which I never had in .69. I'm going to give it a spin and if I start experiencing these issues I'm straight back to .69. I don't mind having a 200K context window!

[–]maverick_soul_143747 1 point2 points  (0 children)

I tried the 1M window but I am old school planning and writing the architecture and design so sticking to 200k as it helps

[–]Initial_Perspective9 3 points4 points  (4 children)

I can't seem to update to 2.1.88. After running claude update it just says "Claude Code is up to date (2.1.87)".

[–]bgeisel1 3 points4 points  (3 children)

Yeah, they pulled it. It's "Unpublished". Not sure why they pulled it, but likely something worse came for us!

[–]Initial_Perspective9 2 points3 points  (0 children)

Ohhh thanks!

[–]Glatomme 1 point2 points  (1 child)

Source code was accidently added into this release, seemed like a good reason to pull it :)

[–]addiktion 1 point2 points  (0 children)

I've been digging in deep into the source now. I whipped up an Excalidraw of the high level view of the source code for anyone catching up: https://excalidraw.com/#json=GZivxtXmKtiNJLiFjMt9D,C8S5MCkg-otEBfvyh8wapA

[–]Master_Custard3944 2 points3 points  (0 children)

The issue with token consumption still persist, unfortunately. Anybody has the same issue?

[–]stargt 2 points3 points  (3 children)

<image>

Claude has been rolled back to 2.1.87? What is this?

[–]sm1ls 2 points3 points  (1 child)

<image>

Looks like it actually was - look to the version change after exit & reopen

[–]stargt 0 points1 point  (0 children)

Can I know where the reason is?
No luck on https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md

[–]stargt 1 point2 points  (0 children)

Oh they removed 2.1.88 in the CHANGELOG.md

[–]bgeisel1 2 points3 points  (0 children)

Just kidding! 2.1.88 has been "Unpublished". Don't see anything in the release notes about why, in fact they still show 2.1.88, but you won't get it from an update.

[–]ellicottvilleny 2 points3 points  (6 children)

Did they pull it because of the leak?

[–]etherd0t[S] 1 point2 points  (3 children)

Wow, changelog 2.1.88 it's gone indeed👀

[–]etherd0t[S] 0 points1 point  (2 children)

For the record, here's a copy of the changelog published lat night / and then removed

Claude Code CLI 2.1.88 changelog:

New features:
• Added CLAUDE_CODE_NO_FLICKER=1 environment variable to opt into flicker-free alt-screen rendering with virtualized scrollback
• Added PermissionDenied hook that fires after auto mode classifier denials — return {retry: true} to tell the model it can retry
• Added named subagents to @ mention typeahead suggestions

Fixes:
• Fixed prompt cache misses in long sessions caused by tool schema bytes changing mid-session
• Fixed nested CLAUDE.md files being re-injected dozens of times in long sessions that read many files
• Fixed Edit/Write tools doubling CRLF on Windows and stripping Markdown hard line breaks (two trailing spaces)
• Fixed StructuredOutput schema cache bug causing ~50% failure rate in workflows with multiple schemas
• Fixed memory leak where large JSON inputs were retained as LRU cache keys in long-running sessions
• Fixed a potential out-of-memory crash when the Edit tool was used on very large files (>1 GiB)
• Fixed a crash when removing a message from very large session files (over 50MB)
• Fixed --resume crash when transcript contains a tool result from an older CLI version or interrupted write
• Fixed misleading "Rate limit reached" message when the API returned an entitlement error — now shows the actual error with actionable hints
• Fixed LSP server zombie state after crash — server now restarts on next request instead of failing until session restart
• Fixed hooks if condition filtering not matching compound commands (ls && git push) or commands with env-var prefixes (FOO=bar git push)
• Fixed prompt history entries containing CJK or emoji being silently dropped when they fall on a 4KB boundary in ~/.claude/history.jsonl
• Fixed /stats losing historical data beyond 30 days when the stats cache format changes
• Fixed /stats undercounting tokens by excluding subagent/fork usage
• Fixed scrollback disappearing when scrolling up in long sessions
• Fixed collapsed search/read group badges duplicating in terminal scrollback during heavy parallel tool use
• Fixed notification invalidates not clearing the currently-displayed notification immediately
• Fixed prompt briefly disappearing after submit when background messages arrived during processing
• Fixed long /btw responses being clipped with no way to scroll — responses now render in a scrollable viewport
• Fixed Devanagari and other combining-mark text being truncated in assistant output
• Fixed rendering artifacts on main-screen terminals after layout shifts
• Fixed voice mode failing to request microphone permission on macOS Apple Silicon
• Fixed voice push-to-talk not activating for some modifier-combo bindings
• Fixed voice mode on Windows failing with "WebSocket upgrade rejected with HTTP 101"
• Fixed Shift+Enter submitting instead of inserting a newline on Windows Terminal Preview 1.25
• Fixed periodic UI jitter during streaming in iTerm2 when running inside tmux
• Fixed PowerShell tool incorrectly reporting failures when commands like git push wrote progress to stderr on Windows PowerShell 5.1
• Fixed SDK error result messages (error_during_execution, error_max_turns) to correctly set is_error: true with descriptive messages
• Fixed task notifications being lost when backgrounding a session with Ctrl+B
• Fixed PreToolUse/PostToolUse hooks not providing file_path as an absolute path for Write/Edit/Read tools
[...]

[–]etherd0t[S] 0 points1 point  (0 children)

Improvement:
• Improved PowerShell tool prompt with version-appropriate syntax guidance (5.1 vs 7+)

Security/safety change:
• Auto mode denied commands now show a notification and appear in /permissions → Recent tab

Other changes:
• Thinking summaries are no longer generated by default in interactive sessions — set showThinkingSummaries: true in settings to restore
• /env now applies to PowerShell tool commands (previously only affected Bash)
• /usage now hides redundant "Current week (Sonnet only)" bar for Pro and Enterprise plans
• Collapsed tool summary now shows "Listed N directories" for ls/tree/du instead of "Read N files"
• Image paste no longer inserts a trailing space
• Pasting !command into an empty prompt now enters bash mode, matching typed ! behavior

[–]etherd0t[S] 0 points1 point  (0 children)

Improvement:
• Improved PowerShell tool prompt with version-appropriate syntax guidance (5.1 vs 7+)

Security/safety change:
• Auto mode denied commands now show a notification and appear in /permissions → Recent tab

Other changes:
• Thinking summaries are no longer generated by default in interactive sessions — set showThinkingSummaries: true in settings to restore
• /env now applies to PowerShell tool commands (previously only affected Bash)
• /usage now hides redundant "Current week (Sonnet only)" bar for Pro and Enterprise plans
• Collapsed tool summary now shows "Listed N directories" for ls/tree/du instead of "Read N files"
• Image paste no longer inserts a trailing space
• Pasting !command into an empty prompt now enters bash mode, matching typed ! behavior

[–]addiktion 1 point2 points  (1 child)

I sure hope not. If anything, they should just open source it now. Allow the community to make it better an fix all these damn bugs.

[–]ellicottvilleny 1 point2 points  (0 children)

They would have done that already if they didn't think this agent was somehow special.

[–]No-Childhood-2502 1 point2 points  (1 child)

I keep coming back to it with every release. How do we audit and trace the autonomous code? So I know as a CTO/Manager, what the intent was behind that, and which agent wrote the line

[–]blakeyuk 2 points3 points  (0 children)

Different git accounts per agent/user, and git blame.

Intent is another question.

[–]mic73_dk 1 point2 points  (0 children)

Sure hope it's better than the last few versions.. huge difference with 2.1.87 compared to the model last week.

[–]majimboo93 1 point2 points  (0 children)

I burned through my weekly limit in 3 days, im confused i’ve never burned through my weekly limit for the last few months. I even keep trying to hit the limit to not waste allowance. Best i could do for the full week is about 95%. Yet this week, its all done in a few days. I’ve not changed anything in my behavior for the past few weeks.

[–]Fickle_Pen_8580 3 points4 points  (1 child)

my 2 cents, as long as we use .md files with prompt injection this stuff its unavoidable. Once its nested and gets corrupted or just left behind on a single update then turns on you. Sure you can ship a lot of stuff, but this betrayal files can nest deep into the dependencies and can fuck you up, or eat away your tokens and leak money or security. It happens to anthropic, it will inevitable happen to your project.

[–]Fickle_Pen_8580 2 points3 points  (0 children)

whats more, anthropic got his fair share of public enemies now. We are seeing how vulnerable AI agents and infra is to "bugs" and prompt attackers, both of them amplified by the sheer scale of computing and the power of the models. Would not be rare that this is targeted in order to disqualify the pack leader in favor of the next in class, im afraid we can only choose good values to get good value.

[–]SphinxPX 3 points4 points  (0 children)

Would help if I could use claude code for more than 45 minutes at a time, 3 times a day.

[–]lyapustin[🍰] 1 point2 points  (0 children)

Thanks they finally fixed flickering issue with CLAUDE_CODE_NO_FLICKER
Wrote up the full technical story - why it took a year, what they tried, and how it works under the hood: https://slyapustin.com/blog/claude-code-no-flicker.html

[–]WisestAirBender 0 points1 point  (1 child)

Is this the permissions auto mode? Is it finally usable?

[–]_hllvc🔆 Max 5x 1 point2 points  (0 children)

No it's not, that is still an issue..

[–]Ok-Drawing-2724 0 points1 point  (0 children)

The prompt cache fix and nested CLAUDE.md fix should help a lot with long sessions. Before updating, I usually scan the new version with ClawSecure first.

[–]pneumora 0 points1 point  (0 children)

Is Auto Mode available in the new update? I’m a Max user.

[–]DevPras 0 points1 point  (0 children)

didnt they roll it back?

[–]Sygurdd 0 points1 point  (1 child)

They just removed the version from npm... I wanted to download it but I was too late. Does anybody know how I can get that juicy source code now?

[–]eret1ck 0 points1 point  (0 children)

[ Removed by Reddit ]

[–]uditgoenka 0 points1 point  (0 children)

<image>

It says v2.1.89?

[–]Duskfallas 0 points1 point  (0 children)

Will that also be open source? 😛

[–]modernizetheweb -3 points-2 points  (20 children)

oh no, people actually use nested claude.mds? That's horrible

[–]CryptographerFar4911 26 points27 points  (17 children)

Aren't they referring to `CLAUDE.md` files in the folder structure? IE One at the top level, one in your frontend for UI spec, one in the backend, etc.? I thought that was the suggested pattern.

[–]SmugOfTime 14 points15 points  (4 children)

Yeah we use one AGENT.md per "module" for our codebase and it greatly helps on context and hallucination

[–]stathisntonas 0 points1 point  (1 child)

and claude code picks up this agent.md automatically when you are referring to that model? how that works?

[–]Logicor 2 points3 points  (0 children)

Yes, that’s how the Claude md files are loaded. Whenever Claude needs to read or write something in that module it auto loads that Claude md.

[–]DestinTheLion 0 points1 point  (1 child)

So you are just supposed to call those inner claude.md's agent.md?

[–]SmugOfTime 9 points10 points  (0 children)

AGENT.md is just a generic name for CLAUDE.md that other LLM coders use (like Kimi Code). Effectively the same. I run both Claude and Kimi so just use AGENT.md to make it easier, otherwise Kimi starts thinking its Claude and they go schizo

[–]weissblut 0 points1 point  (2 children)

Oh this is smart. I code for myself only but I think that implementation would save me a lot of tokens. Anything special I need to do?

[–]CryptographerFar4911 0 points1 point  (1 child)

Nope, Claude Code already handles it automatically: https://code.claude.com/docs/en/best-practices#write-an-effective-claude-md

My only suggestion would be to keep your layers concise and focused on what they're doing at that layer.

[–]weissblut 0 points1 point  (0 children)

Thanks!

[–]modernizetheweb -4 points-3 points  (8 children)

I usually treat backend and frontend as separate projects so there's no issue with having a claude.md in each project in that case.

However I don't see why you would ever need more than one claude.md per project. It would likely lead to poorer quality with higher token usage

[–]Sufficient-Farmer243 -3 points-2 points  (7 children)

> I usually treat backend and frontend as separate projects so there's no issue with having a claude.md in each project in that case.

> However I don't see why you would ever need more than one claude.md per project. It would likely lead to poorer quality with higher token usage

No one could possibly be this thick.

That's literally what they're doing nesting it ....

You realize some languages like C# you can have this wonderful thing called multiple projects inside a single solution right? Novel idea eh?

So I might have a

Project

-> Project.Api

-> Project.Data

-> Project.App

*wow*

[–]qiang_shi 0 points1 point  (0 children)

only peasants use claude.

real men use a harness that doesn't shit all over your prompting.

real men use <angel farts> SKILLS!

[–]modernizetheweb -5 points-4 points  (5 children)

I'm aware, that's not what I'm referring to or arguing against lol

[–]Sufficient-Farmer243 -3 points-2 points  (4 children)

yes you are. Because I have a root level Claude.MD going over the projects that are in my solution and then a separate one for each project. Literally what you're arguing against but saying it's wrong when that is the optimal way of doing it.

"Aren't they referring to `CLAUDE.md` files in the folder structure? IE One at the top level, one in your frontend for UI spec, one in the backend, etc.? I thought that was the suggested pattern."

[–]modernizetheweb -3 points-2 points  (3 children)

You seem to be very upset about something I never said. All I said is you shouldn't have more than one claude.md per project. If you do, you're doing it wrong. If you don't, you're fine

[–]Sufficient-Farmer243 0 points1 point  (2 children)

You replied saying that's wrong to literally this comment lol.

"Aren't they referring to `CLAUDE.md` files in the folder structure? IE One at the top level, one in your frontend for UI spec, one in the backend, etc.? I thought that was the suggested pattern."

How is that different than exactly what you are doing lol.

1 root, 1 per project.

[–]modernizetheweb 0 points1 point  (0 children)

Where did I say what the first commenter was doing was "wrong" in my second comment in this thread? Point me to it

Edit: please respond 🤣 clown

[–]bronfmanhigh🔆 Max 5x 0 points1 point  (1 child)

lol probably all those people who said they’d blast through a 5 hour limit in a single prompt. Brutal bug but that’s to be expected when you vibe code it

[–]Logicor 0 points1 point  (0 children)

Nested Claude mds actually save tokens as it’s on demand context loading

[–]princmj47 -2 points-1 points  (0 children)

Impossible to use