Visual Studio Code 1.119
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. Visual Studio Code 1.119 Follow us on LinkedIn , X , Bluesky Release date: May 6, 2026 Update 1.119.1 : The update addresses these security issues . Downloads for 1.119.1 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the 1.119 release of Visual Studio Code.
This release focuses on smoother agent interactions, enhanced observability, and more efficient trust and security controls. Agent-browser interaction : Let agents discover and ask for integrated browser access. Optimized token usage : Use a lightweight model to manage agent todo lists. OpenTelemetry tracing : Monitor agent sessions with OpenTelemetry. Trust and developer efficiency : Get less interrupted by requests for network access or temp folder writes.
Markdown preview : Quickly switch between Markdown source and preview. Happy Coding! VS Code is rolling out gradually to all users. Use Check for Updates in VS Code to get the latest version immediately. To try new features as soon as possible, download the nightly Insiders build , which includes the latest updates as soon as they are available. Agent experience Sharing browser tabs with agents When agents can access a live browser, they validate changes in real time and iterate faster.
For web development, an agent can edit code, reload the page, and confirm the fix in a single turn. For design workflows, the agent can compare rendered output against your intent and refine layout or styling on the fly. Get started with using the integrated browser with agents in VS Code . An agent does not automatically have access to the integrated browser . You need to explicitly share browser pages with the agent for it to interact with them.
This helps keep sensitive data private. In this release, we've added new ways to share browsers with an agent: Attach browser tabs as context Browser tabs can now be explicitly attached to the chat via typical entry points such as suggested context, context picker, and drag-and-drop actions. When a browser tab is attached, it enters a sharing state where the agent can read and interact with the page. Use the sharing button in the browser to stop sharing when you're done.
Agents-initiated requests to share a page Agents now have information about how many browser tabs you have open and are not shared. They can request to share an open tab when they need to interact with a page, and you can approve or deny the request in a prompt. When an agent tries to open a new tab on the same domain as an existing, unshared tab, a prompt appears to ask if you want to reuse the existing tab. This aims to encourage tab reuse and reduce clutter.
Visual Studio Code Agents (Insiders) Note : Visual Studio Code Agents is currently in preview and only available with VS Code Insiders. Visual Studio Code Agents is a companion experience that ships with VS Code Insiders. It provides a focused, agent-native environment where you can run parallel sessions across repos and iterate on multi-step coding tasks. We first introduced VS Code Agents in 1.115 and continue to refine it based on user feedback.
Updates in this release include: Redesigned new session repo picker : When you start a new session, you can now easily switch between local folders, repos, or remote options. Sub-session improvements : Creating and managing sub-sessions continues to improve, with fixes in areas such as sub-session tabs and lifecycle handling. Web and mobile polish : We continue to iterate on the Agents web client introduced in 1.118 to align the browser experience with the desktop experience.
This includes improvements to the mobile experience, so that you can create and manage sessions and their changes from the browser of your mobile device. Environment management and continuity : We continue investing in the connections between VS Code and Agents and evolving how the environment is managed. This continues to take shape in future releases. Progress UX : When an agent is working on a task, its progress is now more visible, with rotating progress messages and border animations for the chat input box.
Developer joy : We're iterating on UX opportunities to spark developer joy, including a fun easter egg on the new session page. Enable sessions.developerJoy.enabled Open in VS Code Open in VS Code Insiders to see if you can spot it! Your feedback helps us shape the Agents experience, so continue sharing it with us by filing issues in the vscode GitHub repo . You can also explore existing issues to see what others have reported and provide your feedback on specific topics.
OpenTelemetry tracing for agent sessions Settings : github.copilot.chat.otel.enabled Open in VS Code Open in VS Code Insiders , github.copilot.chat.otel.otlpEndpoint Open in VS Code Open in VS Code Insiders As agent sessions grow longer and more autonomous, understanding what the agent did, how long each step took, and where tokens were spent becomes essential for optimizing cost and debugging unexpected behavior. OpenTelemetry is the industry-standard observability framework.
Copilot Chat agent sessions, including the local agent, the Copilot CLI background agent, and the Claude agent, now emit OpenTelemetry traces, metrics, and events that follow the GenAI semantic conventions , so you can monitor agent behavior, latency, and token usage in any OTLP-compatible backend (for example, the Aspire Dashboard ). Each user request produces an invoke_agent root span (for example, invoke_agent claude ) with nested chat , execute_tool , and execute_hook child spans.
Subagent invocations are automatically parented to the calling agent's execute_tool span, giving you full visibility into the agent's work in a single connected trace. Spans report model and token usage, including cache read and cache creation breakdowns. To try it out, enable github.copilot.chat.otel.enabled Open in VS Code Open in VS Code Insiders and point github.copilot.chat.otel.otlpEndpoint Open in VS Code Open in VS Code Insiders to your collector.
Learn how to monitor agent usage with OpenTelemetry in the VS Code documentation. Chat experience Show model details for Copilot CLI and Claude agent responses Setting : github.copilot.chat.agent.modelDetails.enabled Open in VS Code Open in VS Code Insiders Knowing which model handled a response and how it counts against your usage helps you stay in control of cost and quality. Copilot CLI and Claude agent responses in the Chat view now show the model and its multiplier on each response.
The badge appears live as each response completes, without needing to reload the window, and updates when you switch models mid-session. When you use Auto model selection in Copilot CLI, the badge displays the actual model that was used (for example, Claude Sonnet 4.6 ) instead of auto . The resolved model is also preserved when the session is rebuilt from history. The behavior is enabled by default. To turn off the badge, disable the github.copilot.chat.agent.modelDetails.enabled Open in VS Code Open in VS Code Insiders setting and reload the window.
Optimized token usage for managing todo lists (Experimental) Setting : github.copilot.chat.agent.backgroundTodoAgent.enabled Open in VS Code Open in VS Code Insiders Todo lists help an agent stay on track during complex, multi-step tasks by giving it an explicit record of what's been done and what comes next. However, every tool call the main model makes to update a todo list costs tokens, and those costs add up across long sessions.
By offloading todo list management to a lightweight background agent, the main model can focus on the actual task while a smaller model keeps progress tracking in sync. This reduces overall token usage without sacrificing the guidance that keeps the agent focused. When this setting is enabled, the background agent monitors main agent activity and updates the to
The rest of this page is on the live site.