AI 코딩 도구,
이번엔 뭐가 바뀌었나

• ! Windows 환경에서 Local harness의 Windows sandboxing을 더 이상 지원하지 않으며, 대신 Agent Host 세션을 사용하도록 변경한다 # 보안·권한
  원문

  [Chat] Windows sandboxing for Local harness is no longer supported: Windows sandboxing for terminal commands in Local agent sessions has been deprecated. For sandboxed command execution on Windows, use an Agent Host session. See the Agent Host sandboxing documentation for details.

• ~ Local harness에 대한 Windows sandboxing 지원을 중단한다 # 보안·권한
  원문

  [Deprecated features and settings] New deprecations in this release: Windows sandboxing for Local harness is no longer supported

• + Copilot harness를 새 세션의 기본 harness로 점진적으로 도입한다 # 에이전트
  원문

  [Agents] Copilot harness: The Copilot harness is powered by the Copilot SDK, a shared foundation that helps align behavior, capabilities, and improvements across Copilot products. In VS Code, the Copilot harness runs sessions through the Agent Host, which lets sessions continue in the background and be accessed from both the VS Code editor window and the Agents window. The Copilot harness has been available from the harness picker in the chat input. Based on overwhelmingly positive and valuable feedback, we're progressively rolling it out as the default harness for new sessions in VS Code. When you start a new session, Copilot in the harness picker indicates that the session will use the Copilot harness. Thank you to everyone who has shared feedback. We're actively using it to shape the experience. One example is reintroducing Ask as a built-in agent in the Copilot harness. Your feedback showed

• + 에이전트와 협업을 위한 인터랙티브 인터페이스인 Canvases를 프리뷰로 제공한다 # 에이전트
  원문

  [Agents] Canvases (Preview): Setting: chat.canvases.enabled Canvases are interactive interfaces to collaborate with an agent. A canvas opens beside the chat, where you and the agent can inspect and update the same artifact instead of coordinating solely through prompts. For example, use a Kanban canvas to plan and track implementation work. You can create and move cards directly, while the agent can break a feature into tasks, update their status, or add newly discovered work. Canvases work in both the VS Code editor window and the Agents window, and canvas extensions are also supported in the GitHub Copilot app. Canvases are available in Preview in the VS Code desktop app for local sessions that use the Copilot harness. Enable chat.canvases.enabled , and then start a new session with the Copilot harness. Every canvas is provided by a canvas extension. To get started, you have two options: Crea

• + Copilot 및 BYOK 제공자의 모델 선택기를 재설계하여 모델 선택과 전환을 용이하게 한다 # UI
  원문

  [Chat] Redesigned model picker: Copilot and bring-your-own-key (BYOK) providers offer many models, each with strengths for different tasks. The redesigned model picker makes it easier to choose and switch models as your work changes. The model picker uses a tabbed interface to separate Copilot and BYOK models. When you hover over a model in the list, you can further configure its thinking level and context window size.

• ~ Python Environments Extension에서 환경 탐색, 인터프리터 선택, 터미널 활성화 관련 문제를 수정한다 # 에이전트
  원문

  [Languages] Python: This release includes fixes for environment discovery, interpreter selection, and terminal activation in the Python Environments Extension. Environment discovery: Python installations managed by uv now appear under Global. Selecting an interpreter by path adds its virtual environment to the environment list, and deleting a virtual environment outside VS Code updates the selection. Project-specific environments: Automatic selection now prefers a project's own virtual environment over nested environments. Conda environment selection and Poetry package operations respect project scope, and background refreshes no longer overwrite newer interpreter selections. Interpreter configuration: Fixed resolution of ${workspaceFolder}, relative paths, and commands such as python3 in python.defaultInterpreterPath. The project-view environment selector now includes Enter Interpreter Path. Term

• + Enterprise 환경에서 정책 기반의 채팅을 Copilot Agent Host로 자동 이동시키고 정책을 강제하는 기능을 추가한다 # 보안·권한
  원문

  [Enterprise] Automatically move policy-managed chats to Copilot Agent Host: Enterprise managed settings let administrators govern agent permissions and sandboxing. When your organization configures a nonempty permissions object or sets sandbox.enabled to true, VS Code now requires the Copilot harness in Agent Host for full chat sessions, to be able to enforce these policies. Opening an existing, unarchived Local chat automatically moves it to Copilot, preserving the transcript and unsent draft, including attachments. Nothing is sent automatically. The new chat uses its normal model and permission defaults under current organization policy. VS Code archives the original chat only after the new chat opens successfully. If you switch away while the move is in progress, the original stays unchanged and the unopened destination is removed. While these policies apply, Claude, Codex, and terminal chat are

