GitHub Copilot in Slack and Teams: Generally Available
GitHub announced on November 6, 2026 that the @GitHub integration for Slack and Microsoft Teams is now generally available. Inside a chat conversation, a team can investigate a bug, create an issue, implement a change and open a pull request, without leaving the conversation. Microsoft Teams also gains Canvas, a surface for reviewing the implementation plan and the code changes next to the discussion.
The point of the release is where coding work starts. Until now, a bug found in chat had to be carried into an issue, and the issue had to be carried into an editor or an agent session, with context lost at each handoff. Keeping the whole chain inside the conversation removes the transcription step, and it moves the Copilot cloud agent's entry point from the individual editor to the team channel, which is where the request usually originates.
A Full Coding Session Inside the Conversation
The workflow covers the full path from report to pull request. A discussion raises a bug, @GitHub investigates it, the work is scoped into an issue, the change is implemented, and a pull request comes back to the same conversation. The Copilot cloud agent does the implementation work, while the chat app becomes the place that requests it and reviews it.
Starting a session got shorter in the same release. @GitHub now identifies the repository from the message itself, so the user does not have to select it again before work begins. GitHub also reworked the starting points where sessions commonly stall: not being signed in, having no default repository set, switching repositories, and app access permissions. A follow-up message that could previously go unanswered has been fixed as well, so conversations are less likely to break in the middle.
Canvas Review in Microsoft Teams
Canvas is the Teams specific part of the release. The implementation plan, the code changes and previews appear next to the conversation, and the team can review them, exchange feedback and refine the work together there. That design answers the obvious objection to chat driven coding: generation from a thread is easy to start, but hard to review if the plan and the diff live somewhere else.
Read together with the rest of the announcement, Canvas is a signal about where the bottleneck now sits. When an agent produces the change, the scarce resource is reviewer attention, so the review surface moves to where the team already talks. The announcement introduces Canvas for Teams only, and whether Slack receives an equivalent review surface is not stated.
Attribution for Agent Created Issues and Pull Requests
Work created this way is labelled as such. Issues and pull requests created by @GitHub carry an attribution line that reads "Created from a Slack/Teams conversation with @username". That small detail matters for trust: a reviewer opening the pull request can see that it began as a chat conversation, and with whom, instead of guessing how an agent session was started.
The general availability label also closes a staged rollout. An October 15 update had already added working across multiple repositories in one conversation, and this release makes that accumulated feature set the supported product. It lands in the same direction as the Copilot code review settings API announced the same day: Copilot's working surface keeps expanding beyond the editor, into the tools where teams coordinate.
Open Questions on Plans and Admin Approval
Two practical questions are not answered by the changelog. It does not state plans or pricing, so which Copilot plans cover which parts of the integration is unconfirmed from this announcement alone. It also does not explain how organization admins approve the app installation and its permissions, so teams evaluating a rollout need to check the product documentation before enabling it. Neither gap changes the workflow itself, but both decide how fast a larger organization can adopt it.
Related Reading
This release was announced alongside the Copilot code review API management update, which moved review settings into the REST and GraphQL APIs. For another coding agent leaving the editor surface, see the report on Antigravity remote agents.
FAQ
What can @GitHub do inside Slack and Teams?
From a chat conversation, @GitHub can investigate a bug, create an issue, implement a change and open a pull request, without leaving the conversation.
What is Canvas in Microsoft Teams?
Canvas is the Teams surface where the implementation plan, code changes and previews sit next to the conversation, so the team can review them, exchange feedback and refine the work together.
Does Slack have the same Canvas review surface?
The changelog introduces Canvas as a Microsoft Teams feature. Whether Slack gets an equivalent review surface is not stated in the announcement.
Which Copilot plans and prices apply to the chat integration?
The changelog does not state plans or pricing, so which Copilot plans cover which parts of the integration is unconfirmed from this announcement alone.