So, I was working in my shed last night, trying to tune up my old postie bike,
right?
And I- I- I kept thinking, man, if only I could just, like,
hit Ctrl-Z on my life and get that original bolt back in place after I've already
cleaned the whole workbench.
And, well, this new Claude Code update, the v2.1.191
release-brought to you by Jellypod AI-it pretty much does exactly that for your
terminal sessions.
Wait, really?
You're talking about the new /rewind capability?
Because, Lachlan, I was playing with that this morning, and it is a complete
game-changer for token management.
Usually, you run /clear to wipe the session, save your context,
and keep your API costs down, but then you're stuck.
You've lost your history.
Now?
Exactly!
Now, even after you've run /clear to sweep the slate clean,
you can actually /rewind right back to where you were.
It's like a- a- a temporal safety net.
Under the hood, it's managing these checkpoints.
And the cool thing is how granular it is.
You can restore just the code, just the conversation, or both.
Wait, how does it handle the state, though?
Like, if I've been running a bunch of terminal commands, does it undo those too?
Ah, well, that is the massive caveat, mate.
It does not track raw bash commands.
So, if you ran rm -rf on a folder, or initiated some database migration in the
background, /rewind isn't going to magically restore those files or roll back your
database.
It's strictly snapshots of your files and the LLM conversation context.
It's a code and convo time machine, not a full system backup.
Okay, that makes sense.
So, it's taking snapshots of the files in your workspace and the chat history.
If you screw up your code, you can roll back the files.
If you just want to change what you said, you roll back the convo.
But don't expect it to undo a git commit or a curl request.
Spot on!
You've got it.
It's about preserving that precious context window without losing your mind when you
realize you actually needed that bit of code from three prompts ago.
Now, they also snuck in some massive quality-of-life fixes in this 191 release.
My laptop fan is certainly breathing a sigh of relief.
Oh, you mean the CPU usage?
Yeah!
They cut terminal streaming CPU usage by thirty-seven percent!
That is huge for a CLI tool.
Thirty-seven percent!
And you know how they did it?
They're coalescing the text output to one-hundred millisecond intervals instead of
streaming every single character raw.
It stops the terminal from choking on the text waterfall.
Plus, they fixed that annoying scroll-jumping bug where the terminal would just
violently yank your cursor around while it was thinking, and they added permanent
background agent stops.
Finally!
No more dizzying scroll jumps.
Honestly, this makes the whole CLI feel incredibly polished.
Well, I'm going to go update my global npm packages right now.
Good on ya, mate.
Definitely worth the install.
Catch you next time!