GitHub Copilot in Slack and Teams now reads shared files and keeps your chosen model for the whole thread

Copilot in Slack and Microsoft Teams turns a chat conversation into GitHub work, such as an issue or a pull request. The public preview for Copilot Business and Copilot Enterprise now gives it more of the conversation to work from and closes a gap in how Slack sessions switch repositories.

More context from the conversation

In Slack, you can now give Copilot supported files, attachments, and message links. In Teams, it can use inline images, forwarded messages, and channel and thread history.

Before it opens a new issue, Copilot checks for similar existing ones. The work it creates links back to the conversation it came from.

Model choice and repository switching

You can switch the model for your next message, and Copilot keeps that choice for the rest of the conversation. In Slack, you can also set default owners and repositories.

GitHub changed how Slack sessions switch repositories, so a superseded session can no longer keep acting in the old repository. Usage counts against your existing Copilot entitlements and can be capped with Copilot cloud agent budgets.

Agentic autofix now uses Copilot Memory

For customers who have enabled Copilot Memory, agentic autofix reads existing memories when it works on a security alert. When it produces a fix, it stores the fix pattern as a new memory.

Copilot code review and Copilot cloud agent can then draw on those memories in the same repository. Both agentic autofix and Copilot Memory are in public preview.

Two changes for administrators

The repository-level daily reports in the Copilot usage metrics API gain a pull_request_review_times array. It gives the median and the 90th percentile, in minutes, for three stages: ready for review to first review, first to final review, and final review to merge.

Only human reviews are timed, so reviews from Copilot code review and other bots are ignored. There is no backfill: pull requests that became ready for review before September 21, 2026 are left out.

A new validator on the enterprise AI controls page checks copilot/managed-settings.json, copilot/team-mappings.json, and the team files they reference. It reports malformed JSON, unsupported settings, and invalid team mappings, with the file and JSON path of each error.