VS Code 1.140

+ 신기능 26개

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

• 멀티 폴더 세션 기능을 통해 여러 리포지토리나 격리된 워크트리에서 관련 작업을 한 세션에서 조정할 수 있게 한다 # 에이전트
  원문

  [Agents] Multi-folder sessions (Experimental): Multi-folder sessions let you coordinate related work across repositories or isolated worktrees in one session. Previously, every chat in a multi-chat session shared the same folder and checkout. In this release, each chat can use its own folder or worktree without changes leaking between chats. Each chat uses its folder for its terminal, tasks, changes, pull request, and Agent merge state. Chats that use the same folder share that state. In the sessions list, hover over a session to see a summary across all its folders, or hover over a nested chat to see details for only its folder. Example use cases include: Implement a feature across repositories: Ask the main chat to work in one repository and create a peer chat for a second repository. Compare approaches in separate worktrees: Ask the main chat to create peer chats that each use a fresh worktr

• 세션 내에서 작업이 완료된 채팅을 마크하고 보관하여 세션의 나머지 부분을 활성 상태로 유지하게 한다 # 에이전트
  원문

  [Agents] Archive chats in a session: Keep the rest of a session active when one chat finishes its work. Because sessions can contain multiple chats, select Mark as Done to archive only the finished peer chat, not the entire session. To restore it with its title and transcript intact, select the Done filter in the sessions list.

• 위임된 작업 시 세션 계획 또는 결과물 여부와 워크스페이스 및 워크트리 선택을 분리하여 결정하게 한다 # 에이전트
  원문

  [Agents] Choose the session relationship and workspace for delegated work: Make two separate decisions when you ask an agent to delegate work. First, decide whether the task belongs to the current session's plan or deliverable. Then specify a workspace only if the task needs repository files, and request a worktree only if file changes need isolation. Related work can still use a different workspace. Create a peer chat for related work: Ask the agent to create a peer chat in the current session. To reuse the current workspace and checkout, say so in your prompt. Because the peer chat shares the checkout, use this option for research, planning, or related work that doesn't need isolated file changes. Create an independent session for unrelated work: Ask the agent to create an independent session with no workspace when a separate deliverable doesn't need repository files. The new session doesn't

• Agents window에서 새 세션 생성 시 선택적 환영 문구와 사용자 이름을 포함하는 기능을 추가한다 # 에이전트
  원문

  [Agents] Personalize new-session welcome phrases (Experimental): Settings: sessions.chat.experimental.welcomePhrases , sessions.chat.experimental.welcomeName , accessibility.verbosity.newSessionWelcome (Agents window only) Add some personality to the Agents window with an optional welcome heading when you create a new session in the Agents window. The heading shows one of five phrases, such as What are we building? or Let's ship something, and can append your first name from your GitHub profile. Welcome phrases are off by default. When enabled, you can use Set Welcome Name from the heading, its context menu, or the Command Palette to choose a different name. The name syncs across devices. Clear it to use your GitHub first name when available, or a generic phrase when your profile has no name. When screen reader optimized mode is active, VS Code announces the heading once when the composer appea

• 세션 컴포저 레이아웃을 개선하여 제어 항목을 그룹화하고 단축키를 추가한다 # 에이전트
  원문

  [Agents] Improved session composer controls (Experimental): Settings: sessions.chat.experimental.newSessionComposerLayout , sessions.chat.unifiedWorkspacePicker.enabled (Agents window only) The experimental session composer layout reduces the need to move between separate parts of the Agents window. In a new session, the workspace, branch, worktree, and harness controls are grouped above the chat input. Enable both settings to use the layout. The unified workspace picker also has commands for moving directly to its controls. Use ⌘K ⌘F (Windows, Linux Ctrl+K Ctrl+F) to focus the workspace picker or ⌘K ⌘H (Windows, Linux Ctrl+K Ctrl+H) to focus the harness picker. Hovers show your configured keybindings, and each picker's context menu provides a Configure Keybinding action. These keyboard improvements require only the unified workspace picker, not the experimental composer layout. Starting with t

