# LLM.txt - GitHub Copilot's Cloud Handoff Changes Where Agent Work Runs, and Who Pays
## Article Metadata
- **Title**: GitHub Copilot's Cloud Handoff Changes Where Agent Work Runs, and Who Pays
- **URL**: https://www.llmrumors.com/news/copilot-cloud-sandbox-actions-billing
- **Publication Date**: October 31, 2026
- **Reading Time**: 8 min read
- **Tags**: GitHub Copilot, GitHub Universe, AI Agents, Cloud Sandboxes, GitHub Actions, Developer Workflows, AI Billing, Software Development
- **Slug**: copilot-cloud-sandbox-actions-billing
## Summary
GitHub's connected Copilot sessions move between devices, but cloud sandboxes now share an Actions compute allowance. Choose the execution environment before starting work.
## Key Topics
- GitHub Copilot
- GitHub Universe
- AI Agents
- Cloud Sandboxes
- GitHub Actions
- Developer Workflows
- AI Billing
- Software Development
## Content Structure
This article from LLM Rumors covers:
- Data acquisition and training methodologies
- Financial analysis and cost breakdown
- Human oversight and quality control processes
- Comprehensive source documentation and references
## Full Content Preview
TL;DR: GitHub's October 28 release lets users on paid Copilot plans resume one cloud session across web, mobile, CLI, the Copilot app and VS Code; Slack and Teams can initiate work with the required organization setup.[1] From November 2026, a cloud sandbox's running compute and allocated memory draw on the same monthly dollar-based allowance as eligible Actions jobs. GitHub lists that allowance at $12 for Free, $18 for Pro or Team, and $300 for Enterprise Cloud, but Copilot Free does not unlock the new cloud experience.[1][5]
GitHub announced the connected Copilot cloud experience at Universe on October 28, 2026.[2] The pitch is continuity: begin a task from an issue on a phone, inspect it on the web and steer the same session from a development client. GitHub says cloud sandboxes and the cross-surface experience are generally available on paid Copilot plans, with a rollout beginning October 28.[1]
The real story isn't merely another place to chat. GitHub is turning an agent session into portable work while making its execution environment an explicit operational and billing choice. A prompt started in the cloud can outlive the device that sent it; its compute still belongs on somebody's bill. This article describes a workflow to evaluate from GitHub's published documentation. It does not claim that LLM Rumors ran a production session or measured its performance.
The cloud experience is rolling out to paid Copilot users, while sandbox billing starts in November 2026. Teams can establish who owns the repository, which environment a task needs and which budget controls its compute before routine agent use begins.[1][4]
Cover image: generated editorial metaphor for a work folio moving along a crimson thread between devices, a compute workshop and an hourglass. It depicts neither the GitHub interface nor measured usage.
Session Continuity: Carry the Task, Not the Laptop
GitHub's model has three parts: the client where a person talks to Copilot, the session containing the conversation and activity, and the environment where commands run. A cloud sandbox is a GitHub-hosted Linux environment, separate from the user's machine. GitHub says it clones the relevant repositories, runs commands and tests there, and snapshots stopped work so it can resume in another client.[3][8]
A practical handoff begins at the repository, issue or pull request. Attach the relevant context, ask for a bounded change and inspect the session log before requesting a pull request. GitHub says a web session opened over a pull request, file or repository attaches that page as context; its mobile interface accepts voice, images and files. The supported clients show the same cloud session list, so the next device can continue the same task instead of reconstructing the prompt.[1][8]
Slack and Teams add another entry point: with organization policies enabled and the GitHub app connected, a user can mention @GitHub to request a code change or investigate a bug. Treat that as an intake path, not an automatic approval to merge. In organizations, single sign-on governs access to session data; without repository write access, Copilot is read-only.[1]
What's often overlooked is the local exception. Copilot CLI sessions run on the user's machine by default. copilot --cloud starts an interactive cloud sandbox session; GitHub says the flag cannot be combined with the CLI's -p or -i modes. Remote control of an existing local CLI session from mobile leaves the original machine running and online. It is a different workflow from moving execution into a cloud sandbox.