Visual Studio Code 1.147
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. Visual Studio Code 1.147 Release date: November 18, 2026 Stable Downloads for 1.147.0 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap 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. Send later (Experimental) : Schedule local agent requests and follow-ups for later in the Agents window. Browser integration (Preview) : Let agents control your default browser, and preview remote HTML files without copying them to your machine. Draft requests (Experimental) : Keep multiple unsent requests with their context and configuration in the Agents window, ready to send when you are.
Customize assisted permissions : Tell the permission reviewer which actions you consider safe and which should need your approval. Visual chat responses : Review reports, mockups, and charts inline in the Agents window with HTML previews and experimental native visuals. Model routers (Experimental) : Let a model router choose from your preferred models for different tasks. 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. For a specific time, select Choose Date and Time , pick a day in the calendar and a time from the dropdown, and select Schedule . 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.
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. 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. 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. 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. 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 ru
The rest of this page is on the live site.