VS Code 1.125: Agents Can Now Browse Through Remote Proxies — and You'll See Copilot Overage Coming

TL;DR: VS Code 1.125 ships an agent-aware browser proxy for remote workspaces and a Copilot budget gauge to catch overage charges before they hit.

The June 17 release addresses two practical pain points for teams running AI coding agents in VS Code:

Agent-aware port proxying (Remote workspaces): When agents request forwarded ports in a remote VS Code session (SSH, dev containers, Codespaces), the built-in browser now rewrites the URL correctly and notifies the agent of any address changes. Previously, agents silently failed when trying to open local staging services — a broken redirect they couldn't recover from without human intervention. HTTP/HTTPS traffic routes through the remote connection; no manual tunnel required.

Copilot budget monitoring: Since Copilot moved to token-based AI Credits on June 1, teams on additional-usage plans had no in-editor visibility into consumption. VS Code 1.125 adds a percentage gauge to the Copilot status bar so you see how much of your additional monthly budget has been used — before you get a billing surprise at month-end.

Enterprise MDM delivery: Copilot settings can now be enforced via Windows and macOS device management policies without requiring per-user sign-in, giving IT teams a centralized enforcement path.

Why it matters: The port-proxy fix unblocks a real workflow — agents running inside remote environments were silently failing at a common step. The budget gauge is a guardrail most Copilot-heavy teams didn't know they needed until after the June 1 credits switch.

Sources: VS Code 1.125 Release Notes