GitHub Copilot moved into Slack and Microsoft Teams on the same day

GitHub put the same agent behind two chat clients on the same day, and the shape is identical in both. You mention @GitHub in a channel, a thread or a direct message, the agent picks up the task, and it keeps working while you go back to whatever else you were doing. Everything runs in a cloud sandbox, and the pull request it opens carries a link back to the conversation that produced it.

What it does in Slack

GitHub describes the Slack integration as bringing the agentic capabilities of Copilot CLI and the Copilot app into Slack. In practice that means four things: answering questions about your code and your GitHub activity, triaging bug reports and creating, labeling or updating issues, investigating failures and implementing the change with validation inside a secure cloud sandbox, and opening a pull request with a link to the conversation for review.

Agent sessions in Slack are shared: GitHub says anyone in the channel can open a running session, add context to it, change who has access, or stop it. It can also create dedicated channels for a piece of work, and GitHub is a launch partner for Slack Code, a new kind of channel meant for agents. Access requires a Copilot Business or Copilot Enterprise plan, and usage counts against the Copilot entitlements you already pay for, managed with the existing cloud agent budgets rather than a new meter.

What it does in Teams

The Teams version is framed the same way, around the shared session rather than the individual request: a discussion becomes a collaborative agent session that everyone in the channel can watch and steer. You start a task from Teams and the agent works asynchronously in the same secure cloud sandbox.

It requires a paid Copilot plan, and is also in public preview. The activation gesture is the same, a mention of @GitHub in a channel, a thread or a direct message.

The merge is still a human decision

Both announcements name the same control: repository administrators can require additional approval before a pull request authored by the agent is merged. That is the pattern every vendor has converged on, and it is worth naming each time it appears. The agent may write, run, test and propose; a person still merges.

It also tells you where the risk moved. When the agent lives in a chat client, the instruction that starts it comes from a message, and a message can be written by anyone in the channel. The approval gate on the merge is the thing standing between a badly worded request and your main branch.

Why the room matters

Nothing on either capability list is new to Copilot. What is new is that the agent stopped waiting in the editor and moved to where the decision to do the work is actually made. Bug reports arrive in chat, incidents are triaged in chat, and the gap between deciding something needs fixing and opening the tool to fix it is where tasks go missing.

Both are public preview, which is the right label for something you should try on a repository you do not mind seeing an odd pull request against.