{"slug": "vs-code-1-125-remote-browser-fix-and-what-else-changed", "title": "VS Code 1.125: Remote Browser Fix and What Else Changed", "summary": "Microsoft released VS Code 1.125 on June 17, fixing the remote browser proxy for SSH tunnels, adding a two-hour delay for extension auto-updates to improve security, and introducing a Copilot budget dashboard in the status bar. The update also removes Edit Mode, a Copilot Chat feature, and includes device emulation in the integrated browser.", "body_md": "VS Code 1.125 dropped June 17 — the 15th weekly stable release since Microsoft scrapped its decade-long monthly cycle in March. Last week’s 1.124 got the headlines with Autopilot enabled by default. This one is quieter. But the remote browser fix, the extension update delay, and the new Copilot budget dashboard all change something real in how developers work. One breaking change: Edit Mode is gone for good.\n\n## The Remote Browser Finally Works in Remote Environments\n\nVS Code has had an integrated browser for a while. What it didn’t have was a working remote proxy — meaning when you were connected to a remote host over SSH, the browser couldn’t route through that connection cleanly. Port forwarding required manual setup, and URL rewrites broke constantly.\n\n1.125 fixes this. The integrated browser now proxies web traffic securely through your SSH tunnel. Forwarded port URLs rewrite automatically so the browser — and any AI agent using it — can reach the right local address on the remote host without guessing.\n\nDevice emulation is also now built into the integrated browser: screen sizes, mobile/touch emulation, custom user agents. For developers doing responsive testing or running browser-based verification steps in automated agent workflows, this removes the need to alt-tab to Chrome.\n\nThis matters most to developers running VS Code in remote environments: GitHub Codespaces, SSH sessions, dev containers, cloud-hosted workstations. AI agents that need to open a browser to verify their own output — a common agentic workflow pattern — now work without workarounds. The [official release notes](https://code.visualstudio.com/updates/v1_125) cover the full implementation details.\n\n## Extension Updates Now Wait — and That’s a Security Feature\n\nVS Code 1.125 adds a new `extensions.autoUpdateDelay`\n\nsetting with a default delay of two hours before extension updates install automatically. Disabled extensions no longer get silently updated in the background.\n\nThe timing is pointed. On June 18, 15 JetBrains IDE plugins with 70,000 combined installs were found stealing AI API keys. VS Code extensions are a different ecosystem, but the attack surface is the same: a legitimate extension gets compromised, a malicious update ships, auto-update installs it before anyone notices.\n\nA two-hour window does not block a determined attacker. But it gives security teams time to catch flagged extension updates before they land on developer machines. The silent update of disabled extensions was also a straightforward bug — extensions you turned off should not be updating themselves.\n\n```\n// settings.json\n\"extensions.autoUpdateDelay\": 120  // minutes, default is 120\n```\n\nAdmins can also lock this setting at the organization level via MDM. [Security researchers note](https://cipherssecurity.com/vs-code-extension-delay-supply-chain-security/) that this is necessary but not sufficient — extension signatures and runtime sandboxing are the real fix, but a delay buys time during active incidents.\n\n## Copilot Budget Monitoring Is Now in the Status Bar\n\nThe Copilot status dashboard in VS Code 1.125 now shows the percentage of your additional Copilot budget consumed — inline suggestions quota and AI credits, visible in the Status Bar.\n\nGitHub Copilot moved to token-based billing on June 1. Reports of bills jumping from $29 to $750 per month spread quickly across developer forums. Knowing your burn rate is not optional anymore. Having that information in the IDE — not buried in GitHub billing pages — is the right place for it. You should not be surprised mid-session that you have hit your limit.\n\nThe [GitHub documentation on Copilot spending](https://docs.github.com/en/copilot/how-tos/spending/monitoring-your-copilot-usage-and-entitlements) covers how to set budget caps so usage stops automatically when you hit a threshold — worth configuring alongside this new dashboard visibility.\n\n## Edit Mode Is Gone — What to Do\n\nEdit Mode — the distinct edit-focused Copilot Chat workflow — is fully removed in 1.125. It was deprecated since v1.110 and could be re-enabled via `chat.editMode.hidden`\n\nthrough last week. That setting is now inert.\n\nThe migration path is Agent Mode. Microsoft indicated when deprecating Edit Mode that a custom Agent Mode preset would replicate the previous Edit behavior. If your workflow breaks after this auto-update, open Copilot Chat and switch to Agent Mode — it handles the same file-editing tasks with more capability.\n\n## Enterprise: Copilot Policies via MDM\n\nOrganizations can now deliver Copilot compliance settings through native Windows MDM and macOS MDM tooling — Jamf, Intune, and similar systems — without requiring per-user configuration or account-based settings files. MDM-delivered settings appear as policy-enforced in VS Code and cannot be overridden locally. As the EU AI Act high-risk AI provisions take effect in August 2026, enterprises need device-level auditability for AI tool use. This delivers it.\n\n## How to Get It\n\nVS Code auto-updates. If you have auto-update enabled, 1.125 is either already installed or arriving within the next update cycle. Check **Help → About** to confirm your version. Full release notes are at [code.visualstudio.com/updates/v1_125](https://code.visualstudio.com/updates/v1_125).", "url": "https://wpnews.pro/news/vs-code-1-125-remote-browser-fix-and-what-else-changed", "canonical_source": "https://byteiota.com/vs-code-1-125-remote-browser-fix-and-what-else-changed/", "published_at": "2026-06-18 23:11:35+00:00", "updated_at": "2026-06-18 23:39:46.640148+00:00", "lang": "en", "topics": ["developer-tools", "ai-tools", "ai-safety"], "entities": ["Microsoft", "VS Code", "GitHub Copilot", "GitHub Codespaces", "JetBrains"], "alternates": {"html": "https://wpnews.pro/news/vs-code-1-125-remote-browser-fix-and-what-else-changed", "markdown": "https://wpnews.pro/news/vs-code-1-125-remote-browser-fix-and-what-else-changed.md", "text": "https://wpnews.pro/news/vs-code-1-125-remote-browser-fix-and-what-else-changed.txt", "jsonld": "https://wpnews.pro/news/vs-code-1-125-remote-browser-fix-and-what-else-changed.jsonld"}}