Why VS Code Now Ships Weekly: The Rush Behind the Release Cadence

Can't Stop

Between October 7 and November 11, VS Code shipped six stable versions — averaging less than six days per release. Two years ago that pace would have covered half a year of updates. The release notes for those six versions show Agent-related features in nearly every iteration: Agent Host, session grid, Canvas, model comparison, Inbox mode, and remote Agent. Version 1.145's changelog opens with "This week," signaling that Microsoft now organizes releases on a weekly cadence.

The direct driver is competition. Tools such as Cursor and Claude Code target the same developer audience and maintain similarly rapid release rhythms. If VS Code accumulated features for a monthly drop, many capabilities would already be publicized by rivals by the time they ship. Weekly cadence also keeps individual changes small, lowering rollback risk when issues arise.

Bearing the Cost

Three groups absorb the cost of this acceleration:

Extension authors must verify API changes every release; extension host behavior and UI components can shift each week, making the old once-a-year adaptation cycle obsolete.

Enterprises need version pinning, canary testing, and internal plugin compatibility checks on a compressed schedule. Without them, employees upgrading to the latest version will break internal tooling first.

Regular users face faster-changing settings and UI, causing online tutorials and screenshots to expire more quickly. Version 1.146 already announced that Local harness will be removed in February 2027; such dated deprecations will only increase.

How to Keep Up

Individual users can switch updates from automatic to manual check to avoid workflow interruptions. In settings, search for update.mode and change it to manual instead of disabling updates entirely:

// Old approach: disable updates entirely to avoid interruptions
{
  "update.mode": "none"
}

// Better approach: keep manual check, only disable background auto-update
{
  "update.mode": "manual"
}

Teams should do the opposite: pin exact versions in CI pipelines and development machine images, upgrading uniformly only after internal plugins pass validation. Schedule the upgrade window for the same day each week so the organization moves in lockstep. The weekly cadence itself isn't the problem — lacking a version strategy is.

VS Code is transitioning from "an editor with a few major releases per year" into "a platform that changes every week."