GitHub’s Copilot cloud agent can now turn Slack and Microsoft Teams conversations into investigations, issues, code changes and pull requests through the generally available @GitHub integration. The 6 November changelog also adds a Teams Canvas for reviewing implementation plans, changes and previews beside the discussion that prompted the work.
The GitHub Slack workflow moves the starting point for an agent task into a team conversation, without removing repository permissions or organisational controls. Teammates can contribute context and steer the session rather than passing a conversation to one person to reconstruct elsewhere. General availability concerns this integration; it is not a claim that every related Copilot feature has left preview.
GitHub Slack sessions require repository access and a paid plan
The Slack integration documentation says Copilot cloud agent requires a paid Copilot plan. To start or steer work, a user needs write access to every repository selected for the session. The general GitHub app also requires a GitHub account and a Slack workspace where the app can be installed; installing a notification integration alone does not remove the agent’s prerequisites.
For organisation and enterprise users, the documentation says the Copilot in the cloud policy is enabled by default, but an owner can turn it off. Sessions run in a cloud sandbox without requiring a separate sandbox setting. The availability announcement therefore is not permission for any channel member to direct changes in any repository.
Repository notifications and agent defaults are separate configurations. Subscribing a Slack channel to a repository’s events does not select that repository for agent work, and choosing it for agent work does not subscribe the channel to notifications. That distinction separates receiving information from authorising a coding session with a particular scope.
GitHub says onboarding now identifies the repository from the message and starts the session without requiring the user to select it again. It also reports a fix for follow-up messages that previously could fail to receive responses. These are GitHub’s described workflow improvements, not measured productivity gains.
Teams Canvas keeps the implementation beside the conversation
The Teams integration guide describes research, planning and triage, creating issues and pull requests, and starting or steering agent sessions from conversations. Teammates can add context, correct assumptions and review the resulting artifacts. Canvas lets them follow the plan, code changes and previews without leaving Teams.
The same guide distinguishes notification subscriptions, review reminders and Copilot repository settings. It says the combined GitHub app includes notifications and Copilot, with existing subscriptions and scheduled reminders preserved when updating from GitHub Notifications. This is an app-integration change, not an announcement that repository review requirements have disappeared.
GitHub also says issues and pull requests created by @GitHub now include an attribution identifying the originating Slack or Teams conversation and username. That gives a reviewer a connection back to the person who initiated the work. It is a provenance feature, not a statement that the person manually authored or verified every proposed change.
The launch is separate from Copilot Fusion’s general availability. TSN’s coverage of Replit Cloud Agents and pull requests examines another route from a work request to a reviewable change, while Cursor Live Apps covers cloud agents building and hosting applications. Those are comparisons of workflows, not evidence that the products share permissions or execution environments.
A conversation can provide context without becoming approval
The practical change is where a team can express and refine its intent. A discussion may contain the bug report, the constraints and corrections from several colleagues. Keeping the agent’s plan and resulting changes near that discussion can reduce the gap between the request and what reviewers see. The Canvas surface and conversation attribution address different parts of that connection: one exposes the proposed implementation, while the other records where the request originated.
Neither replaces a decision about scope. Write access to the selected repositories and the organisation’s cloud-agent policy remain meaningful boundaries even when the task begins with an ordinary mention in chat. The distinction between notification subscriptions and repository defaults is especially useful here: being informed about a repository is not the same as selecting it for an agent to work on.
The outcome to assess is therefore the proposed artifact, not the apparent fluency of the discussion. A plan, an issue and a pull request serve different purposes and require different review. General availability makes the integration a supported product surface; it does not establish that code created from a conversation is correct or ready to merge without the team’s normal checks.
For a team adopting the integration, the immediate questions remain its Copilot entitlement, repository scope and owner-controlled cloud-agent policy.
Sources
- GitHub changelog: @GitHub in Slack and Teams GA, 6 November 2026
- GitHub Docs: Slack integration
- GitHub Docs: Teams integration
Related stories
Replit Cloud Agents Let Non-Engineers Send Tested Pull Requests is the next read for a different request-to-pull-request workflow and the role of human review.
Follow @tsnmediahub on X for breaking AI news as it happens.
Follow on X
