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

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

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

• + 현재 채팅을 다른 폴더나 Git worktree로 이동하는 기능을 추가한다 # 에이전트
  원문

  [Agents] Move chats between folders and worktrees: Previously, if you started investigating a task in one folder and then wanted to implement it in a Git worktree, or continue in a different repository, you had to start a new chat and rebuild the context. In the Agents window, you can now ask the agent to move the current chat to another folder or into a new Git worktree, and it keeps the conversation history intact. Changing the workspace also works for chats that already have a workspace, and the agent can isolate work in a new worktree. Ask the agent with a natural-language prompt, for example: The agent finishes the current turn, moves the chat, and shows a notice when the workspace changes. Then it continues the task automatically in the new location. Edits and commands run in the new location while your original checkout stays unchanged. The move is available for agent sessions that use t

• + Copilot harness 세션에서 실행 중인 백그라운드 셸을 중단하는 기능을 추가한다 # 에이전트
  원문

  [Chat] Stop background shells: In Copilot harness sessions, the background shells pill above the chat input lists the commands that the agent is still running in the background. When one of those commands is no longer useful, for example a test run that you want to restart or a command that runs longer than expected, you can stop it instead of waiting for it to finish. Select the Background Shells pill, select a shell to open its details, and then select Stop Shell next to its command. Only that command ends, and the shell leaves the list. You can reach Stop Shell with the keyboard, and screen readers announce when the shell stops. Stopping a shell is only available for attached shells, which the agent runs as part of its current request. Detached shells run independently of the agent and can't be stopped from this interface. Shell details also show each shell's full description above its com

• + Agents 창에서 세션별로 레이아웃 설정을 유지하는 실험적 기능을 추가한다 # 에이전트
  원문

  [Agents] Session-scoped layout in the Agents window (Experimental): Setting: sessions.experimental.layoutScope (Agents window only) Previously, when you switched between sessions in the Agents window, VS Code shared layout settings such as editor visibility, details, and panel visibility across sessions. If you're used to VS Code remembering the layout for each workspace, sharing the layout across sessions can be disruptive. With the new experimental sessions.experimental.layoutScope setting, you can choose how much of the layout each session remembers. Reload the window after you change the setting. It supports the following values: session-shared (default): The current behavior. A session and its nested sessions share the same editors and selected panel views. Editor, details, and bottom panel visibility are shared across existing workspace sessions. chat-shared: A session and each of its nes

• + BYOK 커스텀 엔드포인트에서 상태 유지 응답을 위한 설정을 추가한다 # 에이전트
  원문

  [Chat] Stateful responses for BYOK custom endpoints: If your bring-your-own-key (BYOK) model uses a stateless Responses API, set "statefulResponses": false on its model entry in chatLanguageModels.json to send full conversation history with each request. See Custom Endpoint configuration for details.

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

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.

• + 백그라운드에서 실행되는 셸을 추적하는 기능을 추가한다 # 에이전트
  원문

  [Agent loop] Keep track of background shells: When the agent runs a command in the background, it keeps working on other steps while the command runs. In Copilot harness sessions, a Background Shells pill above the chat input lists the shells that are still running, in both the Agents window and the editor window. Select the pill to see each shell's command and how long it has been running, and select a shell to watch its output stream as the command runs, if output is available. A shell leaves the list when its command finishes.

• + 에이전트가 트리거하는 메시지에 대한 제어 기능을 강화한다 # 에이전트
  원문

  [Agent loop] More control for agent-triggered messages: When agents delegate work across conversations, they can adjust the delegated task as requirements change instead of waiting for the other session to finish. The send_message tool supports these actions between sessions and nested sessions on the same agent host: Steer an active conversation with a correction. Queue a follow-up as a separate turn. Replace a queued message while preserving its place in the queue. Cancel a queued message before processing begins. Queued messages run in order. After a message starts processing, it can no longer be replaced or cancelled.

• + 새 세션 제어 항목을 간소화하고 세션 옵션 트레이를 추가한다 # 에이전트
  원문

  [Agent UX] Simplified new-session controls (Experimental): Settings: sessions.chat.experimental.newSessionComposerLayout , sessions.chat.unifiedWorkspacePicker.enabled (Agents window only) The experimental new-session composer keeps your prompt at the center while making session choices easier to review. Workspace, repository, and harness controls now appear in a collapsible Session Options tray above the chat input. Getting-started tips now appear in a rounded notice below the chat input, so they no longer separate the session controls from your prompt. Collapse the tray to reduce visual clutter without changing your selections. The composer remembers your choice, adapts labels as the window narrows, and keeps the options expanded when screen reader optimized mode is active. When you use a custom chat background, the tray has an opaque surface to keep its controls readable.

• + 재로드 없이 로컬 외부 Copilot 세션을 이어받는다 # 에이전트
  원문

  [Agent environments] Continue local external Copilot sessions without reloading: New conversations from the Copilot CLI and GitHub Copilot app are now picked up automatically as external sessions as soon as you send the first request, even when the Agents window is already open. You can open and continue these conversations directly from the Agents window. Use the Created In and Created Externally filters to choose which conversations appear in the sessions list.

• + ChatGPT 앱 또는 Codex CLI에서 시작한 Codex 채팅을 VS Code에서 이어받는다 # 에이전트
  원문

  [Agent environments] Codex chat handoff between apps: Pick up a Codex chat started in the ChatGPT app or Codex CLI and continue it in VS Code's Agents window on the same machine, with your conversation history intact. You can switch back to the ChatGPT app or Codex CLI later and continue the same chat. To use your GitHub Copilot subscription in VS Code, choose a Copilot model in the model picker. For example, you can keep working with Copilot after reaching your ChatGPT usage limit. With Codex enabled and Created Externally sessions visible, chats created or updated in ChatGPT or Codex CLI appear within a few seconds without reloading VS Code. Only one application can send messages to the chat at a time. If ChatGPT or Codex CLI still has the chat open, a This chat is open in another app banner in VS Code explains why sending is unavailable. Fully quit ChatGPT or exit the Codex CLI session, then select Retr

