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

• + 클라우드 에이전트와 Cursor harness를 개선하여 에이전트가 스스로 소프트웨어를 구축하고 배포할 수 있게 한다 # 에이전트
  원문

  Cloud Agents and Cursor Harness Improvements: We're continuing to improve cloud agents and the Cursor harness so always-on agents can operate as a system, building and shipping software on their own without the need for intervention at each loop. With this release, cloud agents can automatically pick up work in response to events, hold a goal until it's met, and stay on course through long-running sessions.

• + 클라우드 에이전트가 이벤트 소스(스레드 또는 대화)를 구독하여 특정 이벤트 발생 시 작동하도록 하는 구독 기능을 추가한다 # MCP·플러그인
  원문

  Subscriptions: Cursor can now monitor your PRs, watch a Slack thread, or run scheduled tasks. Cursor Agent subscribes to an event source (a thread or conversation) and wakes when something happens. Subscriptions are available for cloud agents only, for now. Cloud agents automatically subscribe to PRs they create and drive them to completion, fixing CI and addressing bot comments. In Slack, ask `@cursor check back in an hour and keep going until that feedback is in`.

• + 서브에이전트가 독립적인 가상 머신에서 실행되어 고립된 환경에서 작업을 수행하도록 한다 # 에이전트
  원문

  Subagents on their own machines: Subagents can now run on their own virtual machines. Each gets an isolated copy of the project with clean context in its own cloud environment. Have subagents test the parent agent's changes in fresh environments or swarm independent fixes without collisions. Try `run a swarm of subagents to test my app for bugs, each in its own environment`.

• + 채팅에서 고정된 기술을 사용하여 에이전트가 특정 기술에 집중하도록 하는 Custom Mode를 추가한다 # 에이전트
  원문

  Custom modes: Use any skill as a Custom Mode: a skill that stays pinned in the chat. Custom modes keep agents focused on a skill - you can think about it like "always on" skills. From `/`, pick a skill and press ⌥⏎ (Mac) or Alt+Enter (Windows), or choose **Use as Mode**.

• + 에이전트에게 장기적인 목표를 부여하는 `/goal` 명령어를 추가한다 # 에이전트
  원문

  /goal: Use `/goal` to give the agent a long-lived objective to work towards until it's fully complete. Try `/goal fix all flaky tests and make CI green` in a new chat. Pair it with a custom mode to follow a playbook, or `/loop` for recurring check-ins.

• + 에이전트가 작동하는 동안 중단 없이 메시지를 보내어 에이전트를 유도하는 기능을 개선한다 # UI
  원문

  Steering improvements: You can now send a message to steer the agent while it's working without interruption. Follow-ups wait for the next tool call instead of cutting the agent off mid-action. Type a follow-up and hit Send now, or press ⏎ twice.

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

• + Cursor가 코드를 호스팅하는 Origin Code Hosting 기능을 베타 버전으로 출시한다 # 에이전트
  원문

  Origin Code Hosting: Cursor can now host your code. Origin begins rolling out today in early beta on all paid plans. We're starting with the essentials, designed for agent scale: repos, pull requests, code browsing, and GitHub sync. Agent-native features ship soon.

• + 모든 리포지토리에서 코드 탐색, 질문, PR 업데이트 및 브랜치 푸시를 수행하는 에이전트 기능을 통합한다 # 에이전트
  원문

  Agents in every repo: Your code, PRs, and agents are now in the same place. Ask Cursor questions about code you're browsing. It can answer, make changes, update PRs, or push a branch.

• + Origin 호스팅 리포지토리용 Codebase 탭을 추가하고 CLI 설치 및 리포지토리 생성 기능을 제공한다 # MCP·플러그인
  원문

  Origin Repos: The new **Codebase** tab is home for Origin repos. Click **+New** to create a new repo and name it. Once you do, a page shows you how to install the CLI, with commands for how to clone a repo or push a local project. Push, and your code is hosted on Origin. For Origin-hosted repos, Origin is the source of truth. Pushes land on Origin, and GitHub is not in the path. Name your codebase when you create your first repo. That name becomes part of every repo's URL: cursor.com/codebase/`acme-corp`.

