# GitHub Copilot expands from the IDE into Slack and Teams workflows Source: TechNewsList (https://technewslist.com) Canonical URL: https://technewslist.com/en/article/github-copilot-slack-teams-2026-08-22-morning Section: Software (https://technewslist.com/en/software) Author: TechNewsList Language: en Published: 2026-08-22T05:27:01.142+00:00 Updated: 2026-08-22T05:27:01.323942+00:00 > GitHub is moving Copilot into team chat, where Slack and Teams can now become the place work is planned, reviewed, and handed back as artifacts. ## TL;DR - GitHub launched a new Copilot experience in Slack on August 21, 2026, with a code channel, diffs, and artifact previews. - The same day, GitHub said Copilot can run async tasks from Microsoft Teams in a secure cloud sandbox. - The software story is that team chat is becoming an execution surface, not just a discussion surface. - That makes code review, task planning, and follow-through feel more like one continuous workflow. - The question now is whether teams trust chat-native agent work enough to make it part of daily engineering practice. ## Key points - GitHub is bringing Copilot directly into collaboration tools. - Slack gets a code channel, plan tracking, and output previews. - Teams gets asynchronous task execution in a secure cloud sandbox. - Chat is turning into a place where agents can do real work and hand back artifacts. - This could shorten the loop from request to review to merge. # GitHub Copilot expands from the IDE into Slack and Teams workflows GitHub is pushing Copilot out of the editor and into the team conversation. On August 21, the company launched a new Copilot experience in Slack and also announced shared agentic work in Microsoft Teams, making chat itself a place where software tasks can be planned, executed, and reviewed. ## What happened In Slack, GitHub says teams can follow a plan, inspect diffs, review HTML artifact previews, and keep the work moving inside a dedicated code channel. In Teams, Copilot can take on a task asynchronously in a secure cloud sandbox and then return artifacts back to the conversation. That is a meaningful shift. Chat is no longer just where work gets discussed. It is becoming where work gets handed off to an agent and then checked. ![Developer team reviewing code](https://images.unsplash.com/photo-1516321318423-f06f85e504b3?auto=format&fit=crop&w=1600&q=85) *The collaboration layer is starting to look like the control plane for software work.* ## Why it matters The practical benefit is reduced context switching. Instead of moving from Slack to the IDE to a browser and then back to chat, teams can keep the request, the execution, and the review loop in one place. That matters because many software tasks are not purely coding problems. They are coordination problems. An agent that can work in the background, show diffs, and expose artifacts inside the same thread makes software work more legible to the rest of the team. There is also a subtle governance gain. When the plan, the output, and the comments all live in the same thread, it becomes easier to see who asked for what and when the task changed direction. That matters in engineering teams where the real source of waste is often lost context rather than bad code. If the workflow is reliable, Copilot can become a routing layer for small tasks that would otherwise interrupt deeper work. That creates a cleaner path from request to review, especially for teams that already live in Slack or Teams all day. ## Technical details GitHub's Slack flow centers on a dedicated code channel that stays focused on one task. The user can review the plan, see output previews, and redirect the approach without losing the thread. GitHub's Teams flow uses a secure cloud sandbox, which keeps the execution separate from the user's local environment while still returning useful outputs. That architecture suggests a deliberate split between orchestration and execution. The chat surface handles coordination, while the sandbox or agent environment handles the actual work. The cloud sandbox detail matters because it lets GitHub preserve a security boundary while still making the assistant feel embedded in the conversation. That makes the product easier to trust than an agent that simply reaches into a user's desktop without clear isolation. It also suggests GitHub is treating collaboration surfaces as first-class interfaces for agents. Rather than asking users to switch tools, the company is letting the agent meet the team where they already discuss work. ![Chat and collaboration software on a laptop](https://images.unsplash.com/photo-1552664730-d307ca884978?auto=format&fit=crop&w=1600&q=85) *Agentic software gets more useful when the handoff is visible and reviewable.* ## Market / industry impact This move broadens Copilot's addressable use case. The tool is no longer just for developers inside their IDE. It is becoming part of the broader software operations layer where team members discuss tasks, hand them off, and validate outputs. That could make Copilot more embedded in daily work, but it also raises the bar for trust. If the agent is acting inside chat, the output has to be explainable, reviewable, and easy to stop when the plan changes. The product implication is that software vendors are starting to compete on workflow gravity. The best agent may not be the one with the flashiest benchmark, but the one that becomes the easiest path from a message to a finished artifact. ## What to watch next Watch whether teams prefer Slack, Teams, or the editor as the default place to launch agentic work. Also watch whether GitHub keeps extending artifact previews and review controls so the conversation stays close to the execution. If the pattern sticks, team chat may become the new front end for software delivery. ## Sources - [GitHub Changelog: The new GitHub Copilot experience in Slack](https://github.blog/changelog/2026-08-21-the-new-github-copilot-experience-in-slack/) - [GitHub Changelog: Shared agentic work with GitHub Copilot in Microsoft Teams](https://github.blog/changelog/2026-08-21-shared-agentic-work-with-github-copilot-in-microsoft-teams/) Mentions: GitHub, Copilot, Slack, Microsoft Teams, cloud sandbox, code channel ## Sources - [GitHub Changelog](https://github.blog/changelog/2026-08-21-the-new-github-copilot-experience-in-slack/) - [GitHub Changelog](https://github.blog/changelog/2026-08-21-shared-agentic-work-with-github-copilot-in-microsoft-teams/)