Cline CLI 3.0.49: checkpoints work again, restore is a full workspace rewind
Fixes a regression where the CLI never recorded checkpoints at all, and makes restore rewind the whole workspace instead of just the conversation. Also raises Ollama's response-start timeout to 5 minutes so cold-loading large local models no longer errors mid-load.
PUBLISHED2026-08-02
OBSERVED2026-08-11
AGE9d
SOURCES1
- Checkpoints were never recorded in the CLI due to a run-boundary regression; now created again (from SDK v0.0.69)
- Restore rewinds the workspace: files Cline created during the task return to checkpoint-time content, files created after the checkpoint are removed,
.gitignored paths (build output,node_modules,.env) untouched /undoworks after tool use — the checkpoint picker had counted tool results as user turns, aborting with "Could not find user message for run N"- Restored message is prefilled as plain text, not the raw
<user_input mode="act">envelope - Ollama: response-start timeout 30s → 5min; empty responses retried instead of failing with "Model returned empty response"
- Migrated users with a stored model id missing from the catalog fall back to the default model
- ClinePass promo dialog dismissible with any key and marked shown on appearance; CLI promo code flow removed
- URL opening no longer crashes on hosts without an opener (headless Linux); WSL2 uses
xdg-open, Windows tries the absolute PowerShell path,cline doctor logmaps Linux paths to\\wsl$UNC - Hub restarts via the installed wrapper after Unix self-update so npm cannot reuse a deleted cached executable
- ACP: ClinePass selectable as provider, org selection, session resolution and restart text rendering fixed, real error text on agent failures
- Gateway-forwarded provider errors show the upstream message instead of a Zod dump or
[object Object]; free/recommended models show real display names; filesystem-root (/) sessions work; Windows PowerShell commands sent over UTF-8 stdin; video input capability no longer dropped
COMMUNITY
No curated reactions recorded for this event. Facts and takes are kept in separate layers — community context is added by hand, never blended into the record above.