• + GitHub 리포지토리와 연동하여 실시간 동기화 및 Cursor 내에서 검색 및 탐색이 가능하도록 한다 # MCP·플러그인
  원문

  Bring your GitHub repos: Your GitHub repos can sit alongside the ones Cursor hosts. Connect GitHub to Cursor, pick your org, and you'll see the repos you can sync. Select one and Cursor pulls it in. You choose what gets synced and can disconnect a repo at any time. Anyone with read or write access to a synced repo can view it in Cursor too. Synced repos update in real time. Browse, search, and pull from the copy in Origin. For synced repos, GitHub stays the source of truth: pushes keep going to GitHub, and Origin mirrors the result. Icons next to each repo name tell you which ones Cursor hosts and which came from GitHub.

• + 모든 리포지토리에서 Pull requests 기능을 지원하며, 동기화된 리포지토리에서는 양방향 동기화가 이루어진다 # 에이전트
  원문

  Pull requests: Every repo has pull requests. Open one to see the timeline, commits, checks, and files changed. Review the diff, leave comments, and merge. Pull requests on synced repos sync both ways: comment in Cursor and it posts to GitHub, react or reply on GitHub and it shows up in Cursor within seconds. Got a review assigned to you on GitHub? Review and merge it from Cursor.

• + Vercel, Depot, Buildkite 등과 연동되는 앱 생태계 및 Preview Deployment 기능을 추가한다 # MCP·플러그인
  원문

  App extensions for Cursor repos: We're building an app ecosystem so your whole stack works seamlessly with Origin. Integrations with Vercel, Depot, and Buildkite are already available, with more coming soon. Connect Vercel from a repo's **Apps** tab and every PR gets a preview deployment where you can test and make comments. Merge, and it ships to production. For CI, connect Depot or Buildkite. Both run your existing GitHub Actions workflows and Buildkite also runs its native pipelines. Vercel, Depot, and Buildkite apps connected to an Origin repo

• + 각 리포지토리의 동기화 상태, 접근 권한 관리 및 연결된 앱을 확인하는 설정 기능을 제공한다 # 보안·권한
  원문

  Settings: Every repo has settings. Check sync status for GitHub repos, manage who has access, and see which apps are connected. Origin repo settings showing sync status, access, and connected apps Origin is rolling out in early beta to all paid plan users starting today, except enterprise orgs whose admins opt out. Name your codebase and create your first repo. Learn more in our docs or get started today.

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

• + 에이전트가 미리 준비된 환경에서 시작할 수 있도록 `Builds` 기능을 도입한다 # 에이전트
  원문

  Cloud Agents Start 3x Faster with Builds: Agents do their best work when they start in a ready environment: repos cloned, dependencies installed, and your install script already run. This release introduces **builds**: ready-to-use copies of your development environment that Cursor prepares in the background. Agents boot into a ready environment instead of setting up from scratch each session. Builds are included with Cloud Agents at no additional cost.

• + 환경 빌드 시스템을 통해 에이전트 시작 속도를 3배 향상시키고 첫 토큰 생성 속도를 10배 향상시킨다 # 성능
  원문

  Faster starts: Cursor runs a new build of your environment regularly. When a build succeeds, it becomes the environment future agents start from. Cursor keeps warm copies ready so the next agent does not wait. Internally, our environments now boot 10x faster, with 3x faster time to first token. Use your install command for anything that can be prepared ahead of time. The start command still runs when you first prompt an agent and should focus on services that need to be fresh in the session.

• + 환경이 손상되었을 때 에이전트가 마지막 성공적인 빌드를 사용하여 계속 작동하도록 개선한다 # 에이전트
  원문

  More resilient agent runs: When a bad commit or dependency update breaks your environment, agents keep using the last successful build. The broken build never becomes active, you are notified of the issue, and your agents keep working while you debug in the background.

