Playbooks · Teams tasks
Copilot joins Slack and Teams for real
Written November 8, 2026
GitHub's @GitHub bot is generally available in Slack and Teams, with auto repo detection and a Teams Canvas review view. What it does in chat.
What shipped
GitHub made the @GitHub bot in Slack and Teams generally available on November 6. The pitch is simple: turn a team discussion into working code without leaving the conversation. Investigate bugs, create issues, implement changes, and open pull requests from the chat where the problem was raised.
In Teams, the bot gets a Canvas view: implementation plans, code changes, and previews sit alongside the conversation, so the team can review them, share feedback, and refine the implementation together without switching to GitHub. Canvas is the Teams-only part of this release; the changelog describes it as a Teams view, not a Slack one.
What it does in chat
The bot starts from a message. It now identifies the repository from your message and launches the coding session without requiring you to select it again. Getting started is also easier when you are not signed in, do not have a default repository, want to switch repositories, or need app access — those are the four cases the changelog names.
Two smaller fixes ship in the same entry. Follow-up messages are more reliable: GitHub fixed an issue that could prevent responses to follow-ups, so a conversation that keeps going should keep getting answers. And attribution is clearer: issues and pull requests created by @GitHub now include "Created from a Slack/Teams conversation with @username" in their description, so a reviewer can trace a change back to the chat that asked for it.
What it is not
The bot is a chat surface on Copilot, not a replacement for Copilot itself. It starts coding sessions and carries the conversation, but the work still runs as a Copilot coding session, and anything that needs GitHub itself — the full review flow, branch management, merge controls — still lives there. The changelog does not describe the bot as able to do everything Copilot does, and this page does not either.
The changelog also says nothing about pricing for the bot, about which Copilot plans include it, or about how an organization turns it on. If your team cannot see @GitHub in Slack or Teams, that is an enablement question for your GitHub organization, not something this page can answer from the changelog. Try @GitHub from the links in the changelog entry itself, which point to the Slack and Teams apps.
What to do with it
- Use it where the discussion already happens. A bug report that arrives in Slack is a good first case: ask @GitHub about it in the thread, and let the session start from the message instead of retyping the context into GitHub.
- Check the attribution line on anything it creates. "Created from a Slack/Teams conversation with @username" tells the reviewer who asked and where, which is the context a bare pull request would lose.
- In Teams, review in Canvas before switching to GitHub. Plans, changes, and previews are meant to be discussed in the conversation first; the GitHub review is the second pass, not the first look.
- Do not treat a chat answer as a reviewed change. The bot opens the pull request; the team's normal review still decides whether it merges.
Limits
- No Slack or Teams workspace was available for this page, so no bot session was run and no capability beyond the changelog entry is claimed here.
- Every capability listed above comes from the November 6 changelog entry. Anything the changelog does not list — including plan availability and the enablement path — is not stated here.
- Canvas is described as a Teams view. It is not claimed for Slack.
Related playbooks
- Copilot Automations learn from real outcomes
- Copilot Agent Merge: watch a PR and fix its blockers
- The Copilot app now takes GHES accounts
- Copilot CLI signs in with Microsoft Entra
Sources
- @GitHub in Slack and Teams is generally available and more — GitHub Changelog — the general-availability date, auto repo detection, the Canvas review view, the follow-up fix, and the attribution line
Back to: Small-team playbooks hub · Also: Copilot reviews: how many get addressed · Triage a backlog of issues with an agent · Copilot code review now has an API