Visual Studio Code 1.147

Downloads for 1.147.0

Windows
x64Arm64

Release highlights

Have a task in mind but not ready to send it? This week, save requests as drafts or schedule them for later. When you're ready, let a model router match the task to your preferred model. And when a result is easier to show than explain, ask for a chart or mockup.

Watch release highlights

Happy coding!

Already installed? Use Check for Updates in VS Code. For upcoming features, use the Insiders build.

Agent sessions

Send Later for chat requests (Experimental)

Setting: sessions.sendLater.enabled Open in VS Code Open in VS Code Insiders (Agents window only)

Sometimes you want an agent to run a request after some time has passed. You might want to check a build after it finishes, or follow up on a review in the morning. With the Send Later feature, you can postpone sending a chat request until a specific time.

You can schedule a chat request by using the Send Later menu on the send button in chat.

Screenshot showing the Send Later menu with preset times.

For a specific time, select Choose Date and Time, pick a day in the calendar and a time from the dropdown, and select Schedule.

Screenshot showing the Send Later date and time picker with a calendar, a time dropdown, and a Schedule button.

Where the request waits depends on where you scheduled it:

  • New session: In the Drafts section of the sessions list.
  • Existing chat: In that chat's Scheduled area, with its send time. If the agent is still busy at the scheduled time, the request waits its turn instead of interrupting.

Screenshot showing a scheduled message in a chat, labeled with the date and time it will be sent.

Alternatively, you can ask the agent to schedule a request for you by using plain language in the chat prompt, for example: "Check the build in 10 minutes."

The agent schedules a one-time, text-only request in the current chat and confirms when it will be sent. The request appears in the chat's Scheduled area, like one you scheduled from the menu.

Screenshot showing an agent confirming a request to check the build in 10 minutes, with the follow-up listed in the chat's Scheduled area.

The local agent host must be running at the scheduled time. Scheduling doesn't wake a sleeping computer. A missed request is processed once the host is available again.

To manage your scheduled requests (edit, send immediately, reschedule, or cancel), use the options available when you hover over them in the chat or session list. To find sessions with pending requests, look for the clock indicator in the session list, or select Scheduled Only in the sessions filter menu.

Learn more about scheduling requests in the Send Later documentation.

Note: Scheduled requests work only for sessions on This Computer and require automations to be enabled ( chat.automations.enabled Open in VS Code Open in VS Code Insiders ).

Save and resume drafts (Experimental)

Setting: sessions.drafts.enabled Open in VS Code Open in VS Code Insiders

Previously, the new-session input held a single unsent request at a time. With drafts, you can keep several unsent requests side by side, each with its own workspace, agent, and configuration, and come back to any of them later.

When you leave a new session that has content, VS Code saves it to the Drafts section of the sessions list. Nothing is sent, and no agent session starts. To jump right back, select Open Draft in the notification.

Screenshot showing the Drafts section in the sessions list with two saved drafts.

Each draft keeps everything you set up: text, attachments, inline references, workspace, agent, model, and other configuration. Drafts survive reloads and restarts.

From the Drafts list, you can preview, open, or delete a draft. When you send a draft, it's removed only after the request is accepted, so a failed send doesn't lose your work.

Turning off the setting hides the Drafts section but keeps your saved drafts.

Share remote environments as GitHub Environments

Share a remote as a GitHub Environment to pick up its agent sessions from another device or supported Copilot app, using your GitHub account.

To share a connected SSH host, WSL distribution, or Dev Tunnel, open the Remote Environments editor in the Agents window and select Share as GitHub Environment (GitHub icon) on the remote's row.

A shared remote stays in its group and shows a GitHub icon after its name. Select the action again to stop sharing.

Screenshot showing the Remote Environments editor with the Share Build Server as GitHub Environment action on a connected SSH host, and a Dev Tunnel that is already shared.

Learn more about remote agent sessions.

Keep chat sessions across Dev Container rebuilds (Experimental)

Settings: dev.containers.stateVolume.enabled Open in VS Code Open in VS Code Insiders , chat.agentHost.devContainer.stateVolume.enabled Open in VS Code Open in VS Code Insiders

Rebuilding a Dev Container used to remove the Copilot chat sessions stored inside it. When you enable these settings, VS Code stores the user and agent state of a new Dev Container on a Docker volume, preserving your chat sessions across rebuilds.

Important: A container gets the volume only when it's created with the setting enabled, so rebuild once to start keeping your sessions.

Inbox mode improvements (Experimental)

Setting: sessions.list.inboxEnabled Open in VS Code Open in VS Code Insiders

