Cline 4.1.0 → 4.1.2 — from issue No. 001nofeed.dev
No Feed

No feed. One issue a day. Then you are done.

Weekdays — what shipped, what to skip, what it means. Two minutes on a quiet day, four on a heavy one.
Saturday — one argument, made properly. Sunday — nothing at all.

Every claim links to a primary source. Community posts choose what we look at; they never carry a fact on their own. Corrections run above the fold.
Issue No. 001 · 1 August 2026
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

MATTERS TO · teams standardising on one editor extension
WHAT THE VERDICT MEANS
Available, 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.

Also in this issue

read the whole thing →
Use itGPT-5.6 price cut · Fast mode
Use itMCP 2.0 — stateless
Waitqm — multiplayer agent harness
Use itGemini CLI 0.53.1

One issue a day. Three minutes.

Or Saturdays only, if the week is enough. Full issue in the email — no teaser, no click required.

No feed. One issue a day. Full issue in the email — no teaser, no click.