On September 25, 2026, GitHub announced updates to Copilot for Slack and Microsoft Teams. The updates expand the conversation material Copilot can use for tasks, connect GitHub tasks it creates to the original conversation, and improve how it handles task progress and connection status. Source

In Slack, Copilot can use supported files, attachments, and message links as context for a task. In Teams, it can use images embedded in conversations, context from forwarded messages, and channel and thread history. Source

Before creating a new GitHub issue, Copilot checks for similar issues. An issue is an entry used to track a task or problem. After creating a task, Copilot provides a direct link to it and a link back to the conversation where it originated. Source

Task settings and response handling

If you change the model for the next message, the selected model can remain in use for the rest of the conversation. In Slack, you can also set a default assignee and repository. A repository is a place to store a project’s code and related files and track changes to them. Source

GitHub also improved status indicators for long-running tasks, handling of interrupted or stale responses, and reconnection after a period of inactivity. Teams improvements include preserving channel thread history and preventing duplicate replies. Slack improvements include recovering implementation plans and making repository switching safer. Source

Availability and admin settings

The features are available in public preview to organizations on GitHub Copilot Business or Enterprise plans. A public preview lets users try features before their general release. Usage is included in existing Copilot allowances and can be managed through existing Copilot cloud agent budgets. Source

Some features are rolling out gradually. To start using Copilot in Slack, an organization administrator must enable the Copilot cloud agent policy. For Teams, administrators must enable both Copilot cloud agent and cloud sandboxes. Source