Cline Fixes CLI Checkpoints That Never Recorded

Cline shipped a fix on August 2 disclosing that CLI checkpoints were never being recorded once an agent used a tool, per the v4.1.3 and cli-v3.0.49 release notes.

That's supposed to be the safety net for anyone running an agent that edits files on its own. A checkpoint that silently fails to write doesn't announce itself, so you only discover the gap the moment you actually need /undo.

The bug sat at the run boundary: after any tool call, no checkpoint got written. Calling /undo then threw an error, "Could not find user message for run N," instead of rolling back your changes.

The fix makes /undo a real full workspace rewind. Agent-created or edited files return to checkpoint content, and files created afterward get removed entirely. Anything covered by .gitignore, like node_modules or .env, stays untouched.

Separately, the same release notes disclose a packaging bug: two bundles of the combined rollout were invalidating each other's account sessions.

I trust checkpoint features because they're supposed to be the parachute, not something I double check myself. This one had a hole in it and never said so. Next time an agent harness ships an undo or checkpoint feature, check whether it logs a failure when the write doesn't happen.