Iteration Plan for January 2025

[kieferrm]

This plan captures our work in January 2025. This is a 4-week iteration. We will ship in early February.

Since mid-December, GitHub Copilot has been available for free for everyone. This allows us to treat AI support as an out-of-the-box experience in VS Code. Consequently, going forward, we'll cover our client-side work for Copilot in this plan, similarly to how we have been tracking our work on our Remote Extensions over the last years.

Endgame

• Jan 27, 2024: Endgame begins
• Jan 31, 2024: Endgame done

The endgame details for this iteration are tracked here.

Plan Items

Below is a summary of the top level plan items.

Legend of annotations:

Mark	Description
🏃	work in progress
✋	blocked task
💪	stretch goal for this iteration
🔴	missing issue reference
🔵	more investigation required to remove uncertainty
⚫	under discussion within the team
⬛	a large work item, larger than one iteration

Accessibility

• 🏃 Accessibility issues, see query @meganrogge team
• 🏃 Accessibility issues in GHPRI, see query @alexr00

Workbench

• 🏃 Support video formats in walkthroughs [vscode#237810] (Support video formats in walkthroughs #237810) @bhavyaus
• 🏃 Support moveable quick open widget vscode#17268 @TylerLeonhardt
• 🏃 Support filtering in the output pane vscode#237432 @sandy081
• Support macOS Configuration Profiles as a policy backend vscode#148942 @sandy081 @joaomoreno

Code Editor

• 🏃 Investigation: Use tree-sitter for grammar colorization vscode#210475 @alexr00 @hediet
• 🏃 Explore GPU rendering of the code editor vscode#221145 @Tyriar @hediet
• Add support for variable line heights vscode#147067 @aiday-mar
• Add support for multiple fonts in the editor vscode#237346 @aiday-mar
• 💪 Explore computing the indentation level using tree-sitter's AST vscode#208985 @aiday-mar

Notebook Editor

• 🏃 Show Inline values for variables in cell editor vscode#237263 @Yoyokrazy
• Improve markdown rendering in notebook (e.g., support custom fonts) vscode#143907 @Yoyokrazy

Jupyter Notebooks

• Improve Context key for execution/debug/run-by-line actions vscode-jupyter#16189 @Yoyokrazy
• 💪 Explore kernel persistence for Remote environments vscode-jupyter#16224 @DonJayamanne

Settings

• Fix fuzzy search in settings search vscode#226039 @rzhao271

Languages

Python

• 🏃 Contributions to the Python extension, see plan @karthiknadig team

TypeScript

• None.

Authentication

• 🏃 Adopt Broker flow in Microsoft Auth provider via MSAL-node vscode#229431 @TylerLeonhardt

Source Control

• Add SCM accessibility help dialog vscode#203577 @lszomoru @meganrogge
• 🏃 Support for ref context actions vscode#232992 @lszomoru
• Support holding a modifier key to show/hide editor blame decorations vscode#237433 @lszomoru
• 🏃 Support opening commit in GitHub from blame hover vscode#237434 @lszomoru
• Support GitHub issue/PR links in blame hover vscode#237436 @lszomoru
• 🏃 Support showing full commit message in blame hover vscode#237435 @lszomoru

Testing

• None.

Terminal

• 🏃 Improve upon terminal completions query @meganrogge
• 🏃 Promote terminal ligatures from experimental query @Tyriar
• 🏃 Terminal Environment Variable API vscode#227467 @anthonykim1
  • 🏃 pwsh
  • 🏃 bash
  • 🏃 zsh
  • fish
• 🏃 Terminal Shell Type API vscode#230165 @anthonykim1
• New conpty setting blocks update vscode#225719 @deepak1556

API

• 🏃 API proposals: query @jrieken @mjbvz
• 🏃 API finalization: query @jrieken @mjbvz
• Finalize document paste API vscode#30066 @mjbvz

Extensions

• Notify users of extension runtime model on extension install vscode#215527 @sandy081
• Enable extension signature verification by default on Linux vscode#230816 @sandy081

Extension Contributions

• 🏃 Support global PR queries vscode-pull-request-github#6448 @alexr00

Remote Extension Contributions

General

• None.

SSH Extension

• 💪 Better proxy support for remote (install, download extensions, etc) vscode-remote-release#5927, vscode-remote-release#10491 @joshspicer
• 🏃 💪 SSH Config parsing improvements @joshspicer
  • Upgrade ssh-config dependency vscode-remote-release#10132, vscode-remote-release#10013
  • Wildcard support for remote SSH platform vscode-remote-release#2997
• 💪 Resolve unique connection issues vscode-remote-release#10412, vscode-remote-release#6319, vscode-remote-release#6600 @joshspicer
• 🏃 Allow connecting to unsupported Linux remotes, by use of custom glibc and stdc++ libraries vscode#231623 @deepak1556

GitHub Copilot

• Improve out-of-the-box experience vscode#236511 @bpasero
  • 🏃 Support vscode: protocol handler for initial chat setup @bpasero
  • 🏃 Improve Copilot setup view in secondary sidebar @bpasero
• Consolidate Copilot status bar items vscode#237428 @bpasero
• 🏃 Improve Copilot Edits and explore self-guided multi-step editing in Copilot Edits vscode-copilot-release#3974 @kieferrm team
• 🏃 Provide support for next edit suggestions vscode-copilot-release#3975 @alexdima team
• 🏃 Make language-specific context available to Copilot inline completions vscode-copilot-release#3976 @dbaeumer
• 🏃 Provide support for prompt snippets vscode-copilot-release#3977 @legomushroom

Engineering

• Support building the monaco-editor AMD variant from new sources vscode#234114 @hediet @alexdima

Electron

• 🏃 Electron 34 update vscode#237437 @deepak1556
• ✋ Align Electron fetch with Node.js fetch electron#43715, electron#43712 @deepak1556
• 🏃 GetBoundingClientRect zoom adjustments vscode#233692 @deepak1556

Documentation

• 🏃 Document extension runtime security vscode-docs#7874 @ntrogh @isidorn

---

Deferred

• 💪 Finalize Related code vscode#126932 @connor4312
• 💪 Explore supporting reverse search in tree find to remove filter widget vscode#227009 @meganrogge
• VSCode freezing when adding folder to workspace while working on remote Linux machine vscode-remote-release#10168 @joshspicer

[iwangbowen]

Couldn't wait for the next update

[hickford]

Any time to look at bug fix #216085 ?

[Patrikoska1]

##237297

[commonism]

Hi,

I'd like to discuss #869

For me - the problem is …

Having a ml project which includes the training/validation data on a remote server, the current vscode behavior is spidering all resources, installing inotify handlers, and if these fail due to the number, fstat all files.

You end up with a vscode node.js services breaking your ml storage backend by running fstat for 200k files at the speed possible.

This is bad defaults and currently users are even unable to change these defaults.

Depending on the storage backend, tracking down users/projects causing these metadatalookups is manual task and very time consuming.

[fisforfaheem]

Anything related to UI and UX? because the audio cue are not easily enabled or disabled, also the UI need to be much like windows 11 mica style now

[netcraftz]

Any time to look at bug fix #216085 ?

"Community PR Approvals In progress — Not enough approvals" - tough test.