GitHub Introduces Connected Copilot Cloud Experience and Flexible Compute Entitlement

GitHub has announced a new connected Copilot cloud experience, rolling out to users starting October 28 on paid Copilot plans. The update integrates cloud tasks across multiple surfaces, allowing users to start a session on platforms like github.com, GitHub Mobile, the Copilot CLI, the Copilot app, VS Code, Slack, and Microsoft Teams, and continue it elsewhere.

According to the announcement, sessions run by default in a secure cloud sandbox on GitHub-managed infrastructure. These sandboxes start fast, lack a one-hour running time limit, and save snapshots upon shutdown to let users resume sessions from any surface. Users can initiate tasks using voice or attachments on mobile, or via specific menus and mentions on the web, Slack, and Microsoft Teams.

Key Features of the Connected Experience

• Unified Context: Sessions and pins sync across web and mobile, and opening Copilot over a pull request, file, or repository automatically includes that page as context.
• Tools and Integrations: Cloud sessions support Bash, GitHub CLI, and built-in connectors for services like Sentry, Linear, and Cloudflare, alongside custom Model Context Protocol (MCP) servers and agent skills.
• Permissions: Copilot requests approval prior to any tool call requiring it, and existing repository exclusions or enterprise-managed settings carry over.

Flexible Compute Entitlement

GitHub has updated its included Actions entitlement into a single, shared, dollar-based compute pool instead of fixed standard runner minutes. This pool covers standard GitHub-hosted runners, cloud sandboxes, and—for Team and Enterprise Cloud—larger hosted runners. Billing for cloud sandbox usage begins in November 2026, with free usage drawing from the shared compute entitlement.

Practical Implications and Verification

• Access Requirements: The update is available on paid Copilot plans and governed by "Copilot in the cloud" settings. Free tier users can continue using Copilot Chat on web and mobile and upgrade to access the new experience.
• Security and Access Control: Chat sessions are scoped to a single organization or personal repositories by default, requiring single sign-on where applicable. Users without write access default to read-only mode.
• Verification: Users can review official documentation on the GitHub Blog changelog and product documentation pages to confirm setup steps, billing details, and policy configurations.