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

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

• + 관리자가 전환 기간 동안 Local harness를 유지할 수 있도록 `vscode.temporaryDefaultToLocalHarness` 설정을 추가한다 # 보안·권한
  원문

  [Enterprise] Temporarily keep the Local harness: Administrators who need more time to transition to Copilot Agent Host can set vscode.temporaryDefaultToLocalHarness to true in their unified managed settings: This keeps the Local harness available and stops automatic switching to Copilot, while preserving explicit, remembered, and current harness choices. Set the managed value to false or remove it to restore normal routing. Note: This temporary opt-out also overrides routing required by managed sandbox and permission settings. Local does not enforce those runtime-only rules. Enforcement in Copilot Agent Host sessions is unchanged.

• + 관리자가 Copilot 권한 모드를 독립적으로 관리할 수 있도록 `permissions.disableAssistedPermissionsMode` 설정을 추가한다 # 보안·권한
  원문

  [Enterprise] Manage Copilot permission modes independently: Administrators can permit Assisted while blocking Allow All, giving developers assisted approvals without bypassing permission checks. The Copilot permission picker reflects the modes permitted by your organization's managed settings. For example, merge this configuration into your unified managed settings: Use permissions.disableAssistedPermissionsMode to restrict Assisted independently. permissions.defaultMode supplies a starting default, not a restriction on the modes users can select. The legacy ChatToolsAutoApprove: false policy still blocks both Allow All and Assisted unless you configure explicit managed mode restrictions. Setting only permissions.defaultMode does not replace that legacy restriction. Note: Assisted Permissions is not currently compatible with permissions.{allow,ask,deny}. If you are using any of permissions.allow, p

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

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

• + 여러 개의 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

• + 에디터에서 원격 파일을 로컬로 다운로드하는 기능을 추가한다 # 보안·권한
  원문

  [Agent environments] Download remote files from the editor: Save an open remote file locally, without having to navigate for it in the Files panel. In the Agents window, open the editor's More Actions menu and select Download... to download the file to a local destination.

• + Agent Host 세션을 사용자 및 머신 정보와 연결하여 관리자가 식별하기 쉽게 한다 # 보안·권한
  원문

  [Enterprise] Attribute Agent Host sessions to users and machines: Administrators can more easily attribute Agent Host sessions to users and machines by including operating system usernames and hostnames in VS Code's Agent Host telemetry. Merge this example into your unified managed settings, alongside your existing telemetry exporter configuration: For example, captured identity attributes can include (illustrative values): The OS username (process.user.name) and hostname (host.name) are resource attributes. The signed-in GitHub username (user.name) appears on runtime spans when supported by the bundled Copilot runtime. Identity capture is off by default, and the managed value overrides personal preferences. It is independent of content capture. VS Code's host-side control does not govern a runtime's direct exports.

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

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.

• + Copilot OpenTelemetry 데이터에 개별 개발자 식별 정보를 포함하는 `github.copilot.chat.otel.captureIdentity` 설정을 추가한다 # 보안·권한
  원문

  [Enterprise] Capture user identity in OpenTelemetry: Setting: github.copilot.chat.otel.captureIdentity Organizations can attribute Copilot OpenTelemetry data to individual developers. When identity capture is enabled, Local chat sessions add the following attributes: user.name on agent invocation spans, including subagents and inline chat. process.user.name and host.name as resource attributes. Identity capture is off by default and independent of content capture. Administrators control identity capture with the telemetry.capture.identity managed setting (CopilotOtelCaptureIdentity policy). A managed value takes precedence over COPILOT_OTEL_CAPTURE_IDENTITY and user settings. When a policy denies capture, VS Code removes identity from later exports without a reload, including identity attributes that are set explicitly as resource attributes. This release also changes how managed telemetry settings

• + 인증 세션에서 인증 서버를 식별할 수 있는 기능을 추가하여 올바른 호스트로 토큰을 전송하는 것을 방지한다 # 보안·권한
  원문

  [Proposed APIs] Authorization server on authentication sessions: The authIssuers proposal lets an extension name the OAuth authorization server it wants to authenticate against, which VS Code introduced for MCP in the 1.101 release notes. This release adds the opposite direction, so a session can tell you which authorization server issued it. If your extension talks to more than one deployment of a service, such as public GitHub and a GitHub Enterprise host, you can pair each credential with the destination it was issued for instead of reading a separate setting that the user can change independently. This prevents a valid token from being sent to the wrong host. Keep in mind two things. The value identifies an OAuth issuer rather than an API endpoint, so map it to your own endpoints. The built-in GitHub provider populates it for public GitHub sessions as well as enterprise ones, so its presence alone

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

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

• + AuthenticationSession에 `expiresAfter` 속성을 추가하여 인증 세션의 토큰 만료 정보를 제공한다 # 보안·권한
  원문

  [Proposed APIs] Access token lifetime on authentication sessions: AuthenticationSession exposes an access token but no information about how long that token stays valid. An extension that passes a credential to an SDK with its own refresh callback cannot distinguish between a token that never expires and one that is about to expire. As a result, the extension either refreshes the credential unnecessarily or lets a long-running operation fail when the token expires. The authSessionExpiration proposal adds an optional expiresAfter property to AuthenticationSession: The value is the remaining lifetime when the session is returned rather than an absolute expiration timestamp. The extension host can run on a different machine than the client, and the two clocks can disagree. Authentication providers that return a cached session recompute the value each time and leave it undefined when the token's expiratio

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

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