GitHub announced on November 6, 2026 that @GitHub in Slack and Teams is generally available, adding Teams Canvas for reviewing code work beside a conversation. Its changelog says Canvas lets teams review implementation plans, code changes and previews together. This is GitHub Copilot through @GitHub, not Microsoft 365 Copilot.

#What changes in Teams?

Teams Canvas puts implementation review alongside the discussion that started the work. GitHub says users can share feedback and refine the implementation with teammates. Its Teams page describes the view directly: "Open canvas to review the plan, file changes, and pull requests next to your conversation."

GitHub says mentioning @GitHub starts a shared session in a channel, group chat or meeting chat. People with access to the same repository can add context, make changes and review the pull request together. Participants contribute to one session and shared context, rather than separate environments for each person.

The agent uses a default repository or one named in the request, shares a live task plan, works in a cloud environment and can open a pull request for human review, according to GitHub. Its Teams page says it uses the whole thread as context when mentioned. Issue and pull request notifications can also become starting points: replying with @GitHub can initiate investigation, fixes and a draft pull request in the same thread.

Petri independently reported Teams general availability in a November 5, 2026 article. Petri also reported multi-repository support, external-tool integration through MCP servers, and model selection for different tasks. Those are Petri's Teams claims, not claims about Slack. GitHub's November 6 changelog supplies the announcement date used here; the sources do not explain the publication-date difference.

#What changes in Slack?

GitHub, not Petri, is the source for Slack general availability. Its Slack page says: "Mention @GitHub to start a shared Copilot session. Teammates can follow the task plan, add context, and review the resulting pull request."

Slack Code Channels give complex coding tasks dedicated spaces where colleagues can follow progress and code changes. That is distinct from Teams Canvas, which is the review view next to a conversation. GitHub marks creating an issue linked to its originating Slack thread as a limited rollout; general availability does not mean every related feature has completed rollout.

#Does shared review change repository permissions?

Shared sessions do not grant unrestricted authority over code. GitHub's Slack page says participants can follow work and steer a plan, but "repository permissions and existing approval rules determine who can authorize and merge changes."

Administrator setup also matters:

  • Slack: a workspace administrator may need to approve @GitHub, depending on workspace settings. Once approved, users connect their GitHub accounts.
  • Teams: Microsoft 365 administrators must allow the GitHub app in Teams policies and enable resource-specific consent so users can authorize conversation context.
  • GitHub enterprise: administrators must enable Copilot cloud agent and cloud sandboxes for participating organizations and assign GitHub Copilot licenses to users.

GitHub's Teams setup also calls for connecting an account, granting organization and repository access, and choosing a default repository. General availability alone does not establish that an organization has completed those steps.

#Must users choose the repository again?

The November 6 changelog says @GitHub "now identifies the repository from your message and launches your session without requiring you to select it again." That announcement takes precedence over the Slack landing page's manual-selection description for the updated behavior; it does not mean initial configuration disappears.

GitHub also reports easier onboarding when users are signed out, lack a default repository, want to switch repositories or need app access. It says it fixed a problem that could prevent follow-up responses. Issues and pull requests created by @GitHub gain attribution to the originating Slack or Teams conversation and username.

#How does it compare with other Copilot surfaces?

For GitHub Copilot in an IDE, see Copilot in Xcode's coding assistant. For another approach to app-integrated developer actions, see Apple's Siri AI developer preview. Those are separate integrations, not evidence for Slack or Teams availability.

Our analysis: The useful distinction is between shared visibility and authorization. Canvas and Code Channels can bring a team into the same task, but repository permissions, approval rules and administrator configuration remain the boundaries. Teams users should also understand that a shared thread supplies shared context. Moving the entry point into chat changes where colleagues review work, not who is allowed to merge it.

#What is unclear?

  • Commercial scope: full plan eligibility, prices and usage quotas are not established in these sources.
  • Regions: no complete geographic availability list is provided.
  • Timing: the precise rollout start and why Petri's Teams report predates GitHub's announcement are not explained.