December 2025 (version 1.108)
🎬 Watch The Story of VS Code! VS Code is now on Instagram, follow @vscode.ig for updates, tips, and more. Rewatch GitHub Copilot Day. December 2025 (version 1.108) Release date: January 08, 2026 Update 1.108.1 : The update addresses these issues Update 1.108.2 : The update addresses these issues Downloads for 1.108.2 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the December 2025 release of Visual Studio Code.
Traditionally, the month of December is a time where our team focuses on cleaning up GitHub issues and pull requests across our repositories. This year, we managed to reduce our open issues by nearly 6,000 and triaged over a thousand more. In addition to our housekeeping efforts, we have also made several improvements and feature updates across various areas of VS Code. Happy Coding! If you'd like to read these release notes online, go to Updates on code.visualstudio.com .
Insiders: Want to try new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available. Download Insiders Agents Agent Skills (Experimental) Setting : chat.useAgentSkills Open in VS Code Open in VS Code Insiders VS Code now supports Agent Skills , allowing you to teach the coding agent new capabilities and provide domain-specific knowledge. Agent Skills are folders of instructions, scripts, and resources that GitHub Copilot can load when relevant to perform specialized tasks.
Skills are stored in directories with a SKILL.md file that defines the skill's behavior. VS Code automatically detects skills from the .github/skills folder in your workspace (or .claude/skills/ for backwards compatibility). They are then loaded on-demand into the chat context when relevant for your request. Enable support for Agent Skills by enabling the chat.useAgentSkills Open in VS Code Open in VS Code Insiders setting.
Learn more about creating and using skills in the Agent Skills documentation . Improvements to Agent Sessions view This iteration, we further improved the Agent Sessions view with several enhancements: Keyboard access support for actions such as archive, read state, opening a session Grouping of sessions based on state and age when showing side-by-side Provide information on changed files and associated PRs for a session Support for archiving multiple sessions at once from the new group sections General accessibility improvements Note : chat.viewSessions.orientation Open in VS Code Open in VS Code Insiders no longer provides the auto option.
Use sideBySide as alternative. Chat Chat picker is based on agent sessions The Quick Pick for chat sessions is now based on the same information that drives the Agent Sessions view. You can access any previous chat session from there and perform actions like archiving, renaming or deletion. Note : Agent sessions can also be accessed by typing agent in the Quick Open control ( ⌘P (Windows, Linux Ctrl+P ) ). Chat title improvements The Chat view title control is now showing up, irrespective of how the Activity Bar is configured.
Previously, it only showed up in the default Activity Bar configuration. To quickly jump from one session to another, select the chat title to open the sessions Quick Pick and choose another session. Open empty Chat on restart Setting : chat.restoreLastPanelSession Open in VS Code Open in VS Code Insiders From now on, previous chat sessions are not automatically restored when VS Code is restarted. Instead, an empty Chat view is shown where you can then access previous sessions from the Agent Sessions control.
Modify this behavior with the chat.restoreLastPanelSession Open in VS Code Open in VS Code Insiders setting. Terminal tool auto approve default rules Settings : chat.tools.terminal.enableAutoApprove Open in VS Code Open in VS Code Insiders , chat.tools.terminal.autoApproveWorkspaceNpmScripts Open in VS Code Open in VS Code Insiders The following commands are now auto approved by default when terminal auto approve is enabled ( chat.tools.terminal.enableAutoApprove Open in VS Code Open in VS Code Insiders ): git ls-files git --no-pager <safe_subcommand> git -C <dir> <safe_subcommand> rg (excluding --pre and --hostname-bin ) sed (excluding some args and usage patterns) Out-String In addition, npm scripts run through npm , pnpm or yarn are now auto approved by default when they are included within the package.json .
We do this because using agents already requires Workspace Trust, and we protect agents from editing sensitive files like package.json . This can be disabled with chat.tools.terminal.autoApproveWorkspaceNpmScripts Open in VS Code Open in VS Code Insiders . To improve transparency around auto approve, there is now an informational message when a rule was explicitly denied by either default or custom rules: Add session and workspace rules for future terminal tool commands The allowed commands or command line entries in the Allow dropdown now have options a corresponding action to allow them for the current session or for the workspace.
Terminal tool preventing adding to shell history Setting : chat.tools.terminal.preventShellHistory Open in VS Code Open in VS Code Insiders When shell integration is enabled and working, commands that are run by the terminal tool are no longer included in shell history for bash, zsh, pwsh and fish. The method this uses differs for each shell, for bash for example HISTCONTROL=ignorespace is set and a space is added to the start of the command being run.
If you prefer to keep terminal tool commands in the shell history, configure this with the chat.tools.terminal.preventShellHistory Open in VS Code Open in VS Code Insiders setting. Accessibility Streaming chat responses in Accessible View The Accessible View now dynamically streams chat responses as they are generated. Previously, you needed to close and reopen the Accessible View to see updated content. Now, you can stay in the Accessible View and monitor output as it comes in, making it much easier to follow along with AI responses in real-time.
MCP server output excluded from Accessible View To reduce noise, MCP (Model Context Protocol) server output is now excluded from the Accessible View by default. The standard chat output remains fully accessible, as it's presented in a text area that works well with screen readers. Language ID variable in window title A new ${activeEditorLanguageId} variable is now available for the window.title Open in VS Code Open in VS Code Insiders setting.
This variable displays the language identifier of the currently active editor, which is useful for accessibility tools like Talon that need to determine the current programming language to enable appropriate voice commands. "window.title" : "${activeEditorLanguageId} - ${activeEditorShort}" Editor Experience Import profile by drag and drop You can now import a settings profile by dragging and dropping a .code-profile file into VS Code.
This makes it easier to share profiles with teammates or quickly set up a new environment. When you drop the file, the Profiles editor opens and lets you preview and import the profile. This provides a similar experience to dragging and dropping a .code-workspace file to open a workspace. Copy breadcrumbs path Setting : breadcrumbs.symbolPathSeparator Open in VS Code Open in VS Code Insiders You can now copy the breadcrumbs path to the clipboard by using the Copy Breadcrumbs Path command.
This is useful when you need to share the exact location of a symbol with your team or for documentation purposes. The breadcrumbs.symbolPathSeparator Open in VS Code Open in VS Code Insiders setting enables you to customize the separator character used to join breadcrumb segments. Go to Symbol in Workspace supports special characters in query The Go to Symbol in Workspace ( ⌘T (Windows, Linux Ctrl+T ) ) feature no longer incorrectly filters out all results when the search query contains a # cha
The rest of this page is on the live site.