Inbox mode groups your Agents window sessions by what needs your attention. You can switch to Inbox mode at any time with Grouping > Inbox Mode in the sessions list. The sessions.list.inboxEnabled Open in VS Code Open in VS Code Insiders setting makes it the default grouping.

This release builds on your feedback to make Inbox mode more useful and manageable:

  • Acknowledge sessions you've handled

    If a session doesn't need your attention but isn't finished, you can mark it as acknowledged (eye icon). Acknowledging a session moves it out of the Inbox and into the Acknowledged section. The session isn't marked as read or done, archived, or closed.

    When there is new activity in the session, it returns to the Inbox. You can acknowledge several selected sessions at once.

  • Focus on one workspace or environment

    Use the workspace and environment pickers at the top of the sessions list to see only the sessions you care about right now. The filter applies to every section, including pinned and archived sessions, and is remembered across reloads.

    Screenshot showing Inbox mode with workspace and environment pickers above the Pinned and Inbox sections.

Agent experience

Decision model-based model routers (Experimental)

Setting: chat.copilot.modelRouter.enabled

With a model router, you describe which model you want for which kind of work. A decision model, gpt-6-luna-decisions, then matches your request to one of your routes, and VS Code runs the chat on that route's model. A router is a YAML file in ~/.agents/model-routers/ that appears in the model picker in Copilot harness sessions.

Model routers are at an early stage, and your feedback will help shape them. Tell us what works and what doesn't by filing an issue.

version: 1
description: Opus to build, GPT-6 Luna for quick questions.
routes:
  - model: opus
    when: Building or changing code over many steps, such as a feature, a bug fix, or a refactor.
  - model: gpt-6-luna
    when: Quick answers and small chores, such as where something is or what a setting does.

To try model routers, add "chat.copilot.modelRouter.enabled": true to your user settings.json file.

To author a router, type /model-router in a Copilot harness chat and describe how you want your requests routed. Then select the router in the model picker.

Model comparison improvements (Preview)

Model comparison lets you run the same prompt across models in the Agents window, so you can review, judge, and combine their results. This release makes comparisons easier to find and understand:

  • Comparisons stay with their chat: When you ask an agent to run a comparison, it appears beneath that chat in the sessions list. The agent's response includes an Open Comparison action to go straight to the results.

  • See how a comparison was set up: Hover over a comparison in the sessions list to see its original settings: repository, isolation, base branch, each attempt's model and effort level, judge, and synthesizer. You no longer need to open each attempt to check.

    Screenshot showing the Original comparison settings hover over a comparison in the sessions list, listing the repository, isolation, base branch, four attempts, judge, and synthesizer.

HTML previews and native visuals in agent responses

Settings: chat.htmlPreview.enabled Open in VS Code Open in VS Code Insiders , chat.nativeComponents.enabled Open in VS Code Open in VS Code Insiders (Agents window only)

Some agent responses are easier to review as a visual or a chart than as text, such as a comparison of approaches, a mockup, or build times before and after a change. In the Agents window, agents can show these inline in the response in two ways. Each has its own setting, which is off by default.

  • HTML previews: For free-form layouts, such as reports, diagrams, and mockups. Previews display HTML, CSS, tables, inline SVG, and expandable sections. Scripts, forms, external links, and external resources aren't supported. Enable chat.htmlPreview.enabled Open in VS Code Open in VS Code Insiders and use the built-in /html-preview skill in your request, for example /html-preview compare the two caching approaches.

  • Native visuals (Experimental): For data, such as key numbers and comparisons. Agents can show metrics, badges, tables, bar charts, and expandable details that VS Code renders itself, so they match your theme, including high-contrast themes. Enable chat.nativeComponents.enabled Open in VS Code Open in VS Code Insiders and use the built-in /vscode-ui skill in your request, for example /vscode-ui compare the full and incremental build times.

Both appear as part of the response, without a title bar or permanent buttons. Right-click a preview or visual and select Show Source to see its markup. For an HTML preview, you can also select Open Preview for a larger view or Save HTML to export a self-contained HTML file.

Automations

