Skip to content

Iteration Plan for January 2026 #286040

@kieferrm

Description

@kieferrm
Member

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

Endgame

  • January 26, 2026: Endgame begins
  • January 30, 2026: 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

Workbench

Code Editor

  • Hover on keyboard modifier should trigger instantly vscode#276558 @benvillalobos
    Fix important self host issues with experimental GPU acceleration project @Tyriar
    🏃 Allow configuring font family, font size and line height via syntactic tokens vscode#263545 @aiday-mar

Languages

Python

Terminal

API

  • API proposals: query @mjbvz @alexr00
    API finalization: query @mjbvz @alexr00

Source Control

  • 🏃 Git: Support setup steps for new worktrees vscode#276834 @lszomoru

AI

Chat

MCP

  • Support MCP registry url property vscode#278398 @sandy081
    Explore supporting MCP apps vscode#260218 @connor4312

Inline Chat

  • Make inline chat more discoverable vscode#287105 @jrieken

NES / Completions

Agents

Prompt/Instruction Files and Custom Agents

Code Review

  • 💪 Notify user when CCR no-ops vscode#277286 @benvillalobos
    💪 Add Chat: Code Review command vscode#276977 @benvillalobos

Engineering

  • Consume codicons from npm vscode#283823 @alexr00
    Explore distributing .dmg for macOS arm64 vscode#265849 @deepak1556

Documentation


Deferred

Activity

added this to the January 2026 milestone on Jan 6, 2026
pinned this issue on Jan 6, 2026
iwangbowen

iwangbowen commented on Jan 6, 2026

@iwangbowen

Always looking forward to new updates

OrenMe

OrenMe commented on Jan 6, 2026

@OrenMe

The organization/enterprise custom agents and instructions are a great feature
I would like to raise suggestion to consider more fine grained ability - one custom instruction per org is a stretch IMO and experience and it's more likely that a sub set of repos that are managed by a group might have common standards over and entire org or enterprise
Same goes for custom agents
Commented also on #276636 (comment)

I think .github-private is nice storage solution but then solution would benefit if it would be decoupled, exposed with an api and allow more ways to attach to granular groups by direct assignment or dynamic rules(repo associated to teams or by metadata tags)
Also would benefit by collecting stats on which sessions uses which instruction or ran with which custom agents by some ID to measure usage and effectiveness/ROI

ivanm696

ivanm696 commented on Jan 8, 2026

@ivanm696

Revert "Add workflow badges to README

changed the title [-]Iteration Plan for January 2026 [DRAFT][/-] [+]Iteration Plan for January 2026[/+] on Jan 12, 2026
added
iteration-planVS Code - Upcoming iteration plan
and removed
iteration-plan-draftVS Code - Upcoming iteration plan (Draft)
on Jan 12, 2026
devguyio

devguyio commented on Jan 19, 2026

@devguyio

I'm taking the liberty to add this comment here for better visibility, apologies if it's better suited somewhere else.

It seems for the last couple of releases, the latest release wasn't being set, so the latest release keeps showing "November 2025 Recovery" .

This is breaking any tooling that queries GitHub for the latest release (e.g. flatpak build systems) because the new releases aren't showing up.

I added this comment to the "December 2025 Recovery 1" release issue .

ZWQ652

ZWQ652 commented on Jan 20, 2026

@ZWQ652

Have you considered using new build tools to refactor the build process (eg: esbuild, rolldown)? The current gulp speed is too slow

deleted a comment from on Jan 22, 2026
deleted a comment from DevFlex-AI on Jan 27, 2026
chavezgal

chavezgal commented on Jan 30, 2026

@chavezgal

Los agentes personalizados de la organización/empresa y las instrucciones son una gran característica
Me gustaría sugerir que se considere una capacidad de grano más fino: una instrucción personalizada por organización es un tramo en mi opinión y experiencia y es más probable que un subconjunto de repositorios administrados por un grupo pueda tener estándares comunes sobre toda la organización o empresa
Lo mismo ocurre con los agentes de aduanas
Comentado también en #276636 (comment)

Creo que .github-private es una buena solución de almacenamiento, pero entonces la solución se beneficiaría si se desacoplara, se expusiera con una API y permitiera más formas de unirse a grupos granulares mediante asignación directa o reglas dinámicas (repositorio asociado a equipos o por etiquetas de metadatos)
También se beneficiaría de recopilar estadísticas sobre qué sesiones usa qué instrucción o se empetró con qué agentes de aduana por alguna identificación para medir el uso y la efectividad/ROI

unpinned this issue on Feb 7, 2026
locked and limited conversation to collaborators on Mar 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

iteration-planVS Code - Upcoming iteration plan

Type

No type

Projects

No projects

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @joaomoreno@rebornix@devguyio@karthiknadig@kieferrm

      Issue actions