GitHub's May release cycle for Copilot in VS Code moves the editor closer to an agent-first workspace. The Agents window is now in Stable as a preview, while remote agents, session sync, BYOK model routing, and terminal safety controls make longer-running coding sessions easier to govern.

This is useful news for teams comparing local IDE agents with cloud agents: VS Code is becoming a command center for multiple sessions, changed-file search, screenshots, and model selection rather than only a chat sidebar.

Field|Current evidence
Primary source|GitHub: GitHub Copilot in Visual Studio Code, May releases
Source date|2026-06-03
Update scope|VS Code agent sessions, BYOK controls, sync, browser, and terminal safety
Verification note|Official source only; no search-result scraping, no ranking guarantee, no uncited claims

This update matters because the editor is moving from one chat pane to a multi-session control surface. The Agents window, changed-file search, screenshots, and session sync make it easier to compare work across agent attempts without leaving VS Code. BYOK support also changes procurement because teams can route work through approved model vendors.

Teams evaluating Copilot should test the full session lifecycle: start an agent task, inspect files changed, check terminal commands, resume the session on another machine, and confirm which model handled the work. That workflow is more important than a single prompt demo.

The decision point is whether VS Code should become the main operator console for agentic development. If developers already live in VS Code, these controls may reduce tool switching; if governance lives elsewhere, the team still needs audit exports and policy alignment.

Limits and open questions: the changelog does not settle enterprise rollout timing, default BYOK cost controls, or how every terminal safeguard behaves in complex repositories. Those claims should be verified against product docs or admin-console evidence before publication. Source handling note: KyenAI records the publisher, publication date, and source URL on the page, then keeps the update date tied to evidence-backed edits rather than automatic refreshes. When source material is thin, the system keeps interpretation narrow and waits for stronger documentation. Editorial review compares the new claim against the article summary, fact table, internal links, and listed source before allowing another optimization pass. Search outcomes are measured after publication rather than assumed at writing time.

GitHub's June 3 changelog highlights the Agents window preview, BYOK controls, session sync, terminal safety, and integrated browser improvements in VS Code.

VS Code agents

GitHub Brings Agent-First Workflows Deeper into VS Code Stable