Skip to content
NO FEED

Understand the changes. Choose the tools. Put AI to work.

← News
News · Wait

Cline 4.1.0 → 4.1.2

The stable VSIX now ships two extensions in one package — legacy and a new SDK build — with a loader that activates one per window under a staged rollout starting at 1%. Check which you are running before filing a bug.5

Relevant to: teams standardising on one editor extension

What the verdict meansAvailable, but early — bugs, limits or price.
Deeper — how to tell which build you are on, and one fix worth having
  • 4.1.2 added a Legacy / Next indicator next to the version on the About page in settings. That is the only reliable way to know which of the two extensions your window activated, and the two have different internals — a bug report without it is unactionable.
  • 4.1.1 removed the MCP server-key machinery: native MCP calls now route by server name instead of a random in-memory uid, so routing survives restarts and changes to the server list.
  • SDK 0.0.67 honours the per-server timeout in cline_mcp_settings.json for initialize, tools/list and tools/call. It was previously hardcoded at 1.5 and 5 seconds; it now defaults to 60 and clamps between 1 and 3600. If you disabled a slow MCP server months ago because it kept timing out, that was probably why.

Sources

  1. github.com/cline/cline — releases 4.1.0–4.1.2 · read
Originally part of the 1 August 2026 edition.

The useful part, in your inbox.

One complete edition every weekday, with practical takeaways.