GitHub Copilot in Slack and Teams Gains Broader Context and Duplicate-Issue Checks
GitHub updated Copilot’s Slack and Microsoft Teams integrations with broader context awareness, more model control, and clearer traceability from conversation to action.
Details
- More context: in Slack, Copilot now processes supported files, attachments, and message links; in Teams, it works with inline images, forwarded-message context, and channel/thread history
- Model control: users can switch models for the next message and have that choice persist for the rest of the conversation; Slack users can also set default owners and repositories
- Conversation-to-action traceability: Copilot checks for duplicate issues before creating a new one, embeds direct links to the resulting work, and keeps a link back to the originating conversation
- Reliability fixes: better status visibility and interruption handling for longer-running tasks, plus Teams-specific improvements to channel-thread retention and image handling, and Slack-specific improvements to repository-switching safety and recovery
- Availability: public preview for Copilot Business and Enterprise plan subscribers
What happened next
The update focuses on making chat-based Copilot usage feel less like a one-off command and more like a persistent, traceable workflow — carrying model preferences forward, avoiding duplicate work, and keeping a clear link between a Slack or Teams conversation and whatever GitHub work it produced.