Follow us on LinkedIn, X, Bluesky, Instagram | Follow Insiders Changelog on X or Bluesky
Last updated: September 8, 2026
Welcome to the 1.138 Insiders release of Visual Studio Code.
These release notes cover the Insiders build of VS Code and continue to evolve as new features are added.
You can still track our progress in the Commit log and our list of Closed issues.
Happy Coding!
September 8, 2026
-
Agent Host sessions and chats provide browser-addressable links, making it easier to reopen or share a specific Agents window session from another app, issue, or terminal output. #334963
-
You can create a new Agent session beside the current one in one step, so you can keep the current work visible while starting another session. #334508
-
When you start an Agent session without a workspace, you can attach issue or pull request context by choosing the repository first. #335064
-
Voice mode has more accurate Agent session awareness, including finding recent sessions, switching between them, and reporting current session status. #334600
September 7, 2026
- Setting: editor.forceFullwidthCharacterWidth enables full-width characters to occupy exactly two cells when you use a monospace editor font, improving alignment for CJK text in tables, comments, and other grid-like editor content. #155588
September 5, 2026
- Agent Host offers the Claude or Codex SDK download action whenever the selected agent needs its SDK, so setup recovery is available outside signed-out account setup. #334675
September 4, 2026
-
Agent Host resolves sandbox defaults consistently with the shared runtime, reducing surprises when the same managed sandbox policy is used across clients. #334275
-
The Agents window workspace picker uses a unified searchable list for local folders, GitHub repositories, Cloud repositories, and remote targets, while keeping remote connection actions available in the Remote entry. #334563
September 3, 2026
- Agent sessions with merged pull requests can be configured to archive inactive sessions, permanently delete automatically archived sessions after a grace period, and remove safe worktrees, giving users and admins more control over agent-session cleanup. #334352
September 1, 2026
- Agents chat background image layout preferences are saved separately for light and dark themes, so switching themes preserves each theme's alignment. #333690
We really appreciate people trying our new features as soon as they are ready, so check back here often and learn what's new.
Facts Only
Visual Studio Code 1.138 (Insiders) was updated on September 8, 2026.
Agent Host sessions and chats now include browser-addressable links.
Users can create new Agent sessions adjacent to current sessions.
Repository selection now allows attaching issue or pull request context to sessions without a workspace.
Voice mode supports finding recent Agent sessions and reporting session status.
The setting editor.forceFullwidthCharacterWidth allows full-width characters to occupy two cells in monospace fonts.
Agent Host provides download actions for Claude or Codex SDKs.
Agent Host sandbox defaults are now consistent with the shared runtime.
The Agents window workspace picker uses a searchable list for local folders, GitHub, Cloud repositories, and remote targets.
Agent sessions with merged pull requests can be configured for automatic archiving and permanent deletion.
Agent chat background image layout preferences are saved separately for light and dark themes.
Executive Summary
Visual Studio Code 1.138 (Insiders) introduces a series of updates primarily focused on expanding the functionality of "Agent Host" and improving editor accessibility. Key enhancements to the Agent environment include the implementation of browser-addressable links for sessions, the ability to launch concurrent sessions, and a unified workspace picker that aggregates local folders, GitHub, Cloud repositories, and remote targets. Integration improvements allow for attaching issue or pull request context when starting sessions without a workspace and provide a streamlined SDK download process for Claude or Codex.
Beyond AI agents, the update addresses CJK text alignment through a new setting that forces full-width characters to occupy two cells in monospace fonts. Administrative controls have also been added to manage the lifecycle of agent sessions, including automated archiving and deletion for merged pull requests. These updates reflect an ongoing effort to refine the intersection of autonomous agent workflows and traditional IDE environment management.
Full Take
The strongest version of this narrative is a technical changelog detailing the incremental evolution of an Integrated Development Environment (IDE) moving toward an "Agent-centric" workflow. It presents a shift where the IDE is no longer just a text editor, but a coordinator for autonomous AI entities (Agents) that manage their own sessions, SDKs, and cloud-remote contexts.
The pattern here is the gradual normalization of the "Agent Host" as a primary architectural layer. By introducing browser-addressable links and session-lifecycle management (archiving/deletion), the software is treating AI sessions as first-class citizens, akin to how a browser treats tabs or an OS treats processes. The move toward a unified workspace picker—blurring the line between local folders and remote cloud repositories—suggests a paradigm where the physical location of code is secondary to the Agent's ability to access it.
This trajectory suggests a future where human agency shifts from "writing code" to "orchestrating agents." The benefit is a massive increase in velocity and context-handling. The cost is a potential erosion of deep system knowledge, as the "Agent" becomes the primary interface between the developer and the codebase. If the Agent handles the SDK setup and the session context, the developer may lose visibility into the underlying plumbing of their own environment.
Patterns detected: none
If this were a coordinated influence campaign, the playbook would involve "feature-creep" to create dependency, making the user so reliant on Agent orchestration that switching to a manual workflow becomes cognitively expensive. The current content is a standard technical release log and does not match this manipulative pattern.
Bridge Questions:
1. As IDEs move toward session-based Agent orchestration, how does the mental model of "project structure" change for the developer?
2. What happens to developer sovereignty when SDK recovery and environment setup are abstracted into "download actions" managed by the Agent?
