Work from anywhere with a new, connected Copilot cloud experience #211011
Replies: 2 comments
|
Hi, I don't understand the following points from the docs:
Thanks ! |
GitHub Copilot on GitHub.com: plan-review controls are hard to find and don't reliably returnI've been using GitHub Copilot mainly on GitHub.com, with Cloud sessions, my repository, and Spaces as my preferred working setup. I like the idea of being able to start a coding task in the browser and continue working with Copilot in a cloud environment. My concern is that the browser interface makes some basic parts of that workflow harder to understand and use than they should be. This feedback is about two related problems I've encountered when reviewing a plan in a GitHub.com Cloud session. 1. The plan-review choices are not immediately visibleI started a session for a repository and Space, selected Plan mode, and asked Copilot to investigate the code and prepare an implementation plan. Copilot generated the plan. The session then displayed:
I expected to see clear choices for accepting the plan, asking for changes, or leaving Plan mode. Instead, the normal After some experimentation, I sent this follow-up:
Only then did the interface display the choices I had been looking for:
Once those choices appeared, the next step was clear. The confusing part was having to discover that I needed another natural-language prompt to make the controls appear. If the session is waiting for me to review a plan, shouldn't the review choices be visible without needing a special prompt? 2. The plan-review choices disappear after leaving the page or waitingThere is a second problem, which makes the first one even more frustrating. After the plan-review choices finally appeared, I could leave the session and come back later, or refresh the browser page. When I returned, those choices were gone again. Instead, the composer showed what looked like an active generation state: a stop control and a running-time indicator. In one instance, the displayed time was around 30 minutes. I had not necessarily changed my mind about the plan. I might simply have stepped away for a while and returned to make my decision. But the interface no longer showed the choices that had previously been available. To get them back, I had to send another natural-language follow-up. In other words, I had to prompt Copilot again just to recover the plan-review interface. I don't know whether the underlying session was genuinely still generating, whether the browser was showing an outdated state, or whether the pending plan-review interaction simply wasn't restored after the page was reloaded. From the user's point of view, that distinction is not clear—and the interface gives no reliable explanation of what is happening. 3. The session state and the browser display need to stay in syncI understand that the cloud session and the GitHub.com interface are different parts of the system. The session may be running, waiting for input, waiting for a plan decision, or finished. The browser is responsible for showing that state and giving me the appropriate controls. I am not claiming to know where the technical fault is. It may be a session-state problem, a UI restoration problem, or a mismatch between the two. But the visible behaviour is confusing: the session previously asked me to review a plan, the review choices appeared after a follow-up, and those choices then disappeared after a refresh or a period away. The interface instead looked as though generation was still in progress. A pending decision should remain available until I (end user) make it. Refreshing the page or returning to the session later should not make the decision controls disappear. Unfortunately, after refreshing the browser, the following UI is gone, very frustrating!
Also, after switching from
I have also observed inconsistent presentation after refreshing or returning to the session. At this stage, I cannot establish whether this is caused by the mode change, an ongoing agent operation, session-state restoration, or a browser UI issue. Regardless of the underlying cause, it is confusing that a user who has just been presented with plan-review options can lose access to them without a clear explanation of what happened or how to return to that decision. Suggested improvement: Make the current agent state and available user actions explicit and persistent across working-mode changes, page refreshes and session restoration. A pending plan decision should remain accessible until the user makes a decision, or the interface should clearly explain why it is no longer available. 4. What would make this workflow clearer?A few practical improvements would help:
5. A separate but related permissions concernI have also seen GitHub Copilot app issue #5693, which describes a different but related problem: an Autopilot action could be denied when the approval system could not obtain a human decision, without showing the user an approval request. I understand that approving an implementation plan and approving an individual tool action are two different things. I'm not suggesting they should be treated as the same mechanism. I mention the issue because both experiences point to the same user-facing need: when Copilot needs a decision from me, I should be able to see that request and respond to it clearly. Final thoughtI don't mind having Interactive, Plan, and Autopilot modes, or having a cloud environment behind the browser experience. Those capabilities are useful. What I do mind is having to guess what state the session is in, work out where the relevant controls have gone, or send another prompt just to make those controls appear again. If Copilot is waiting for my decision, please show me the decision controls—and keep them visible when I return to the session. I want to spend my time working on my code, not figuring out how to recover the interface that is supposed to let me work on it. |


Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Copilot is now one connected experience in the cloud. Start a cloud task wherever you are, on github.com, GitHub Mobile, the Copilot CLI, the Copilot app, VS Code, or right from a conversation in Slack or Microsoft Teams. Then pick it up wherever you work next.
By default, every session runs in a secure cloud sandbox that starts fast and resumes right where you left off. The compute behind it can now be drawn from your included Actions entitlement, the same one that already runs your builds. That entitlement is now one flexible pool you can use for builds, cloud sandboxes, and, on Team and Enterprise Cloud, larger hosted runners.
The new Copilot cloud experience across surfaces (e.g., Web, Mobile, App, CLI, VS Code, Slack, and Microsoft Teams) and cloud sandboxes are both generally available on paid Copilot plans.
Why this new connected experience matters
Start cloud sessions and continue your work anywhere
On github.com and GitHub Mobile, you can chat and kick off code changes in the same conversation, with the same deep integration with your GitHub workflow as Copilot Chat and Copilot coding agent. Ask a question across multiple repositories in an organization or pick a repository for a code change. In Slack or Teams, mention @github to create an issue, request a code change, or investigate a bug.
@. In Slack and Teams, Copilot can use messages and threads as context.For more information, see the documentation on using Copilot in a cloud environment.
Give Copilot the tools & context it needs
Cloud sessions have the same tools as the Copilot CLI and Copilot app, plus ways to bring in context and customize how Copilot works:
/rubber-duck,/context, and more now work on github.com and GitHub Mobile.Run on Copilot on secure cloud sandboxes
By default, every session runs Copilot in a secure cloud sandbox. These cloud sandboxes are a secure, fast, and resumable execution environment on GitHub-managed infrastructure. Snapshots let you resume a session later from any surface.
Billing for cloud sandbox usage begins in November 2026. Free usage will draw from the shared compute entitlement described in the next section.
copilot-setup-steps.yml, you still need to use Actions as the environment for your session.--environment-hostto register your own computer or VM as an environment in your Copilot clients.A unified, flexible way to use your Actions entitlement
Your included Actions entitlement is now one shared, dollar-based compute entitlement, instead of a fixed number of standard runner minutes. It's the same value, and you can now use it across:
Usage draws from one shared entitlement, while each product keeps its own published meter and rate. Choose the compute that best fits your work.
For the latest pricing and included compute by plan, see product usage included with each plan.
How it works:
The flexible Actions compute entitlement change applies to GitHub Free, Pro, Free for organizations, Team, and Enterprise Cloud. Larger hosted runners draw from the entitlement only on Team and Enterprise Cloud. Billing for cloud sandbox usage begins November 2026 and draws from your included Actions entitlement.
Manage cloud access and permissions
Access to cloud experiences, including Copilot on github.com and GitHub Mobile, is governed by the policy in Copilot settings titled “Copilot in the cloud”. If you previously had cloud agent enabled, but opted a repository out of Copilot cloud agent, this repository exclusion will be brought over into the new experience.
If your organization has configured enterprise-managed settings for agent permissions or MCP server allowlists, these will apply to the updated cloud experience. For more information, see supported enterprise keys in the cloud.
To ensure data security, chat sessions are scoped to a single organization or your personal repositories by default. Members of an organization will have to use single sign-on to access session data from a repository associated with that organization.
If you do not have write access to a repository you're looking at, your Copilot use in that repository will automatically be read-only.
See more on managing access and permissions in the cloud.
Getting started
The new Copilot cloud experience is available on paid Copilot plans only and is rolling out to users starting October 28th. Copilot Free users can continue to use Copilot Chat on github.com and GitHub Mobile and can get the updated experience by upgrading their Copilot plan. Cloud sandbox usage can now be drawn from your included Actions entitlement.
Go to the GitHub Copilot page or the Agents tab in a repository or open the Copilot tab in GitHub Mobile. To start or continue a cloud session from Copilot CLI, the Copilot app, or VS Code, see our documentation.
Onboarding in Slack and Microsoft Teams is now simpler. With the required organization policies enabled, install or upgrade the GitHub app and connect your GitHub account to start working with @github.
🌟 Leave a comment!
Join the discussion and leave feedback in the comments below!
Tune in for Day 2 of GitHub Universe & check out our round-up post of releases in the Community that need your input ⏭️
All reactions