VS Code 1.108.0 release notes: housekeeping, real changes, and a sane upgrade plan

“6,000 issues closed” sounds like bragging until you need to debug a weird editor hiccup at 2 a.m.

I’ve watched teams ignore housekeeping releases, then spend a week chasing flaky behavior that quietly got fixed. VS Code 1.108.0 (the December 2025 update, published January 8, 2026) leans hard into cleanup, but it also ships a few user-visible tweaks that can surprise you if you run a tightly managed dev setup.

What actually changed in 1.108.0 (not just “maintenance”)

Here’s the thing.

The official notes call this a housekeeping month, but the build still changes knobs people touch every day, especially if you use Copilot Chat or live in the terminal. I pulled these straight from the official v1.108 notes and the 1.108.0 tag page, so you can trace them.

• Housekeeping numbers (use the real counts): The team reports 5,951 issues closed and 1,203 issues triaged across maintained repositories. That’s not “fixes,” it’s throughput, but it does lower noise for maintainers.
• Agent Skills (experimental): VS Code adds “Agent Skills” with a chat.useAgentSkills setting, which lets agent tooling load a SKILL.md from a folder. If you run Copilot features in locked-down environments, expect policy conversations.
• Snippet transformations: Snippets gain snakecase and kebabcase transforms. Small change, but extension authors and heavy snippet users will notice fast.
• Terminal behavior tweaks: Terminal IntelliSense defaults shift for people who hate auto-suggestions. Good for some workflows, annoying if you relied on suggestions popping up constantly.
• API surface changes: Quick Pick gets new properties (QuickPick.prompt and QuickPickItem.resourceUri). Extension authors should at least run their test suite once after upgrading.

The housekeeping metric is not the point (but it still matters)

My hot take: ignore the GitHub issue count.

Use it as a signal, not a reason. Closing 5,951 issues can mean “we fixed bugs,” but it can also mean “we closed duplicates and stale reports.” What matters for you is whether 1.108.0 changes the stuff you rely on: terminal UX, chat tooling defaults, and the extension API edges.

So.

If you manage a team image or a devcontainer base, treat this like any other upgrade. Run a quick smoke test, then roll it forward. Some folks yolo patch updates on Friday. I don’t, but I get it.

Who should upgrade, and who should stage it first

Pick your risk level.

I’d love to say “everyone upgrade today,” but that’s not how real machines behave, especially with 40 extensions and a pile of custom settings.

• Solo dev laptops: Upgrade when the prompt pops up. If something feels off, disable one or two heavy extensions (linters and AI assistants tend to be the loud ones) and retest.
• Extension-heavy setups: Stage it. Create a fresh VS Code profile or use a clean user-data directory, then open your largest workspace and run your normal loop: search, debug, tests, terminal.
• Enterprise fleets and CI images: Roll out in rings. Push to a small canary group, watch crash reports and extension failures for a week, then expand. Test this twice if your developers can’t work without a specific extension.

How to upgrade (and how I verify it didn’t go sideways)

Keep it boring.

Upgrade paths vary by OS and package manager, but you can still do the same verification every time.

• In-app update: Open VS Code, then use Help > Check for Updates. Restart VS Code when it prompts you.
• Verify version: Open Help > About and confirm it shows 1.108.0. If you need CLI verification, run code –version in a terminal.
• Quick extension sanity check: Open your main repo, run one build, run one debug session, and watch the Extensions view for anything that fails to activate.

No, I can’t promise “no known issues.” The official notes don’t list any, but community reports pop up for every release. Monitor your own stack.

Known issues (what I’m willing to say out loud)

“Known issues: none” is a sentence I do not trust from any project.

The official release notes page does not list a known-issues section for 1.108.0. That does not mean nothing broke for anyone. If you run a weird mix of remote SSH, devcontainers, and a custom shell prompt, you already know the drill. Check your team’s top five extensions and your most cursed workspace before you declare victory.

Other stuff in this release: dependency bumps, some image updates, the usual.

Official links

Read the upstream notes and diff details if you need primary sources: the official VS Code v1.108 update page and the GitHub 1.108.0 tag release.