Enhanced Context and Conversation Traceability

According to the official [GitHub Changelog](https://github.blog/changelog/2026-09-25-updates-to-github-copilot-for-slack-and-microsoft-teams/), GitHub Copilot in Slack and Microsoft Teams now provides users with deeper context, tighter control, and a clearer pathway from everyday chat discussions to actual development work. Teams can leverage more of the context already embedded within their ongoing conversations to streamline development pipelines.

In Slack environments, developers can utilize supported files, attachments, and message links as active context. Meanwhile, Microsoft Teams users can leverage inline images, forwarded-message context, along with complete channel and thread histories. Copilot is also designed to check for similar preexisting issues before generating a new one, incorporating direct links to the resulting work while maintaining a trace link back to the originating conversation.

Model Selection and Repository Management

The latest updates also introduce greater flexibility regarding model handling and repository configurations. Users are now able to switch models for their next message and retain that preference throughout the duration of the conversation.

Additionally, Slack users can establish default owners and repositories, making it simpler to sustain workflow momentum across multiple repositories and shared conversational spaces. Developers looking for setup details can consult documentation on [how to use Copilot coding agent with Slack.](https://docs.github.com/copilot/how-tos/use-copilot-agents/coding-agent/integrate-coding-agent-with-slack)

Reliability Improvements for Long-Running Tasks

GitHub has refined how Copilot handles prolonged tasks across both communication platforms. Enhancements include clearer implementation-plan statuses, improved management of interrupted or stale replies, and more predictable reconnection handling when conversations experience idle periods.

Within Microsoft Teams, the updated integration more reliably preserves channel-thread histories, prevents duplicate answers, correctly processes Teams-converted images, and functions more consistently alongside user-owned repositories and large-scale channels.

For Slack, the platform improvements address implementation-plan recovery, resolve repository picker and code-channel glitches, and enforce safer repository switching to prevent superseded sessions from continuing operations within an old repository.

Availability and Integration Requirements

The public preview rollout is currently available to organizations operating on GitHub Copilot Business and GitHub Copilot Enterprise plans. Resource usage counts toward existing Copilot entitlements and is manageable via established cloud agent budgets, though some specific capabilities may roll out gradually across workspaces.

To get started on Microsoft Teams, organizations must ensure an administrator has enabled the necessary cloud agent policies and cloud sandboxes, and then install or upgrade the GitHub app for Microsoft Teams. Comprehensive setup guidance can be found by reviewing [how to integrate GitHub Copilot cloud agent with Microsoft Teams.](https://docs.github.com/copilot/how-tos/copilot-integrations/integrate-cloud-agent-with-teams)

Sources

• GitHub ChangelogUpdates to GitHub Copilot for Slack and Microsoft Teams