• + Cloud Agents 대시보드에 `Builds` 탭을 추가하여 빌드 상태와 로그를 확인할 수 있게 한다 # UI
  원문

  Build history and debugging: Each environment has a **Builds** tab in the Cloud Agents dashboard. You can inspect build status, logs, commit SHAs, and which build each agent run used. Agents can also inspect and manage builds using built-in tools.

• + 기존 환경에서 `Builds` 기능을 활성화하고 수동 빌드 및 설정된 임계값에 따라 빌드를 갱신하는 기능을 제공한다 # 에이전트
  원문

  Getting started: New environments use Builds automatically. For an existing environment, open it in the Cloud Agents dashboard, go to the **Builds** tab, and click **Enable Builds**. Or click **Run setup agent** first to test the migration and review any proposed config changes. You can also trigger a Build manually, debug a failing Build with an agent, and control how stale Builds refresh with a configurable threshold. Learn more in our announcement post and docs.

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

• + AI 에이전트가 실시간 커널을 통해 .ipynb 노트북을 생성, 수정, 실행하며 데이터가 셀 간에 유지되도록 한다 # 에이전트
  원문

  AI agents like Claude Code and Codex can now create, edit, and run .ipynb notebooks against a live kernel, so data persists across cells

• + AI 에이전트가 시스템 환경 대신 프로젝트에 설정된 인터프리터(uv, Poetry, pip, conda)를 대상으로 삼도록 한다 # 에이전트
  원문

  AI agents now target your project's configured interpreter - uv, Poetry, pip, or conda - so packages land in the right environment instead of a system one.

• + marimo 팀의 새 플러그인을 통해 PyCharm에서 marimo 노트북을 직접 열고, 수정하고, 실행한다 # MCP·플러그인
  원문

  Open, edit, and run reactive marimo notebooks directly in PyCharm via the new plugin from the marimo team.

• + 접근 가능한 종속성 트리와 인라인 Install/Update 링크를 포함하는 재설계된 Python Packages 창을 제공한다 # UI
  원문

  Explore the redesigned Python Packages window with a collapsible dependency tree and inline Install/Update links.

• + 대상 환경과 종속성 그룹을 보여주는 새로운 플로팅 검색 팝업으로 패키지를 빠르게 찾고 설치한다 # UI
  원문

  Find and install packages fast with a new floating search popup that shows the target environment and dependency group.

• + inspection 툴팁에 전체 렌더링된 이름과 타입을 표시하고 클릭 가능한 링크를 추가한다 # UI
  원문

  See fully rendered names and types in inspection tooltips, with clickable links

• + 타입 불일치 오류를 상세하게 분석하여 왜 타입이 일치하지 않는지 보여준다 # UI
  원문

  Read richer type-mismatch errors that break down why the types don't match

• + 호출 가능(callable) 및 복합 타입에 대한 타입 차이를 시각화하여 양쪽이 동일하게 읽히도록 한다 # UI
  원문

  View a type diff for callables and composite types so both sides read the same way

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

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

• + WebStorm에서 Figma 파일의 레이어를 선택하고 디자인 컨텍스트를 AI Chat에 자동으로 연결하는 Figma Connect for WebStorm 플러그인을 도입한다 # MCP·플러그인
  원문

  We've introduced the Figma Connect for WebStorm plugin. Select a layer in your Figma file and get its design context directly in WebStorm. The context is attached to the AI Chat automatically. Requires a one-time setup. Read the blogpost for more details.

• + AI 에이전트가 Chrome을 열고 콘솔 로그, 네트워크 요청, 스크린샷을 촬영하며 실행 중인 페이지와 상호작용할 수 있는 Chrome DevTools CLI 스킬을 번들로 포함한다 # MCP·플러그인
  원문

  We've bundled a Chrome DevTools CLI skill into WebStorm, so AI agents can open Chrome, read console logs and network requests, take screenshots, and interact with the running page. One-time package installation on first use, automatic startup after that.

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

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

