The agent needs more compute or access to internal resources. Where can it run?
Why C is the answer
On GitHub Actions larger runners or self-hosted runners
GitHub documents upgrading to larger runners and running on self-hosted runners.
In detail
- Larger runners give more compute.
- Self-hosted runners can reach internal resources.
- Check the network and access of a self-hosted runner.
Use case
An illustrative scenario, not a real incident.
An agent must reach an internal package server. A self-hosted runner can see it, and larger runners help with heavy builds.
See it in different ways
flowchart LR A["copilot-setup-steps.yml"] --> B["Install tools and dependencies"] B --> C["Agent starts work"]
stateDiagram-v2 [*] --> Trigger Trigger --> Setup: copilot-setup-steps Setup --> Runner: standard, larger or self-hosted Runner --> Working Working --> DraftPullRequest DraftPullRequest --> [*]
flowchart TD
Q{"What does it need?"}
Q -->|"More compute"| A0["Larger runner"]
Q -->|"Internal resources"| A1["Self-hosted runner"]Key point: Pick the runner for the need.
Why the other options are wrong
- A. In a browser tab that remains open for the whole task
- It does not run in a browser tab.
- B. Only on GitHub-hosted standard runners
- Standard runners do not give that extra access.
- D. Only on a virtual machine owned by the MCP server vendor
- It does not run on a vendor's machine.