AI, in your work.

The conversation as a starting point

GitHub announced general availability of @GitHub in Slack and Microsoft Teams on November 6, 2026. The official changelog also describes improvements to recognising the repository specified when starting a session.

The integration lets users request investigations, create issues and prepare changes from a conversation. In Teams, the official Canvas overview places the plan, code changes and pull requests alongside the thread: a shared reference point for following the work before deciding whether to merge it.

Canvas in Teams and work channels in Slack

The Teams guide specifies that Canvas displays the plan, file changes and a pull request overview. It is read-only and displays only content the linked GitHub account is authorised to view.

In Slack, GitHub organises work in a dedicated channel called Slack Code, keeping the session, plan, branch and pull request together. Its product page describes this experience separately; the Canvas announcement concerns Teams.

Nexo's interpretation: the organisational benefit is a common place for the team to examine progress and discuss it. Its usefulness will depend on someone reviewing the scope, checking the changes and verifying the result.

Access, policies and permissions

The Teams and Slack guides state availability for all paid Copilot plans. Users need to install the relevant app and link their GitHub account.

Installation may depend on Slack workspace administrators. For Teams, GitHub says Microsoft 365 administrators must allow the app and enable resource-specific consent, RSC, to use conversation context. These requirements appear on the official Slack and Teams pages.

• Organisations and enterprises can disable Copilot in the cloud through policies. The current guides say these sessions use a cloud sandbox without requiring a separate sandbox setting.
• Starting changes or steering a session requires write access to every selected repository. Any conversation participant can contribute context.
• Workspace guests and outside repository collaborators cannot start or steer these sessions.

Usage to account for

GitHub measures Copilot usage through licences and AI credits. Allowances and conditions depend on the plan and account, as explained in its licensing documentation.

Cloud sandbox execution also meters compute, memory and snapshot storage. Compute and memory can draw from the account's included monthly allowance; additional usage is billed under the applicable terms. Sandbox budgets are configured by product or billing SKU and are separate from AI credit budgets. The billing guide also explains when usage may be blocked after exhausting an allowance or reaching a budget with usage stopping enabled.

Attribution provides a clue to the origin

The announcement says issues and pull requests created by @GitHub identify the originating conversation platform and user in their descriptions. In Nexo's view, this helps reconstruct the starting point, although that attribution alone does not demonstrate that the change has been reviewed.

GitHub explains on its Teams page that Copilot uses the entire thread as context and can incorporate that context into generated artifacts. Teams should therefore agree on what information belongs in the conversation from which work is delegated.

Synthetic example: reviewing a pagination bug

Suppose a list becomes empty after its status filter changes because it retains a page that no longer exists. This example was devised by Nexo and has not been run. A demonstration request could be:

@GitHub In the demonstration repository, investigate why changing the status filter leaves an empty page. Propose a plan and prepare a pull request with pagination tests.