Latest in AI
GitHub Copilot Projects and Cloud Sessions: What Changed at Universe
Projects organize ongoing agent work while resumable cloud sessions introduce a new reason to watch Actions compute usage.
GitHub introduced Copilot Projects in public preview on October 28 and made its connected cloud experience generally available on paid Copilot plans. Projects organize broader goals across work sessions, while cloud sessions can be resumed across clients instead of staying tied to one machine.
Projects are broader than a repository session
The Copilot app update lets a project gather repositories, supporting material, agents and results around an ongoing goal. Work can span multiple repositories or involve no repository at all. A direct session remains available for a focused coding task.
The distinction is useful for a migration that affects several services. Individual changes still need review, but the surrounding plan, dependencies and unresolved decisions need a home too.
According to the Projects documentation, the Overview groups work into Needs input, Open, Working and Done. Supporting files can be added through the Library, and users can inspect or steer an individual session. Projects remain subject to change during preview.
A broad goal is not a substitute for constraints. Tell the agent which repositories it may change, what evidence should accompany a result, and which decisions need a person.
Connected cloud sessions are generally available
The separate cloud announcement covers a consistent session experience across the web, mobile, app, CLI, VS Code, Slack and Teams. GitHub-managed sandboxes can save snapshots for later resumption and no longer impose the old one-hour limit on total session runtime.
Paid Copilot access and relevant policies still apply. The new sandbox is not the right environment for every existing setup: workloads depending on Actions-based self-hosted runners or copilot-setup-steps.yml must continue using Actions environments.
Cloud compute has a separate budget consequence
Sandbox billing begins in November 2026. GitHub is turning the included Actions allowance into a shared dollar-based compute entitlement, retaining its value while letting supported compute types draw from the same pool. Team and Enterprise Cloud also include larger hosted runners in that pool. Products retain their own rates.
A shared allowance is not unlimited agent compute. Longer sessions can compete with build workloads for included value. Before moving routine work into the cloud, teams should identify who owns the bill and which limits actually stop spending.
The interesting change is continuity: the same work can survive a closed laptop or a switch from editor to phone. Whether that continuity saves time depends on the quality of the checkpoints, review requests and results it carries with it.
I'm Paras. I work at the intersection of AI, engineering and distribution.
I help technical teams turn product updates and engineering decisions into stories developers can understand and share.