GitHub put the agentic capabilities of Copilot CLI and the Copilot app into Slack in public preview on 21 August. Mentioning @GitHub in a direct message, channel or thread starts an agent session that can answer questions about code and GitHub activity, triage bug reports, update or create labelled issues, investigate failures, implement changes and validate them in a secure cloud sandbox, then open a pull request linked back to the conversation. GitHub is also a launch partner for Slack Code, a new channel type designed for agents.
The mechanism worth noting is asynchrony. The session keeps working while the requester is in a meeting or commuting, can be steered from Slack as it runs, and is then picked up from the pull request in a terminal, the Copilot app or an IDE. The conversation becomes one control surface over a job rather than the place the job lives.
That is why the useful abstraction is the one in an organization agent being a scoped runtime rather than one Slack bot: a mention handle is an entry point, and the permitted GitHub context is the actual boundary. The coding agents hub tracks how those entry points multiply.
This is a public preview changelog: it lists capabilities and the permitted-context framing without publishing how permissions are scoped per channel. The condition to watch is whether a Slack Code channel carries its own permission scope, because a channel built for agents is a new place for access to be granted by habit.