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

• + Copilot 및 BYOK 제공자의 모델 선택기를 재설계하여 모델 선택과 전환을 용이하게 한다 # UI
  원문

  [Chat] Redesigned model picker: Copilot and bring-your-own-key (BYOK) providers offer many models, each with strengths for different tasks. The redesigned model picker makes it easier to choose and switch models as your work changes. The model picker uses a tabbed interface to separate Copilot and BYOK models. When you hover over a model in the list, you can further configure its thinking level and context window size.

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

• + 현재 채팅을 다른 폴더나 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

• + Markdown 편집 모드를 소스 코드와 더 가깝게 변경하여 문서 구조를 파악하기 쉽게 한다 # UI
  원문

  [Markdown editor] Editing mode closer to the Markdown source: When you edit Markdown, each source line appears on a separate visual line, making the document structure easier to follow. Read-only mode continues to render Markdown as before.

• + Markdown 편집기에 이미지를 직접 붙여넣기 기능을 추가한다 # UI
  원문

  [Markdown editor] Paste images: To add an image, for example a screenshot, to your Markdown document, simply paste it directly into the Markdown editor, like you could already do in the text editor. This makes it easier to include visual content without having to save and insert files manually.

• + Markdown 편집기에서 Rename Symbol(F2)을 지원하여 파일 링크를 인플레이스(in-place)로 변경한다 # UI
  원문

  [Markdown editor] Rename file links: The Markdown editor now supports Rename Symbol (F2), so you can rename file links in place and have the changes reflected throughout your document.

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

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.

• + 여러 개의 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 loop] Reclaim storage from inactive worktrees: Run Chat: Open Worktree Cleanup to see how much disk space inactive agent session worktrees use and remove the ones you no longer need. Filter sessions by how long they have been inactive, review each worktree's size, and select the worktrees to clean up. The cleanup editor also lets you configure automatic cleanup for sessions with merged pull requests and control whether VS Code suggests cleanup when session storage grows large. When chat.agentSessions.sessionStorageCleanupSuggestion.enabled is enabled, the Agents window notifies you when enough inactive worktrees accumulate or they use enough disk space to make cleanup worthwhile. Cleaning up marks the selected sessions as done and deletes their worktrees. You can restore a session later to recreate its worktree. Active, running, needs-input, and pinned sessions are protected from cleanup.

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

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

