Which environments can a Copilot cloud session use?
Why C is the answer
A cloud sandbox, GitHub Actions, or a remote custom environment
GitHub lists three choices: Cloud, GitHub Actions-based and Remote.
In detail
- A cloud session can use a cloud sandbox, GitHub Actions or a remote custom environment.
- GitHub calls these Cloud, GitHub Actions-based and Remote.
Use case
An illustrative scenario, not a real incident.
A team chooses how cloud sessions run: a cloud sandbox for most, GitHub Actions for one workflow, and a remote custom environment for a service with special needs.
See it in different ways
flowchart LR A["Issue or chat request"] --> B["Agent in a cloud environment"] B --> C["Branch with changes"] C --> D["Pull request"] D --> E["Human review and merge"]
sequenceDiagram participant D as Developer participant A as Copilot cloud agent participant G as GitHub D->>A: Task A->>G: Opens a branch and pull request G-->>D: Asks for review D->>G: Approves or asks for changes
mindmap
root(("Cloud session"))
n1["Cloud"]
n2["Sandbox"]
n3["GitHub Actions-based"]
n4["Runs on Actions"]
n5["Remote"]
n6["Custom environment"]Key point: Cloud sessions have three environment choices.
Why the other options are wrong
- A. Only a browser tab that has to stay open for the whole session
- The session does not need an open browser tab.
- B. Only a virtual machine that the organization owner has logged in to
- No owner has to be logged in to a machine.
- D. Only the local machine of the developer who started it
- Cloud sessions are not tied to a local machine.