What @GitHub does in Slack and Teams
- Investigates, plans, writes code and opens issues and pull requests from a chat thread, using the whole thread as context.
- Works asynchronously in a cloud sandbox and posts a summary with links to what it created.
- Creates one issue, several, or parent and child issues; works across up to 11 repositories owned by the same organization or account.
- Supports choosing a model, MCP servers set up by repository admins, and Copilot Memory (in preview).
- Since the November 6 release it picks the repository from your message, notes in each issue and PR which conversation and user it came from, and in Teams shows plans, diffs and previews in a Canvas next to the chat.
How to set up GitHub Copilot in Slack
Check you can use it
You need a paid Copilot plan and write access to the repositories you want changed. In organizations and enterprises the "Copilot in the cloud" policy is on by default, but an owner can turn it off; for enterprise-owned repositories an admin installs the app and chooses which repositories it can reach.
Install the GitHub app for Slack
Add the GitHub integration to your workspace from slack.github.com (for Teams, teams.github.com).
Connect your account
Open a direct message with the GitHub app, or type
@GitHubin a thread, and follow the prompts to link your GitHub account.@GitHub helplists the commands.Set default repositories for a channel
Run
@GitHub settingsin a channel to pick an owner and repositories; the first becomes the primary one. Direct messages have no default, so name the repository and branch in the prompt.Ask for work in plain language
Mention
@GitHubwith the task, or reply to a GitHub notification with one. Copilot reads the thread, works in the cloud and replies with links to the issue or pull request.@GitHub Add "Hello World" to the README in octo-org/octo-repo on the develop branch @GitHub settings # choose default repositories for this channel @GitHub help # list commands
Source: GitHub Docs, Integrate Copilot cloud agent with Slack
Permissions and limits
- Only people with write access to every selected repository can start or steer a session; anyone in the thread can add input.
- Guests and outside collaborators can't start or steer sessions.
- In a direct message Copilot acts with your linked account's permissions; in a shared channel it creates issues and PRs under its app identity.
- The whole thread is captured as context and stored in the resulting pull request, so keep secrets out of the conversation.
- GitHub's announcement doesn't spell out billing for Slack sessions; check your plan's Copilot usage before rolling it out widely.
GitHub Copilot in Slack vs Claude Code in Slack vs an AI employee
| GitHub Copilot in Slack | Claude Code in Slack | Crewmark AI employee | |
|---|---|---|---|
| How work starts | Mention @GitHub or DM the app | Mention @Claude in a team channel | A heartbeat during working hours takes the next issue; you can also assign it |
| Where it runs | GitHub's cloud sandbox | Anthropic's cloud (Claude Code on the web) | Your machine, in Claude Code, Codex, DeepSeek Harness or OpenCode |
| What it delivers | Issues and pull requests | Pull requests and reviews | Work on any issue on the board, with comments and messages to you |
| Plans | Paid Copilot plans | Pro, Max and Ultra, with Claude Code on the web enabled | Your existing agent subscription |
| Keeps going without you | No: one task per mention | No: one task per mention | Yes, through its working hours |
When a chat bot is enough, and when it isn't
Copilot in Slack is great for the moment a bug report lands in a thread: one mention and a pull request follows. It's still reactive: nothing happens until someone asks, and each mention is one task. If you want an agent that works through a backlog on its own, with a role and goals, look at AI employees and how to make Claude Code proactive. For more ways to run several agents, see Claude Code orchestration tools.
From "@ the bot" to an employee that picks up the next task
Crewmark turns a Claude Code, Codex, DeepSeek Harness or OpenCode session into an AI employee with a role, a goal and working hours. It wakes on a heartbeat, takes the next issue from a shared board, comments as it works, and messages you when it needs a decision.
Assign work like you would in chat
Create an issue and assign it, from any browser or your phone; the employee hears about it right away.
Let it keep going
Between your messages it works through its issues on a 15, 30 or 60-minute heartbeat.
Keep Copilot for quick fixes
They don't conflict: use
@GitHubfor one-off requests in a thread and an employee for the ongoing backlog.
GitHub Copilot in Slack FAQ
Is GitHub Copilot in Slack generally available?
Yes. GitHub announced that @GitHub in Slack and Teams is generally available on November 6, 2026.
How do I add GitHub Copilot to Slack?
Install the GitHub app for Slack from slack.github.com, then DM the app or mention @GitHub in a thread and link your GitHub account. Use @GitHub settings to set default repositories for a channel.
Which plan do I need for Copilot in Slack?
A paid Copilot plan, plus write access to the repositories it should change. Organization owners can turn off the "Copilot in the cloud" policy that it relies on.
Can GitHub Copilot in Slack open pull requests?
Yes. It investigates, writes the change in a cloud sandbox and opens the pull request, then posts a summary with links in the thread.
Does it work in Microsoft Teams?
Yes. @GitHub is generally available in Teams too, where a Canvas shows plans, code changes and previews next to the conversation.
Who can trigger Copilot in a Slack channel?
Only people with write access to every selected repository can start or steer a session. Others in the thread can add input; guests and outside collaborators can't trigger it.
GitHub Copilot in Slack vs Claude Code in Slack?
Both turn a mention in Slack into a cloud coding task. Copilot works with a paid Copilot plan and creates issues and PRs; Claude Code in Slack needs a Claude Pro, Max or Ultra plan with Claude Code on the web.
Checked against GitHub's changelog (November 6, 2026), GitHub Docs and Anthropic's Claude Code docs on November 7, 2026.