• + Windows에서 숫자형 정책이 DWORD 및 QWORD 값을 지원하도록 개선한다 # 보안·권한
  원문

  [Enterprise] Windows numeric policies support DWORD values: On Windows, policies that accept numeric values support DWORDs and QWORDs.

외 14개 항목은 원문에서 볼 수 있습니다.

AI가 만든 요약입니다. 원문과 다르면 오류 제보해 주세요.

• + Copilot harness를 통해 새로운 에이전트 기능을 추가한다 # 에이전트
  원문

  [Agent loop] Copilot harness: The Copilot harness adds exciting new agent functionality to VS Code. It's powered by the Copilot SDK, so its behavior and capabilities are consistent with other Copilot products, including the standalone GitHub Copilot app and the Copilot CLI. To start using the Copilot harness, select it from the harness picker in the chat input. In this release, it might already be the default selection for you. You can continue working as you normally do. The harness runs in a dedicated agent host process based on the Agent Host Protocol (AHP), so you can connect to the same agent session from multiple VS Code windows. Learn how to work with the Copilot harness, or explore the architecture and workflows in the agent host blog post. If you have feedback or requests, please file an issue.

• ◆ Copilot 에이전트 호스트에서 `chat.agent.sandbox.enabled` 설정을 통해 샌드박싱을 지원한다 # 보안·권한
  원문

  [Agent security] Sandboxing in the Copilot agent host: Settings: chat.agent.sandbox.enabled Sandboxing gives you more control over what Copilot can access while working on a task. It limits how supported agent operations access files and network resources, and helps to reduce the impact of model mistakes, prompt injection, untrusted dependencies, and locally launched tool servers. Depending on the operation and platform, these restrictions use operating-system protections or checks within the agent host process. Sandboxing adds a layer of protection, but does not replace endpoint security or provide a standalone security boundary. Sandboxing is available on Windows, macOS, and Linux. On Windows, required operating-system updates must be installed. Refer to Check platform availability for more details. To configure sandboxing for all your sessions, enable the chat.agent.sandbox.enabled setting. You can

• + 여러 개의 GitHub Enterprise 인스턴스에 동시에 로그인할 수 있도록 `github-enterprise.uris` 설정을 추가한다 # 보안·권한
  원문

  [Authentication] Sign in to multiple GitHub Enterprise instances: Setting: github-enterprise.uris Many organizations use GitHub Copilot through a GHE.com account but keep their code on GitHub Enterprise Server (GHES). The github-enterprise.uri setting held a single instance, so you couldn't be signed in to both at once. For example, you couldn't use Copilot with your GHE.com account and review pull requests on GHES in the same VS Code window. The new github-enterprise.uris setting takes a list of GHE.com and GHES instances: The GitHub Enterprise authentication provider holds accounts from every instance in the list. Each account is labeled with its host, such as monalisa - octocat.ghe.com, so you can tell them apart in the Accounts menu. When more than one instance is configured, signing in asks which instance to use. The order of the entries doesn't select a default instance. To check or change which

외 27개 항목은 원문에서 볼 수 있습니다.

AI가 만든 요약입니다. 원문과 다르면 오류 제보해 주세요.

• + Copilot harness를 통해 새로운 에이전트 기능을 추가하고 여러 VS Code 창에서 동일한 에이전트 세션에 연결할 수 있게 한다 # 에이전트
  원문

  [Agents] Copilot harness: The Copilot harness adds exciting new agent functionality to VS Code while keeping the way you work familiar. It's powered by the Copilot SDK, so its behavior and capabilities are consistent with other Copilot products, including the standalone GitHub Copilot app and the Copilot CLI. To start using the Copilot harness, select it from the harness picker in the chat input. In this release, it might already be the default selection for you. You can continue working as you normally do. The harness runs in a dedicated agent host process based on the Agent Host Protocol (AHP), so you can connect to the same agent session from multiple VS Code windows. Learn how to work with the Copilot harness, or explore the architecture and workflows in the agent host blog post. If you have feedback or requests, please file an issue.

