GitHub Copilot changelog

@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.
Better Slack conversation context: @GitHub can use shared Slack messages and threads as context, making it easier to reference discussions without copying and pasting details.
Improved reliability: We’ve made several improvements to reduce errors, improve task startup, and help @GitHub recover more smoothly from interruptions in Slack and Teams.

Join the discussion within the GitHub Community.

The post Multi-repository support and other improvements for GitHub in Slack and Teams appeared first on The GitHub Blog.

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:

*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.

No action is required to remove the models after they have been deprecated.

GitHub Enterprise customers with questions or concerns are encouraged to contact their account team for assistance.

Share your feedback

To learn more about the models available in Copilot, see our documentation on supported models.

Join the GitHub Community to share your feedback.

The post Upcoming deprecation of selected GitHub Copilot models in mid-November appeared first on The GitHub Blog.

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

When enabled, agentic autofix replaces the free Generate Fix option on individual code scanning alerts with an Assign to Copilot button.

You can use agentic autofix:

• From any code scanning alert on the repository’s default branch, by assigning the alert to Copilot.
• In the list of security alerts in your repository or security campaign, by selecting up to 25 alerts for Copilot to fix together in a single pull request.
• Via the Update a Code Scanning Alert REST API by setting assignees to ["copilot-swe-agent[bot]"].

Agentic autofix supports code scanning alerts on the repository’s default branch. Alerts detected only on pull requests or other branches cannot be assigned to Copilot.

Access

Agentic autofix requires an enterprise administrator to enable access to it via the new “Agentic autofix” policy in Advanced Security policies.

Once the policy is enabled by an enterprise administrator, an organization or repository administrator can turn on agentic autofix in the Code Security settings for the organization or the repository.

Access also requires a Copilot billing method to be defined.

Billing

Agentic autofix for code scanning alerts consumes AI Credits from your Code Security budget and GitHub Actions minutes. AI Credit usage will be displayed in the “AI usage” section of enterprise billing and licensing as the “Advanced Security” product. You can also set SKU level budgets for Code Security AI credits. Learn more about Copilot usage-based billing.

Learn more

Learn more about agentic autofix in the documentation.

Join the discussion within the GitHub Community.

The post Agentic autofix for code scanning alerts general availability appeared first on The GitHub Blog.

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:
  • Cascade: Previously used an initial model to solve the task, with escalation to a stronger model when needed. It can now include a judging step that inspects the initial work and requests a repair only when needed.
  • Critique: Previously relied heavily on text summaries. It now relies more on tools to inspect the actual workspace directly. Critique now also uses parallel critic models to inspect work.

Introducing HydraFusion Max

HydraFusion Max is built on the same architecture and uses the same workflow techniques as HydraFusion, but is tuned for frontier capability on more demanding tasks. It applies higher reasoning efforts where depth and thoroughness matter most, while still using orchestration to consider token efficiency.

Both options are supported across all three clients, so you can access the latest HydraFusion experience whether you work in VS Code, the GitHub Copilot app, or the terminal.

HydraFusion and HydraFusion Max are available on Copilot Pro, Pro+, Business, and Enterprise plans with experimental or preview features enabled, subject to your organization’s model policies.

Learn more in the HydraFusion documentation.

Share your feedback in the HydraFusion discussion.

The post HydraFusion updates and new Max option appeared first on The GitHub Blog.