GitHub Copilot

The new GitHub app in Teams brings notifications and Copilot together, helping teams turn issues into fixes and ship code faster without leaving the conversation. Get notified in channels, group chats, or private chats, then @mention GitHub to turn updates into action. Turn an issue notification into a pull request

• Get notified: A bug report arrives in Teams.
• Take action: @github investigates the issue, fixes the bug, and creates a pull request.
• Review and ship: Your team reviews, tests, and merges the fix. Get started Explore the new GitHub app in Microsoft Teams , previously called GitHub notifications. If you already have GitHub notifications installed, update the app to the latest version. Your existing notification capabilities will continue to work. If you use the legacy GitHub app, which will be renamed "GitHub (deprecated)" and retired on November 16, install the consolidated GitHub app using the link above to continue using Copilot in Teams. In the consolidated app, mention @GitHub and follow any prompts to connect your GitHub account and select a repository. Join the discussion within the GitHub Community . Table of Contents

The Copilot usage metrics API now reports model usage from more of the tools your developers use with Copilot, including tools like OpenCode that weren't previously captured in your reports. A new totals_by_client array is available in the enterprise, organization, enterprise-user, and organization-user 1-day and 28-day reports. What's new Each totals_by_client entry represents one client and includes:

• client : The tool that sent the requests, such as opencode , claude_code , codex , zed , copilot_cli , github_app , cloud_agent , code_review , vscode , or jetbrains . Unrecognized clients are grouped under other .
• request_count : The number of successful model requests from the client.
• session_count : The number of distinct sessions from the client.
• token_usage : Prompt tokens, output tokens, and average tokens per request.
• totals_by_model : The same request and token metrics broken down by model, with a model_selection_mode that shows whether the model was requested directly ( user_selected ), chosen by auto ( auto ), or chosen by the product ( product_selected ). Selection modes that aren't reported individually yet appear as other , and values that can't be normalized

The Copilot impact dashboard now includes an "Industry comparison" section. Enterprises, and organizations that aren't owned by an enterprise, can compare their Copilot agentic adoption and leverage with aggregated benchmarks from participating peers. Participation is opt-in and disabled by default. What's new

• Agentic adoption and leverage benchmarks — See the percentage of your users who are agent-first or multi-agent, and how the pull request merge rate of agentic users compares with nonagentic users. Once enough businesses have opted in, each score is ranked against the peer median for the 28-day reporting period and against the top decile as the peer group grows.
• Peer groups by company size and industry — Choose a company size (e.g., 1–999, 1,000–4,999, or 5,000+ employees) and one of ten industries, then switch between your industry and all industries. If your industry's peer group is too small, the comparison widens to all industries for your company size, and the dashboard labels the peer group it used.

In September, we announced a global default policy for generally available GitHub Copilot features and supported client capabilities on Copilot Business and Copilot Enterprise plans. Starting today, we're gradually rolling out enforcement of the policy through October 26, so it may take effect at different times for different enterprises and organizations. Eligible features left unconfigured will be set according to the global policy. Administrators can still make explicit choices for individual features at any time. The policy applies to eligible settings on "Features & clients" and "MCP servers in Copilot". You can review your setting under AI Controls → Copilot → Default policy for new features . For eligibility and exceptions, see the documentation on default availability . What's changing Once the policy takes effect for your enterprise or organization:

• Eligible generally available features and capabilities left Unconfigured will be set according to the selected global default of Enabled , Disabled , or Let organizations decide . This is a one-time change. Subsequent changes to the default policy won't change feature policies that are already set.

Copilot usage metrics now show the names of the skills, custom agents, Model Context Protocol (MCP) servers, slash commands, and plugins that your organization creates, instead of grouping them under other or custom . This builds on the agentic CLI customization metrics released in September. What's new

• Named entries: In enterprise and organization reports, including per-user 1-day and 28-day reports, aggregated 1-day reports, and day_totals in aggregated 28-day reports, the totals_by_skill , totals_by_custom_agent , totals_by_mcp , totals_by_slash_cmd , and totals_by_plugin arrays now show the configured name of a customer-defined item instead of other or custom .
• More entries: Each totals_by_* list now includes up to 25 entries per record, up from five, so you can see more of the long tail of customizations your developers use. Any remaining activity is combined into a trailing other entry.
• Unchanged counts: interaction_count and the distinct_*_use_count fields are calculated the same way as before. Why this matters

September 2026 brought deeper visibility into your work: explore pull requests without leaving chat, bring the AI model your team trusts, and fix vulnerable packages the moment Visual Studio flags them. Highlights Here's what's new with GitHub Copilot in Visual Studio 2026. Check the Insiders channel for the latest:

