VS Code 1.109.0 Release Notes: Claude Agents, Integrated Browser, and the Stuff People Actually Mention

Reddit’s already arguing about this one.

The consensus seems to be “yeah, upgrade,” mostly because 1.109 tightens Copilot Chat and adds an integrated browser preview, but Linux folks keep side-eyeing the Snap packaging situation.

Community take: what people are saying this week

I’ve watched teams treat VS Code updates like Chrome updates. They just happen, until they don’t.

On the k8s and devtools Slacks, the vibe around 1.109 feels practical: frontend folks like the in-editor browser, AI-heavy teams like having Claude in the mix, and ops-minded people immediately ask “where do the keys go?”

• Most teams are upgrading for Copilot Chat and agents: The chatter I see centers on “agent sessions feel less sticky now” and “streaming feels snappier,” not on big editor changes.
• Linux users keep bringing up Snap disk usage: Some teams report deleted files piling up in a snap-local Trash folder and eating disk. Others say “just use .deb and move on.” Either way, do not write “no known issues.”
• Frontend devs like the integrated browser preview: As one SRE put it, “anything that kills the alt-tab loop is worth trying,” but they still keep Chrome open for real debugging.

So. If you run VS Code via Snap on Linux, read the community reports before you hit update.

If you install via .deb/.rpm or you sit on macOS/Windows, you probably won’t notice drama. You’ll just notice new toys.

Official changelog recap (what 1.109.0 actually ships)

The official notes call out three big buckets: chat improvements, multi-agent workflows, and the new integrated browser preview.

They also sneak in a couple operational changes people miss until their terminal stops working on an old Windows VM.

• Claude Agent support (Preview): VS Code adds Claude agent support through Anthropic integration in Copilot Chat. Expect “preview” sharp edges, and expect your security team to ask where the Anthropic API key lives.
• Integrated browser (Preview): VS Code can open a browser inside the workbench with DevTools. You can test localhost flows and keep it in a tab next to your code.
• Chat UX changes: The notes mention faster streaming and better reasoning display. You feel this as “less waiting for the full blob,” not as magic correctness.

Two more official bits matter for upgrades, even if they don’t sound exciting.

VS Code deprecates the old Copilot extension in favor of Copilot Chat, and VS Code also removes winpty support, which can hit older Windows installs.

My synthesis: who should upgrade now, who should test first

Upgrade if you use chat daily.

I do not think “feature release, upgrade immediately” is always smart, but 1.109 lands in the category where most teams won’t regret it, unless you sit on a brittle packaging path or an old Windows baseline.

• Upgrade now if you live in Copilot Chat: If your day includes “ask for a refactor,” “write tests,” and “explain this stacktrace,” you’ll notice the streaming and session workflow tweaks.
• Test first if you manage a fleet image: If you bake VS Code into a golden image, test the Copilot extension deprecation behavior. Extensions disappearing during an update creates fun tickets.
• Be paranoid on Linux Snap: If your devs install from Snap, you should probably prefer .deb/.rpm for now, or at least warn people to check disk usage and Trash behavior after updating.

Ignore the GitHub commit count. It’s a vanity metric. I care about “does my terminal still work,” and “did my extensions behave.”

How to upgrade (and what I check right after)

Keep it boring.

Restart VS Code when it prompts you, then do a quick smoke test before you trust it with an incident.

• Confirm the version: Open Help, then About, and verify you see 1.109.0.
• Smoke test the terminal: Open a terminal, run node -v or python –version, and make sure the shell actually starts.
• Smoke test chat: Ask Copilot Chat to explain a small function. Watch streaming. If it lags or stalls, you’ll notice immediately.

Quick usage examples (the stuff people will try first)

People won’t read a long guide before clicking buttons.

They’ll try the browser tab, then they’ll try Claude, then they’ll ask why auth or keys feel weird.

• Try the integrated browser preview: Open a local web app, then open it in the integrated browser. Use DevTools to check network calls, especially auth redirects, because embedded browsers love to surprise you.
• Try Claude in chat (if your org allows it): Add your Anthropic key per your org policy, then select a Claude model for review-style prompts. Keep an eye on what context you share. “Paste the whole repo” turns into a compliance conversation fast.
• Run two agent sessions on purpose: Put one agent on “write tests,” another on “document behavior,” then see if session switching feels sane. This is where the update pays off if you actually work that way.

Known issues (official vs community)

The official notes do not list a known-issues section.

The community still reports issues, especially around VS Code on Linux via Snap and disk usage related to Trash behavior. If you hit that, switch install methods and move on with your life.

There’s probably a better way to test this, but…