VS Code just dropped another release, and this one feels different. š
Not in a "they changed a color somewhere" kind of way. More like "wait, the editor just started doing things I used to do manually, and I can now talk to it." VS Code 1.137, released on September 9, 2026, is packed with features that push the editor closer to a real AI-powered coding partner.
If you've ever thought, "I wish my editor could just handle this on its own while I grab a coffee" ā this release was made for you.
Let's break down everything that's new, what it actually means for your workflow, and how to get the most out of it.
What Is VS Code 1.137?
VS Code 1.137 is the latest stable update to Visual Studio Code, Microsoft's widely used free code editor. This version focuses heavily on agent-powered automation, smarter chat workflows, voice interaction, and better GitHub integration ā all without ever leaving your editor.
Think of it as VS Code leveling up from "smart assistant" to "proactive team member." It's still your editor. It just does more now.
Why This Release Matters
Here's the thing: most developers spend a big chunk of their day on repetitive work. Triaging issues. Catching up on recent changes. Reviewing pull requests. Switching between tools ā editor, browser, GitHub, back to editor.
VS Code 1.137 tackles all of that head-on. You can now:
- Schedule agent tasks to run on a timer, like a cron job but for AI
- Talk to the agent with your voice and interrupt it while it's working
- Review GitHub issues and pull requests right inside the editor
- Continue a quick chat even after deciding it needs a full workspace
This isn't just a list of shiny features. These are actual developer pain points getting solved.
Key Features ā What's New and Why It's Useful
ā” Automations (Preview): Let the Agent Handle the Routine Stuff
Setting: chat.automations.enabled
You know those Monday morning tasks that are the same every single week? Checking what changed over the weekend, scanning for new bugs, triaging open issues? You can now schedule a Copilot agent task to handle those automatically ā hourly, daily, or weekly.
You pick a template (catching up on changes, triaging issues, finding bugs) or write your own prompt. Set the schedule. Done.
This is genuinely one of those features where the first time it runs and saves you 20 minutes, you'll wonder how you worked without it.
How to try it: Enable chat.automations.enabled, open the Agents window, and select Automations in the sidebar.
Note: Automations is in Preview and rolling out gradually.
šļø Voice Mode (Experimental): Talk to Your Agent Like a Human
Setting: agents.voice.enabled
This is the feature people will demo at meetups. Voice Mode lets you have a real spoken conversation with the Copilot agent while it works on your code.
And the useful part? You can interrupt it. While the agent is speaking or working, you can jump in with a new instruction or correction ā just like you would with a teammate. No waiting for it to finish before you can redirect it.
You can also:
- Show a live transcript in the chat input (
agents.voice.showTranscript) - Choose which voice reads responses aloud (
agents.voice.voice) - Pick your input microphone from the Command Palette
It's aware of your active session too ā so you can ask things like "which model are we using?" or "what files are attached?" and it'll answer correctly.
How to try it: Enable agents.voice.enabled, then select the Voice Mode button in the chat input.
š GitHub Issues and Pull Requests, Right in the Agents Window (Experimental)
Setting: extensions.experimental.enableAgentsWindowCapability
This one is a workflow changer for teams using GitHub.
Normally, when a chat conversation references a GitHub issue or PR, you'd click the link, open it in the browser, read through it, come back. VS Code 1.137 removes that detour. Select a github.com issue or pull request link and its details open directly in the Agents window ā even if the repository isn't open locally.
You can also add GitHub issues or pull requests as context using the Add Context... menu in any chat input. The description, comments, or PR changes become available to the agent without you copy-pasting anything.
Or paste a GitHub URL directly into the chat ā VS Code automatically adds it as a context attachment.
To enable: Install the GitHub Pull Requests extension and enable extensions.experimental.enableAgentsWindowCapability.
š¬ Continue Quick Chats in a Workspace
This one's subtle but genuinely useful.
You start a quick chat to explore an idea ā maybe you're not sure if it's project-specific yet. The conversation develops, and it turns out you do need access to project files.
Before, you'd have to start over in a workspace session and lose your chat history. Now, you just ask the Copilot agent to attach a local folder. After you confirm, the chat converts into a workspace session ā keeping its title, conversation history, and current request. The agent picks up right where it left off, now with access to your files.
š¤ Agent Host and Parallel Agent Workflows
VS Code 1.137 introduces a few important agent infrastructure improvements worth knowing about.
Agent-queued messages let you keep agents working in parallel. If an agent tries to contact a busy chat, VS Code queues the message and processes it in order once the active turn finishes. No interruptions, no lost messages.
The agent host lets you connect to the same agent session from multiple VS Code windows. It runs agent harnesses in a dedicated process and aligns behavior with the Copilot CLI and the standalone GitHub Copilot app.
š Smart Diff Editor and Binary Files in Diffs
Small but polished improvements to the diff editor:
- You can now choose Inline, Side by Side, or Automatic layout consistently across regular diffs, multi-file diffs, and the Agents window Changes editor.
- Binary files (like images) now stay visible in multi-file diffs instead of disappearing. You'll see a "Binary file changed" placeholder, and you can select Open Diff to review the file properly.
š GitHub Rich Links in the Markdown Editor (Experimental)
Settings: markdown.experimental.richLinks.enabled, chat.experimental.richLinks.enabled
Paste a GitHub issue or PR link in your Markdown editor and it shows the current title and status inline ā including CI updates. No more opening the browser just to check if an issue is still open or a PR was merged.
Set chat.experimental.richLinks.enabled to true to get the same behavior in chat.
Before vs. After: How 1.137 Changes Your Daily Workflow
| Situation | Before 1.137 | After 1.137 |
|---|---|---|
| Weekly issue triage | Manual, every time | Scheduled automation handles it |
| Redirect an agent mid-task | Wait for it to finish | Interrupt with Voice Mode |
| Review a PR in a chat context | Open browser, copy info, paste back | Add as context or click the link in Agents window |
| Quick chat ā workspace | Restart conversation | Continue same chat, history intact |
| Binary file in multi-file diff | Invisible ā just missing | Placeholder shown, Open Diff available |
| GitHub link in Markdown | Just a URL | Live title and status inline |
Practical Tips for Getting the Most Out of VS Code 1.137
ā Do's
- Enable Automations for recurring tasks first. Start with one of the built-in templates. See what it does automatically before writing your own prompt.
- Try Voice Mode with a clear workspace. It works best when you have a session active and files attached. Give it a focused task.
- Install the GitHub Pull Requests extension before trying the Agents window GitHub integration. It's required.
- Use Add Context from the chat menu when discussing GitHub issues. It's cleaner than copy-pasting descriptions.
- Update to 1.137 immediately using Check for Updates, or download the Insiders build if you want the latest features even earlier.
ā Don'ts
- Don't expect Voice Mode to replace the keyboard entirely ā it's a conversation layer, not a full replacement.
- Don't skip reading the automation output. Even scheduled agent tasks need a human review occasionally.
- Don't paste GitHub URLs into chat expecting context without the GitHub Pull Requests extension installed.
- Don't use the Agents window GitHub integration without enabling
extensions.experimental.enableAgentsWindowCapabilityfirst ā nothing will work.
Common Mistakes Developers Make with New VS Code Features
1. Enabling everything at once and getting confused
It's tempting to flip on every experimental setting and see what happens. The problem is, when something doesn't work as expected, you won't know why. Enable features one at a time so you understand what each one does.
2. Ignoring the "rolling out gradually" note
Some features in 1.137, like Automations, are not available to everyone on day one. If you enable the setting and don't see the feature, wait a day or check the Insiders build.
3. Writing automation prompts that are too vague
"Check things" is not a useful automation prompt. "Summarize any new issues opened in the last 24 hours and flag ones labeled 'bug'" is. The agent follows the prompt you give it. Be specific.
4. Forgetting to install the required extension
The GitHub integration in the Agents window needs the GitHub Pull Requests extension installed in your default VS Code profile. If you use separate profiles, make sure it's in the right one.
5. Not trying the quick-chat-to-workspace transition
This feature is easy to overlook because it solves a problem you might not realize you're having. Next time you start a quick chat that grows into something project-specific, try attaching a workspace instead of starting over.
Conclusion
VS Code 1.137 is a thoughtful release. It's not just adding features for the sake of it ā it's solving the annoying, repetitive, context-switching parts of a developer's day.
Scheduled automations mean your routine tasks can run without you. Voice Mode means you can direct the agent without stopping to type. GitHub integration means you never have to leave your editor to check an issue. And continuing quick chats in a workspace means your conversational momentum doesn't get lost when work gets real.
It's a genuinely good update. š
Give it a try, explore the experimental features, and see which ones fit naturally into your workflow. Chances are at least two of them will stick.
If you found this helpful, share it with a teammate who still manually triages issues every Monday morning. They'll thank you.
For more practical dev tutorials, tools, and blog posts like this, head over to hamidrazadev.com ā there's plenty more where this came from. š§
Top comments (0)