GitHub announced on 6 November 2026 that @GitHub in Slack and Teams is now generally available. The changelog describes moving from a chat conversation to code work, including investigating bugs, creating issues, implementing changes and opening pull requests, without leaving the conversation.
What the changelog says
- Canvas in Teams. Implementation plans, code changes and previews can be reviewed next to the conversation, then discussed and refined with teammates.
- Faster onboarding. @GitHub works out the repository from your message and starts a coding session without asking you to pick it again.
- Clearer attribution. Issues and pull requests it creates say “Created from a Slack/Teams conversation with @username”.
- A reliability fix for an issue that could stop it replying to follow-up messages.
The changelog does not mention pricing, plan requirements or regional limits, so check those before you plan around it.
The interpretation
The place where software requests start is moving. Until now a bug report in a team chat became a ticket, then waited for a developer. Now the same message can become a draft change that a person reviews. The conversation, not the ticket queue, is becoming the front door to the codebase.
That speeds up small fixes. It does not remove the need for someone to judge whether the change is right, safe and in keeping with the product. Every pull request created from chat still needs a reviewer who understands the system, and the attribution line makes it easy to see which changes started as a chat message.
So what
If your product team asks for changes in Slack or Teams, decide now who reviews what an AI agent proposes, and which repositories it may touch. Fast drafts without clear review ownership just move the bottleneck. BuildApps sets up this kind of workflow as part of AI-assisted development and ongoing custom software development. To talk it through, start a project.