Skip to content

foryourhealth111-pixel/Vibe-Skills / bundled/skills/vscode-release-notes-writer

vscode-release-notes-writer

Verified

Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code.

examples/v1_109.md

View on GitHub
---
Order: 118
TOCTitle: Insiders
PageTitle: "Visual Studio Code January 2026 (Insiders)"
MetaDescription: Learn what is new in the Visual Studio Code January 2026 Release (1.109).
MetaSocialImage: 1_109/vscode-insiders-header.webp
Date: 2026-02-04
DownloadVersion: 1.109.0
Milestone: February 2026
---
# January 2026 Insiders (version 1.109)

![VS Code Insiders banner](images/1_109/vscode-insiders-banner-medium.png)

_Last updated: January 9, 2026_

These release notes cover the Insiders build of VS Code and continue to evolve as new features are added. To try the latest updates, [download Insiders](https://code.visualstudio.com/insiders).
To read these release notes online, go to [code.visualstudio.com/updates](https://code.visualstudio.com/updates).

You can still track our progress in the [Commit log](https://github.com/Microsoft/vscode/commits/main) and our list of [Closed issues](https://github.com/Microsoft/vscode/issues?q=is%3Aissue+is%3Aclosed+milestone%3A%22January+2026%22).

_These release notes were generated using GitHub Copilot and might contain inaccuracies._

Happy Coding!

---

<!-- TOC
<div class="toc-nav-layout">
  <nav id="toc-nav">
    <div>In this update</div>
    <ul>
      <li><a href="#january-8-2026">January 8, 2026</a></li>
      <li><a href="#january-7-2026">January 7, 2026</a></li>
      <li><a href="#december-28-2025">December 28, 2025</a></li>
    </ul>
  </nav>
  <div class="notes-main">
Navigation End -->

## January 8, 2026

* The terminal tool now supports a `timeout` parameter to control how long terminal commands run before timing out, preventing unnecessary polling commands. [#286598](https://github.com/microsoft/vscode/issues/286598)

* Updated the list of npm commands that are safe for automatic execution. [#286463](https://github.com/microsoft/vscode/issues/286463)

* The terminal suggest toolbar no longer shows the selection mode option when quick suggestions are disabled, reducing confusion. [#286440](https://github.com/microsoft/vscode/issues/286440)

* The `terminal.integrated.suggest.quickSuggestions` setting can now be configured in the Settings editor instead of requiring manual JSON editing. [#286075](https://github.com/microsoft/vscode/issues/286075)

* Added a `workbench.mcp.startServer` command to start a specific or all MCP servers to discover their tools. [#283959](https://github.com/microsoft/vscode/issues/283959)

* Exploration work on rich integrated web browser using WebContentsView or controlledframe to overcome limitations of the current iframe-based Simple Browser. [#277298](https://github.com/microsoft/vscode/issues/277298)

* A new proposed API enables extensions to show buttons inline after the input box in quick inputs, in addition to the title bar location. [#221397](https://github.com/microsoft/vscode/issues/221397)

## January 7, 2026

* You can now import a chat session into the Chat view instead of only opening it in a new editor tab. [#283954](https://github.com/microsoft/vscode/issues/283954)

* Fixed an issue where auto approval information for the fetch tool was not visible when hovering over the tool call. [#282238](https://github.com/microsoft/vscode/issues/282238)

* Added built-in support for MCP Apps, enabling servers to provide custom UI for tool invocation. [#260218](https://github.com/microsoft/vscode/issues/260218)

## December 28, 2025

* The quick input now supports overflow buttons, enabling secondary actions to be placed in an overflow menu. [#285213](https://github.com/microsoft/vscode/issues/285213)

---

We really appreciate people trying our new features as soon as they are ready, so check back here often and learn what's new.

<a id="scroll-to-top" role="button" title="Scroll to top" aria-label="scroll to top" href="#"><span class="icon"></span></a>
<link rel="stylesheet" type="text/css" href="css/inproduct_releasenotes.css"/>
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall