Cline · 2026-06-26 · major
Cline 4.0 — SDK rewrite rolled back to 3.89 two days after launch
Cline 4.0.0 migrated the VS Code extension to a shared SDK session layer with a Plugins marketplace, ClinePass billing, queued chat, and edit-and-regenerate — but launch-day regressions led to a 4.0.1 rollback to the 3.89.2 codebase two days later.
Cline shipped a major SDK rewrite as 4.0.0, then rolled it back two days later as 4.0.1 after launch-day regressions.
Quick facts
| Maker | Cline |
|---|---|
| License | Apache-2.0 |
| Stars | 64,000+ on GitHub |
| v4.0.0 shipped | 2026-06-26 |
| v4.0.1 rollback | 2026-06-28 |
| Effective codebase on 4.0.1 | 3.89.2 (SDK work continues on main) |
What is it?
Cline 4.0.0 is the first major version of the 64k-star open-source coding agent in months, and it rewrote the VS Code extension to run on the shared Cline SDK session layer. The release added a Customize marketplace (Skills, MCP servers, Plugins), ClinePass for inference billing inside the extension, queued chat messages, and edit-and-regenerate. Two days later, Cline 4.0.1 reverted to the pre-migration 3.89.2 codebase.
How does it work?
The SDK migration consolidates agent turns, tools, MCP, checkpoints, telemetry, and task history into one shared layer used by the VS Code extension, CLI, and SDK consumers. Cline 4.0.1 ships the 3.89.2 extension code under a higher version number so the VS Code marketplace auto-pushes the rollback to users already on 4.0.0; SDK-migration work continues on main rather than as a hotfix branch. Auto-approval defaults to off and Subagents are temporarily disabled while the new layer stabilizes.
Why does it matter?
Cline is one of the most-installed open-source coding agents — a rollback of a flagship release is a public reminder that shared-runtime rewrites are risky even with broad test coverage. For users, the takeaway is that 4.0.1 is functionally 3.89.2; for builders evaluating the Cline SDK as a foundation for their own agent, the SDK path is still moving on the main branch rather than as a stable cut.
Who is it for?
Developers using Cline in VS Code or evaluating its SDK as a substrate for custom coding agents.
Frequently asked questions
- Why did Cline roll back v4.0.0?
- Cline 4.0.0 migrated the VS Code extension to a shared SDK session layer, but launch-day regressions led the team to ship 4.0.1 two days later. The 4.0.1 release ships the pre-migration 3.89.2 codebase under a higher version number so users on 4.0.0 automatically receive the rollback. SDK-migration work continues on the main branch.
- What was new in Cline 4.0.0?
- Cline 4.0.0 added a Customize marketplace for Skills, MCP servers, and Plugins; ClinePass for subscription billing and live model lists; queued chat messages so input is not lost while Cline processes; edit-and-regenerate for previous messages; and restructured provider/model configuration. Auto-approval was disabled by default and Subagents were temporarily unavailable during stabilization.
- Is Cline free to use?
- Cline is Apache-2.0 open source and free to install as a VS Code extension or CLI. The 'Open Source' tier charges only for AI inference credits — paid through ClinePass or by bringing your own API keys (BYOK) from supported model providers. An Enterprise tier with SSO, SLA, RBAC, and centralized billing is sold under custom pricing.
- What is ClinePass?
- ClinePass is the Cline subscription that handles provider selection, live model lists, and pay-as-you-go billing for inference credits directly inside the extension. It is the default credits path introduced in 4.0.0; users can still bring their own API keys instead of using ClinePass.
Try it
code --install-extension saoudrizwan.claude-dev