• Explore pull requests with the Git agent : The Git agent can now explore a pull request for you. Open GitHub Copilot Chat, select the Git agent, and attach a pull request as context from the Git Repository window to get a summary with navigable links to the underlying comments and files. This functionality requires connecting your Git provider's MCP servers; GitHub and Azure DevOps are both supported.
• Updates to Bring Your Own Model (BYOM) : BYOM is available in preview and lets you use the models your team prefers, through GitHub Copilot or your own model deployments, whether or not you're signed in to GitHub. This feature is on by default across the Community, Professional, and Enterprise editions. Breaking change: BYOM now requires the new Agent (Preview), built on the GitHub Copilot SDK-powered harness. The previous Ask and Agent modes no longer support BYOM,

As of today, October 19, 2026, we have deprecated the following models across most GitHub Copilot experiences (including Copilot Chat, inline edits, ask and agent modes, and code completions). These deprecations were announced on September 18, 2026 . Model Deprecation date Suggested alternative Gemini 3.7 Flash 2026-10-19 Gemini 3.8 Flash GPT-5.5 2026-10-19 GPT-6.1 Sol GPT-5.4 2026-10-19 GPT-6.1 Sol GPT-5.4 mini 2026-10-19 GPT-6 Luna GPT-5 mini 2026-10-19 GPT-6 Luna Grok 4.5 2026-10-19 Grok 4.7 Please update your workflows and integrations to use supported models. Copilot Enterprise administrators may need to enable access to alternative models through their model policies in Copilot settings. As an administrator, you can verify availability by checking your individual Copilot settings and confirming that the policy is enabled for the specific model. Once enabled, you'll see the model in the Copilot Chat model selector in VS Code and on github.com. No action is required to remove the deprecated models. GitHub Enterprise customers with questions or concerns are encouraged to reach out to their account manager for further assistance. Share your feedback

You can now use the REST API to retrieve and update Copilot model policies for enterprises, enterprise teams, enterprise apps, and organizations. What's new GET and PATCH endpoints are now generally available for model policies at four levels:

• Enterprise: /enterprises/{enterprise}/copilot/model-policies
• Enterprise teams: /enterprises/{enterprise}/teams/{team_slug}/copilot/model-policies
• Enterprise apps: /enterprises/{enterprise}/copilot/apps/model-policies
• Organization: /orgs/{org}/copilot/model-policies Together, these endpoints make it easier to manage Copilot model availability across your enterprise. Enterprise policies can delegate model control to organizations in organization mode, or to teams and apps in enterprise teams mode. Reference our documentation on managing availability of models in your enterprise and our REST API documentation to get started. copilot enterprise management tools Share Copied Shared Related Posts Oct.19 Retired GitHub Copilot models deprecated on October 19, 2026 copilot Oct.15 Improvement Multi-repository support and other improvements for GitHub in Slack and Teams collaboration tools copilot ... +1 Oct.15 Retired

@GitHub in Slack and Teams now supports working across multiple repositories in a single conversation. Whether you're creating issues, opening pull requests, or investigating bugs, you can work across repositories without switching conversations. For example, you can ask @GitHub to: Create issues from conversations: "@GitHub Create an issue in github/issues to track this bug, using the context from this thread." Make code changes: "@GitHub Fix this bug in our frontend repository and open a PR with the changes." Track your PRs: "@GitHub Show me all my open PRs across repositories and highlight which ones need my attention." Investigate bugs: "@GitHub Investigate this issue using the code in our frontend and backend repositories." You can do all of this directly from Slack or Teams, without switching repositories or starting a new conversation. Additional improvements We've also made several improvements to GitHub in Slack and Microsoft Teams: More natural conversations: Mention @GitHub anywhere in your message, not just at the beginning. Smoother repository switching: Move between repositories more easily during a conversation.

Multi-repo support in Slack and Teams GitHub Copilot in Slack and Teams now supports working across multiple repositories in a single conversation. Whether you're tracking pull requests, investigating issues, or catching up on project activity, you can get the information you need across repositories without switching between conversations. For example, you can ask @GitHub to: Track your work: "@GitHub Show me all my open pull requests across repositories and highlight which ones need my attention." Get updates: "@GitHub What pull requests were merged this week across my repositories?" Investigate issues: "@GitHub Help me investigate an issue that spans our frontend and backend repositories." Review progress: "@GitHub Summarize recent activity across our repositories." You can ask these questions directly in Slack or Microsoft Teams, making it easier to stay on top of work across projects without leaving the conversation. Additional improvements We've also made several improvements to GitHub Copilot in Slack and Microsoft Teams: More natural conversations: Mention @GitHub anywhere in your message, not just at the beginning.

