Text of code.visualstudio.com › docs › agents › run › agent-harnesses as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Choose an agent 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. Choose an agent harness View as Markdown Ask in VS Code Ask in VS Code Insiders VS Code supports multiple agent harnesses, each with its own tools, customizations, and workflows.

An agent harness coordinates the language model, context, and tools that an agent uses to complete your task. Use this guide to compare the available options, identify which harness your session uses, select a harness or the Cloud execution target, and review its setup requirements. For a deeper explanation of how harnesses work and differ from models and hosts, learn about agent harness concepts . Important The Local harness is deprecated and will be removed by February 2027 .

Move your workflows to the Copilot harness before then. Follow Move from the Local to the Copilot harness to review customization compatibility, continue existing conversations, and verify organization controls. Compare agent harnesses Start with the Copilot harness for day-to-day coding and agent tasks. Choose another harness or the Cloud target when you need different tools, customizations, or execution workflows. Harness What runs What this means for your work Copilot Run tasks using the Copilot SDK, which provides the shared agent experience across GitHub Copilot products.

The agent works in the Agent Host . Sessions run independently of the editor window and can continue in the background after you close it, while the Agent Host stays running. You can also continue sessions across supported interfaces. See Copilot requirements and limitations . 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 .

Run tasks within VS Code's built-in agent harness. The agent works in VS Code's extension host . Available only while you migrate to the Copilot harness, until removal in February 2027. The session is tied to the editor window: closing that window stops the agent's ongoing work. See Local requirements . Claude The Anthropic Claude Agent SDK is integrated into VS Code. Sessions use Claude project configuration and provider workflows in your current workspace or an isolated worktree.

See Claude requirements . Codex OpenAI Codex runs through the OpenAI Codex extension or the experimental Agent Host integration. Sessions support interactive or background coding. Available interfaces depend on the integration. See Codex requirements . Cloud The Copilot harness runs in a managed cloud environment. Cloud is an execution target, not a separate harness. Use an interactive cloud session Cloud sessions is experimental and might change or be removed. and reconnect to continue work without keeping your own machine online.

Cloud work uses a separate workspace rather than your local editor state. See Cloud target requirements . For Agent Host sessions managed by desktop VS Code on your machine, keep the application running. Closing an editor window is different from quitting the application. Tools provided by a window also require that window to stay connected. Changing the model or agent role does not change the harness. For example, selecting a Claude model in a Copilot harness session still uses the Copilot harness.

Opening the same session in another supported interface also keeps its harness. A session can group chats that use different harnesses with mixed-harness chats Mixed-harness chats is experimental and might change or be removed. . This starts a separate conversation on the chosen harness rather than handing off an existing conversation. 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 . is a harness name, not a synonym for running on your machine. The Copilot, Claude, and Codex harnesses can also run on your machine. Available models depend on the harness and how you access models , such as through a GitHub Copilot subscription, another supported account, or your own API key. Harness-specific customizations, including hooks , follow the selected harness. Note Claude and Codex harnesses are disabled when Copilot enterprise-managed settings apply , including managed permission or sandbox settings, unless your administrator explicitly permits them.

Contact the IT team that deployed the settings to discuss access. If you don't know the owner, ask your IT help desk to find the responsible administrator. Select a harness Select a harness before you submit the first prompt for a session: Open the Chat view or open the Agents window . Select New Chat ( + ) in the Chat view, or select New in the Agents window. In the Agents window, select the folder or GitHub repository for the session.

Open the Session Target UI control and select an available harness or the Cloud target. The control only lists targets whose requirements are met in the current window. Choose a built-in agent After selecting a harness, choose an available built-in agent from the agent picker. The available built-in agents depend on the harness: Harness Built-in agents Copilot Ask answers questions and researches your codebase without making changes.

It only uses read-only tools and can't edit files or run state-changing commands. Agent implements changes and validates the result. Plan researches a task and creates an implementation plan for you to review. Invoke it with /plan . 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 . Ask answers questions without changing your code.

Agent implements changes and validates the result. Plan researches a task and creates an implementation plan for you to review. Switching agents doesn't change the harness. You can also select custom agents from the same picker. In the Copilot harness, Autopilot is a mode with its own workflow, not an additional built-in agent. Your harness choice is separate from where the session changes code. In the Agents window, you can also choose between a folder and a worktree or run a session in a Dev Container .

Identify your current harness To identify the current harness for a chat session, use one of the following methods: In the editor window, the active harness is shown as a prefix in the chat title. In the Agents window, the chat input box shows the active harness as the watermark. In the Agents window, hover over the session entry in the sessions list to see a tooltip showing the harness. For a nested chat that uses a different harness from its parent session, hover over its chat tab or its entry in the sessions list to see the chat's harness.

Requirements and setup Check the accounts, extensions, and settings needed for your chosen harness or the Cloud target. If a choice does not appear in the Session Target UI control, start with its requirements below. Your harness and model access are separate choices. Using a provider's model through Copilot is different from using that provider's own credentials. The access option you select determines which account's usage limits and billing apply.

If you're starting with an existing account or key: GitHub Copilot access : Start with the Copilot harness . The Anthropic Claude and OpenAI Codex integrations also offer Copilot-routed models, subject to their requirements. Anthropic Claude credentials : Follow the authentication options . ChatGPT account : Follow the Codex setup for your chosen integration. Another model API key or local model : Configure a model provider for Local sessions or supported Experimental Copilot harness workflows.

For access through a provider's own credentials, that pr

The rest of this page is on the live site.