GitHub Copilot in Teams and Slack Adds Multi-Repository Chat Support

On October 15, 2026, GitHub published a changelog update announcing that GitHub Copilot in Slack and Microsoft Teams now supports working across multiple repositories within a single conversation. Alongside cross-repository support, the update introduces more flexible @GitHub mention placement, smoother repository switching, enhanced Slack thread context, and underlying reliability improvements for task startup and interruption recovery.

For Windows developers, DevOps engineers, and IT administrators who spend half their day inside Microsoft Teams or Slack, this update removes one of the most annoying friction points of conversational ChatOps. However, understanding what this update actually does—and what security, licensing, and governance rules still apply under the hood—is essential before you turn the agent loose in your workspace.

Breaking Down Multi-Repository Support in Slack and Teams​

The headline capability of the October 15 update is straightforward: you no longer have to splinter your chat threads just because your codebase is divided into multiple repositories. According to the GitHub Changelog, developers and project leads can now track pull requests, investigate cross-cutting issues, and summarize project activity across repositories from a single Slack or Microsoft Teams conversation.

GitHub highlights four primary ways teams can prompt Copilot using this expanded scope:

• Tracking personal work: @GitHub Show me all my open pull requests across repositories and highlight which ones need my attention.
• Gathering merge updates: @GitHub What pull requests were merged this week across my repositories?
• Cross-repo bug investigation: @GitHub Help me investigate an issue that spans our frontend and backend repositories.
• Reviewing broader progress: @GitHub Summarize recent activity across our repositories.

Why does this matter in practice? Think about a typical Tuesday morning standup or an incident response bridge in Microsoft Teams. A customer-facing API starts throwing 500 errors after a deployment. Is the culprit a malformed payload in the frontend repo, or a schema change in the backend service repo? Previously, because the GitHub integration relied heavily on single-repository defaults per session or channel, investigating both sides meant running parallel conversations or manually feeding details from one session into another.

That said, veteran IT pros know how to read vendor release notes with a healthy dose of skepticism. While GitHub's example prompts demonstrate cross-repository querying, status rollups, and multi-repo issue investigation, the October 15 announcement does not explicitly claim that Copilot can execute coordinated, simultaneous code modifications or open synchronized multi-repo pull requests in a single autonomous pass. It also does not specify a hard cap on how many repositories can be queried at once or explain the exact discovery mechanism Copilot uses when a user asks about "our repositories" without naming them explicitly. Teams should treat the update primarily as a major leap forward in cross-project visibility and triage, and test how it behaves against their specific repository structures.

Section Summary: Copilot in Slack and Teams can now query pull requests, summarize activity, and investigate issues across multiple repositories in one thread, though GitHub has not published specific repository limits or promised simultaneous multi-repo code commits in this changelog.

Quality-of-Life and Context Upgrades​

Beyond multi-repository queries, GitHub shipped four practical refinements designed to make interacting with the bot feel less like typing rigid terminal commands and more like talking to a colleague in chat:

1. Flexible @GitHub Mentions: Previously, invoking the agent required placing @GitHub right at the start of your message. You can now mention @GitHub anywhere inside a sentence or paragraph. If you are typing a natural reply to a teammate—such as "I think the auth token is expiring early, @GitHub can you check recent PRs in the gateway and client repos?"—the bot will pick it up without forcing you to rewrite the sentence.
2. Smoother Repository Switching: When you do need to pivot focus from one specific repository to another mid-conversation, GitHub states that moving between repositories during a live session is now smoother. This builds on earlier September 2026 stability work where GitHub patched repository-switching logic in Slack so superseded sessions could not accidentally continue acting in an old repository.
3. Shared Slack Message and Thread Context: Specifically for Slack users, Copilot can now ingest shared Slack messages and threads directly as context. Instead of copying and pasting a wall of text from a customer support channel into an engineering thread, you can share the Slack message or thread directly so Copilot can read the discussion details. (Note: GitHub previously rolled out support for forwarded-message context and channel/thread history in Microsoft Teams, as well as Slack message links and attachments, in its September 25, 2026 update.)
4. Task Startup and Interruption Reliability: GitHub says it has implemented backend improvements in both Slack and Teams to reduce errors, speed up task startup, and help the agent recover more gracefully when a conversation or connection is interrupted. While GitHub does not attach hard latency numbers or error-rate percentages to these claims, smoother recovery is critical when dealing with asynchronous cloud agents.

Section Summary: Conversational friction is reduced thanks to natural mid-message @GitHub mentions, smoother repository switching, native reading of shared Slack messages and threads, and backend reliability fixes across both chat platforms.

