What the VS Code extension auto-update delay is and why it exists
The VS Code extension auto-update delay is a new security feature in Visual Studio Code that waits two hours before automatically installing many third-party extension updates, giving teams a short review window to detect potentially compromised releases and reduce exposure to software supply chain attacks without fully disabling auto-updates for developers who value staying current. In VS Code 1.123, automatic updates remain on by default, but most third-party extensions now enter a “cooldown” period after a new version is published. During this time, the IDE holds back auto-installation, though the extension can still be updated manually. Microsoft’s goal is to cut the risk that a malicious or flawed extension update spreads instantly across developer machines and enterprise environments. The change follows a prior compromised VS Code extension incident and reflects growing attention on developer tool security as a supply chain attack vector.
How the two-hour delay works inside VS Code
From the user’s perspective, the new VS Code security update keeps the familiar extension experience but adds a small safety buffer. When automatic updates are enabled, VS Code 1.123 now waits two hours after an extension publisher releases a new version before applying that update in the background. According to Microsoft, “new versions are auto-updated two hours after they are published, adding an extra layer of protection against problematic or potentially compromised releases.” This extension auto-update delay does not apply uniformly: extensions from trusted publishers such as Microsoft, GitHub, and OpenAI still update immediately. When an extension has a pending update, the extension details view shows that an update exists, why it has not yet been applied, and when the automatic update is scheduled. Developers can override the delay and apply the new version right away by clicking the Update button.
Supply chain attack prevention and the role of developer tools
Extension ecosystems have become a practical target for attackers because they sit at the heart of developer workflows and can quietly influence code, build scripts, and CI pipelines. A compromised extension can plant malicious code, exfiltrate secrets, or pivot deeper into enterprise systems under the guise of a trusted tool. The new VS Code extension auto-update delay directly addresses this supply chain attack prevention problem by enforcing a minimum “age” before new versions spread widely. This move parallels cooldown features in package managers like RubyGems Bundler, npm, pnpm, Bun, and Yarn, which introduce minimum release ages before installations. By aligning developer tool security with these controls, VS Code reduces the chance that a zero-day malicious update is installed everywhere within minutes, while still keeping the path open for deliberate, reviewed updates when teams decide the risk is acceptable.
Balancing fast updates with enterprise security needs
For individual developers, the two-hour delay may feel small, but in larger organizations it can be the difference between controlled rollout and instant blast radius. Security and DevOps teams gain a narrow but valuable window to review release notes, run smoke tests, or compare behavior in a staging environment before the update reaches every workstation. At the same time, developers who depend on quick fixes or new features are not locked out; they can opt into the latest version immediately via manual update. This default delay, rather than a hard block, keeps extension ecosystems lively while making supply chain attack prevention a standard part of extension lifecycle management. Teams that want more control can formalize internal guidance: for example, only security-approved extensions should be manually fast-tracked, while others ride the automatic schedule and benefit from the built-in pause.
Safer agent workflows and the future of VS Code security
VS Code 1.123 is not only about delaying extensions; it is part of a broader shift toward safer, more persistent agent workflows. The release introduces AI session sync, project memory via /chronicle commands, and an Agents window that keeps multi-step, multi-device work aligned. These capabilities mean agents can touch more of a codebase and run longer across remote sessions, raising the stakes for developer tool security. By adding guardrails like the extension auto-update delay while expanding AI and agent features, VS Code aims to let teams explore richer automation without ignoring supply chain risk. Local-agent terminal commands now have network-aware fallbacks, and air-gapped or highly controlled environments gain more enterprise-focused controls. Together, these changes show a direction where auto-updates, agents, and extension ecosystems remain convenient but are framed with time-based checks and clearer oversight for security-conscious teams.
