Visual Studio Code 1.129 リリースノートVisual Studio Code 1.129 Release Notes

Microsoft has published the release notes for Visual Studio Code 1.129, the latest entry in the editor's long-running monthly cadence. As with most point releases, the update bundles incremental refinements to the core editing experience, AI-assisted workflows, and surrounding developer tooling rather than sweeping structural changes. For the millions of developers who rely on VS Code as a daily driver, these steady updates matter because they compound over time, keeping the free, cross-platform editor competitive with heavier integrated development environments.

The headline themes of a 1.x monthly release typically fall into a few consistent buckets, and 1.129 appears to follow that pattern. Editor improvements usually target everyday friction points such as syntax highlighting, code folding, search and replace, and multi-cursor behavior, while accessibility work continues to expand screen reader support and keyboard navigation. Source control integration, the terminal, notebook editing, and task running also tend to receive smaller quality-of-life fixes in each cycle. Because VS Code develops in the open on GitHub, many of these changes originate as community pull requests, and the release notes generally credit external contributors alongside the core team.

AI-assisted features have become the most visible area of investment across recent releases, and 1.129 is likely to continue that trajectory. Over the past year, Microsoft has steadily folded GitHub Copilot capabilities more deeply into the editor, including inline suggestions, a chat sidebar, and an agent mode that can plan and execute multi-step edits across a workspace. Much of the underlying chat and language-model tooling has been moving toward open-source availability, reflecting Microsoft's stated intention to make the AI layer of VS Code more transparent and extensible. Readers should consult the official notes for the specific model, quota, or interface changes included in this particular build, since those details shift from month to month.

A significant piece of context for current VS Code releases is the Model Context Protocol, an open standard for connecting AI assistants to external tools and data sources. Support for MCP servers has been maturing inside the editor, allowing extensions and chat agents to call out to file systems, databases, documentation, and other services through a common interface. If 1.129 refines this integration, it would align with a broader industry trend in which editors and assistants increasingly act as orchestrators of external context rather than closed, self-contained tools. Adjacent products such as JetBrains IDEs, the Cursor editor, and various command-line coding agents are pursuing similar directions, which helps explain why VS Code keeps iterating quickly in this space.

Extension authoring remains another recurring focus. Each release tends to expand or stabilize APIs so that the vast VS Code marketplace ecosystem can take advantage of new capabilities, particularly around chat participants, language model access, and custom tool registration. Developers maintaining extensions should review the API changes and any proposed API updates, since features that begin as experimental in one version often graduate to stable in later ones. The release notes usually flag deprecations and breaking changes as well, which is essential reading for anyone shipping to the marketplace.

It is worth remembering how VS Code's update mechanics work in practice. Stable builds ship monthly, while an Insiders channel offers nightly previews for those who want to test upcoming features early. The editor auto-updates by default on most platforms, so many users will receive 1.129 without manual intervention, though enterprise deployments frequently pin versions and roll out on their own schedule. VS Code is built on the open-source Code - OSS project and the Electron framework, and it shares a runtime lineage with tools like the browser-based vscode.dev and GitHub Codespaces, which benefit from the same underlying improvements.

For teams evaluating whether to upgrade, the pragmatic approach is to read the full release notes, verify that critical extensions remain compatible, and watch the issue tracker for any regressions reported shortly after launch. Point releases are generally low risk, and Microsoft often follows a major monthly update with a recovery release that addresses early bugs. As always, the authoritative source for exact feature descriptions, screenshots, and contributor acknowledgments is Microsoft's published 1.129 documentation rather than any summary.