News
Slack and Teams are a path into the repo
On 25 September 2026, GitHub updated Copilot in Slack and Microsoft Teams so a thread can carry more of the conversation into GitHub work. Files, images, and history become context. The issue or pull request can link back to the chat that started it. The grade question is whether this company will let chat create that work.
What shipped
On 25 September 2026, GitHub updated Copilot in Slack and Microsoft Teams: more of the conversation can be context, and the handoff into GitHub work is easier to trace. In Slack, supported files, attachments, and message links count. In Teams, Copilot can use inline images, forwarded messages, and channel and thread history. It checks for a similar issue before opening a new one, then links the result and points back at the thread that started it. You can switch models for the rest of the conversation. In Slack you can also set default owners and repositories. GitHub calls the update a public preview for Copilot Business and Copilot Enterprise, rolling out gradually. The Slack and Teams docs describe the job under that preview: mention @GitHub, and the cloud agent can investigate, plan, write code, and create issues and pull requests from the thread.
Why this moves a grade
The last question in every SaaS Grade catalog is Chat, Suggest, Act, or Build. Chat is people messaging people. Suggest drafts and summarizes, and a person still sends. Act creates work in the thread. Build is custom agents and APIs that developers have to want. A recap of a Slack or Teams thread is Suggest. An issue, a pull request, or a repo task opened from that thread, with a link back to the discussion, is Act. Richer context does not move the grade by itself. The grade moves when the company allows workplace chat to create real work items, not only summarize them. If it does, Slack and Teams are a path into the repository, on a paid Copilot plan, under the permissions already on the repo.
What did not change
WhatsApp still has no company-owned history and no agent that can open a GitHub issue. Hospitality and retail crews who already live on the phone did not get this runtime, and a clearer Copilot handoff will not make them open a desk chat. The preview also does not land everywhere. An administrator has to enable the cloud agent and cloud sandboxes, only people with write access can trigger changes, and GitHub says some capabilities are still rolling out. A team that wants a summary and a human to file the ticket should stay on Suggest. Teams does not suddenly beat Slack, or the reverse. The stack the company already pays for still picks the winner.
How to use the quiz
Answer how far AI is allowed to go: Chat, Suggest, Act, or Build. If chat may open issues and pull requests, Act is the honest answer. If a person must still turn the thread into the ticket, stay on Suggest. Build is a different purchase. Then send the poster. The winner should match the company you have, not the changelog you read.
Grade the company you actually have
90 seconds. The last question is Chat, Suggest, Act, or Build. Then send the poster to the person still arguing in the abstract.
Sources
Vendor pages and research the claims above rest on. Open them.
- GitHub Changelog, 25 September 2026: Richer conversation context, similar-issue checks, and links from Slack and Teams into GitHub work. Public preview on Copilot Business and Enterprise.
- GitHub Docs, Copilot cloud agent in Slack: From a Slack thread, the cloud agent can plan, write code, and create issues and pull requests when cloud agent, sandboxes, and write access are in place.
- GitHub Docs, Copilot cloud agent in Teams: Same handoff in Teams: conversation context in, issues and pull requests out, still a public preview.