Under the Hood: Cloud Sandboxes, Permissions, and Governance​

If you are an enterprise administrator managing Microsoft 365, Teams, or GitHub Enterprise, a natural question arises: If a developer asks Copilot to search across multiple repositories in a shared Teams channel, whose permissions is it using, and where does that conversation data go?

According to GitHub’s official documentation for the Teams and Slack integrations, the Copilot experience in chat is powered by the Copilot cloud agent (currently in public preview), which executes tasks asynchronously inside secure cloud sandboxes. Understanding how identity, context capture, and repository rulesets work in these integrations will save your security team a headache:

• Full Thread Context Capture: By default, when you mention @GitHub in a Microsoft Teams thread, the Copilot cloud agent captures the entire thread history as context for its decision-making and stores that context in the resulting artifacts (such as issues or pull requests). If a channel thread contains sensitive credentials, unrelated customer data, or noisy side debates, GitHub recommends starting a fresh thread or messaging the GitHub app in a direct message to keep the context clean.
• Personal Identity vs. App Identity: How Copilot authenticates depends on where you talk to it. According to GitHub Docs, if you interact with Copilot in a direct message, it acts using the permissions of your linked personal GitHub account. However, when you invoke Copilot in a shared context (like a group thread or a Teams/Slack channel), any artifacts it creates—such as pull requests—are generated under the GitHub app's identity rather than an individual user's account.
• The Extra Approval Rule for Shared PRs: Because pull requests generated in a shared channel use the app’s identity rather than a human developer's account, GitHub enforces a crucial safety rail by default: if your repository rulesets require at least one approval before merging, any PR created by Copilot in a shared context automatically requires one additional approval before it can be merged.
• Write Access Boundaries: While any internal member of a Teams channel or Slack thread can chime in to add context or help steer a conversation, GitHub documentation specifies that only users with write access to a target repository can trigger Copilot to actually make changes. Guest members of a workspace and outside repository collaborators cannot initiate or steer Copilot cloud agent sessions in Teams.

Section Summary: Copilot chat integrations run on asynchronous cloud sandboxes and capture full thread history by default. In shared channels, Copilot creates pull requests under the app's identity, triggering an automatic extra-approval requirement on protected repositories.

How to Configure and Test the Integration​

Want to put multi-repo querying to the test in your own workspace? Because the Copilot cloud agent in Slack and Microsoft Teams remains in public preview, features roll out gradually and require specific administrative gates to be opened first. Based on GitHub's official documentation and its September 25, 2026 rollout notes, here is the checklist for getting Teams and Slack ready:

1. Verify Admin Policies and Licensing​

• Plan Requirements: GitHub’s documentation notes that the Teams cloud agent integration is available for paid Copilot plans, while its September 25 changelog specifically notes public preview availability for organizations on GitHub Copilot Business and GitHub Copilot Enterprise. Usage counts against your existing Copilot entitlements and can be governed via Copilot cloud agent budgets.
• Enable Cloud Sandboxes and Agent Policies: For organization or enterprise accounts (including Enterprises with Managed Users), an administrator must explicitly enable both the Copilot cloud agent policy and cloud sandboxes before users can invoke the agent in Teams.
• Workspace App Approval: A Microsoft Teams administrator or Slack workspace administrator must install (or upgrade) the official GitHub app in the workspace.

2. Connect Your Account and Set Defaults​

1. Link Your Identity: Open a direct message with the GitHub app in Microsoft Teams or Slack, type @GitHub (or follow the welcome prompt in Slack), and complete the browser authentication flow to map your chat identity to your GitHub account.
2. Understand Channel Default Repositories: In Teams or Slack channels, you can configure a default repository by typing @GitHub settings and following the interactive prompts. If a Teams channel does not have a default repository configured, Copilot automatically assigns the repository used in the channel's very first session as the default. When creating single-repo issues or PRs, you can also explicitly target a repo and base branch using parameters like repo=OWNER/REPO_NAME branch=BRANCH_NAME.
3. Run a Cross-Repo Prompt: Once connected, jump into a channel or DM and test a multi-repository query—such as asking @GitHub to list your open pull requests across repositories or summarize recent merges—to see how the agent aggregates activity across the repositories your account is authorized to access.

As development teams continue merging their chat platforms with their CI/CD pipelines, being able to interrogate multiple repositories without playing window-management gymnastics is a welcome step forward. Just remember to keep an eye on your thread context—and don't be surprised when the bot asks for an extra human sign-off before merging code from a group chat.