Skip to content
NewsProduct launch

GitHub's @GitHub bot exits preview, reaches general availability in Slack and Teams

· by

The short version

GitHub moved its @GitHub conversational bot out of public preview on November 6, 2026, adding a Teams-only Canvas review view and automatic repository detection for Slack and Teams chats.

GitHub's @GitHub bot exits preview, reaches general availability in Slack and Teams

Any org already on a Copilot Business or Enterprise plan can now turn on @GitHub, the conversational bot that investigates bugs, opens pull requests, and reviews implementation plans from inside Slack or Microsoft Teams, with a console toggle instead of a preview request. GitHub moved the integration to general availability on November 6, closing out a public preview that ran since August, per the GitHub changelog.

What changed on November 6, and what it means today

The GA entry lists three concrete changes. Teams users get Canvas, a side-by-side view for reviewing code changes and implementation plans without switching out of the chat; Slack does not get Canvas in this release, so the feature is Teams-only for now. Both platforms also gained automatic repository detection, so @GitHub identifies which repo a message is about and starts a session without the user picking one manually. Issues and pull requests the bot creates now carry the line "Created from a Slack/Teams conversation with @username" in their description, giving reviewers a visible trail back to the originating chat.

The console toggle is the practical change for a team already paying for GitHub Copilot: setup no longer waits on a preview acceptance. The admin controls from preview, cloud-agent and cloud-sandbox usage budgets plus the option to require a second approval on any bot-opened pull request, carry over unchanged into GA, so an org that locked those down during the preview does not need to reconfigure anything. The Canvas split is the one tradeoff to plan around for an org running both platforms. Code review inside Slack still gets chat-based bug investigation and PR creation, but a reviewer who wants the side-by-side diff view needs to be in Teams to get it; GitHub has not said whether Canvas will extend to Slack.

From a simultaneous preview launch to a six-week hardening cycle

GitHub launched @GitHub in both Slack and Teams the same day, August 21, as a public preview restricted to organizations on Copilot Business or Enterprise plans for Slack. From the start, Slack usage counted against existing Copilot entitlements and could be capped with the same cloud-agent budgets admins already used elsewhere, and repo admins could require a second approval on any pull request the bot opened before it merged, the Slack launch post said.

A separate post the same day covered Teams with a different pitch and billing model: the preview could turn a meeting discussion into a work item that teammates directed together, with the agent working asynchronously in a cloud sandbox and posting progress back into the channel thread. Cloud agent sessions consumed AI credits under usage-based billing, cloud sandbox time billed separately against its own product-level or SKU-level budget, and org or enterprise admins had to explicitly turn on both the cloud agent and cloud sandbox settings before anyone in the workspace could use it. Work started in a Teams thread could continue from a terminal, the standalone Copilot app, or an IDE, according to GitHub's Teams launch post.

GitHub spent the rest of the preview closing gaps rather than adding scope. A September 25 update let the bot read Slack file attachments and message links plus Teams inline images and forwarded messages for added context, added the ability to switch models mid-conversation and have that choice persist, and had it check for similar open issues before filing a new one. That update also improved status messaging on long-running tasks and fixed Teams thread-history retention, both groundwork the November GA release built on, the September changelog entry said.

Canvas itself predates this release: the standalone Copilot app shipped it as a feature on top of its own general-availability launch back on June 17, and Teams is the first chat surface to carry it inside the conversation rather than in a separate app window, GitHub's app-GA changelog entry noted. The Slack launch also made @GitHub a partner for Slack Code, a dedicated channel type that keeps a coding task's back-and-forth out of the original conversation; that channel-isolation pattern carries into GA alongside the new automatic repo detection.

What to watch next

Whether Canvas reaches Slack, and whether GitHub's weekly Copilot changelog rollups start folding in usage data from this integration as a distinct cohort, are both open questions with no stated timeline in the GA announcement.

Sources