GitHub Copilot Cloud Sessions Are GA: How Cross-Device Work Uses Actions Entitlement
One session can move across web, mobile, CLI, app, and VS Code, while cloud-sandbox billing begins in November
Key takeaways
GitHub made its connected Copilot cloud experience and cloud sandboxes generally available on paid Copilot plans on October 28, 2026. A user can start a task on github.com, GitHub Mobile, Copilot CLI, the Copilot app, VS Code, Slack, or Microsoft Teams, then continue the same session elsewhere. The included Actions compute entitlement becomes one shared, dollar-based pool for standard hosted runners, cloud sandboxes, and certain larger runners. Billing for cloud-sandbox usage begins in November 2026, so cross-device convenience can affect the same budget used by builds. This article helps users check repository scope, write access, tool permissions, entitlement consumption, and stop conditions before their first cloud session.
By ENHE AI · 2026-11-01 · AI-assisted drafting and editorial checks.
Direct answer: Sessions continue across surfaces, but their compute shares a pool with builds
GitHub made the new connected Copilot cloud experience and cloud sandboxes generally available on paid plans on October 28, 2026. A task can start on web, mobile, CLI, the Copilot app, VS Code, Slack, or Teams and continue elsewhere. Cross-device convenience does not mean that compute is free.
What context follows the session
The same session list appears across surfaces. Web sessions can attach repositories, Copilot Spaces, or files; mobile sessions can use voice, images, or files; Slack and Teams can provide message threads as context. Connectors, MCP, skills, and slash commands may also enter a cloud session, so the first trial should verify each authorization separately.
How the shared Actions entitlement changes
The Actions compute entitlement is now a shared, dollar-based pool rather than a fixed number of standard-runner minutes. It can cover standard GitHub-hosted runners, cloud sandboxes, and certain larger runners on Team and Enterprise Cloud. Each product deducts usage at its published rate, so higher-rate compute consumes the pool faster.
November billing and permission boundaries
Cloud-sandbox billing begins in November 2026, and the shared entitlement resets at the start of each billing cycle. A session is scoped by default to one organization or personal repositories. If a user lacks write access, Copilot becomes read-only for that repository. Tool calls still request approval according to permission settings.
Frequently asked questions
Can a task started on a phone continue in VS Code?
Yes. GitHub says the same cloud session can continue across surfaces, provided the account has access to the same organization or repository.
Do cloud sessions include unlimited separate compute?
No. Sandbox use draws from the shared Actions entitlement, and overage follows existing rates, budgets, and payment settings.
Why this matters
Cross-device continuity reduces task interruption and surface switching. The new cost question is that builds and AI sandboxes compete for the same budget. Teams need to observe both delivery time and entitlement consumption, not only whether the session finished.
Related tools and reading
These pages support the same task, workflow, or risk boundary.
- Codex Cloud cross-device tasks
- Hybrid routing between local models and cloud
- Copilot Automations cost-control checklist
Conclusion
Start with a non-production repository and a read-only question or small reversible change. Record session scope, tool approvals, sandbox time, and movement in the Actions entitlement. Use cloud sessions for longer work only after the shared budget, organization policy, and external connections are understood.
What this means for everyday users
Cloud-sandbox billing begins in November 2026, and the shared entitlement resets at the start of each billing cycle. A session is scoped by default to one organization or personal repositories. If a user lacks write access, Copilot becomes read-only for that repository. Tool calls still request approval according to permission settings.
Related tutorials
[[zh]][[/zh]][[en]]Review a public website[[/en]]
SearchScope SEO/GEO
[[zh]][[/zh]][[en]]Access and usage guide[[/en]]
AI Prompt Management System | 418 Bilingual Prompts for Writing, SEO and AI Creation
High-Frequency AI Prompts for Work, Learning, and Teaching guide
High-Frequency AI Prompts for Work, Learning, and Teaching
Related reading
Codex Cloud adds reusable team environments and cross-device task continuity
OpenAI's September 29 Business, Enterprise, and Edu release notes describe Codex Cloud environments that package a project's repositories, tools, and dependencies for reuse. Members can start or continue coding tasks from desktop, web, or mobile, each task receives an isolated workspace, and work can continue while the local computer sleeps. Enterprise administrators can authorize environment sharing and configure approved tool connections and recurring-task connections for teams. The convenience changes the operating boundary: organizations should define which repositories, branches, secrets, network destinations, and publishing actions are allowed in cloud environments, then retain audit evidence for each task, environment version, permission grant, and external write before broad rollout.
When Should an AI Agent Use a Local Small Model or the Cloud? A Hybrid Routing Checklist
AWS published an Adaptive Agentic Intelligence Framework guide using Strands Agents on October 21, 2026. The reference routes routine status checks and local vision work to small models through Ollama, while complex analysis goes to Amazon Bedrock. This durable guide helps teams decide when an AI agent should stay local and when it should use a cloud model. It classifies tasks, marks data that may leave the device, establishes local and cloud quality baselines, defines timeouts and fallbacks, applies one safety policy across both paths, and measures actual routing before estimating cost. The example can run on an 8 GB Raspberry Pi, but that hardware detail is not evidence that every workload belongs on a small local model.
How to Control Copilot Automations Cost: A Four-Layer Budget Checklist
GitHub expanded Copilot Automations on October 28, 2026 with external REST API triggers, 24 additional GitHub event triggers, 20 new tools, custom MCP tools, workflow chaining, and AI-credit limits for each run, day, week, or month. A per-run limit stops the current run when reached. Daily, weekly, and monthly limits prevent new runs until the relevant period resets. Automations without limits continue running under the existing behavior. This durable guide treats budgets as one control rather than a savings guarantee. It provides a sequence for bounding triggers and tools, setting four layers of limits, requiring approval for consequential actions, handling failure, and reviewing usage before expanding scope.
GitHub Copilot Repository Plugin Defaults Are GA: Prevent Permission Drift Across Teams
GitHub made repository plugin defaults and enterprise-managed plugin controls generally available in VS Code, Copilot CLI, and the GitHub Copilot app on October 28, 2026. A maintainer can define a marketplace and default plugins for a trusted repository so contributors avoid repeating setup. Enterprise administrators can require or block plugins and restrict installation to approved marketplaces. Managed settings take precedence over repository and personal choices, and a required plugin cannot be disabled by the user. This article gives teams a rollout checklist for validating publisher identity, plugin contents, MCP connections, credentials, uninstall behavior, repository trust, and the difference between a convenient default and a mandatory enterprise control.
GitHub Copilot Security Extension Preview: Handle Code-Scanning Alerts in the App
GitHub released the Security extension for the GitHub Copilot app in public preview on October 28, 2026. It brings existing code-scanning alerts into one security canvas, where users can filter findings, ask Copilot for an explanation or a local fix, and compare those alerts with findings from a security review of current changes. Copilot changes only the local working copy and does not commit or push automatically. Explain, Fix, and security-review requests consume AI credits, while browsing and dismissing alerts do not. This article provides a low-risk workflow for installing the extension in a test repository, choosing one alert, validating the patch, and preserving human ownership of the final commit.
GitHub Agent Merge Can Watch Pull Requests in the Cloud: What to Check Before Auto-Fixes
GitHub integrated Agent Merge directly into pull requests on October 28, 2026. A paid Copilot user can select Watch and fix in the merge box, choose failing Actions workflows, merge conflicts, or both, and let Copilot start a cloud development environment when a selected blocker appears. Agent Merge can also be combined with auto-merge, which raises the importance of branch protection, tests, and patch review. The feature does not prove that a generated fix is correct or that business behavior remains unchanged. This article provides an acceptance checklist for choosing blocker types, reviewing the cloud-generated diff, rerunning required checks, and deciding whether automatic merging is appropriate for a repository.