GitHub announced on November 6, 2026 that its conversational agent @GitHub is now generally available in Slack and Microsoft Teams. The tool lets developers investigate a bug, file an issue, or open a pull request straight from a team conversation, without switching over to the GitHub interface. The move extends a trend already visible with Copilot’s arrival in Xcode and JetBrains Air: coding agents are steadily moving out of their home editor and into the places teams already talk.
A full handoff from conversation to code
Mentioning @GitHub in a Slack channel or a Teams chat is enough to kick off a working session on a repository. The agent identifies the relevant repository straight from the message, without asking the user to pick it manually, whether the task is investigating a bug report, drafting a structured issue, or implementing a fix as a pull request.
@GitHub fix the broken link reported in #support-prod,
open a pull request on the marketing-site repo
Canvas, a shared review space inside Teams
The most structural addition lands in Microsoft Teams: a new space called Canvas displays the implementation plan, the code changes, and a preview right alongside the conversation. Teammates can leave feedback and refine the work there without leaving Teams, bringing code review closer to the familiar flow of reviewing a shared document.
An integration built to cut friction
GitHub highlights several adjustments meant to smooth day-to-day use: the agent detects the right repository even when the user is signed out, has no default repository set, wants to switch repositories, or still needs to grant the app access. A fix also addresses a bug that could block replies to follow-up messages within the same conversation.
| Milestone | Date | Status |
|---|---|---|
| Copilot coding agent joins Slack | October 2025 | General availability, alongside the already-available Teams app |
| Copilot updates for Slack and Teams | September 2026 | Public preview, Copilot Business and Enterprise |
| @GitHub agent in Slack and Teams | November 6, 2026 | General availability, with Canvas in Teams |
Traceability for automated contributions
Every issue or pull request created from a Slack or Teams conversation now carries a note in its description, flagging that it came from a chat exchange and naming the person who requested it.
Triage and implementation work no longer has to leave the team conversation, and every automatically opened ticket keeps a record of who asked for it.
Key takeaways
The @GitHub agent in Slack and Teams reaches general availability on November 6, a year after its first steps in Slack alongside the Teams app, already available at the time. Canvas introduces a genuine shared review space inside Teams, and every automated action stays attributed to whoever requested it. What remains to clarify, for teams adopting it, is which plans are covered and which permissions to grant before a broad rollout.
The habit worth building before rolling this out widely: deciding, as a team, who gets to trigger a pull request from a single Slack message. It’s convenient, but it deserves the same guardrails as direct repository access — Simon Janvier.
Further reading: the full announcement on GitHub’s changelog.
