官方更新 GitHub Changelog Sat, 10 Oct 2026 正文 ok 389 words

Copilot for JetBrains 新增控制选项与聊天改进

英文标题:New controls and chat improvements in Copilot for JetBrains

GitHub Copilot for JetBrains 此次更新让企业管理员可通过托管设置指定新对话的默认 Agent 模型,同时保留用户手动选择模型的能力。更新还为诊断意图菜单新增 Fix 操作,并允许关闭 Copilot 和 Claude 的 MCP 服务器自动启动。聊天导航、账户切换、登录流程、消息操作和 Agent 引导均获得改进,同时增强了语言服务器、模型切换、MCP 配置及 worktree 工作流的可靠性。GitHub Copilot 现已停止支持 JetBrains IDE 2025.1,插件用户需升级至 JetBrains IDE 2025.2 或更高版本。
打开原文相关 3 · 机会 4
media12.2 KB media26.4 KB

中文

此次更新为 GitHub Copilot for JetBrains 带来了对默认模型和 MCP 服务器更精细的控制。它还让诊断问题更易处理,改进了聊天导航和账户控制,并提升了 Agent 会话、自定义配置及 worktree 场景下的可靠性。

企业管理员现在可以通过托管设置,将任意可用的 Copilot Agent 模型指定为新对话的默认模型。这让组织能够更好地控制初始使用的模型,同时仍保留用户通过模型选择器显式选择模型的能力。

诊断意图菜单现在新增了 Fix 操作,可打开内联聊天并要求 Copilot 修复问题。该操作在 Agent 模式可用时使用 Agent 模式,否则使用 Ask 模式,帮助你以更少步骤从报告的问题进入建议的修复方案。

新增的 MCP 设置允许你关闭 Copilot 和 Claude 的服务器自动启动,从而更好地控制已配置工具何时启用。

此版本让日常聊天、账户和导航工作流更加清晰:

  • 账户控制:已登录的 Copilot 账户现在拥有更清晰的标签、更简洁的状态显示、更适合长列表的导航方式,以及 Switch Account 操作。
  • 聊天发现与登录:一次性提醒可帮助新用户找到 Chat;登录页面则提供了响应式布局、更清晰的标题、改进后的提供商选项、Copilot 套餐的直接链接,以及浏览器授权期间可取消的进度操作。
  • 对话导航:聊天消息现在按轮次分组,并提供在不同轮次间快速跳转的控制项。
  • 消息操作:用户消息现在包含复制或编辑其内容的操作。
  • Agent 引导:Copilot Agent 占位提示现在会突出显示问题、编辑、上下文和命令。
  • 迁移流程:接受迁移命令后,即使你继续本地对话,Go Back 也会打开一个 Copilot 主页会话。

此版本提高了语言服务器启动、模型和提供商切换、MCP 配置、自定义配置刷新、文件变更以及 worktree 工作流期间的可靠性。它还解决了模型管理、工具调用详情、工作集和 JetBrains IDE 设置中的交互与显示问题。

GitHub Copilot 已停止支持 JetBrains IDE 2025.1。现在需要使用 JetBrains IDE 2025.2 或更高版本才能使用该插件。

我们鼓励你试用最新版 GitHub Copilot 插件并分享反馈。你的意见对于我们持续优化和改进产品至关重要。

你的反馈将推动产品改进。我们期待通过以下渠道了解你的使用体验:

English / 原文

This update brings more control over default models and MCP server in GitHub Copilot for JetBrains. It also makes diagnostics easier to address, improves chat navigation and account controls, and strengthens reliability across agent sessions, customizations, and worktrees.

Enterprise administrators can now use managed settings to choose any available Copilot agent model as the default for new conversations. This gives organizations more control over the starting model while still preserving an explicit model picker choice.

Diagnostic intention menus now include a Fix action that opens inline chat and asks Copilot to repair the issue. The action uses agent mode when it is available and ask mode otherwise, helping you move from a reported problem to a proposed fix with fewer steps.

A new MCP setting lets you disable automatic server startup for Copilot and Claude, giving you more control over when configured tools become active.

This release makes everyday chat, account, and navigation workflows clearer:

  • Account controls : Signed-in Copilot accounts now have clearer labels, a simpler status display, better navigation for long lists, and a Switch Account action.
  • Chat discovery and sign-in : A one-time reminder helps new users find Chat , while the sign-in page has a responsive layout, clearer headings, improved provider choices, a direct Copilot plans link, and cancellable progress during browser authorization.
  • Conversation navigation : Chat messages are grouped by turn, with controls for moving quickly between turns.
  • Message actions : User messages now include actions to copy or edit their content.
  • Agent guidance : The Copilot agent placeholder now highlights questions, edits, context, and commands.
  • Migration flow : After you accept a migration command, Go Back opens a Copilot home session even when you continue the local conversation.

This release improves reliability during language server startup, model and provider switching, MCP configuration, customization refreshes, file changes, and worktree workflows. It also resolves interaction and display issues in model management, tool-call details, working sets, and JetBrains IDE settings.

GitHub Copilot has ended support for JetBrains IDE 2025.1. You now need JetBrains IDE 2025.2 or later to use the plugin.

We encourage you to try out the latest version of the GitHub Copilot plugin and share your feedback. Your input is invaluable in helping us refine and improve the product.

Your feedback drives improvements. We’d love to hear about your experience in the following channels: