Brought to you by Jellypod AI, if you were coding with Claude Code around August
eighteen, twenty twenty six, you might have noticed version two point one point two
three five dropping a fix for a massive hidden token sink.
It, it, it turns out that whenever your Language Server Protocol or LSP reconnected
mid session, your whole prompt cache was getting completely wiped.
Wait, the whole prompt cache?
So if your language server just blinks or restarts in the background,
it invalidates hundreds of thousands of context tokens?
Whole thing, mate!
Total cache invalidation.
Because the prompt cache relies on keeping that long context prefix static on
Anthropic servers, any tiny break from the LSP triggered a full cache rebuild.
That meant Claude Code had to reindex and resend two hundred thousand plus tokens
back over the wire.
Wow, that explains those sudden multi second lag spikes during long sessions.
You think the model is taking forever to answer, but in reality,
you are paying to resend your entire codebase history and waiting for it to process
from scratch!
Spot on!
You get hit with massive latency, plus a surprise jump on your API bill.
But version two point one point two three five stops those mid session LSP
reconnects from blowing away the cache key, so your sessions stay fast and cheap.
That is a massive win.
What else landed in two point one point two three five?
I saw something about terminal spellcheck?
Yeah!
They added an optional spellcheck setting in slash config.
As you type your prompt in the terminal UI, it underlines misspelled words in real
time.
And, uh, it does it by leveraging your local system tools, whether you have aspell,
hunspell, or ispell installed.
Oh, I love that!
Using local binaries like aspell means zero extra latency or API calls just to catch
typos before sending a prompt.
What about performance for local tools like grep?
Ah, totally!
The embedded grep in native macOS and Linux builds got a big improvement.
If you accidentally throw a pathological regex pattern at it,
grep now fails fast instead of exhausting system memory and freezing your terminal.
That is huge.
No more killing the process because a runaway search locked up your machine!
Did they touch background tasks like slash ultrareview or slash autofix pr as well?
They did!
Background cloud sessions like ultrareview and autofix pr got a massive CPU and
memory optimization.
Previously, every single update was rescanning and rerendering the entire event
stream from scratch.
Now it handles background streams way smarter, so your local CPU stays nice and
cool.
My laptop fans are crying tears of joy right now.
Any other quality of life tweaks or caveats we should know about?
A couple of small but sweet ones!
If an Agent tool call omits subagent type in a session where that subagent isn't
available, it now throws an explicit error listing all valid available agents
instead of advertising a general purpose default.
And inside permission prompts, pressing Shift Tab in the comment field won't
accidentally approve the edit and grant session wide edit permissions anymore.
It just closes the comment box like it should.
Man, accidentally approving a session wide permission because you tried to tab out
of a text field is terrifying!
Glad that one is patched.
Good updates all around.