If you've ever been deep in an AI-assisted coding session and got interrupted by one approval popup after another, you know the pain. It's like trying to watch a movie and someone keeps pausing it to ask, "Are you sure? Are you really sure?"
VS Code 1.130, released on July 22, 2026, quietly fixes a lot of those friction points. And along the way, it brings some genuinely useful upgrades to agent workflows, chat visibility, terminal file links, and more.
So — what actually changed, and does any of it matter in your daily dev life? Let's walk through it. 🚀
What Is VS Code 1.130?
VS Code releases updates on a regular cadence. Version 1.130 is the latest stable release, and it's focused heavily on making AI agent sessions smoother and more manageable.
If you use GitHub Copilot, Claude, or Codex inside VS Code, this update is directly relevant to your workflow. Even if you don't, there are quality-of-life improvements worth knowing about.
Why This Release Matters
The way we write code is changing fast. AI coding agents now handle multi-file edits, run terminal commands, and take actions on your behalf — all inside the editor.
But managing those agents has been clunky. You'd approve tool after tool manually, get lost in long diff views, and lose track of what the agent actually changed.
VS Code 1.130 addresses these pain points directly. The team has rearchitected how agent sessions work, improved how you review changes, and added smarter ways to handle approvals.
If AI-assisted coding is already part of your workflow, this update makes it noticeably cleaner. If it isn't yet, now is a good time to start paying attention.
What's New in VS Code 1.130
🔧 The Agent Host — A Smarter Foundation for AI Sessions
The biggest architectural change in this release is the agent host.
Think of it like moving your AI coding session into its own dedicated room, instead of running it in the same crowded space as everything else. The agent host is a separate process that runs agent harnesses — including Copilot, Claude, and Codex — based on the Agent Host Protocol (AHP).
Why does that matter? Because now the same agent session can be connected to and rendered from multiple VS Code windows at once. You can have your agent running in one window and check its progress from another — no need to restart or duplicate work.
The Copilot agent on the agent host is also powered by the Copilot SDK, which aligns it with the Copilot CLI, the standalone GitHub Copilot app, and other Copilot products. This means more consistent behavior across tools.
To try it, enable chat.agentHost.enabled and select an agent host harness from the harness dropdown.
✅ Assisted Tool Approvals — Fewer Interruptions, Smarter Decisions
Setting: chat.assistedPermissions.enabled
Here's the one that's going to save you the most frustration.
When an AI agent runs a task, it often calls multiple tools along the way — reading files, running commands, making edits. Each tool call can trigger an approval prompt. On a long-running task, those prompts stack up fast and break your flow.
With assisted tool approvals, the language model itself evaluates the risk level of each tool call. Low-risk actions can run automatically. Only genuinely risky actions ask for your approval.
It's like having a capable assistant who uses good judgment — they handle the routine stuff and only interrupt you when something actually needs your sign-off.
Enable the setting to add Assisted permissions to the permissions picker for agents running on the agent host.
👀 Agents Window Improvements (Preview)
The Agents window got a meaningful round of upgrades. Here's what changed:
File-level diff statistics
Each file header in the Changes editor now shows live insertion and deletion counts next to the file path. No more guessing how much each file changed — you can scan a multi-file diff and immediately know which files were touched heavily and which had minor edits.
Compact multi-file diff view
The diff view now uses a tighter gutter layout. Empty space before the code is removed. File headers, line numbers, and unchanged-region controls share consistent alignment. More room for actual code review — especially helpful on narrower screens.
Compact quick chats
Quick chats now appear as single-line rows in the sessions list. Regular sessions still show a second line with stats, status, and timestamps. This makes it easier to tell quick chats from full project sessions at a glance.
Worktree support for all agent harnesses
Previously, the New Worktree checkbox in the Agents window only worked with the Copilot harness. Now Claude and Codex sessions also support Git worktrees, so you can spin up parallel sessions for different features in the same workspace — regardless of which agent you're using.
💬 Chat Timestamps
Setting: chat.verbose
Small addition, surprisingly useful. Chat requests and responses now show timestamps. You can hover over the message toolbar to see when an interaction happened and how long it took.
If you've ever come back to a chat session and had no idea whether those edits were from two minutes ago or two hours ago, this solves that problem. You can disable it with chat.verbose if you prefer a cleaner view.
📊 Aggregate AI Credit Usage for Copilot Business and Enterprise
If your organization uses Copilot Business or Copilot Enterprise, you can now see your total AI credit usage for the current billing cycle directly in the Copilot status menu.
Before this change, credit usage only appeared when you had a user-level budget configured. Most org-managed users had no way to see how many credits they'd consumed.
Now, even without a user-level budget set, the status menu shows the total credits used so far in the billing cycle. It's a small thing, but it helps you understand your usage without leaving the editor.
⚡ Clickable File Links in Git Diffs with Mnemonic Prefixes
This one's for terminal users.
When Git's diff.mnemonicPrefix option is enabled, Git diff output uses prefixes like i/ for the index and w/ for the working tree. These look informative but have historically made file paths in terminal output non-clickable.
VS Code 1.130 now recognizes those prefixes and removes them from the link target so the correct file opens when you click. VS Code also handles the numeric 1/ and 2/ prefixes produced by git diff --no-index.
If you rely on terminal-based Git workflows, this removes a small but real piece of friction.
🏗️ TypeScript 7 — Under the Hood
The VS Code codebase is now compiled using the release version of TypeScript 7. The team also switched to the TypeScript 7 extension.
This is an engineering milestone more than a user-facing feature, but it signals a big step in the TypeScript ecosystem. If you want to read more, the TypeScript team published a full release announcement worth checking out.
Before vs. After: Agent Workflows in VS Code
| Before 1.130 | After 1.130 |
|---|---|
| Approval prompt for every tool call | Model evaluates risk; low-risk calls run automatically |
| Agent session tied to one window | Same session visible from multiple windows |
| Worktrees only for Copilot harness | Worktrees work for Claude and Codex too |
| No timestamps in chat | Timestamps visible on hover |
| Mnemonic prefix paths not clickable in terminal | Clickable and correctly resolved |
| Credit usage hidden without user budget | Total usage shown in status menu |
Best Tips for Getting the Most Out of VS Code 1.130
💡 Enable the agent host gradually. It's still rolling out and some features require it. Start by enabling chat.agentHost.enabled and testing your preferred harness.
💡 Try assisted permissions on a low-stakes project first. It's a smart feature, but get familiar with how the model evaluates risk before relying on it for critical tasks.
💡 Use worktrees for parallel feature work. Now that Claude and Codex support them, you can run separate agent sessions for different branches without interfering with your main workspace.
💡 Check the Copilot status menu if you're on a Business or Enterprise plan. Knowing your credit usage in real time helps you plan more effectively.
💡 Enable mnemonic prefixes in Git if you use the terminal heavily. The clickable link support makes diff navigation genuinely faster.
Common Mistakes to Avoid
Skipping the update and wondering why new features aren't showing up.
VS Code 1.130 is rolling out gradually. If you want it immediately, use Check for Updates in VS Code. Or download the Insiders build if you always want the latest.
Enabling assisted permissions and forgetting about it.
This feature is smart, but it's not infallible. The model makes judgment calls. Keep an eye on what runs automatically, especially in the early days of using it.
Confusing quick chats and project sessions in the Agents window.
The compact row style makes quick chats visually distinct from regular sessions. Take a few minutes to understand the new layout so you don't accidentally close a session you wanted to keep.
Ignoring the chat timestamp feature.
It sounds minor. But if you run long sessions or collaborate on the same workspace, knowing when an AI interaction happened can save real debugging time.
Wrapping Up
VS Code 1.130 isn't a flashy release, but it's a thoughtful one. The team is building toward a more stable, more capable foundation for AI-assisted development — and the improvements in this release show real progress.
The agent host architecture is the biggest story here. It's still rolling out, but once it lands fully, it's going to change how agent sessions feel in a meaningful way. Fewer interruptions, more visibility, better multi-harness support — it all adds up.
If you work with AI coding agents regularly, update today and explore the new settings. The improvements are subtle but genuinely useful.
And if you're just starting to explore AI-assisted coding in VS Code, this is a solid time to dive in. The tooling is getting better with every release. 😊
Happy coding — and as always, keep building things that matter.
Want more practical dev content like this? Head over to *hamidrazadev.com** for more articles, guides, and resources. If this post saved you some time or taught you something new, share it with a fellow developer — it goes a long way.* 🙌
Top comments (0)