Automations allow you to define tasks that run automatically based on specific triggers and conditions. You can create, manage, and monitor automations from the Automations view in the Agents window. This release adds guided setup, end dates, and filters for automation runs:

  • Agent-guided automation creation

    Creating an automation with an agent is now a more guided experience. The agent helps you define what a successful result looks like, decide when the automation runs, and choose where it runs. To start, ask an agent to create an automation. You can also select Create with Agent in the Automations view to continue in chat.

    If you prefer configuring everything yourself, open the dropdown next to Create with Agent and select Create Manually.

  • Set an end date for automations

    Automations can stop automatically after a specified duration. Set an end date when creating an automation with an agent, or choose Days, Weeks, or Months under Advanced Settings in the manual configuration form. Select Never to remove an existing end date.

  • Filter automation runs in session lists

    Automation runs are hidden from session lists by default. Use the Automations filter to include or exclude them in the Agents window and the editor Chat sessions list.

More context for assisted permissions

Setting: chat.permissions.assisted.instructions Open in VS Code Open in VS Code Insiders

With assisted permissions, an LLM reviewer assesses each tool call in Copilot harness sessions and approves low-risk calls for you. Previously, the reviewer relied only on its default guidance, so it couldn't account for what you consider safe or risky in your own work.

Use chat.permissions.assisted.instructions Open in VS Code Open in VS Code Insiders to give the LLM reviewer your own instructions, for example:

Always ask before installing packages or pushing to a remote.
Running tests and read-only Git commands doesn't need my approval.

Your instructions take precedence over the reviewer's default guidance. Changes to the setting apply to sessions that are already open. They can't override permission rules, organization policy, or the sandbox, and they aren't sent to the agent.

The reviewer also takes into account who asked for the work:

  • Automations and other agents: Requests that an automation starts or that another agent sends are no longer treated as if you wrote them. In these sessions, tool calls might ask for approval where they previously didn't.

  • Your answers: Your answers to an agent's questions and plan reviews count, including when you decline. An approval can cover later work that your answer describes, and a refusal can block an action that was approved before.

Arrange the Details panel around the editor (Experimental)

Settings: sessions.experimental.detailsPosition Open in VS Code Open in VS Code Insiders , sessions.experimental.floatingDetails Open in VS Code Open in VS Code Insiders (Agents window only)

In the Agents window, you can position Files, Changes, and other Details views around the editor to make better use of the available space. Open View > Appearance > Details Position and choose Left, Right, Above Editor, Below Editor, or Floating. Right is the default.

Floating Details overlays the editor instead of reserving space. Hover over or focus the widget to preview its contents, then select the pin control to keep it open. You can also drag and resize it.

View extension info

The Extensions section of Customizations shows the same detailed information about each installed extension, including its version, publisher, and available commands, as you can from the Extensions view in the editor window.

Screenshot of the GitHub Pull Requests extension in the Extensions section of Customizations.

Chat

Attach screenshots of other apps (Experimental)

Setting: chat.appWindowScreenshots.enabled Open in VS Code Open in VS Code Insiders

Give the agent a view of the app you're building, even when it runs in another application. Select Add Context > Screenshot App Window and choose a window, such as a browser or simulator.

You can also press ⌃⌘S (Windows, Linux Ctrl+Shift+Alt+S) while another app is in the foreground to capture its window and attach it to the chat. From VS Code, the shortcut captures the app window you just left. You can mark up the image before sending.

Capture and mark up images in chat

Select Mark Up on any image attachment in the chat input to crop it, draw arrows or shapes, or add text before sending. This works with screenshots, pasted images, and images attached from files, so you can point out a layout problem or highlight the part you want changed.

Inline chat attachment pills (Experimental)

Setting: chat.inlineAttachments.enabled Open in VS Code Open in VS Code Insiders

Inline chat attachments show files, images, and other context as pills at the position where you added them in your prompt, so references stay next to the instructions they belong to. Recent updates make the pills more useful in the chat input and in sent requests:

  • Preview and open GitHub references: Hover over or focus a GitHub issue or pull request pill to see its title, status, and description. Select the pill to open the issue or pull request. In sent requests, where selecting a pill previously did nothing, this also works when inline attachments are off.

  • Rearrange pills by dragging: Drag a pill to a new position in the same chat input, rather than removing the context and attaching it again.

  • Clearer sent requests: Sent requests show attached images as thumbnails above the text, in addition to the inline pills. Pills and slash commands line up with the surrounding text. Image and GitHub pills are restored after you reload the window, instead of appearing as plain links.

Screenshot showing an image pill and two file pills inline with the prompt text in the chat input, each next to the instruction it belongs to.

Inline attachments are enabled by default in Insiders and off by default in Stable.

Browser integration

Let agents use your browser with browser use (Preview)

Setting: chat.agentHost.browserUse.enabled Open in VS Code Open in VS Code Insiders