• + Cursor에서 Google Workspace(Gmail, Google Drive, Calendar)를 다룰 수 있는 새로운 플러그인을 추가한다 # MCP·플러그인
  원문

  Google Workspace Plugins: Cursor can now read, write, and act across your Google Workspace. New plugins give coding agents direct access to Gmail, Google Drive, and Calendar, so you can pull context, draft and update files, and manage your inbox and calendar without leaving Cursor. Install plugins to connect: **Google Drive:** search files and folders, open and download content, create and organize files **Gmail:** search and read mail, draft and send messages, apply labels and manage threads **Google Calendar:** read schedules, create and update events, find free time Browse the new plugins in the Cursor Marketplace or install them from the Customize page in Cursor. Learn more in our docs.

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

• + Cursor를 iPad용으로 출시하고 모든 유료 플랜에서 사용 가능하게 한다 # UI
  원문

  Cursor, now on iPad: Cursor for iPad is now available on all paid plans. New to both iPhone and iPad: an inbox to stay organized, and a review experience that covers the full PR. Create, review, and merge from anywhere.

• + iPad 화면에 맞춰 레이아웃을 재구성하고 Apple Pencil을 활용한 마크업 기능을 추가한다 # UI
  원문

  Built for the bigger screen: The iPad layout is rebuilt around the extra space. Sidebar chats stay pinned so you can watch several agents run at once. Split screen keeps a review open next to a chat, and file diffs render in full. Markup gets more room to work too. Attach a screenshot, then tap to drop a comment at a specific point, or draw directly on the image with Apple Pencil.

• + iPhone과 iPad에서 전체 PR을 검토하는 리뷰 화면을 제공한다 # 에이전트
  원문

  A full review surface: On iPhone and iPad, the review screen now covers the full PR: comments, checks, and approvals. Add or change reviewers, read comments, and prompt the agent to resolve them. The whole path from agent output to merged PR now travels with you.

• + 정리 및 관리를 돕는 Inbox 기능을 추가한다 # UI
  원문

  Inbox: An Inbox helps you and your agents stay organized. See what's in progress, what needs your attention, and which PRs are in review. Inbox on Cursor for iPad

• + Bitbucket 및 Azure DevOps SCM에서 Multi-PR 세션을 지원하며, 소속 팀을 앱 내에서 직접 전환할 수 있게 한다 # 에이전트
  원문

  Additional improvements for Cursor on iPhone and iPad: Bitbucket and Azure DevOps SCM support Multi-PR sessions: when one chat creates multiple PRs, you can now open every one of them, not just the last. Switch between teams that you belong to directly in the app Download the Cursor App or read our docs to learn more.

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

• + 인도 지역을 위한 새로운 Cursor Start 요금제를 출시한다 # 에이전트
  원문

  Cursor Start: We're introducing Cursor Start, a new ₹649 monthly plan for developers in India, making daily agentic development accessible and payment easy with local pricing and UPI. Existing Free users in India can upgrade their plan from the dashboard. New users in India can visit cursor.com/signup and select the Start plan during onboarding. Start bills monthly with auto-renewal and is available from July 28, 2026. Cursor Start includes: **Generous access to Cursor models:** Grok and Composer, with enough usage to build with agents every day. **Always-on cloud agents** that build, test, and ship code while you keep working. **Cursor for iOS** with remote control, so you can launch and steer agents from your phone. **Plugins, MCP servers, hooks, and skills** to extend Cursor across your workflows. **Local pricing** at ₹649 per month, tax inclusive, billed in INR with UPI or card. Le

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

• + 프록시 인증 처리를 개선하여 프록시 서버가 407 상태 코드를 반환할 때 IDE가 인증 정보를 다시 요청하도록 한다 # 보안·권한
  원문

  We've improved proxy authentication handling, so the IDE now prompts to enter authentication credentials again if the proxy server returns a 407 status code (IJPL-210659).

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

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

