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

• + orchestrator connector ID에 대해 선택적으로 Guardian trust를 추가한다 # 보안·권한
  원문

  [Changelog] #52250 Add opt-in Guardian trust for orchestrator connector identities @ankushg

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

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

• + 승인이 필요한 커넥터 동작에 대해 Slack 스레드에 개인적인 Allow once / Deny 카드를 추가한다 # 보안·권한
  원문

  [What's changed] [Claude Tag] Added a private Allow once / Deny card in Slack threads for connector actions that need your approval, so Claude asks instead of refusing; others only see that it's waiting on you

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

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.

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

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

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

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

• + 관리자 설정의 Claude Tag spend limits 페이지에서 조직 전체 및 기본 spend limit 박스를 클릭 시 이동할 때가 아닌 Save 또는 Enter를 눌렀을 때만 저장하도록 변경한다 # 보안·권한
  원문

  [What's changed] [Claude Tag] Changed the organization-wide and default spend limit boxes on Claude Tag's spend limits page in admin settings to save only when you press Save or Enter, not when you click away

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

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가 만든 요약입니다. 원문과 다르면 오류 제보해 주세요.

• + Bedrock 및 Vertex 시작 시 모델 체크를 개선하여 사용 불가능한 모델을 최대 하루 동안 기억하도록 한다 # 보안·권한
  원문

  [What's changed] Improved Bedrock and Vertex start-up model checks: models your account cannot use are now remembered for up to a day instead of being re-checked on every launch

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

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

• + Rollouts와 Security Review 봇을 출시하여 배포 시 상태를 모니터링하고 보안 취약점을 점검한다 # 보안·권한
  원문

  Rollouts and Security Review: Today we're launching two Cursor bots for the last mile of shipping code. Rollouts watches every change as it deploys and reports its health per environment. Security Review reports exploitable bugs on every pull request. Both are available today on Teams and Enterprise plans.

• + Rollouts가 모든 pull request에서 변경 사항을 모니터링하고 환경별로 상태를 보고한다 # 보안·권한
  원문

  Rollouts: Rollouts attaches a monitor to every pull request and watches the change as it deploys, reporting change health per environment: verified healthy, regression detected, or inconclusive. It's the Cursor version of Firetiger Change Monitors, rebuilt with the Bot Development Kit. Enable it from the dashboard and connect source control, your deploy system, and your telemetry provider. Rollouts starts watching on the next pull request. When a pull request opens, Rollouts reads the diff and the systems it touches, then writes a monitoring plan as a PR comment. The plan lists the risks it identified, the effect the change is meant to have, the signals it will check, and any gaps in instrumentation that would make the change hard to verify. Edit the plan in the PR and Rollouts uses your version. Rollouts wakes on deploy events for the change's commit and runs the plan against your log

• + Security Review가 모든 pull request에서 취약한 버그를 찾아내고 수정 제안을 포함한 리뷰 코멘트를 작성한다 # 보안·권한
  원문

  Security Review: Security Review is available today. It reads every pull request in the context of the codebase and posts one review comment reporting exploitable bugs. Style and quality stay with Bugbot. Security Review comment on a pull request reporting an exploitable bug with a severity and proposed fix Enable it from the dashboard for the repositories you want reviewed. Draft PRs are skipped. Security Review looks for injection across SQL, command, and template surfaces, along with authentication and authorization bypasses, including checks that a refactor stopped running. It also flags secrets and credentials committed to source, SSRF and unvalidated redirects, unsafe deserialization, and dependency changes that introduce known vulnerabilities. It traces where user input enters and what it passes through. Each finding carries a severity, the attack path, and a proposed fix. Dismi

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

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

• + `claude self-hosted-runner --drain-marker-file <path>` 명령어를 추가한다 # 보안·권한
  원문

  [What's changed] Added `claude self-hosted-runner --drain-marker-file <path>`: when that file exists at a SIGTERM drain, the runner reports its exit to the server as a host drain (telemetry only)

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

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