SNACK: 3-line summary
- GitHub Copilot in Slack and Teams can now carry more conversation context into GitHub work and switch models mid-thread.
- Developers can bring details from a chat into an issue without starting over; Copilot checks for similar issues first.
- The public preview is for Copilot Business and Enterprise organizations, requires admin setup, and is rolling out gradually.
A bug report often starts in a team chat, with the useful details scattered across messages and attachments. GitHub Copilot can now carry supported Slack files and message links, or Teams images and conversation context, into GitHub work. Before creating an issue, it checks for similar ones and links the work back to the chat where it began.
Snackgirls react
AIKO: I want to see the similar-issue check catch a duplicate before it becomes another ticket. That is a useful place to put a pause in the workflow.
Red: I’d rather follow a link back to the original chat than rebuild a bug report from memory. Keeping that trail attached would make picking up the work easier.
What Copilot can bring from each chat
In Slack, Copilot can use supported files, attachments and message links, and teams can set default owners and repositories. In Microsoft Teams, it can use inline images, forwarded-message context, and channel or thread history. Those additions give a developer more of the original discussion when moving a task into GitHub.
Switch models without leaving the thread
Both integrations let users change models during a conversation. The selected model continues for that thread, so a change of approach does not require starting a new chat.
Who can use the preview
The update is in public preview for organizations on GitHub Copilot Business or Enterprise. An administrator must enable the cloud agent policy, and Teams also requires cloud sandboxes. Usage counts toward existing Copilot entitlements and cloud agent budgets; some capabilities are rolling out gradually.
Sources and date: 2026-09-26 KST