Cline 4.1.3: rollout bundles no longer invalidate each other's account session
Fix release for the VS Code extension. The main fix stops the two bundles of the combined rollout package from consuming each other's shared refresh token, which produced spurious "Unauthorized" prompts and sign-outs; checkpoint reliability and several settings-persistence bugs are also fixed.
PUBLISHED2026-08-02
OBSERVED2026-08-11
AGE9d
SOURCES1
- A still-open legacy window refreshing its token after promotion to the new extension consumed the shared refresh token, causing spurious "Unauthorized" / re-authenticate prompts and sign-outs. Promoted legacy windows keep their current session and get a one-time Reload Window prompt
- Migrating a setup referencing an unrecognised model id falls back to the default Cline model instead of leaving the provider unconfigured
- Checkpoints created consistently; restore rewinds the whole workspace instead of a subset of files
- Settings edits made before provider config finishes loading are kept (base URLs, API keys, Qwen/Moonshot API line); custom base URL fields no longer lose keystrokes; checkbox state survives a failed clear
- AskSage custom API URL used at inference time
- Pending tool approval settled when an edited message replaces the session, so tasks stop hanging; attachments dropped from edited messages
- Terminal commands complete when shell execution ends, so finished commands no longer stall tasks; Windows Store PowerShell profiles run correctly
- Untracked files included when generating commit messages
- Gateway-forwarded stream failures surface the upstream provider error; Ollama empty-response retry and 5-minute response-start timeout; real display names for free/recommended models; video input capability preserved; plan/act input border tracks textarea focus
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.