GitHub has made its Copilot cloud agent generally available inside Slack and Microsoft Teams, allowing a team conversation to become the starting point for an issue, a code change, or a pull request.
What changed
Mentioning @GitHub in a supported conversation can now investigate a bug, create an issue, implement a change, and open a pull request. In Teams, a new Canvas view places implementation plans, code changes, and previews beside the discussion. GitHub also says the integration can infer the repository from a message and now records the originating Slack or Teams user in generated issue and pull-request descriptions.
Why it matters
The collaboration thread becomes a control surface for a shared coding session. Teammates can add context and steer the work where the request originated, while the resulting artifacts remain reviewable in GitHub. That can reduce the loss of context that occurs when a bug report is manually copied from chat into an issue and then into an editor.
Important limits
The feature requires a paid Copilot plan, the GitHub app for Slack or Teams, a connected GitHub account, and the necessary organization policies. Repository permissions and single sign-on still apply; GitHub says a user without write access is automatically limited to read-only work. Tool calls that require approval still ask for it.
Sessions normally run in GitHub-managed cloud sandboxes. Their usage draws from the shared Actions compute entitlement, and GitHub began billing cloud-sandbox use in November 2026. Organization controls for cloud access, agent permissions, repository exclusions, and MCP allowlists continue to govern the session.
GitHub has not published a controlled performance, accuracy, or defect-rate benchmark for the Slack and Teams workflow. The capability descriptions are vendor claims, and DrComps has not independently tested the integration.