• + HydraFusion 모델 오케스트레이션 시스템을 도입하여 작업에 따라 모델과 워크플로우를 자동으로 선택하게 한다 # 에이전트
  원문

  [Agents] HydraFusion model orchestration (Research Preview): HydraFusion is an adaptive model orchestration system that chooses the models and workflow for each coding task. It can solve a task with one model, escalate to a stronger model, or have another model critique and revise the result. This approach aims to improve result quality while balancing speed and cost, without requiring you to coordinate models yourself. Eligible users with preview features enabled can select HydraFusion in the model picker.

• + Agents window에서 연결된 원격 에이전트 호스트로 작업을 위임하는 기능을 추가한다 # 에이전트
  원문

  [Agents] Delegate tasks to remote agent hosts (Experimental): Settings: chat.remoteAgentHostsEnabled , chat.remoteSessions.tools.enabled (Agents window only) Your agent can delegate work to connected remote agent hosts from the Agents window, without you selecting a host in a picker for each task. The new built-in tools let your agent: Discover hosts, models, resource capacities, and session load with list_agent_hosts. Start a session with create_remote_session. Specify a host, or let automatic placement match an operating system (Windows, Linux, or macOS), minimum memory capacity, logical CPU count, and optional model. Among matching hosts, placement favors the host with the fewest running sessions and pending creations. Check a remote session's status and latest response with get_remote_session. Send follow-up work or report results and questions back to the originating chat with send_remote_

• + 관리자가 AI 기능 사용 전 최소 버전 요구사항을 설명하도록 하며, 업데이트가 필요한 경우 적절한 안내를 제공한다 # 보안·권한
  원문

  [Enterprise] Explain minimum version requirements: Administrators can require developers to update VS Code before using AI features, for example, to adopt newer sandboxing protections. Instead of an Update Required dialog, VS Code now explains the requirement wherever AI features are unavailable: Chat: shows the required and installed versions, with an update action. Editor window: shows a banner even when Chat is closed. Other editor features stay available. Agents window: shows a blocking overlay, with an Open Editor Window action. When an update is available, VS Code offers the matching Check for Updates, Download Update, Install Update, or Restart to Update action. If your organization disables built-in updates by policy, VS Code instead asks you to contact your administrator. The notices clear once the requirement is met. How VS Code enforces the requirement is unchanged.

외 22개 항목은 원문에서 볼 수 있습니다.

AI가 만든 요약입니다. 원문과 다르면 오류 제보해 주세요.

• + 원격 호스트의 Dev Container에서 에이전트 세션을 실행할 수 있도록 `chat.agentHost.devContainer.enabled` 설정을 추가한다 # 에이전트
  원문

  [Agents] Run agent sessions in Dev Containers on remote hosts: Setting: chat.agentHost.devContainer.enabled (Agents window only) Let agents build and test your remote project with the right tools and dependencies, without duplicating toolchain setup on your laptop or the remote host. This release extends Dev Container sessions from local folders to projects on SSH, Tunnel, and WSL hosts. To get started, enable chat.agentHost.devContainer.enabled and select Use Dev Container from the folder menu in the Agents Window. The remote folder must have a supported Dev Container configuration, and Docker must be available on the remote host. Note: Dev Container sessions are rolling out gradually, so the setting might not be enabled by default for you yet. You can enable the setting manually to try the feature now.

• ! Linux 데스크톱 런처 이름 변경으로 인해 기존 핀 고정된 런처가 작동하지 않을 수 있으므로 제거 후 다시 추가해야 한다 # 보안·권한
  원문

  [Deprecated features and settings] Linux desktop launcher names: If a pinned launcher stops working after updating to version 1.139, remove it and add the application again from your desktop's application menu. The Linux DEB and RPM packages now use reverse-DNS desktop file names to align with the application's desktop identity. For the Stable packages, the files in /usr/share/applications/ are renamed as follows: Existing favorites, pinned launchers, and custom references to the old names are not updated automatically. On KDE Plasma, a stale favorite can report "You are not authorized to execute this file" even though this is a missing desktop file, not a permissions problem. Remove the old favorite or pinned launcher, then add the application again from the application menu. On KDE Plasma, use Remove From Favorites on the old entry, then Add to Favorites on the entry under Applications > Development. Update custom sho

외 10개 항목은 원문에서 볼 수 있습니다.

AI가 만든 요약입니다. 원문과 다르면 오류 제보해 주세요.