• + Cursor Router를 통해 Auto 모드를 강화하고 요청에 따라 적절한 모델을 자동으로 선택하도록 한다 # 에이전트
  원문

  Cursor Router: Auto mode is now powered by Cursor Router. Cursor Router is our intelligent model router. It analyzes each request and sends it to the right model for the job. Frontier models handle work that demands them. Price-efficient models handle the rest.

• + Auto 모드에서 Intelligence, Balance, Cost 세 가지 최적화 모드를 선택할 수 있게 한다 # 에이전트
  원문

  Optimization modes: Select Auto, then choose how the router optimizes: **Intelligence:** Frontier quality, matching the most expensive and powerful models that might be out of reach for daily use. **Balance:** Strong quality, matching the frontier models that most people like to daily drive. **Cost:** Good quality, reaching the highest available intelligence while optimizing token spend. Balance and Intelligence bill at the routed model’s rate. Each mode moves you along the cost-intelligence pareto frontier.

• + 관리자가 팀 또는 그룹별로 Router를 활성화하고, 최적화 모드 제한 및 기본 모델 허용/차단 목록을 설정할 수 있게 한다 # 보안·권한
  원문

  Admin controls: Admins can enable the router per team or group, restrict which optimization modes members can use, set the default mode, and allow or block underlying models. Cursor Router is available across desktop, web, iOS, CLI, and our SDK. It is on by default for Teams plans. Enterprise admins can enable it from the dashboard. Learn more in our announcement and docs. Improvements Per-request classification by task type and complexity Optimization modes: Cost, Balance, and Intelligence Admin controls: per-team and per-group enablement, mode restrictions, default mode, and model allow and block lists Routed model can be displayed or hidden (hidden by default) Soft and hard enforcement options for standardizing on Auto Grok 4.5 required as a price-efficient routing option

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

• + 의존성 정보에 대한 인라인 버전 힌트와 빠른 문서를 한눈에 확인한다 # UI
  원문

  See inline version hints and quick documentation for your dependencies at a glance.

• + AI를 사용하여 자연어 프롬프트로 전체 프로젝트를 생성한다 # 에이전트
  원문

  Generate entire projects from natural language prompts with AI.

• + Rust 플러그인으로 Python 확장 모듈을 직접 개발한다 # MCP·플러그인
  원문

  Develop Python extension modules directly with the Rust plugin.

• + uvx를 통해 실행되는 도구의 설정 UI를 재설더하여 더 빠르게 설정한다 # UI
  원문

  Configure external tools faster with the redesigned settings UI for tools running via uvx.

• + debugpy를 기본으로 활성화하여 디버깅 워크플로우를 표준화한다 # 에이전트
  원문

  Standardize your debugging workflow with debugpy enabled by default.

• + 터미널 세션에 파일과 이미지를 드래그 앤 드롭으로 추가한다 # UI
  원문

  Drag and drop files and images straight into terminal sessions.

• + 편집기 내에서 대화형 Docker Compose 컨테이너 상태를 추적한다 # MCP·플러그인
  원문

  Track interactive Docker Compose container statuses right in the editor.

• + Pyrefly 타입 엔진 통합을 통해 더 빠른 진단을 제공한다 # 성능
  원문

  Get faster diagnostics through the Pyrefly type engine integration.

• + 전용 Jupyter Notebook 미니맵 레이아웃으로 노트북을 탐색한다 # UI
  원문

  Navigate notebooks with the dedicated Jupyter Notebook minimap layout.

• + 기본적으로 멀티 프로젝트 설정과 uv 워크스페이스를 지원한다 # MCP·플러그인
  원문

  Work with multi-project setups and uv workspaces by default.

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

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

• + Slack에서 Cursor가 실행 전 계획을 공유하고, 멀티 레포지토리 환경에서 작동하며, 채널과 스레드 간에 작동할 수 있게 된다 # 에이전트
  원문

  Improvements to Cursor in Slack: Cursor in Slack now shares a plan before it starts, runs in multi-repo environments, and can work across channels and threads.

