# GitHub Copilot turns Slack and Teams conversations into shared coding-agent sessions GitHub has put its Copilot cloud agent directly into Slack and Microsoft Teams, where whole conversations can start, steer and review coding work before the agent opens a pull request. GitHub Copilot can now turn Slack or Teams threads into collaborative cloud-agent sessions. Teammates can add context and steer the work in public, while repository permissions, agent budgets and optional extra PR approvals remain the main control boundaries. - Status: Active - Published: 2026-08-22T22:56:06+12:00 - Updated: 2026-08-22T22:56:06+12:00 - Categories: Artificial Intelligence, Web Development, AI Agents, AI Coding, Developer Tools - Tags: AI agents, Coding agents, GitHub, GitHub Copilot - Canonical HTML: https://beyondthe.news/dossiers/github-copilot-slack-teams-shared-coding-agent-sessions ## What changed On August 21 GitHub launched new Copilot integrations for both Slack and Microsoft Teams. Mentioning `@GitHub` can start a shared cloud-agent session from a channel, thread or direct message. The agent can investigate problems, plan and implement changes in a cloud sandbox and open a pull request, while participants in the original conversation can add context or redirect the work. In Teams, only participants with repository write access can trigger code changes. In Slack, GitHub is also a launch partner for Slack Code, which can move agent work into a dedicated code channel. ## Why it matters The workflow shift is from a developer privately delegating to a coding agent inside an IDE to a team collectively delegating from the place where work is discussed. That can shorten the path from bug report, incident discussion or meeting decision to an actionable pull request, and it makes agent prompting and intermediate work visible to peers. It also changes governance: chat membership is not the authorization boundary, repository permissions and Copilot cloud-agent policies are. Teams need to decide who can start write-capable sessions, how agent usage is budgeted, and when agent-authored pull requests require additional human review. ## The chat thread becomes an agent control surface In Slack, `@GitHub` can answer code questions, triage issues, investigate failures, implement changes in a secure cloud sandbox and open a pull request. The session keeps working asynchronously, while participants can continue to steer it from the thread. Slack Code can create a separate code channel where the team can inspect the plan, diffs and rendered artifacts without flooding the original discussion. ## Teams adds collaborative delegation with repository-aware permissions The Microsoft Teams integration follows the same shared-agent model: anyone in the conversation can ask questions or add context, but GitHub says participants need write access to the repository before they can trigger code changes. Sessions can begin from a meeting discussion, keep running in the cloud, then hand their artifacts back to the terminal, Copilot app or IDE. ## Usage and approval controls still live in GitHub Slack public preview is available to Copilot Business and Enterprise organizations and consumes existing Copilot entitlements and cloud-agent budgets. The Teams preview is available with paid Copilot plans; cloud-agent AI credits and cloud-sandbox usage are separately governed by budgets. Repository administrators can require an extra approval for pull requests attributed to the relevant Copilot integration identity before merge. ## Shared prompting is useful, but shared context needs discipline Moving the agent into team chat makes delegation observable and collaborative, but it also increases the amount of conversational context that may influence a coding task. Teams should keep repository access narrow, avoid pasting secrets or unrelated customer data into agent-visible threads, and define when a discussion is authoritative enough to become implementation work. The chat transcript should be treated as input to a coding system, not merely informal conversation. ## Key details - GitHub announced the new Slack and Microsoft Teams Copilot experiences on August 21, 2026. - Slack sessions can plan changes, investigate problems, edit code in a cloud sandbox and open pull requests. - Slack Code can create dedicated agent-focused code channels with visible plans, diffs and previews. - Teams participants with repository write access can trigger Copilot to make code changes; other participants can still contribute context. - Both integrations support asynchronous cloud-agent work that can continue in GitHub Copilot's other surfaces. - Repository administrators can require an additional human approval for pull requests created by the integration identity. - Slack usage is governed by existing Copilot entitlements/cloud-agent budgets; Teams documents AI-credit and cloud-sandbox budget controls. ## Builder takeaways - Treat repository permissions, not chat membership, as the primary authorization boundary for shared agent sessions. - Start with bounded tasks such as issue triage, small bug fixes and investigation work before delegating broad refactors from chat. - Enable the extra approval requirement for agent-authored pull requests in repositories where code changes have meaningful production or compliance impact. - Set explicit Copilot cloud-agent and sandbox budgets before encouraging team-wide use, because chat lowers the friction to starting sessions. - Train teams to keep secrets and unrelated sensitive context out of agent-visible threads and to give the agent an explicit task boundary when a long conversation contains multiple ideas. - Use the shared transcript as an audit/debugging aid: review how a task was framed and redirected when an agent-generated change is wrong. ## What to watch - Whether GitHub expands shared agent sessions beyond Slack and Teams to other collaboration systems. - How usage, latency and duplicate work behave when many teammates can start or redirect agent sessions from busy channels. - Whether GitHub adds finer-grained policies for which chat spaces can invoke write-capable agent actions. - Adoption of Slack Code and whether dedicated agent channels become a durable collaboration pattern rather than a preview novelty. ## Uncertainties - Both integrations are public previews, so supported workflows, billing details and policy controls may change. - GitHub's announcements describe the collaboration model but do not yet provide independent evidence that chat-started sessions improve delivery speed or code quality. - Slack and Teams have slightly different plan and usage language, so organizations using both should verify their own entitlement and billing configuration. ## Sources - [The new GitHub Copilot experience in Slack](https://github.blog/changelog/2026-08-21-the-new-github-copilot-experience-in-slack/) — GitHub · primary · 2026-08-21T00:00:00+12:00. Primary announcement for Slack capabilities, Slack Code, availability, budgets and additional PR approval. - [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/) — GitHub · primary · 2026-08-21T00:00:00+12:00. Primary announcement for Teams collaboration, write-access boundary, billing controls and additional PR approval.