• + Dev Container 샘플을 통해 즉시 사용 가능한 개발 환경을 제공한다 # 에이전트
  원문

  [Agent environments] Dev Container samples (Experimental): Setting: chat.agentHost.devContainer.samples.enabled (Agents window only) Try an agent with a ready-to-use development environment without first cloning a repository or installing its language tools locally. The Agents window now offers Dev Container samples for Go, .NET, Node.js, PHP, Python, and Rust. Install and start Docker, and then enable the setting. Open a new session in the desktop Agents window, select Dev Container Sample from the workspace picker, and send a prompt. This also requires chat.agentHost.devContainer.enabled and chat.remoteAgentHostsEnabled to be enabled.

• ~ 정책 확인 시 선택한 에이전트를 유지하도록 고친다 # 에이전트
  원문

  [Enterprise] Keep your selected agent through policy checks: When your enterprise requires a fresh policy check with forceRemoteSettingsRefresh, chat preserves your selected agent during policy checks instead of switching to Ask or Edit. Routine background refreshes also keep the last accepted policy active while loading. Startup, account changes, and failed refreshes continue to block submissions until policy checks succeed. Newly accepted restrictions continue to apply.

• + 중첩된 세션에서 활동을 추적한다 # 에이전트
  원문

  [Agent UX] Track activity across nested sessions: Nested sessions let you split related work across separate conversations. In the Agents window, each nested session shows its unread status and last-modified time, helping you find recent activity and conversations that need your attention without opening them individually. Status is tracked independently for each conversation: Opening a nested session marks only that conversation as read. An unread nested session does not make the main session appear unread. The last-modified time reflects activity in that conversation, not activity in the main session or another nested session. Read status and last-modified times persist when you reload the window or restart VS Code. To clear unread status for an entire session tree, right-click the main session and select Mark as Read. Unrelated sessions are not affected.

• + Add Context 선택기의 위치를 호출 버튼 옆으로 개선한다 # 에이전트
  원문

  [Agent UX] Improved context picker positioning: The Add Context picker now opens next to the button that invoked it and closes when you select the button again. This keeps the picker visually connected to the chat input in the editor and Agents windows.

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

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_

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

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

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

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.

• + 에이전트 세션 목록을 더 빠르게 로드하고 새로고침하도록 개선한다 # 에이전트
  원문

  [Agents] Faster session list loading: The Agents Window opens and refreshes large session lists faster. The agent host now keeps lightweight session and chat metadata in a central catalog, instead of opening every conversation database each time the list is built. Full conversation content stays isolated in the individual session and chat databases. The improvement grows with the number of sessions, because the previous approach did work in proportion to your session count. Measured with around 645 sessions on a development machine:

• + 많은 세션이 있는 경우에도 에이전트 세션 목록을 더 빠르게 로드하고 새로고침하도록 개선한다 # 에이전트
  원문

  [Agents] Faster session list loading: VS Code loads and refreshes large agent session lists faster. The agent host keeps lightweight session and chat metadata in a central catalog instead of opening every conversation database each time the list is built. Full conversation content remains isolated in the individual session and chat databases. The improvement grows with the number of sessions because the previous approach did work in proportion to your session count. Measured with around 645 sessions on a development machine: If you have few sessions, expect a smaller difference. Sessions created before this release are migrated automatically in the background.

• + 에이전트 세션 목록에 Compact View를 활성화하여 더 많은 세션을 표시하도록 한다 # 에이전트
  원문

  [Agents] Compact sessions list: Fit more sessions in the sessions list by enabling Compact View in the sessions list view of the Agents Window. Compact rows show the session title at rest and reveal workspace details when you hover over or focus the row. A row expands when the session needs input or approval, so these requests remain visible. Progress also appears on the row for the chat that owns the work. When you collapse a session, the parent row summarizes progress from its hidden chats.

• + 세션 목록에서 세션이나 중첩된 채팅을 직접 이름 변경하도록 한다 # 에이전트
  원문

  [Agents] Rename sessions and chats in place: Rename a session or nested chat directly in the sessions list. Double-click its title, use the Rename context menu action, or focus the row and press F2 for a session or F2 for a nested chat. Inline validation prevents blank titles, and canceling restores the previous title.

• + 세션 내에서 채팅이 표시되는 방식을 선택할 수 있는 `sessions.showChatTabs` 설정을 추가한다 # 에이전트
  원문

  [Agents] Choose how chats appear in a session (Preview): Setting: sessions.showChatTabs (Agents window only) An agent session can contain multiple chats, each representing a different conversation or context. When a session contains multiple chats, choose the presentation that best fits your workflow from the session header menu: Multiple shows each chat on its own tab. Single shows only the active chat and hides the tab bar. Switching presentations preserves your open chats, active chat, and conversation state. In Single mode, chats that you explicitly open to the side remain independent panes with their own header actions.

• ~ Filter Sessions에서 Empty Groups를 비활성화하여 빈 커스텀 그룹과 Chats 섹션을 숨기도록 한다 # 에이전트
  원문

  [Agents] Filter empty session groups: Disable Empty Groups from Filter Sessions to hide empty custom groups and the empty Chats section. This preference is stored in your profile and resets with the other sessions list filters.

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

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