GitHub Copilot in Slack: Shared Agent Session Setup Guide

Quick answer

GitHub’s new Copilot experience in Slack entered public preview on August 21, 2026 for organizations on Copilot Business and Enterprise. After an administrator enables the Copilot cloud-agent policy and the GitHub app for Slack is installed or upgraded, a linked user can mention @GitHub in a direct message, channel, or thread to investigate, plan, create issues, or hand off coding work.

Do not start with a sensitive discussion. GitHub says the entire thread becomes context and can be stored in generated artifacts. In shared contexts, Copilot creates artifacts under its app identity. Only a participant with repository write access can trigger code changes, but other eligible participants can add context and steer the session.

Before installation

Confirm these facts in the live organization:

• Copilot Business or Enterprise assignment for the pilot users;
• Copilot cloud agent is enabled by the correct organization or enterprise owner;
• cloud sandbox policy and budgets match the repositories in scope;
• the GitHub app for Slack is the approved installation and OAuth scope;
• repository write access, branch rules, CODEOWNERS, Actions approval, and secret access are reviewed;
• the Slack workspace, channel, retention, exports, guests, and app governance fit the source-code data class.

Public preview is a rollout stage, not proof that every workspace already has access or that interfaces, billing, or controls will remain unchanged.

Install and connect

1. Have a Slack administrator install or upgrade the GitHub app for Slack.
2. Have a GitHub owner verify Copilot cloud-agent and sandbox policies.
3. Link each pilot user’s GitHub identity through the app; do not share one linked account.
4. Start with a direct message or a fresh low-sensitivity thread.
5. Name the repository and base branch explicitly in the first task.
6. Confirm the plan before permitting changes.
7. Review the generated branch, pull request, checks, and attribution in GitHub.

A channel default repository is shared across the channel. Changing it affects other users, and an omitted repository or branch can route work to the channel default and the repository default branch. For consequential work, keep the repository and base branch in the request and verify them again in the generated artifact.

How Slack Code changes collaboration

For a task, Copilot creates a dedicated Slack Code channel where participants can see the plan, status, repository, branch, model, diffs, previews, and artifact links. Use one code channel per session and steer it from that channel after creation. When finished, the channel can be archived while its history remains viewable and searchable.

Define who may join, steer, stop, and archive a session. Treat an archive as retained collaboration history under Slack governance, not as deletion from GitHub, agent-session records, or generated pull requests.

Context, identity, and review

Use a direct message when the full channel thread contains unrelated or sensitive context. In a shared context, Copilot acts with the app identity rather than a person’s identity. GitHub documents an additional approval for unattributed Copilot pull requests when repository rulesets already require at least one approval; keep that control unless an equivalent reviewed policy replaces it.

Do not treat a secure cloud sandbox as merge approval. Inspect dependencies, generated files, workflows, secrets, tests, security findings, and the actual diff. By default, Actions workflows on Copilot branches can require human approval because unreviewed workflow changes may reach secrets.

Usage and budget checks

GitHub’s Slack launch says usage counts against existing Copilot entitlements and can be managed with existing cloud-agent budgets. Verify included usage, AI-credit behavior, sandbox metering, the billed owner, alerts, and hard-stop behavior in the current billing UI before the pilot. A notification threshold is not necessarily a blocking budget.

Compare Slack with Microsoft Teams in the shared-session selection guide, or use the Teams setup guide. The ChatOps readiness tool turns the rollout controls into a local checklist.

Official sources

• Slack public-preview announcement
• Integrating Copilot cloud agent with Slack
• Copilot usage-based billing

Source check: August 23, 2026. Recheck preview availability, app scopes, policies, budgets, thread retention, and repository rules before rollout.