We will deprecate the following models across all GitHub Copilot experiences (including Copilot Chat, inline edits, ask and agent modes, and code completions) on November 16th, 2026: Model Deprecation date Suggested alternative Claude Opus 4.8* 2026-11-16 Claude Opus 5.5 Claude Opus 5 2026-11-16 Claude Opus 5.5 GPT-5.6 Terra 2026-11-16 GPT-6.1 Sol or GPT-6 Luna *Claude Opus 4.8 will remain available to individual GitHub Copilot subscribers on annual plans so they retain an Opus offering. The deprecation of Claude Opus 4.8 does not apply to these customers. Please update your workflows and integrations to use the supported models before this date. Under default model enablement, the suggested alternatives are automatically enabled for Copilot Enterprise and Copilot Business customers unless an administrator has turned off the global default or explicitly disabled the model. If you've turned off the global default, you can enable access to the alternative models through their model policies in Copilot settings. Once enabled, users will see the model in the Copilot Chat model selector in supported GitHub Copilot experiences.

Multi-repo support in Slack and Microsoft Teams GitHub Copilot in Slack and Microsoft Teams now supports working across multiple repositories in a single conversation. Whether you're tracking pull requests, investigating issues, or catching up on project activity, you can get the information you need across repositories without switching between conversations. For example, you can ask Copilot to: Track your work: "@GitHub Show me all my open pull requests across repositories and highlight which ones need my attention." Get updates: "@GitHub What pull requests were merged this week across my repositories?" Investigate issues: "@GitHub Help me investigate an issue that spans our frontend and backend repositories." Review progress: "@GitHub Summarize recent activity across our repositories." You can ask these questions directly in Slack or Microsoft Teams, making it easier to stay on top of work across projects without leaving the conversation. Additional improvements We've also made several improvements to GitHub Copilot in Slack and Microsoft Teams: More natural conversations: Mention @GitHub anywhere in your message, not just at the beginning.

Agentic autofix for code scanning alerts is now generally available. It remediates alerts by working across your codebase the way a developer would: it explores relevant files, proposes a fix, and reruns CodeQL to confirm the fix closes the alert before opening a pull request for your review. Agentic autofix is available to GitHub Code Security and GitHub Advanced Security customers on GitHub Enterprise Cloud, including GitHub Enterprise Cloud with data residency. How it works When you assign a code scanning alert to Copilot, it:

• Explores relevant files across your codebase.
• Generates a proposed fix.
• Validates the fix works by rerunning CodeQL.
• Iterates if needed, then opens a draft pull request ready for your review. The pull request includes a summary of the fix, why it closes the alert, and the validation steps Copilot took to confirm that it works. When the pull request containing the fix is ready, you can instruct Copilot to make further changes to it by commenting on the pull request or interacting with the session in the Agents tab of your repository. How to use it

HydraFusion has an updated model pool, improved orchestration workflows, and introduces HydraFusion Max. Both HydraFusion and HydraFusion Max are available across VS Code, the GitHub Copilot app, and GitHub Copilot CLI and remain in research preview. HydraFusion orchestrates multiple models to produce a single response, bringing together their strengths so you don't have to choose an individual model for each task. What's new in HydraFusion

• Latest frontier models: HydraFusion and HydraFusion Max draw from a pool that now includes Claude Opus 5.5, GPT-6 Astra, GPT-6.1 Sol, and GPT-6 Luna. The models used for each task vary based on the orchestration workflow.
• Reasoning effort tailored to each step: Previously, HydraFusion only used each model's default reasoning effort. With this update, it explicitly tailors effort to each stage, using medium effort for initial drafts and high effort for review. This keeps drafting efficient while dedicating deeper reasoning to checking and improving the work.
• Optimized Cascade and Critique workflows:

Enterprise administrators can now require supported GitHub Copilot clients to retrieve current server-managed settings at startup instead of relying on a cached policy. We are also adding minimum client version requirements to governance-focused managed settings keys over time, starting with the sandbox key. Force refresh settings on client startup Set forceRemoteSettingsRefresh to true through server-managed, MDM-managed, or file-based settings when a policy change must take effect before Copilot starts. The setting is supported in Copilot CLI, VS Code, and the GitHub Copilot app. MDM-managed and file-based delivery can require freshness before the client signs in for the first time. A server-managed value begins requiring refreshes on subsequent startups after the client has received it once. While the setting is active, a cached response cannot satisfy the freshness requirement. If the client cannot confirm current policy, it fails closed rather than running with a stale or unconfirmed policy. Without this setting, clients continue to use the normal managed-settings cache for faster startup and resilience during transient service failures. Minimum required client version