• 에이전트 오케스트레이션의 한도를 높여 복잡한 워크플로우가 중단되지 않도록 개선한다 # 에이전트
  원문

  [Agents] More reliable agent orchestration (Experimental): Setting: chat.agentHost.agentOrchestrationLimits Coordination-heavy agent workflows are less likely to stop before the work is complete. This release raises the process-wide limits for agent-created sessions, chats, inter-session messages, and recursive session creation. For example, an agent can classify CI failures, delegate each fix to a separate session, and coordinate those sessions without exhausting the message limit before the work is complete. Reaching a limit blocks new orchestration actions but does not interrupt work that is already running. The setting defaults to on, and changes apply without restarting the Agent Host. Set it to off to remove the orchestration limits. Confirmation requirements and input validation continue to apply.

• URL을 통해 에이전트 세션과 프롬프트가 포함된 상태로 Agents window를 여는 기능을 추가한다 # 에이전트
  원문

  [Agents] Open a new session in the Agents window from a URL: Open the Agents window from another tool or webpage with a workspace and an editable prompt ready for review. Use a URL with the agents/new path and the optional prompt and workspace query parameters. For example, this URL opens a new session with no workspace and the prompt already entered: VS Code places the decoded prompt in the New Session composer without sending it. To select a workspace, add the workspace parameter with a URL-encoded folder URI. If the URL omits workspace, the draft uses No Workspace. An existing occupied composer remains unchanged, so opening a link does not overwrite work in progress. Learn more about opening VS Code with URLs. Note: Use vscode-insiders:// instead of vscode:// for VS Code Insiders.

• 에이전트 응답 시 진행 상황을 지속적으로 표시하고 렌더링을 개선한다 # UI
  원문

  [Chat] Persistent progress for agent responses (Experimental): Settings: chat.experimental.persistentProgress , chat.experimental.persistentProgressVerbosity Long-running agent responses are easier to follow with persistent progress. When enabled, chat keeps a progress indicator visible at the bottom until the response finishes. Enabling persistent progress also improves the rendering and visibility of in-progress responses. Reasoning appears in separate collapsible previews, and tool calls remain visible while they run. With Compact verbosity, completed tool groups collapse into expandable summaries when response text resumes or the response finishes. Select Verbose to keep the full tool-call details visible. Use chat.experimental.persistentProgress to turn the indicator off or choose a colored or monochrome Draw animation. The setting defaults to Draw in VS Code Insiders and is rolling out

• 에디터 창에서 여러 채팅을 사용할 수 있도록 세션에 여러 채팅을 포함하며, Sessions 뷰에서 이를 확인하고 선택할 수 있게 한다 # 에이전트
  원문

  [Chat] Use multiple chats in the editor window: A session can contain multiple chats. Until now, the main chat with its nested peer chats appeared only in the Agents window. The editor window also shows them: the Sessions view lists the main chat with its peer chats nested underneath, next to the Chat view. Select any row to open that chat in the Chat view.

• MCP 서버를 휴대용 구성 파일에 추가하여 여러 Copilot 도구에서 동일한 설정을 공유할 수 있게 한다 # MCP·플러그인
  원문

  [MCP] Add MCP servers to portable configuration files: You can add MCP servers to portable configuration files from the MCP: Add Server flow, so you can use the same server configuration across compatible Copilot tools without editing JSON manually. For global servers, choose Copilot Global to save the server to $COPILOT_HOME/mcp-config.json, or ~/.copilot/mcp-config.json when COPILOT_HOME is not set. For workspace servers, choose .mcp.json to save the server at the workspace root.

• Git worktree에서 무시된 폴더를 심볼릭 링크로 연결하여 의존성 재설치나 빌드 결과물 중복을 방지하는 `git.worktreeSymlinkFolders` 설정을 추가한다 # 성능
  원문

  [Source Control] Reuse ignored folders across worktrees (Experimental): Setting: git.worktreeSymlinkFolders Avoid reinstalling dependencies or duplicating large build artifacts in each Git worktree. Configure git.worktreeSymlinkFolders with .gitignore-style patterns for ignored folders, such as node_modules. When VS Code creates a new worktree, including for an agent session, it creates symlinks to matching folders in the current checkout.