Browser Use lets agents interact directly with your default browser (Google Chrome or Microsoft Edge). This complements VS Code's integrated browser, for example by allowing agents to reuse existing authenticated sessions and interact with web pages outside of VS Code.

Browser Use requires the GitHub Copilot browser extension, a Copilot harness session that runs on your own machine, and Node.js 22 or later on your PATH.

To get started with Browser Use:

  1. Enable the chat.agentHost.browserUse.enabled Open in VS Code Open in VS Code Insiders setting and restart VS Code.
  2. Open a local Copilot session and enter /plugin enable browser-use to enable the browser-use plugin.
  3. Ask Copilot to perform a browser task, for example: Open my app at localhost:3000, check the navigation, and capture a screenshot.
  4. Approve site access when prompted; complete sign-in and sensitive steps yourself.
  5. Run /browser-use:doctor and follow its guidance to check your setup in case of any issues.

Preview remote HTML files in the integrated browser (Preview)

Setting: workbench.browser.enableRemoteProxy Open in VS Code Open in VS Code Insiders

You can now open HTML files from a remote workspace, such as SSH, WSL, or a Dev Container, in the integrated browser, just like local HTML files. In the Explorer, right-click an HTML file and select Open in Integrated Browser. The page keeps its file:// address, and the file and the resources it references, such as scripts, styles, images, and fonts, load from the remote workspace. Remote files only load from folders you trust.

This also works in the Agents window for sessions on a remote agent host, so you and the agent can preview a page the agent wrote without copying it to your machine.

Enable workbench.browser.enableRemoteProxy Open in VS Code Open in VS Code Insiders to try it out, and file any issues you encounter in the VS Code repository.

Setting: workbench.externalUriOpeners Open in VS Code Open in VS Code Insiders

Localhost links could already open in the integrated browser with workbench.browser.openLocalhostLinks Open in VS Code Open in VS Code Insiders . The integrated browser is now listed as an opener in the workbench.externalUriOpeners Open in VS Code Open in VS Code Insiders setting, so you can choose it for other links instead of using the default browser. For example, to open links to your company's sites in the integrated browser:

"workbench.externalUriOpeners": {
  "*.contoso.com": "workbench.integratedBrowser"
}

Use * as the pattern to open every link there instead.

Turn off dimming in the integrated browser

Setting: workbench.browser.dimOnOverlay Open in VS Code Open in VS Code Insiders

When something overlaps the integrated browser, such as a tab hover or a tooltip, the page pauses and dims. As hovers come and go, the page repeatedly darkens and returns to normal, which might appear as flicker and be uncomfortable for users who are sensitive to it.

You can now disable workbench.browser.dimOnOverlay Open in VS Code Open in VS Code Insiders to keep the page undimmed while it's paused. Notifications still dim the page.

Sandboxing

Retry with updated permissions inside the sandbox

If a terminal command fails because it can't access a file or folder, you can grant access at the session, workspace, or user level. With sandbox bypass enabled, Copilot can use that permission to retry the command inside the sandbox instead of asking to run it outside.

Use the approval dropdown to choose where the permission applies:

  • Allow for This Session (default): Applies to all chats in this session, even after you resume it.
  • Allow for This Workspace (when available): Applies to sessions with the same workspace folders on the same Agent Host. The host saves the permission without changing your workspace settings.
  • Allow for This User: Saves the permission in your User settings so it applies across sessions and workspaces.

The command retries inside the sandbox. None of these options grants permission to run outside it.

Accessibility

Clearer focus and session attention

In high-contrast themes, Agents window controls now use a dashed outline for pointer hover and a solid outline for keyboard focus and open or expanded states. This makes it easier to follow your focus when navigating.

Sessions that need input are also easier to spot: light themes use a clearer amber indicator, and high-contrast themes show a marker at the left edge of the session row. You can customize the color with agentSessionNeedsInput.foreground in workbench.colorCustomizations Open in VS Code Open in VS Code Insiders .

Screenshot showing needs-input markers on session rows in high-contrast dark and light themes.

Editor Experience

Customize panel corners and spacing

Setting: workbench.sizeCustomizations Open in VS Code Open in VS Code Insiders

Customize panel corners and spacing in the editor window and in Agents windows with the Modern UI enabled. Set corner radii in whole pixels from 0 to 8 and spacing from 0 to 16. For example, you can use square panel corners, add space between panels, and give agent chat panels their own corners:

{
  "workbench.sizeCustomizations": {
    "panels.cornerRadius": 0,
    "panels.spacing": 12,
    "agentsWindow.chatPanels.cornerRadius": 4
  }
}

