VS Code 1.137

· 기타 11개

• [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. 요약 대기
• [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 . 요약 대기
• [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] 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. 요약 대기
• [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. 요약 대기
• [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. 요약 대기
• [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 요약 대기
• [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. 요약 대기
• [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. 요약 대기
• [Languages] GitHub links in the Markdown editor (Experimental): Settings: markdown.experimental.richLinks.enabled , chat.experimental.richLinks.enabled GitHub issue and pull request links in the Markdown editor show the current title and state, so you can understand each reference without opening it first. The link updates when its issue or pull request state changes, including CI updates. To use the same link rendering in chat, set chat.experimental.richLinks.enabled to true. 요약 대기