• 관리자가 Auto 모델의 기본 티어를 설정할 수 있는 `autoTier` 관리형 설정을 추가한다 # 에이전트
  원문

  [Enterprise] Set a default Auto tier: The Auto model in VS Code can operate in different tiers, optimizing for efficiency, balance, or intelligence. Administrators can align the Auto model's default behavior with organizational priorities without preventing developers from choosing another tier. Administrators can set the default tier for the Auto model with the autoTier managed setting. Accepted values are efficiency, balance, and intelligence. The tier applies to new chats in the Local harness and the Copilot agent host on the same machine. The managed tier appears as Default in the model picker. The managed tier is a starting point, not a restriction. Developers can still choose a different tier. VS Code keeps explicit and restored choices when the managed tier changes or is removed.

• 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

• Dev Container를 사용하는 세션이 일정 시간 동안 비활성 상태일 때 컨테이너를 자동으로 정리하고 다시 시작할 때 재시작하게 한다 # 에이전트
  원문

  [Agents] Automatic Dev Container cleanup: Settings: chat.agentHost.devContainer.enabled , chat.agentHost.devContainer.idleTimeout (Agents window only) When all sessions that use a Dev Container are inactive for five minutes, VS Code stops the container. It restarts automatically when you continue working. Marking as done or deleting the last session removes the container.

• 캐시된 VS Code Server 및 CLI 다운로드를 재사용하여 Dev Container의 시작 속도를 높인다 # 에이전트
  원문

  [Agents] Faster Dev Container startup: Setting: chat.agentHost.devContainer.enabled (Agents window only) Dev Container sessions let agents use your project's tools and dependencies in an isolated environment. Fresh containers can reuse cached VS Code Server and CLI downloads, which reduces setup time and repeated downloads across projects.

• 원격 에이전트 호스트에서 워크스페이스 없이 채팅을 실행할 수 있도록 지원을 추가한다
  원문

  [Agents] Create workspace-less chats on remote agent hosts: Setting: sessions.chat.unifiedWorkspacePicker.enabled (Agents window only) Agent Host lets you run and track agent sessions on a remote host. This release adds support for running workspace-less chats on a remote host. Select a connected host from the unified workspace picker without choosing a workspace. The Chat entry identifies the selected host, so you can confirm where the session runs before you start. Remote folders also appear alongside local folders in the main picker. This makes frequently used remote workspaces easier to select without opening the Remote submenu.

• Agents window의 Done 섹션에서 최근 완료된 세션을 먼저 표시하도록 정렬 방식을 변경한다 # 에이전트
  원문

  [Agents] See recently completed sessions first: The Done section in the Agents window now sorts sessions by when you marked them as done, with the most recently completed session listed first. This order stays the same when you switch between Created and Updated sorting and after you reload VS Code.

• 채팅에서 터미널 출력의 줄바꿈(reflow) 여부를 설정으로 제어할 수 있게 한다 # UI
  원문

  [Chat] Terminal output reflow: Setting: chat.tools.terminal.outputReflow Since VS Code 1.132, terminal output in chat reflows to fit the width of the output preview. The new chat.tools.terminal.outputReflow setting lets you control this behavior. If you prefer output to keep a fixed width instead, disable the setting and scroll horizontally to read long lines. Reflow remains enabled by default.

• 축하 효과가 나타날 때 소리가 나도록 하는 `accessibility.signals.confetti` 설정을 추가한다 # UI
  원문

  [Accessibility] Hear when confetti appears: Setting: accessibility.signals.confetti The new Confetti accessibility signal provides the same celebratory feedback when you cannot see the animation. The joyful sound plays when chat thumbs-up confetti appears and when you successfully mark a session as done in the Agents window.

• 선택 영역의 대소문자 구분 여부를 제어하는 `editor.selectedTextMatchMode` 설정을 추가한다 # UI
  원문

  [Code Editing] New option to control selection text matching case sensitivity: Setting: editor.selectedTextMatchMode We have added a new setting editor.selectedTextMatchMode to control the case sensitivity of selection matching. The default value, findOptions, means selection matching sensitivity is tied to the Find widget, as was previously the case. There are two other values caseSensitive and caseInsensitive, which match case-sensitive and case-insensitive selections respectively.

• macOS 고해상도 디스플레이에서 터미널 텍스트를 더 선명하게 표시하도록 `terminal.integrated.fontRendering` 설정을 추가한다 # UI
  원문

  [Terminal] Sharper terminal text on macOS (Experimental): Setting: terminal.integrated.fontRendering On macOS high-DPI displays, terminal text can look softer than the same font in other terminals. Set terminal.integrated.fontRendering to grayscale to make terminal text look sharper.