在 Microsoft Teams 中与 GitHub Copilot 共享 Agent 工作

将 Microsoft Teams 讨论转变为所有人都能查看并协助引导的协作式 Agent 会话。在频道、讨论串或私信中提及 @GitHub，即可启动 GitHub Copilot 云端 Agent 会话。对话中的任何人都可以提问、补充上下文，并协助规划或引导工作。拥有仓库写入权限的参与者可以触发 Copilot 进行更改。

当会议产生待办事项时，可在讨论过程中或会议结束前将其交给 Copilot。例如，在团队站会讨论问题时，可以让 Copilot 调查该问题并开始解决。Copilot 会创建一个专属代码频道，所有人都可以在其中监控进度并补充上下文。代码频道创建后，你可以继续在其中引导该会话。

从 Teams 发起任务，让 Copilot 在安全的云端沙盒中异步工作。在代码频道中跟踪进度，然后可通过终端、GitHub Copilot 应用或你偏好的 IDE，继续使用 Agent 生成的产物开展工作。更多信息请参阅关于云端沙盒的文档。

该公测功能适用于付费 GitHub Copilot 计划。在 Microsoft Teams 中启动的 GitHub Copilot 云端 Agent 会话会消耗 AI credits。对于组织而言，云端 Agent 的 AI credit 用量受按用量计费预算管理。云端沙盒用量单独计费，并可通过产品级或 SKU 级预算进行控制。

开始使用：

1. 对于组织或企业中的用户，请确保管理员已启用 GitHub Copilot 云端 Agent 和云端沙盒。云端沙盒策略与云端 Agent 策略使用相同的配置。
2. 安装 GitHub for Microsoft Teams 应用。
3. 在 Teams 中提及 @GitHub，并按照提示连接你的 GitHub 账户。
4. 对于公开频道，如系统提示，请配置默认仓库。私信不使用默认仓库。
5. 提及 @GitHub，然后输入你的任务。你也可以使用 @GitHub help 查看可用命令。

仓库管理员现在可以要求：任何归属于 Microsoft Teams Copilot 集成身份的 Pull Request，在合并前均须获得额外审批。如果你的仓库要求两项审批，启用此设置后，Copilot 创建的 Pull Request 将需要三项审批。要求额外审批可确保由 Agent 编写的工作在交付前始终有人类参与审核。团队既能保持快速推进，也不会失去合规监督。

有关设置细节、权限、仓库和分支选择以及支持的工作流，请参阅如何将 GitHub Copilot 云端 Agent 与 Microsoft Teams 集成。

Turn a Microsoft Teams discussion into a collaborative agent session everyone can see and help direct. Mention @GitHub in a channel, thread, or direct message to start a GitHub Copilot cloud agent session. Anyone in the conversation can ask questions, add context, and help plan or steer the work. Participants with write access to the repository can trigger Copilot to make changes.

When a meeting produces an action item, hand it to Copilot during a discussion or before it ends. For example, ask Copilot to investigate a problem while you discuss it in your team’s standup and start resolving it. Copilot creates a dedicated code channel where everyone can monitor progress and add context. After the code channel is created, you can continue steering the session there.

Start a task from Teams and let Copilot work asynchronously in a secure cloud sandbox. Follow progress in the code channel, then continue working with the agent-generated artifacts from your terminal, the GitHub Copilot app, or your preferred IDE. For more information, see our documentation about cloud sandboxing.

The public preview is available with paid GitHub Copilot plans. GitHub Copilot cloud agent sessions started in Microsoft Teams consume AI credits. For organizations, cloud agent AI credit usage is governed by usage-based billing budgets. Cloud sandbox usage is billed separately and can be controlled with a product-level or SKU-level budget.

To get started:

1. For users in an organization or enterprise, make sure an administrator has enabled GitHub Copilot cloud agent and cloud sandboxes. Cloud sandbox policies share the same configuration as cloud agent policies.
2. Install the GitHub app for Microsoft Teams.
3. In Teams, mention @GitHub and follow the prompts to connect your GitHub account.
4. For public channels, configure a default repository if prompted. Direct messages don’t use a default repository.
5. Mention @GitHub, followed by your task. You can also use @GitHub help to see available commands.

Repository administrators can now require an additional approval for any pull request attributed to the Microsoft Teams Copilot integration identity before it can merge. If you require two approvals in a repository, with this enabled you will need three for Copilot-created pull requests. Requiring an additional approval keeps a human in the loop before agent-authored work ships. Your team moves fast without losing compliance oversight.

For setup details, permissions, repository and branch selection, and supported workflows, see how to integrate GitHub Copilot cloud agent with Microsoft Teams.