GitHub Copilot gets agent mode integrated into Slack with team collaboration
GitHub has launched a public preview of an integration that brings GitHub Copilot agent mode to Slack. The team assigns a task by mentioning @GitHub, the agent works asynchronously in a dedicated code channel, and the PR can be made subject to approval before merging.
GitHub has launched a public preview of a new integration in Slack that brings the agent capabilities of GitHub Copilot CLI and the GitHub Copilot app into conversations. Mentioning @GitHub in a direct message, channel or thread can start an agent session and let Copilot plan changes, investigate issues or directly handle part of the coding. GitHub is also a launch partner for Slack Code, a new type of channel designed specifically for agents.
Copilot continues working asynchronously even when the user is in a meeting, on the move or doing something else, and the session can be steered directly from Slack. The agent can create a dedicated code channel that keeps the task organized without overwhelming the original conversation — the team can follow the plan, review diffs, check output previews (e.g. HTML artifacts) and join the session at any time to add context, change direction or stop the session. Sessions are shared, so the team works on the task together instead of one person working privately with the agent.
According to GitHub, issues and pull requests created from the conversation are attributed to the Copilot app identity, and their actions remain constrained by existing GitHub permissions and controls. Repository administrators can require additional approval before merging pull requests attributed to the Copilot identity, keeping human oversight in the process.
The public preview is available to organizations with a GitHub Copilot Business or GitHub Copilot Enterprise plan. Use of the integration counts toward existing Copilot entitlements and can be managed using existing cloud budgets for agents.
Why it matters
The integration moves the assignment and tracking of agent coding tasks into the tool where teams already coordinate work, reducing the need to switch between Slack and GitHub. Shared code channels also make agent prompting visible to the whole team, making it easier to learn best practices, while optional approval before merging and existing GitHub permissions maintain oversight of what the agent actually changes in the code.
Two audiences, two different impacts
What this means
For individuals
Developers can assign, track and steer GitHub Copilot agent tasks directly from a conversation in Slack and continue working on the pull request in a terminal, app or IDE; shared code channels also let them see how colleagues prompt the agent.
For a business
Companies with a GitHub Copilot Business or Enterprise plan can incorporate agent work into their existing workflow in Slack; repository administrators can enforce human approval before merging, so faster development does not have to come at the expense of compliance oversight. Usage counts toward existing Copilot entitlements and cloud budgets for agents.
DevelopmentCheck the original
Event sources
clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.