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

• + 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.

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

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

• ◆ 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

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

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

• + 관리자가 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.

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

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

• ! 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

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

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