GitHub Copilot: General availability in Slack and Teams, Teams Canvas collaboration

1. From conversation to code work

GitHub announced Copilot's general availability in Slack and Teams on November 6, 2026. Supported tasks include investigating bugs, creating issues, implementing changes, and opening pull requests. A pull request asks others to review and merge code changes. This takes a conversation beyond discussing a problem to producing something ready for review.

The published Slack example shows a bug report becoming an issue. A user reports that the dashboard's date filter resets after a refresh. A teammate then asks for an issue with reproduction steps, expected behavior, and criteria for confirming the fix. Copilot replies that it has created the issue with those details and provides a link. The example turns a report in a team conversation into a reviewable work item.

To get started, mention @GitHub in Slack or Teams and request a task. The announcement links to getting-started pages for both apps and a GitHub Community discussion. The space where developers already communicate with their team becomes the starting point for work requests.

2. Review plans and code together in Teams Canvas

Canvas in Teams provides a space for review materials beside the conversation. Teams can view implementation plans, code changes, and previews alongside their chat. Teammates can keep discussing, share feedback, and refine the implementation together without leaving Teams.

The inclusion of plans and previews, not just code, matters. Teams can see discussions about what to build beside the actual changes and continue giving feedback on the same materials. This adds a shared review space to the ability to request code work.

3. Identify the repository from a message and start work

The startup process that turns a request into a coding task has also changed. GitHub says @GitHub identifies the target repository from the message and starts a task session. A repository stores code and its change history, while a task session handles a single request. Users no longer need to reselect the repository specified in their message, reducing the steps between a request and the actual work.

GitHub says getting started is also easier when users are not signed in or have no default repository. Improvements also cover switching repositories and cases requiring app access permissions. These changes address the different situations teammates encounter when starting work.

An issue that could prevent responses to follow-up messages has also been fixed. The fix concerns conversations where users add questions or instructions after the initial request. Alongside a shorter startup process, the improvements cover continuing the conversation after a request.

4. Less switching, with user attribution on deliverables

The way creation details are displayed has also changed. Descriptions of Copilot-created issues and pull requests state that they originated from a Slack or Teams conversation with a specific user. This lets readers see both the conversational tool's role and the username in the repository's deliverables.

Teams benefit from less tool switching when moving from discussion to development work. They also need to check what user information remains on deliverables created through chat. Requests become easier within chat, but the attached creation details also become something for the team to review.

The core of this general release is making conversation the starting point for development work and using Teams Canvas to review discussions alongside implementation results.