GitHub Copilot in Slack and Teams can now work across several repositories at once

GitHub says its Copilot assistant in Slack and Microsoft Teams can now handle work that spans more than one repository inside a single conversation. The company announced the change in a changelog post dated 15 October 2026.

GitHub's post says users can now stay in one thread while asking about several repositories. It does not describe how the earlier behavior worked.

GitHub's examples are all questions rather than code changes: list my open pull requests across repositories, show what was merged this week, help investigate an issue that spans frontend and backend repositories, and summarize recent activity. These are illustrative prompts from the company, not test results.

The same post lists smaller changes. The @GitHub mention can now appear anywhere in a message, not only at the start. Switching repositories mid-conversation is described as easier. In Slack, Copilot can use shared messages and threads as context, so users need not paste details in. GitHub also says it made changes to reduce errors, speed up task startup and help the assistant recover from interruptions.

Everything above comes from one source, GitHub's own announcement. We searched for independent coverage of this specific release and found none, so none of it has been verified by a second party or tested by Guth News.

The post leaves several practical questions open:

- Which Copilot plans or organizations get the feature, and whether it is a preview or generally available.
- How repository permissions apply when one question touches many repositories.
- How many repositories can be included, and how well the assistant handles large result sets.
- Whether the Slack-only thread-context feature is coming to Teams.
- No figures are given for the reliability improvements.

Engineering conversations rarely respect repository boundaries. A bug in a web front end often traces to a service in another repository. An assistant limited to one repository forces users to restate context or switch threads. Cross-repository queries inside the chat tools where teams already discuss work make the assistant more useful for status checks and triage. Whether it handles those questions accurately is something the announcement does not demonstrate.

Revised 16 October 2026: Guth re-read the original sources and rewrote this article. The earlier version remains available as revision 1.