Cline SDK 0.0.69: checkpoint recording fixed, restore now captures created files
Fixes the run-boundary bug that meant neither VS Code nor the CLI ever recorded checkpoints, and upgrades restore into a real workspace rewind that also removes files created after the checkpoint. Ollama handling gets a 5-minute response-start default and retries on empty turns.
PUBLISHED2026-08-02
OBSERVED2026-08-11
AGE9d
SOURCES1
- Run-boundary detection assumed the run prompt arrives as run input, but both hosts seed it into the initial messages — no checkpoints were ever recorded. Fixed, and detection now survives process restarts and compaction
- Restore captures files Cline created during a task and restores them to checkpoint-time content; files created after the checkpoint are removed;
.gitignored paths untouched; a pre-restore recovery snapshot can roll back the whole operation - Checkpoints taken before this change keep the old conservative behaviour of never touching untracked files
- Ollama response-start timeout defaults to 5 minutes (was 30s); unreachable servers still fail immediately, requests stay cancelable, explicit
requestTimeoutMsstill honoured - Completely empty Ollama turns (no text, reasoning, or tool call) retried at the model boundary; non-empty turns stream with no added latency; errored or token-limited turns pass through unchanged
- Migrated users with a stored model id absent from the runtime catalog fall back to the default Cline model
- Tool-use mistake notices no longer reported as provider API errors; provider errors no longer double-counted; error details preserved
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.