Compact layouts remain gapless, and the setting doesn't change controls, individual tabs, or native window corners.

Connected panel tabs (Experimental)

With the Modern UI enabled, the connected tab style now extends from editor tabs to horizontal panel and side bar tabs. Selected views visually connect to their content, including when the Activity Bar is at the top or bottom. Choose connected (the default) or pill with workbench.experimental.modernUIEditorTabStyle Open in VS Code Open in VS Code Insiders . The default vertical Activity Bar is unchanged.

Screenshot showing connected tabs extending from editor tabs to horizontal panel and side bar tabs.

Edit Markdown tables cell by cell

Editing a Markdown table in the source means keeping pipes and separator rows intact by hand. In the Markdown editor, tables stay rendered while you edit them, and you edit one cell at a time.

Screenshot of a Markdown table in the Markdown editor, with the cursor in a cell that shows its bold syntax while you edit it.

Collapsible details sections in the Markdown editor

Long documents often hide optional content in <details> sections. The Markdown editor now renders <details> and <summary> as collapsible sections, like GitHub does. Sections with the open attribute start expanded, and other sections start collapsed.

Screenshot of the Markdown editor showing an expanded details section with its source tags and pin, and a collapsed section below it.

Enterprise

Permit Claude and Codex alongside managed settings

Previously, any Copilot enterprise-managed setting disabled the Claude and Codex harnesses, because they don't enforce those settings. An organization couldn't govern Copilot and still offer Claude or Codex to its developers.

Administrators can now permit one or both harnesses by listing them in vscode.allowedHarnesses:

{
  "permissions": {
    "disableBypassPermissionsMode": "disable"
  },
  "vscode": {
    "allowedHarnesses": ["claude", "codex"]
  }
}

Screenshot showing a managed settings file that lists claude and codex in allowedHarnesses, next to the harness picker offering Claude and Codex below Copilot and Local.

  • The list permits the harnesses it names and blocks the others, so an empty list blocks both. Without the setting, managed settings disable both harnesses, as before.
  • Valid entries are claude and codex, in lowercase. Other entries are ignored.
  • Permitting a harness only lifts this restriction. Other controls still apply, such as vscode.temporaryAllowLocalHarness: false.
  • Set it in file-based or MDM-managed settings. Server-managed settings don't support it yet.

Note: Permitting a harness doesn't make it enforce your managed settings. Claude and Codex sessions run without Copilot's managed permission, sandbox, MCP, and plugin controls.

Regular expressions in managed shell permission rules

Previously, managed shell permission rules matched only exact text or * wildcards, so a single rule couldn't cover alternatives or word boundaries. In Copilot harness sessions, Shell(...), Bash(...), and PowerShell(...) rules in enterprise-managed settings accept a JavaScript regular expression written as /pattern/flags in permissions.deny, permissions.ask, and permissions.allow.

For example, require approval for commands that start with git push or git pull:

{
  "permissions": {
    "ask": ["Shell(/^git\\s+(push|pull)\\b/)"]
  }
}

Contributions to extensions

GitHub Pull Requests

There has been more progress on the GitHub Pull Requests extension, which enables you to work on, create, and manage pull requests and issues. New features include:

  • When GitHub Actions workflows are waiting for a maintainer's approval, such as for a pull request from a first-time contributor, the checks section of the pull request overview has an Approve workflows to run button.

  • Comments and other timeline items in the pull request overview use the full width once they're below the sidebar, and the overview switches to a single column below 1000px wide instead of 768px.

  • In the Agents window, the pull request overview can be split into Timeline, Checks/Merge, and Metadata tabs with the experimental setting "githubPullRequests.experimental.agentsOverviewTabs". The Timeline tab shows the number of unresolved conversations, and the Checks/Merge tab shows whether the pull request is ready to merge.

Review the changelog for the 0.180.0 release of the extension to learn about everything in the release.

Deprecated features and settings

New deprecations in this release

  • VS Code desktop on macOS Ventura and macOS Sonoma is deprecated. For details, see the VS Code FAQ.

  • VS Code desktop on 32-bit ARM Linux is deprecated. For details, see the VS Code FAQ.

  • The experimental AI usage statistics in the Status Bar (editor.aiStats.enabled) are removed because of low usage.

Upcoming deprecations

Thank you

Issue tracking

Contributions to our issue tracking:

Pull requests

Contributions to vscode:

Contributions to vscode-pull-request-github:


We really appreciate people trying our new features as soon as they are ready, so check back here often and learn what's new.

If you'd like to read release notes for previous VS Code versions, go to Updates on code.visualstudio.com.