A customer reports in Slack that their purchase confirmation never arrived. The team spends twenty messages debating whether email delivery, a queue, or the payment event failed. Someone asks AI to “fix it.” If an agent treats the whole thread as an instruction, casual hypotheses can become code changes. GitHub's new release lets teams take that discussion into an investigation and a PR from Slack or Teams. The real decision is which parts of a conversation should become verifiable work.

On November 6, 2026, GitHub announced general availability of @GitHub in Slack and Teams. The integration can investigate bugs, create issues, request code changes, and open pull requests from a conversation. Teams adds Canvas for reviewing plans, code changes, and previews alongside discussion. GitHub says repository selection is smoother, and issues or PRs created this way include attribution to the Slack or Teams conversation and the initiating user.

What changes for a small product team

The point is not replacing your editor with a chat room. It is carrying product context — the report, questions, and team decision — into technical investigation. GitHub's Slack integration guide says Copilot can use the entire thread, work asynchronously in a cloud sandbox, and leave a PR for review on GitHub. Multi-repository work is supported when the task needs it.

That same convenience creates a boundary: the whole thread becomes agent context and may appear in generated artifacts. If it contains customer details, secrets, or speculation that should not guide implementation, start a clean thread or send a direct message with a sanitized summary. Never paste credentials or personal data to save a step.

A small test with a reusable instruction

1. Install the official GitHub Slack integration in a test workspace, link your account, and invite the app to the channel if needed. GitHub's Copilot Slack guide lists a paid Copilot plan and write access to the repository as requirements for starting or steering work.
2. Choose a reproducible bug with no sensitive data. Separate evidence from guesses in the thread: “Observed: a test purchase produced no confirmation email. Hypothesis: a queue failed. Root cause unknown.” Link an existing issue if you have one.
3. Send: @GitHub Investigate why a test purchase in OWNER/REPO does not produce a confirmation email. Explain the cause with evidence first. If there is a bounded fix, open a PR with a regression test. Do not merge the PR or change payment logic without human approval. Replace OWNER/REPO and adapt the case to your app.
4. Inspect the session and PR outside chat: correct repository, changed files, tests run, and any data copied into the description. Reproduce the bug and fix. In a shared channel, check who can add context and who can steer the agent.

GitHub says a direct-message session acts with your linked account's permissions. In a shared thread or channel, artifacts use the app identity; participants can provide context, but only people with write access to every selected repository can start or steer code work. Where a PR approval rule already exists, a PR created in shared context may require an extra human approval. This is a permission boundary, not an agent failure.

What we have not tested

This is a SoyJB test plan, not a claim that we connected a workspace or ran a PR. Before using it with customer information, check your organization's Copilot cloud-agent policy and the app's permissions. Use the integration to turn clear decisions into traceable work; an ambiguous or sensitive discussion still needs a human edit before delegation.

Sources: GitHub announcement, Nov 6, 2026; Copilot cloud agent in Slack guide; official installation guide. Reviewed Nov 7, 2026.