• + Slack에서 Cursor가 단일 기본 레포지토리 대신 이름이 지정된 멀티 레포지토리 환경에서 시작할 수 있게 된다 # 에이전트
  원문

  Multi-repo environment support: From Slack, Cursor can now start in a named multi-repo environment instead of a single default repository. If your frontend, backend, and shared code live in separate repos, Cursor reads your request and targets the environment that gives it access to all of them. Mid-task, when Cursor needs a repo outside the current environment, it prompts you with a **Switch repository** button. Click it, choose the repo or environment, and Cursor picks up right where it left off.

• + Cursor가 시작 전 계획을 공유하고 상태를 업데이트하며, Slack 내 메시지 버튼을 제거하고 콤팩트한 푸터 링크로 대체하며, 테이블, PR, 아티팩트의 렌더링을 개선한다 # UI
  원문

  Interaction improvements: Cursor now responds with a plan before it begins, so you can jump in and redirect early. As it works, it updates its status so you can follow each step. We also refined how Cursor's responses look in Slack. In-message buttons are gone, replaced by compact footer links. Tables, PRs, and artifacts now render more cleanly.

• + Cursor가 다른 Slack 채널과 스레드에서 메시지를 읽고 보낼 수 있게 된다 # 에이전트
  원문

  Cross-channel workflows: Cursor can now read from and send messages to other Slack channels and threads. During a task, it can pull context from elsewhere in the workspace and post updates back in the original thread or the relevant channel. Learn more in our Slack docs.

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

• + Remote Development이 Beta 상태를 벗어나 필요한 사례들을 지원한다
  원문

  Remote Development is no longer in the Beta state and supports the required use cases (WEB-77898).

• + /language-server 3.0.0 지원을 추가한다
  원문

  We've added support for @vue/language-server 3.0.0 (WEB-73932).

• + Svelte 지원을 확장한다
  원문

  We've extended support for Svelte (WEB-70810, WEB-73120, WEB-72801, WEB-62966, WEB-70432, WEB-70333)

• + Search Everywhere 기능에 여러 개선 사항을 추가한다 # UI
  원문

  We've introduced multiple improvements to the Search Everywhere funtionality (IJPL-237834, IJPL-234737, IJPL-243626, IJPL-239455, IJPL-243357, WEB-78242).

• + TypeScript Go를 위한 지원을 강화한다
  원문

  We've enhanced support for TypeScript Go (WEB-78522, WEB-77663, WEB-78658).

• + Angular 애플리케이션에서 TypeScript GO를 지원한다
  원문

  We've added support for TypeScript GO in Angular applications (WEB-77722).

• + SASS, SCSS, 그리고 Less 파일에서 CSS color() 및 color-mix()의 색상 미리보기를 지원한다
  원문

  Color preview for CSS color() and color-mix() now works in SASS, SCSS, and Less files (WEB-76917, WEB-76104).

• + Documentation 팝업과 도구 창에서 JSDoc에 대한 특별한 서식을 추가한다 # UI
  원문

  We've added special formatting for JSDoc @linkcode in the Documentation popup and tool window (WEB-70925).

• + Native Dev Containers에서 Node.js 런타임의 자동 감지를 추가하여 GUI 테스트 실행기의 실패를 방지한다
  원문

  We've added automatic detection of the Node.js runtime in Native Dev Containers, thus preventing failures of GUI test runners (WEB-77458).

• + tsconfig 및 jsconfig 스키마가 ES2025 및 ES2026을 지원하도록 업데이트한다
  원문

  We've updated tsconfig and jsconfig schemas to support ES2025 and ES2026 (WEB-78158).

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

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

• + Native GitHub Copilot 통합을 지원한다 # MCP·플러그인
  원문

  Native GitHub Copilot integration

• + Agent skill을 지원한다 # 에이전트
  원문

  Agent skills

• + 제33자 제공자의 AI completion을 지원한다 # MCP·플러그인
  원문

  AI completion support for third-party providers

• + Dependency completion을 지원한다 # 성능
  원문

  Dependency completion