• + Agents 윈도우에서 세션을 그리드 형태로 배치한다 # UI
  원문

  [Agent UX] Arrange sessions in a grid: Compare results, monitor long-running tasks, or work across related conversations without repeatedly switching between sessions. Like in the editor window, the two-dimensional session grid in the Agents window lets you drag sessions into horizontal or vertical splits and resize the panes. Maximize a session when you need to focus, then return to the grid to continue working across conversations.

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

  [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

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

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

외 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_

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

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

• + 줄 바꿈 표시기를 추가하여 줄 바꿈이 일어난 위치를 더 쉽게 식별하게 한다 # UI
  원문

  [Editor experience] Word wrap indicators: Display word wrap indicators to make wrapped lines easier to identify. An arrow at the word wrap column on the right side of the editor indicates that a line wraps.

• + 괄호 자동 닫기 동작을 개선하여 중복된 닫는 괄호를 삽입하지 않도록 한다 # UI
  원문

  [Editor experience] Improved bracket auto-closing behavior: VS Code avoids inserting duplicate closing brackets when you type an opening bracket. If a matching closing bracket exists, VS Code uses it. Otherwise, VS Code inserts one.

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

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

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

• + 워크스페이스와 리포지토리 선택기를 통합하고 `sessions.chat.unifiedWorkspacePicker.enabled` 설정을 추가한다 # 에이전트
  원문

  [Agents] Unified workspace and repository picker (Experimental): Setting: sessions.chat.unifiedWorkspacePicker.enabled (Agents window only) Start agent work from one searchable list of local folders, GitHub repositories, Cloud repositories, and remote targets. Remote connection actions remain available from the Remote entry. Selecting Work in Repository uses a cloud-first workflow. A GitHub repository that is not already local is selected immediately with the Cloud harness, without a clone prompt. If you later choose a local harness, VS Code prompts you to clone the repository and preserves the cloud selection if you cancel.

• + Automations를 기본적으로 활성화하고 공유할 수 있게 기능을 추가한다 # 에이전트
  원문

  [Agents] Automations are now enabled by default and can be shared: Settings: chat.automations.enabled (Agents window only) Automations are now enabled by default, making it easier to streamline repetitive tasks. You can also export and import automations to share them across different environments or with your team. Learn more about Automations in the VS Code docs.

• + 로컬 Dev Containers에서 에이전트 세션을 실행할 수 있는 기능을 추가한다 # 에이전트
  원문

  [Agents] Run agent sessions in local Dev Containers: Setting: chat.agentHost.devContainer.enabled (Agents window only) Keep agent work aligned with your project's toolchain by running a session inside a local folder's Dev Container. The agent uses the environment and dependencies configured for the project instead of those on your local machine. When the setting is enabled, local folders with a supported Dev Container configuration automatically show a folder menu with a Use Dev Container action. Select the action to run the agent session in the folder's Dev Container. Docker must be installed on your machine. Note: Local 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.

• + 에이전트 호스트에서 Codex 지원을 확장한다 # 에이전트
  원문

  [Agents] Expanded Codex support in the agent host: Settings: chat.agentHost.codexAgent.enabled , chat.editor.codex.preferAgentHost This release expands Codex support in the agent host, so you can keep the same coding session while changing where and how you work. If you are not signed in to GitHub Copilot and want to use the Codex harness just with your ChatGPT subscription, you also have to enable chat.agentHost.allowSignedOutWhenUsable . Continue across apps: move the same Codex session between the ChatGPT app and VS Code instead of starting a new conversation. Interact with desktop apps from VS Code: if the ChatGPT app is installed and configured for computer use, the Codex harness in VS Code can reuse that setup to interact with apps on your computer. This works with models from either your Copilot subscription or your ChatGPT subscription. Use VS Code tools: Codex can use the full set of t

• + 워크스페이스 내에서 Codex quick chats를 이어가는 기능을 추가한다 # 에이전트
  원문

  [Agents] Continue Codex quick chats in a workspace: Last release, we introduced continuing quick chats in a workspace for Copilot sessions. This release extends the same flow to Codex, so starting project-specific work no longer means abandoning a workspace-less Codex quick chat. Ask Codex to attach a local folder, then choose whether to use the folder directly or create an isolated worktree. After you confirm the change, the same chat and native Codex thread become a workspace session. The session retains its title, conversation history, current request, selected model, and permission mode. Codex then continues the request with access to the project files. Workspace conversion is available for idle Codex quick chats in Interactive mode and supports single-root workspace targets. If the change is canceled or cannot be applied, the original workspace-less chat remains available.

• + 에이전트 세션에서 pull request를 생성하는 기능을 추가한다 # 에이전트
  원문

  [Agents] Create pull requests from agent sessions: Setting: chat.agentMerge.enabled (optional, for agent merge only) Create pull requests from Agent Host sessions in the Agents window using one form to review and edit generated titles and descriptions, choose draft status, and configure available merge options. Create the pull request directly or send the request to your agent, with your preferred options remembered for next time. Note: The Agent Merge option is experimental and is only available when the setting above is enabled.

• + 다크 및 라이트 테마에 따라 에이전트 창의 채팅 배경을 개별적으로 설정할 수 있게 한다 # UI
  원문

  [Agents] Customize chat backgrounds by color theme (Experimental): Settings: chat.agentSessions.preferredDarkBackgroundImageLayout , chat.agentSessions.preferredLightBackgroundImageLayout (Agents window only) The Agents window can show a decorative chat background behind your sessions, either a pattern of built-in VS Code icons or an image of your own, chosen separately for dark and light color themes. Previously, the image was per theme kind but its layout was not, so right-aligning your dark background and then left-aligning your light one left both of them aligned left. Layout is now stored per theme kind alongside the image, and switching between a dark and a light theme restores that theme's placement. The two new settings replace chat.agentSessions.backgroundImageLayout. Clearing a background also moved. Chat: Set Background... now leads with No Background, which clears the background for

• + Voice Mode에서 병렬 에이전트 작업을 탐색하고 모니터링하며 세션 간 이동이 가능해진다 # 에이전트
  원문

  [Chat] Improved Voice Mode session awareness (Experimental): Navigate and monitor parallel agent work without leaving Voice Mode. Voice Mode can find recent agent sessions, switch between them by label, and report each session's status.

• + 필요할 때 에이전트 SDK를 다운로드하도록 안내를 개선한다 # 에이전트
  원문

  [Agents] On-demand agent SDK downloads: The Claude and Codex agents in the Agents window rely on an SDK that is not shipped with VS Code and is downloaded when you first need it. Previously, the offer to download it appeared only as part of signed-out account setup, so if you were signed in it would download at first message. The offer now appears whenever the SDK is missing for transparency that a download is needed to continue. When models are already available for that agent, the notification presents two options: select Download or send a message to download the SDK as part of the turn. The wording updates in place if models become available while the notification is showing.

• + 완료된 세션을 정리하는 기능을 추가한다 # 에이전트
  원문

  [Agents] Keep completed sessions organized (Preview): Settings: chat.agentSessions.archiveNudge.enabled , chat.agentSessions.autoMarkAsDoneMergedSessionsAfterDays , chat.agentSessions.autoDeleteArchivedMergedSessionsAfterDays , sessions.markAsDoneConfetti (Agents window only) Keep finished work out of the way while preserving the conversation for later. When all of an inactive session's pull requests have merged, the Agents window can suggest marking the session as done. A first-use guide shows you where to find Mark as Done in the sessions list. Enable chat.agentSessions.archiveNudge.enabled to show these suggestions. To automate cleanup, mark inactive sessions as done after their pull requests merge, and optionally delete them after a separate grace period. Both automatic-cleanup settings are disabled by default. When all pull requests for a session are merged, select Configure Automatic Clea

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

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

• + 정기적인 작업을 수행하는 Automations 기능을 추가한다 # 에이전트
  원문

  [Agents] Automations (Preview): Setting: chat.automations.enabled Automations run recurring agent tasks on a schedule, so routine work does not have to be started manually. Start with a template for catching up on changes, triaging issues, or finding bugs, or define your own prompt and schedule. To try automations, enable chat.automations.enabled , open the Agents window, and select Automations in the sidebar. You can run an automation on demand or schedule it to run hourly, daily, or weekly. Learn more about automations in the documentation. Automations is in Preview and is rolling out gradually to all users.

• + 에이전트와 음성으로 대화할 수 있는 Voice Mode를 추가한다 # 에이전트
  원문

  [Chat] Voice Mode (Experimental): Settings: agents.voice.enabled , agents.voice.showTranscript , agents.voice.voice Voice Mode enables you to have a natural, spoken conversation with an agent while it works on your code. Note: Voice Mode is rolling out gradually and might not be available to every eligible account immediately. It requires an eligible individual GitHub Copilot plan and is not available with GitHub Copilot Business or GitHub Copilot Enterprise. Organizations can also turn off Copilot preview features by policy. To try it, enable agents.voice.enabled and select the Voice Mode button in the chat input. While the agent is speaking, start speaking or use the push-to-talk shortcut to interrupt the response and continue the conversation. Voice Mode is aware of your active session and can answer questions about running sessions, the selected model, and attached files. You can also ask

• + GitHub 이슈 및 PR 상세 정보를 Agents window에서 직접 확인하는 기능을 추가한다 # 에이전트
  원문

  [Agents] Open GitHub issues and PR details (Experimental): Setting: extensions.experimental.enableAgentsWindowCapability When a chat conversation references work on GitHub, the Agents window can provide direct integration with the GitHub Pull Requests extension. Select a github.com issue or pull request link to open its details directly in the Agents window, without switching to a browser. This also works when you don't have a workspace for that repository open. To try this initial integration, install the GitHub Pull Requests extension in your default VS Code profile and enable extensions.experimental.enableAgentsWindowCapability .

• + 채팅 입력 시 GitHub 이슈 또는 PR을 컨텍스트로 추가하는 기능을 추가한다 # 에이전트
  원문

  [Agents] Attach GitHub issues and pull requests in any chat: Add a GitHub issue or pull request as context from the Add Context... menu in any chat input, including the Chat view, Chat editor, and Agents window. This makes the issue description, comments, or pull request changes available to the agent without copying them into your prompt. You can also paste a GitHub issue or pull request URL into the new-session input. The URL remains in your prompt and a context attachment is added automatically.

• + Agents window에서 워크스페이스 없이 시작한 quick chat을 워크스페이스 세션으로 전환하는 기능을 추가한다 # 에이전트
  원문

  [Agents] Continue quick chats in a workspace: You can start a quick chat in the Agents window without associating it with a workspace, for example, to discuss general questions or ideas. If the conversation later becomes project-specific, ask the Copilot agent to attach a local folder and continue the same chat. After you confirm the workspace and choose whether to use the folder directly or create an isolated worktree, the chat becomes a workspace session. The session retains its title, conversation history, and current request, and the agent automatically continues with access to the project files when workspace setup finishes. Alternatively, you can start the project work in a new workspace session. Note: Continuing a chat conversation in a workspace session is currently available only in the Copilot harness.

• + 에이전트가 처리 중인 채팅에 메시지를 큐에 추가하여 병렬로 작업하게 하는 기능을 추가한다 # 에이전트
  원문

  [Agents] Agent-queued messages: Keep agents working in parallel without interrupting a chat that is already processing a request. When an agent uses the send_message session-management tool to contact a busy chat, VS Code queues the message and starts it after the active turn completes successfully. An agent can queue multiple messages for chats in the same session or another session. VS Code processes queued messages in the order they were sent, making multi-chat workflows more predictable.

• + 여러 VS Code 창에서 동일한 에이전트 세션을 연결할 수 있는 Agent host를 도입한다 # 에이전트
  원문

  [Agents] Agent host: The agent host lets you connect to the same agent session from multiple VS Code windows. It runs agent harnesses in a dedicated process based on the Agent Host Protocol (AHP). The agent host's Copilot agent is powered by the Copilot SDK, which aligns the agent's behavior and functionality with the Copilot CLI, the standalone GitHub Copilot app, and other Copilot products. We're actively developing the agent host. Learn more in the agent host documentation and our agent host blog post, where we share why we built the agent host, what it enables in VS Code, how the architecture and open protocol work, and workflows you can try yourself. If you have any feedback or requests, please let us know by filing an issue.

• + 일반, 다중 파일, 에이전트 창의 Changes 에디터에서 동일한 방식으로 Smart diff 에디터 레이아웃을 선택할 수 있게 한다 # UI
  원문

  [Code Editing] Smart diff editor layout: Choose a diff layout in the same way across regular diffs, multi-file diffs, and the Agents window Changes editor. Open More Actions (...) > Diff View, and then select Inline, Side by Side, or Automatic. The Automatic option shows which layout is active and adapts as the editor width changes. If you deliberately widen an inline diff by dragging a sash, the diff remains inline while you resize so the content doesn't shift unexpectedly.

• + VS Code pet의 이름을 짓는 이벤트를 진행한다 # 에이전트
  원문

  [Agents] Help name the VS Code pet (Experimental): The experimental VS Code pet is an interactive companion that reacts as you work with agents. Enter /vscode-pet in chat to meet it, then help choose its name. From September 10 through September 17, 2026, submit a name for the VS Code pet. Review the contest terms and conditions.

• + 다중 파일 diff에서 변경된 바이너리 파일을 생략하지 않고 표시하며, Open Diff를 통해 표준 diff 경험으로 확인하도록 한다 # UI
  원문

  [Code Editing] Binary files in multi-file diffs: Changed binary files, such as images, remain visible in multi-file diffs instead of being omitted. The diff shows a Binary file changed placeholder in the file's original position. Select Open Diff to review the file in the standard diff experience, such as an image diff or applicable custom editor. Multi-file diffs in editor windows also use the same visual design as multi-file diffs in the Agents window.

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

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

• + 풀 요청을 완료하기 위해 에이전트가 피드백을 처리하고 충돌을 해결하며 워크플로우를 재실행하는 Agent merge 기능을 추가한다 # 에이전트
  원문

  [Agents] Agent merge (Preview): Setting: chat.agentMerge.enabled Agent merge helps you take a pull request across the finish line. It asks an agent to address review feedback, fix failed checks and merge conflicts, and rerun workflows. Agent merge repeats this process until the pull request is ready to merge. To try agent merge, enable chat.agentMerge.enabled . You can currently enable agent merge for a session only from the Agents window. Run Enable Agent Merge for Active Session or select the Agent Merge button in the title bar. Learn more about using agent merge.

• + 여러 VS Code 창에서 동일한 에이전트 세션에 연결할 수 있는 Agent host를 도입한다 # 에이전트
  원문

  [Agents] Agent host: The agent host lets you connect to the same agent session from multiple VS Code windows. It runs agent harnesses in a dedicated process based on the Agent Host Protocol (AHP). The agent host's Copilot agent is powered by the Copilot SDK, which aligns the agent's behavior and functionality with the Copilot CLI, the standalone GitHub Copilot app, and other Copilot products. We're actively developing the agent host. The following screenshot shows the Copilot harness selected for an agent host in an editor window: Learn more in the agent host documentation and our new agent host blog post, where we share why we built the agent host, what it enables in VS Code, how the architecture and open protocol work, and workflows you can try yourself. If you have any feedback or requests, please let us know by filing an issue.

• + 기업용 정책을 통해 받아쓰기 데이터의 모델 및 언어 모델 전송 방지 제어를 추가한다 # 보안·권한
  원문

  [Chat] Enterprise controls for dictation data: Administrators can manage the dictation model and language-model transcript cleanup through enterprise policies. The new controls make it possible to require on-device transcription and disable language-model cleanup, so dictation remains available while preventing dictation data from being sent to cloud transcription or a Copilot model. Learn more about enterprise controls for dictation data.

• + 편집기 창에서 멀티 루트 워크스페이스를 지원하며, 관련 훅은 단일 폴더에서 로드되도록 설정한다 # 에이전트
  원문

  [Agents] Multi-root workspaces in editor window (Experimental): Settings: chat.agentHost.copilotAgent.multiRootEnabled , chat.agentHost.claudeAgent.multiRootEnabled Copilot and Claude agent sessions in the editor window Chat view support multi-root workspaces. This capability is currently scoped to the editor window. Agent hooks remain scoped to a single workspace folder. If hooks are detected in multiple folders, VS Code prompts you to select the primary folder from which to load them.

• + 새 세션 입력창을 재설계하여 프롬프트, 모델 선택, 워크스페이스 선택 및 기타 세션 제어 항목을 한데 모은다 # 에이전트
  원문

  [Agents] Redesigned new-session input: Start delegated work with less setup in the redesigned new-session input. The updated experience brings the prompt, model selection, workspace selection, and other session controls together in one layout.

• + 에이전트가 절대 경로 및 워크스페이스 URI 외에 프로젝트 이름으로 워크스페이스를 식별하도록 개선한다 # 에이전트
  원문

  [Agents] Improved workspace resolution: Agents can resolve workspaces by their project name in addition to absolute paths and workspace URIs. Session tools also preserve project URIs and all working directories for multi-root workspaces. As a result, you can make requests such as "run this in the vscode workspace" without providing a full path. If multiple workspaces have the same name, the agent reports the possible matches instead of silently choosing one. Remote workspace URIs are supported as well.

• + 에이전트 창에서 관련 채팅과 세션을 계층 구조로 표시하고 관리하기 쉽게 개선한다 # 에이전트
  원문

  [Agents] Navigate related chats and sessions: Keep related agent work organized and move between sessions and chats from the sessions list in the Agents window. Chats appear as children of their parent session, so you can understand which chats belong together without managing a collection of unrelated sessions. Each chat row shows its own title, status, and pending approvals, so you can see which chat needs your input. Expand or collapse the hierarchy, and open, rename, move, or delete individual chats directly from the tree. When an agent delegates independent work to multiple chats, each created chat gets a meaningful title and appears in this hierarchy. The new session or chat is placed close to its source, and the receiving request includes a source link such as Sent by another session or Sent from another chat. Select the link to return to the exact session or chat that initiated it.

• + 에이전트 세션이 사용자 입력을 필요로 하거나 작업이 완료되었을 때 알림을 표시한다 # 에이전트
  원문

  [Agents] Agent session notifications: Settings: chat.notifyWindowOnConfirmation , chat.notifyWindowOnResponseReceived VS Code can notify you when an agent session needs your input or finishes its work. This is especially useful when you delegate work across multiple sessions, workspaces, or VS Code windows. By default, notifications only appear when the VS Code window is not focused. You can configure notifications separately for sessions that need input and sessions that have received a response. Notifications include a direct link back to the relevant session, so selecting one focuses the correct window and opens the session that needs attention.

• + Compact layout density 설정을 통해 에디터 창에 더 많은 콘텐츠를 표시한다 # UI
  원문

  [Editor experience] Layout density for the editor window (Experimental): Settings: workbench.experimental.modernUI , window.density.layout Fit more content in the editor window with the Compact layout density. When workbench.experimental.modernUI is enabled, you can choose between two layout densities: Default layout density is the same as the current editor window layout. Compact layout density removes the spacing between panels and reduces inner panel spacing. This setting is available in the Layout Density section of the Settings menu and can also be set using window.density.layout .

• + 세션 파일의 브레드크럼에 내부 식별자 대신 안정적인 제공자 및 세션 레이블을 사용한다 # 에이전트
  원문

  [Agents] Readable breadcrumbs for session files: Files created in the internal session state directory previously showed internal session identifiers in editor breadcrumbs. Breadcrumbs now use stable provider and session labels, making it easier to identify the file location without exposing implementation details.

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

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

• + Agent host를 통해 여러 VS Code 창에서 동일한 에이전트 세션에 연결할 수 있게 한다 # 에이전트
  원문

  [Agents] Agent host: The agent host lets you connect to the same agent session from multiple VS Code windows. It runs agent harnesses in a dedicated process based on the Agent Host Protocol (AHP). The agent host's Copilot agent is powered by the Copilot SDK, which aligns the agent's behavior and functionality with the Copilot CLI, the standalone GitHub Copilot app, and other Copilot products. We're actively developing the agent host. The following screenshot shows the Copilot harness selected for an agent host in an editor window: Learn more from our VS Code Agent Host documentation and the video below. If you have any feedback or requests, please let us know by filing an issue. See it in action in our Agent Host introduction YouTube video.

• + 다른 애플리케이션에서 생성한 Copilot 또는 Claude 에이전트 세션이 Sessions 리스트에 표시되도록 지원한다 # 에이전트
  원문

  [Agents] Continue external agent sessions in VS Code: Setting: chat.agentSessions.showExternal The Sessions list in VS Code can now show recent Copilot or Claude agent sessions that you created in other applications. By default, VS Code shows up to two recently updated external sessions. Select a session from the Sessions list to view the conversation and continue it in VS Code with your Copilot subscription. When you open an external session, a banner at the top of the chat lets you configure how many external sessions appear in the Sessions list. You can also use the External submenu in the Sessions list filter to choose which external sessions are shown. Change this preference at any time with the chat.agentSessions.showExternal setting.

• + 에이전트의 작업에 대해 보완적인 모델로부터 의견을 얻을 수 있는 Rubber Duck 기능을 추가한다 # 에이전트
  원문

  [Agents] Rubber Duck (Experimental): Rubber Duck is an experimental feature that allows you to get a second opinion from a complementary model on the agent's work. It helps surface missed details or edge cases. You can use Rubber Duck by invoking the /rubber-duck command in a Copilot agent host session. Learn more about Rubber Duck in GitHub Copilot CLI.

• + Agents 창에서 single-pane side layout을 기본값으로 설정하고 레이아웃을 개선한다 # UI
  원문

  [Agents] Single-pane side layout is now the default: Setting: sessions.layout.singlePaneDetailPanel In the previous release, we introduced the single-pane layout. In this layout, session details and editors are located in a single side pane, with a shared tab bar next to chat. The single-pane layout is now enabled by default for the Agents window on desktop. This release also improves the layout: Diffs use a side-by-side view when space permits and switch to an inline view when the side pane becomes too narrow. Use Always Show Inline Diff from the editor title menu to keep diffs inline at every width. The action bar is less crowded. Editor-specific actions for diffs, view modes, code review, and attachments move to the editor title area, while the shared header focuses on showing or hiding Details. To use the classic layout, disable sessions.layout.singlePaneDetailPanel and reload the window.

• + 세션 헤더를 간소화하고 세션 정보를 채팅 입력창 바로 위에 배치하여 가독성을 높인다 # UI
  원문

  [Agents] Simplified session controls and information: The session header is less crowded, so you can identify the active session more easily and focus on the conversation. The session title has a prominent position, while an overflow menu next to the title groups actions for creating a chat and pinning the session. Search remains available in the Sessions list. When a session contains multiple chats, chat tabs replace the single-chat header. Session information moves directly above the chat input, where it is easier to find while you work. Pills can show changes, pull requests, issues, browsers the agent is interacting with, and artifacts from the session. For example, the Changes pill shows live file and diff counts and opens the complete set of session changes. Right-click an individual pill to open a context menu and choose which pill types are visible. The Changes pill remains visible whene

• + 긴 응답을 검토할 때 현재 프롬프트를 계속 볼 수 있게 하는 채팅용 Editor-style sticky scroll을 추가한다 # UI
  원문

  [Chat] Editor-style sticky scroll for chat (Experimental): Settings: chat.stickyScroll.enabled , chat.experimental.stickyScroll.enabled Chat sticky scroll lets you keep the current prompt visible as you scroll through and review long responses. We've further refined the behavior to make it more consistent with sticky scroll in the editor. Enable both settings to try the redesigned experience.

• + 채팅 응답 하단에 모델별로 사용된 입력, 캐시된 입력, 출력 토큰 수를 상세히 표시한다 # 성능
  원문

  [Chat] View detailed chat turn usage: To give you better insight into your chat usage, we've redesigned the chat response footer. When you hover over it, the footer shows a per-model breakdown of the input, cached input, and output tokens used in that chat turn.

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

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

• + 여러 VS Code 창에서 동일한 에이전트 세션을 연결할 수 있는 Agent host를 도입한다 # 에이전트
  원문

  [Agents] Agent host: The agent host lets you connect to the same agent session from multiple VS Code windows. It runs agent harnesses in a dedicated process based on the Agent Host Protocol (AHP). The agent host's Copilot agent is powered by the Copilot SDK, which aligns the agent's behavior and functionality with the Copilot CLI, the standalone GitHub Copilot app, and other Copilot products. We're actively developing the agent host. The following screenshot shows the Copilot harness selected for an agent host in an editor window: You can learn more in our VS Code Agent Host documentation. If you have any feedback or requests, please let us know by filing an issue.

• + 세션 내 채팅을 가로 또는 세로 그룹으로 배치하는 Grid layout을 추가한다 # 에이전트
  원문

  [Agents] Grid layout for chats in a session: Keep related conversations visible by arranging chats in horizontal or vertical groups. Drag chats or subagent chats into a group to compare results or monitor work side by side. VS Code restores the chat-group layout and focus when you return to the session or reload the window. Create a side chat to open a new conversation beside the current chat. Drag and drop a subagent chat into a group to view it side by side with the current chat. You can also Alt+select a chat in the Chats picker to open it to the side.

• + 긴 에이전트 세션에서 이전 프롬프트를 쉽게 찾을 수 있는 Prompt timeline을 추가한다 # 에이전트
  원문

  [Agents] Prompt timeline: Setting: sessions.chatTimeline.display Long agent sessions can make it difficult to find earlier prompts and identify which ones changed files. The Agents window includes a timeline in the transcript gutter. Each dot represents one of your prompts, and the highlighted dot marks your current position. Hover over the timeline to view your prompts, then select one to jump to it. For prompts that changed files, the list shows the number of lines added and removed and lets you open the changes directly for review. Use the sessions.chatTimeline.display setting to show the timeline beside the scrollbar (ruler) or hide it (off).

• + Chat 뷰, 채팅 에디터, Agents 윈도우에서 ⌘F(Windows, Linux Ctrl+F)를 사용하여 대화를 검색한다 # UI
  원문

  [Chat] Find in chat: Finding information from earlier in a long conversation previously required scrolling through the transcript. Use ⌘F (Windows, Linux Ctrl+F) to search conversations in the Chat view, chat editors, and the Agents window. Search includes the entire conversation, even content that is not currently rendered on screen. As you move between matches, VS Code scrolls each match into view and expands a collapsed work summary if it contains the match. You can also match case, match whole words, or use regular expressions.

• + 사이드 패널 레이아웃을 개선하여 세션 전환 시 레이아웃 변화를 방지한다 # 에이전트
  원문

  [Agents] Improvements to the side pane layout: Settings: sessions.layout.singlePaneDetailPanel and workbench.editor.showTabs The single-pane layout keeps session details and editors in a shared tab bar next to chat. This release makes the layout easier to control: The layout follows the workbench.editor.showTabs setting. Multiple tabs remain visible, while the single and none values use a compact single-title header. Text file editors use the same header structure as the Changes editor, with file breadcrumbs in the header. The side pane keeps its size and visibility when you switch sessions, avoiding unexpected layout shifts. Enable sessions.layout.singlePaneDetailPanel and reload the window to use this layout.

• + Alt 키를 누른 채 탭을 선택하여 다른 에디터를 닫고 하나만 남기는 기능을 추가한다 # UI
  원문

  [Editor Experience] Close other editors from a tab: Keep one editor open without using the tab context menu. Hold Alt to change the close action on each editor tab to Close Other Editors, then select the action on the tab you want to keep.

• + 로컬 HTML 파일을 기본적으로 통합 브라우저에서 열도록 설정하는 기능을 추가한다 # UI
  원문

  [Editor Experience] Open HTML files in the integrated browser by default: Setting: workbench.editorAssociations If you often preview local HTML files instead of editing them, set the integrated browser as their default editor. Configure this behavior with the workbench.editorAssociations setting or from the editor header. The integrated browser provides the same features as a standalone browser tab while remaining associated with the HTML file. To preserve this association, links and other navigation open in new tabs.

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

• + Agent host를 통해 여러 VS Code 창에서 동일한 에이전트 세션을 연결할 수 있게 한다 # 에이전트
  원문

  [Agents] Agent host: The agent host lets you connect to the same agent session from multiple VS Code windows. It runs agent harnesses in a dedicated process based on the Agent Host Protocol (AHP). The agent host's Copilot agent is powered by the Copilot SDK, which aligns its behavior and functionality with the Copilot CLI, the standalone GitHub Copilot app, and other Copilot products. We're actively developing the agent host. The screenshot below shows how to select the Copilot harness on the agent host in the editor window: You can learn more in our VS Code Agent Host documentation. If you have any feedback or requests, please let us know by filing an issue.

• + Agent Plugins 표준을 지원하여 한 번에 설치 가능한 에이전트 커스터마이즈를 제공한다 # MCP·플러그인
  원문

  [Agents] Support for the Agent Plugins standard: Plugins bundle agent customizations into something you can install in one step. The catch has been that every agent tool expected its own layout, so publishing the same skill and MCP server to several tools meant maintaining a separate package for each. Agent Plugins 1.0 replaces those per-tool layouts with one open standard, and VS Code was part of its launch on August 6 along with other agent clients. A plugin that follows the standard is a directory with a plugin.json manifest, skills in skills/, and MCP server configuration in mcp.json. VS Code loads those portable components, and it also reads Copilot-specific components from the com.github.copilot namespace in the same package: Clients that don't implement the namespace ignore it. One package can therefore stay portable and still bring your custom agents, slash commands, rules, and hooks to

• + Claude 세션에서 Anthropic 및 Copilot 모델을 혼합하여 사용할 수 있게 한다 # 에이전트
  원문

  [Agents] Mix Anthropic and Copilot models in Claude sessions: Previously, a Claude session ran entirely through either your GitHub Copilot subscription or Claude's existing configuration, such as an API key. Switching providers required reconfiguring the agent host. Now, the model picker displays both groups, so you can switch providers between turns. The model you select is used for the next turn. Models under Anthropic bill your API key, and models under Copilot use your Copilot subscription.

• + GitHub 로그인 없이 Agents 창을 열 수 있는 설정을 추가한다 # 보안·권한
  원문

  [Agents] Open the Agents window without GitHub sign-in (Experimental): Setting: chat.agentHost.allowSignedOutWhenUsable The Agents window used to open with a GitHub sign-in prompt you could not dismiss. That blocked anyone whose machine can't reach github.com or anyone who doesn't interact with GitHub. Users with Claude already configured with an API key who don't need GitHub sign-in had this extra step. Enable this setting to open the Agents window without signing in to GitHub. GitHub authentication is then associated with individual agents or models instead of the Agents window. In this release, this behavior only supports Claude. Support for Copilot with your own model keys and Codex is planned for future releases.

• + 채팅에서 프롬프트가 상단에 고정되는 Sticky scroll 기능을 추가한다 # UI
  원문

  [Chat] Sticky scroll for prompts: Setting: chat.stickyScroll.enabled When you scroll through a long conversation, you can lose track of which prompt a response belongs to. The prompt you have scrolled past now stays pinned to the top of the chat, similar to sticky scroll in the editor. The pinned prompt shows its position in the conversation. Select it to jump back to that prompt, or use the previous and next buttons beside it to step through your prompts.

• + 통합 브라우저에서 HTML 파일이 변경될 때 자동으로 다시 로드되도록 한다 # UI
  원문

  [Editor Experience] Auto-reload HTML files in the integrated browser: Setting: workbench.browser.autoReloadOnFileChange When a local HTML file is open in the integrated browser, it now refreshes automatically when the file changes on disk. This helps you see agent edits or your own saved changes immediately. You can toggle automatic reload for individual browser tabs and configure the default with the workbench.browser.autoReloadOnFileChange setting.

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

• + 여러 VS Code 창에서 동일한 에이전트 세션을 연결할 수 있는 Agent host를 도입한다 # 에이전트
  원문

  [Agents] Agent host: The agent host lets you connect to the same agent session from multiple VS Code windows. It runs agent harnesses such as Copilot, Claude, and Codex in a dedicated process based on the Agent Host Protocol (AHP). The agent host's Copilot agent is powered by the Copilot SDK, which aligns its behavior and functionality with the Copilot CLI, the standalone GitHub Copilot app, and other Copilot products. We're actively developing the agent host and progressively rolling it out to users. The screenshot below shows how to select the Copilot harness on the agent host in the editor window: You can learn more in our VS Code Agent Host documentation. If you have any feedback or requests, please let us know by filing an issue.

• + 여러 에이전트 세션을 시작하고 모니터링할 수 있는 Agents window를 제공한다 # 에이전트
  원문

  [Agents] Agents window: The Agents window gives you a dedicated space to start and monitor multiple agent sessions. When an agent works across files, subagents, previews, and browsers, you can use live status pills above the chat input to follow its progress and quickly return to related work. The pills update with the activity for the session you are viewing: Changes summarizes the number of changes. Select it to view the changes for the current turn in a multi-file diff that updates live. Previews provides access to Markdown previews for files the agent creates or edits. Subagents lets you follow what the agent is doing in a subagent by opening its work in a separate chat. Browsers lets you follow along while the agent interacts with an integrated browser. Setting: breadcrumbs.showEditorType When multiple editor types are available, an editor type dropdown in the Agents window shows the curre

• + 현재 턴을 방해하지 않고 질문을 할 수 있는 /btw 명령어로 Side chat을 열 수 있다 # 에이전트
  원문

  [Agents] Side chats with /btw: When you want to ask a question without interrupting the current turn, you can open a side chat by typing /btw in the chat input. The side chat shares the context and prompt cache of your primary chat, so you can ask questions about the current turn. Similarly, you can select text in a chat response to ask contextual questions about that response. You can also share context by referencing chats in other chats, either by dragging the chat tabs into the input box, or typing #chat: and then picking the title of the chat to include.

• + 음성을 텍스트로 변환하는 Dictation 기능에 온보딩과 설정 옵션을 추가한다 # 에이전트
  원문

  [Editor experience] Dictation onboarding and customization: Setting: agents.voice.language The built-in dictation converts speech to text in chat inputs, editors, and terminals. When you use dictation for the first time, an onboarding experience helps you verify the selected microphone before you start. It shows a live microphone waveform, provides a device picker when multiple microphones are available, and links to dictation settings and customization. You can reopen this experience with Voice Mode: Show Introduction from the Command Palette. Dictation now uses multilingual Nemotron 3.5 as its default on-device model. The model keeps audio on your device and follows agents.voice.language . With automatic language selection, dictation uses your system or browser locale when supported and otherwise lets the model detect the language. To adapt the final transcript to project terminology or formatting prefe

• + hybrid Markdown 에디터에서 Markdown diff를 열 수 있도록 지원한다 # UI
  원문

  [Editor experience] Markdown diffs in the hybrid Markdown editor (Experimental): In the previous release, we introduced the hybrid Markdown editor, which combines rendered Markdown with in-place editing and agent-actionable comments. In this release, Markdown diffs can open in the hybrid Markdown editor. The modified document remains editable, while gutter indicators highlight added, changed, and deleted content. You can use the editor type dropdown to switch between text diff and the Markdown editor with diff annotations.

• + 통합 브라우저에서 웹 페이지 요소를 선택하고 에이전트 피드백으로 주석을 달 수 있게 한다 # UI
  원문

  [Editor experience] Commenting in the integrated browser: To provide feedback on web pages, it is often useful to comment on specific elements. In this release, the integrated browser adds support for selecting web page elements and annotating them with agent feedback. You can trigger this mode by using the ⌥⌘C (Windows, Linux Ctrl+Alt+C) keyboard shortcut. In this mode, you can select multiple elements and add a comment to each before sending to the chat.

• + 터미널 명령어를 위한 쉘 문법을 인식하여 음성을 텍스트로 변환하는 기능을 개선한다 # UI
  원문

  [Terminal] Better dictation for terminal commands: Terminal dictation applies shell-aware cleanup, so spoken commands preserve shell syntax. For example, saying "git commit dash m hello world" produces git commit -m "Hello World" instead of inserting the words literally. Select the active microphone button to stop recording.

• + 에디터 모드에 따라 커스텀 에디터 우선순위를 설정하는 `customEditors.priority` 기능을 추가한다 # 에이전트
  원문

  [Proposed APIs] Configure custom editor priorities by editor mode: The proposed customEditors.priority feature lets extensions choose different priorities for text and diff editors. For example, an extension can use its custom editor by default for regular files while keeping the built-in editor as the default for diffs and vice versa. Existing single priority values continue to work, and diff editors use explicit by default. Extension authors can learn more about configuring custom editor priorities. We plan to promote this feature to stable in the next release.

• + Chat에서 확장된 터미널 출력을 뷰 크기에 맞춰 리플로우(reflow)하도록 개선한다 # UI
  원문

  [Chat] Terminal output reflow: Expanded terminal output in Chat reflows to the available width as the view is resized. Previously, output used a fixed width, which caused lines to wrap too early and left unused space in wider views. This improvement applies to terminal output from both the Local agent harness and the Copilot harness running on the agent host.

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

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

• + Agent Host 기반의 새로운 에이전트 세션 구조를 도입하고 관련 기능을 점진적으로 출시한다 # 에이전트
  원문

  [Agents] Agent host: As mentioned in our last few releases, we're rearchitecting how agent sessions work in VS Code around the agent host - a dedicated process that runs agent harnesses such as Copilot, Claude, and Codex, based on the Agent Host Protocol (AHP). Because a session lives in its own process, the same session can be connected to and rendered from multiple VS Code windows at once. The agent host's Copilot agent is powered by the Copilot SDK, which means that its behavior and functionality is aligned with the Copilot CLI, the standalone GitHub Copilot app, and other Copilot products. We're actively developing the agent host and progressively rolling it out to users. To opt in, enable chat.agentHost.enabled and then select an agent host harness from the harness dropdown. The screenshot below shows how to select the Copilot harness on the agent host in the editor window: You can learn m

• + 별도 확장 프로그램 없이도 채팅, 에디터, 터미널에서 사용할 수 있는 내장 받아쓰기 기능을 추가한다 # UI
  원문

  [Editor Experience] Built-in dictation across VS Code (Experimental): Setting: dictation.enabled , dictation.showTranscript (VS Code Insiders), dictation.experimental.llmCleanup To use dictation in VS Code, you no longer need to install the VS Code Speech extension. The built-in transcription service works in chat inputs, text editors, and the integrated terminal, with live text and controls suited to each surface. A single speech session and microphone selection are shared across all three surfaces, which prevents overlapping recordings and keeps dictated text in the intended location. Built-in dictation uses the private, offline Nemotron model. The model downloads on first use and keeps audio on your device. With dictation.experimental.llmCleanup enabled, Copilot refines your transcript as you speak by adding formatting and removing filler words. Transcript text is sent to a language model for cleanup.

• + Agents 창에서 실행 중인 서브에이전트의 상태 정보를 표시하고 클릭하여 별도 대화창에서 열 수 있게 한다 # 에이전트
  원문

  [Agents] More information about running subagents (Agents window): When working on complex tasks, the agent can delegate tasks to subagents to run them in parallel in its own context window. You can now quickly see what a running subagent is doing without opening its conversation. In the Agents window, the main conversation shows the following information for each running subagent: The model used by the subagent How long the subagent has been running The tool that the subagent is actively calling Select a running subagent to open its conversation in another chat, where you can review its full progress while the parent conversation remains available.

• + Agents 창에서 마크다운 파일을 직접 편집하고 주석을 추가할 수 있는 하이브리드 마크다운 에디터를 도입한다 # UI
  원문

  [Editor Experience] Hybrid Markdown editor (Experimental): Setting: workbench.editor.markdownDefaultEditorInAgentsWindow In this release, we introduce a new hybrid Markdown editor in the agents window. It lets you view Markdown files, edit them in-place, and add comments that an agent can act on. By using Reopen Editor With you can switch between the text editor and this new Markdown editor, both in the Agents window and editor windows.

• + Python 환경 관리 경험을 개선하고 Conda 및 Pylance 관련 성능 최적화를 수행한다 # 성능
  원문

  [Languages] Python: Python Environments is the default environment-management experience in VS Code Stable and Insiders after its rollout reached 100% of users. Review the Python Environments rollout details and tracking. Python projects start faster and spend less time refreshing environments. Conda discovery is deferred until needed, concurrent environment scans are consolidated, and Pylance can use the last-known interpreter while a full refresh continues. #1600: Lazy-register Conda manager, #1598: Coalesce concurrent native finder refreshes with the same key, #1607: Return last-known environment when getEnvironment times out

• + 터미널의 접근성 뷰에서 커서 위치를 유지하고 알림 방식을 개선하여 스크린 리더 사용자를 위한 제어 기능을 강화한다 # UI
  원문

  [Accessibility] More control over terminal screen reader updates: Setting: terminal.integrated.accessibleViewPreserveCursorPosition Screen reader users can read terminal output at their own pace while commands continue to produce output. Set terminal.integrated.accessibleViewPreserveCursorPosition to always to preserve the cursor position in the terminal Accessible View, including when new content arrives. Existing true and false values continue to work. Terminal live updates also use a non-interrupting ARIA status announcement instead of an assertive alert. Output remains available to screen readers without repeatedly interrupting other speech.

• + 터미널 크기 조절 시 나타나는 치수 오버레이를 설정으로 끄고 켤 수 있게 한다 # UI
  원문

  [Terminal] Control the terminal resize dimensions overlay: Setting: terminal.integrated.resizeDimensionsOverlay.enabled If you find the columns-by-rows overlay distracting when resizing the terminal, you can disable it with the terminal.integrated.resizeDimensionsOverlay.enabled setting. The overlay remains enabled by default, and setting changes apply immediately to open terminals without a restart.

• + 채팅에서 /vscode-pet 명령어로 실험적인 펫을 소환하는 기능을 추가한다 # UI
  원문

  [Chat] VS Code pet (Experimental): A new highly experimental pet has been discovered in VS Code! Enter /vscode-pet in chat to meet your new companion. From September 10 through September 17, 2026, submit a name for the new VS Code pet. Review the contest terms and conditions.

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