Cline 4.1.0: one VSIX ships both the legacy and SDK-based extension behind a staged rollout
The stable VS Code extension becomes a combined A/B package: a single VSIX containing the current extension and the new SDK-based extension, with a loader that activates exactly one per window under a remotely controlled staged rollout starting at 1% of users. Settings and credentials are shared between the two, but tasks created on the new extension are not visible while running the old one.
PUBLISHED2026-07-31
OBSERVED2026-08-11
AGE11d
SOURCES1
- One VSIX contains both bundles plus a loader that activates exactly one per window
- Rollout is staged and remotely controlled; assignments apply on window reload, never mid-session; starts at 1%
- If the new extension fails to activate, the loader falls back to the current extension in the same window
- Settings, credentials, and preferences are shared; nothing is migrated or lost when switching
- Tasks created on the new extension aren't visible while on the old one (they return if re-promoted)
- Legacy bundle:
legacy-extension@ 3fdc186f1 (4.0.12 + free-model button wording); next bundle:main@ 0746ea72bf6 - Rollout machinery lives in apps/vscode-rollout
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.