GitHub Copilot Expands Slack and Microsoft Teams Context Controls

GitHub Copilot Expands Slack and Microsoft Teams Context Controls

AI-generated editorial illustration; not a documentary photograph.

GitHub announced on September 25, 2026, that GitHub Copilot integrations for Slack and Microsoft Teams can draw on more conversation context, offer model switching, and provide clearer links between discussions and generated GitHub work. The changes are available in public preview for organizations using GitHub Copilot Business or GitHub Copilot Enterprise.

More Conversation Context

In Slack, Copilot can use supported files, attachments, and message links as inputs. In Microsoft Teams, it can incorporate inline images, forwarded messages, and channel or thread history. This gives development teams a way to move requirements and supporting material from workplace conversations into GitHub tasks without manually restating every detail.

Traceable GitHub Work

Before opening an issue, Copilot checks for similar existing issues. Newly created work includes direct links, while the GitHub item retains a connection to the originating Slack or Teams conversation. The bidirectional trail is intended to help teams recover the discussion behind a decision and reduce duplicate issue creation.

Models and Repository Controls

Users can select a different model for their next message and retain that selection for the rest of the conversation. Slack users also gain controls for setting default repositories and owners. GitHub says repository switching has been made safer so that superseded sessions cannot continue operating against a previously selected repository.

Reliability and Availability

The update addresses longer-running tasks, interrupted responses, idle reconnections, stalled work, and access-related failures. Teams-specific fixes cover duplicate answers, converted images, retained thread history, user-owned repositories, and large channels; Slack fixes include implementation-plan recovery, repository selection, and code-channel behavior.

Administrators must enable the relevant Copilot cloud agent policy, while Teams also requires cloud sandboxes. Organizations must install or update the GitHub app and connect user accounts. Usage consumes existing Copilot entitlements and cloud agent budgets, and GitHub cautions that some capabilities are rolling out gradually and may not yet appear in every workspace.

Source: Updates to GitHub Copilot for Slack and Microsoft Teams

Share this article
FacebookThreadsLinkedInX

Leave a Reply

Your email address will not be published. Required fields are marked *