GitHub has announced new Copilot integrations for Slack and Microsoft Teams. Teams will be able to start an agent session from a conversation, add context, and review the work before code changes are merged.

Copilot will work from conversations

In Slack, a person will be able to mention @GitHub in a channel, thread, or direct message. Copilot will use the permitted conversation and repository context to answer questions, investigate issues, or prepare a programming task.

The agent will also be able to create and update issues, work on changes in a separate environment, and open a pull request so the team can review the result.

In Microsoft Teams, a session can start from a channel, thread, direct message, or meeting chat. This will allow a decision made during a discussion to become a task that Copilot can begin investigating.

Shared sessions for the team

Sessions will not be limited to one person. Several team members will be able to add information, ask questions, review the plan, and redirect the work.

Copilot can continue working asynchronously while people focus on other activities. Progress can be followed from the conversation, and the task can later be continued from GitHub, a terminal, or an integrated development environment.

Code changes will remain under human control

Copilot will not be able to modify any repository automatically. Its actions will depend on existing GitHub permissions, and only authorized people will be able to request code changes.

Results can be presented through a pull request. Administrators will also be able to require an additional approval before code prepared through these integrations is merged.

Availability

Both integrations are available in public preview.

The Slack experience requires GitHub Copilot Business or Enterprise. The Microsoft Teams integration requires a paid GitHub Copilot plan, and some sessions may consume artificial intelligence credits.

In both cases, the organization will need to install the GitHub app, enable the corresponding features, and keep repository access permissions configured.