Move from the Local to the Copilot harness
AI agents: See llms.txt for documentation discovery and navigation. Documentation articles are also available as Markdown by appending .md to the article URL. Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. Move from the Local to the Copilot harness View as Markdown Ask in VS Code Ask in VS Code Insiders The Copilot harness brings the shared coding agent runtime behind Copilot CLI and the Copilot app into VS Code.
Your editor workflows benefit from the same ongoing work on model integration, context efficiency, and tool use as those products. You can work alongside your code in the editor or use the Agents window to supervise tasks across projects. For organizations, the shared runtime provides a common approach to governing agents across supported clients and development environments. Administrators can manage permissions and sandbox restrictions that the legacy Local harness The Local harness is deprecated and will be removed in February 2027.
Move your workflows to the Copilot harness before then. Learn more about Local harness deprecation . cannot enforce, while developers use approved tools and services in their workflows. Important The Local harness The Local harness is deprecated and will be removed in February 2027. Move your workflows to the Copilot harness before then. Learn more about Local harness deprecation . is deprecated and will be removed by February 2027 .
Move your workflows to the Copilot harness before then. The temporary vscode.temporaryDefaultToLocalHarness enterprise-managed setting will also be removed. Use this guide to review the customizations and integrations your work depends on, continue existing conversations where needed, and verify your organization's controls. The goal is a working setup for your daily tasks, not just a different session target. Why move to the Copilot harness An agent's ability to complete a task depends on more than the model you choose.
The harness prepares the context the model receives, coordinates tool calls and approvals, and maintains the conversation as the work progresses. Changing the harness can change how the agent carries out your request, even when you use the same model. With the Copilot harness, you can: Run builds, tests, and other agent commands within the file system and network boundaries you configure with local sandboxing . Let Copilot Fusion choose models and coordinate drafting and review for your task.
Delegate tasks across projects in the Agents window , then continue the same session in the editor when you want to edit, debug, or test. Both interfaces stay in sync. Spend less time approving routine tool calls with assisted permissions . Calls that the risk assessment doesn't approve still come to you for confirmation. Delegate work to a cloud sandbox Cloud sessions is experimental and might change or be removed. and close your laptop.
Reconnect later to review progress and continue the task. Bring context from your team's services into agent tasks through Copilot connectors Copilot connectors is in preview and might change before it becomes generally available. , without configuring MCP servers yourself. Plan work on a task board or explore an interactive diagram with your agent through canvases Canvases is in preview and might change before it becomes generally available. .
For organizations, the Copilot harness adds governance that the Local harness The Local harness is deprecated and will be removed in February 2027. Move your workflows to the Copilot harness before then. Learn more about Local harness deprecation . cannot enforce. Administrators can: Enforce file system and network restrictions through managed sandbox policy . Block operations your organization doesn't permit and control which approval levels developers can use.
The runtime enforces these restrictions, rather than relying on the model to follow instructions. Give the team a consistent starting model and effort level , while letting developers choose another available option for a particular task. Administrators can also distribute approved skills, tools, and hooks through required plugins and controlled marketplaces across supported clients, without individual setup. To put these capabilities and controls into practice, follow the organization rollout steps .
Understand what changes Local The Local harness is deprecated and will be removed in February 2027. Move your workflows to the Copilot harness before then. Learn more about Local harness deprecation . and Copilot are harness choices in the Session Target picker. The Local harness The Local harness is deprecated and will be removed in February 2027. Move your workflows to the Copilot harness before then. Learn more about Local harness deprecation . is the legacy, editor-specific implementation.
The Copilot harness uses the Copilot SDK, the shared runtime across GitHub Copilot products. Switching between them changes the software that coordinates the agent's work, not whether you use GitHub Copilot. The harness is also separate from the model and where your code runs. Selecting a Claude model doesn't switch to the Claude harness, and selecting the Copilot harness doesn't move your files to the cloud. The Agent Host is the process that runs Copilot sessions.
The editor's Chat view and the Agents window are interfaces for working with those sessions. Use the Copilot harness for new workflows, but review compatibility before replacing an existing Local harness The Local harness is deprecated and will be removed in February 2027. Move your workflows to the Copilot harness before then. Learn more about Local harness deprecation . setup. Tools and customization support can differ, and personal settings don't automatically synchronize across clients.
If an integration still requires the Local harness The Local harness is deprecated and will be removed in February 2027. Move your workflows to the Copilot harness before then. Learn more about Local harness deprecation . , review the temporary fallback guidance with your administrator. For more background on these distinctions, see agent harness concepts . Before you start Update to your organization's current approved VS Code release.
Check feature-specific prerequisites and any managed minimum-version requirement . Sign in with the GitHub account that has your approved Copilot access. Follow Copilot setup or the GHE.com account guidance as applicable. Choose a small task that already works in the Local harness The Local harness is deprecated and will be removed in February 2027. Move your workflows to the Copilot harness before then. Learn more about Local harness deprecation . .
Record the expected result, required tools, customizations, and approvals so you can compare the workflow after the switch. Back up customization files and settings before changing them. Set up your workflow Start a Copilot session Open the Chat view in the editor, or open the Agents window . Select New Chat ( + ) in the Chat view, or New in the Agents window. Select your project when prompted. Open Session Target and select Copilot .
Select an available model and agent for your task. To use assisted permissions, open the permissions picker in the chat input and select Assisted permissions . See permission levels for the available options. To check an existing session, identify its current harness . Choosing a different model or opening the session in another interface doesn't change its harness. Review customizations and integrations Selecting Copilot doesn't convert every customization.
Open Chat: Open Customizations , select Migrations , and review the detected items. Follow Migrate customizations to the Copilot harness for file locations, supported conversions, and manual steps. Use this compatibility checklist for the workflows you need: Check What to verify Prompt files Convert recurring prompts to skills. Recheck agent, model, and tool choices that the co
The rest of this page is on the live site.