• + Gradle 10 초기 지원 및 마이그레이션 지원을 제공한다 # 성능
  원문

  Early Gradle 10 support and migration assistance

• + Git 충돌 해결 흐름을 간소화한다 # UI
  원문

  Streamlined Git conflict resolution flow

• + Docker Compose 기능을 개선한다 # 성능
  원문

  Docker Compose improvements

• + Java 27을 지원한다 # 성능
  원문

  Java 27

• + Kotlin 2.4 Stable 기능을 지원한다 # 성능
  원문

  Kotlin 2.4 Stable features

• + Spring 지원을 개선한다 # 성능
  원문

  Spring support improvements

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

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

• + Side Chats, 에이전트 대화 내용 검색, 그리고 간소화된 프로젝트 및 리포지토리 선택기를 도입한다 # 에이전트
  원문

  Side Chats and Conversation Search: This release makes it easier to stay in flow with side chats that run alongside your main chat, the ability to search agent transcripts, and simplified project and repo pickers.

• + 메인 에이전트 대화의 흐름을 방해하지 않고 질문이나 아이디어를 탐색할 수 있는 Side Chats 기능을 추가한다 # 에이전트
  원문

  Side chats: Open a side chat to ask questions, explore ideas, and investigate tangents without interrupting your main agent conversation. Use `/side`, `/btw`, or the plus button at the top of the chat panel to create a new side chat that has context from the main chat. Each side chat is a durable, full agent conversation that you can follow up on, revisit later, and at-mention to pull context back into the main thread. By default, side chats focus on reading, searching, and answering. Use them to ask clarification questions, research alternatives without committing to a pivot, and sanity-check a decision while the main agent continues running.

• + 이름과 PR 번호를 넘어선 에이전트 대화 내용 검색 기능을 강화한다 # 에이전트
  원문

  Conversation search: Find past agent chats faster with search results that go beyond names and PR numbers. In the Agents Window, you can search agent transcripts from the command palette (Cmd+K). Cursor builds a local search index that scales search to thousands of conversations with snappy performance. You can also search within an existing conversation using Cmd+F. Jump between matches, see a match counter, and keep searching as you scroll through long transcripts.

• + 프로젝트 및 리포지토리 선택기를 재설계하여 기능을 강화하고 검색 범위를 좁힌다 # UI
  원문

  Redesigned project and repo pickers: We've simplified the project and repo pickers and made them more powerful. You can now stay in the picker for workflows that used to send you elsewhere. For example, you can create a project and connect GitHub, GitLab, or Azure DevOps without leaving the picker. Redesigned project and repo pickers Search is now scoped to where you're working—This Computer, Cloud, or a specific remote machine—instead of one global search box. You can also remove projects from Recents with one click.

• + 에이전트 대화 자체를 관찰하고 제어할 수 있는 새로운 클라우드 에이전트 훅을 추가한다 # 훅
  원문

  New cloud agent hooks: Cloud agents already support team hooks around tool execution and file/shell work. We've added new hooks that let you observe and control the agent conversation itself: prompts, responses, thinking, subagents, compaction, and turn completion. See all the supported hooks in our docs. New hooks like `beforeSubmitPrompt`, `afterAgentResponse`, `afterAgentThought`, `stop`, `subagentStart`, and more allow you to better observe output and reasoning, control subagents, and build self-correcting loops with cloud agents. Picker Improvements Improved repo picker grouping with options under No Repo, On This Computer, and Cloud. Added the "Run on" picker that shows where your agent can run (Cloud, This Computer, or Remote Machines) and drills into the relevant choices (environments, local options, and so on) from there. The branch picker opens on your default branch and rece

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

• + Shift+F6 리팩팩터링 동작으로 Python 모듈을 이름 변경하고 모든 프로젝트 참조와 임포트를 올바르게 업데이트한다 # UI
  원문

  Rename Python modules via the Shift+F6 refactoring action and expect all corresponding project references and imports to update properly across your workspace directories

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

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