← Back to the saved comparison

GitHub Copilot: the evidence

This page explains the answers in the comparison. Each section gives an answer, its limits, and the vendor documentation behind it.

Configuration: Cloud agent · Standard runner. Paid Copilot plan · standard GitHub-hosted ubuntu-latest · one GitHub repository.

The default GitHub-hosted runner, with repository access enabled. These answers apply to this setup; other ways of using GitHub Copilot may work differently.

AI-Buzz saved these answers on . This is a documentation review; AI-Buzz has not tested this configuration. Check later corrections.

Where commands run

GitHub Copilot · Cloud agent · Standard runner

The standard configuration runs on a GitHub-hosted Actions runner using ubuntu-latest. Self-hosted runners are a separate configuration.

Limits of this answer: This record uses the standard ubuntu-latest runner. Self-hosted and custom runners are separate configurations.

The machine where the agent edits your files and runs builds and tests.

Where model requests go

GitHub Copilot · Cloud agent · Standard runner

Not established for this configuration. GitHub documents model-specific hosting; runner location does not establish inference or orchestration location.

Limits of this answer: Model-dependent hosting; no model selected. Separate orchestration location is also unknown.

Model hosting is separate from where commands run. A local tool can still use a remote AI model.

“LLM” means language model. “Inference” means that model generating a response. “Orchestration” means coordinating the agent’s next steps. The machine editing your files and the service answering model requests can be in different places.

Hosting of Copilot models

Why this source is relevant: Hosting depends on the selected model. This comparison has not selected a Copilot model and does not infer hosting from the runner.

Short excerpt from the vendor’s documentation:

This article explains how these models are hosted and served.

Where to read the full passage: Lines 15–39; model-specific sections

Open the vendor’s current page

Where your code lives

GitHub Copilot · Cloud agent · Standard runner

Works on a GitHub repository, with one target repository per task. Managed-user-owned repositories and repositories where access is disabled are excluded.

Limits of this answer: One target repository per task; managed-user-owned or disabled repositories are excluded.

The code-hosting service or local Git repository used by this setup.

About GitHub Copilot cloud agent

Why this source is relevant: Cloud agent overview, GitHub.com branch/PR paths and issue assignment. The access reusable is pinned at the same repository revision.

Short excerpt from the vendor’s documentation:

make code changes on a branch

Where to read the full passage: Lines 24–73, 103–111, 149–163

Open the vendor’s current page

How work starts

GitHub Copilot · Cloud agent · Standard runner

Start from the agents panel on GitHub.com, assign an issue, or mention Copilot in a pull-request comment.

Limits of this answer: GitHub.com, issue assignment and PR comments are documented; no API trigger is established in this record.

How you can give the agent a task.

About GitHub Copilot cloud agent

Why this source is relevant: Cloud agent overview, GitHub.com branch/PR paths and issue assignment. The access reusable is pinned at the same repository revision.

Short excerpt from the vendor’s documentation:

make code changes on a branch

Where to read the full passage: Lines 24–73, 103–111, 149–163

Open the vendor’s current page

How you review the result

GitHub Copilot · Cloud agent · Standard runner

Changes are made on a branch. From GitHub.com, inspect the diff and iterate before choosing to create a pull request.

Limits of this answer: GitHub.com supports review before PR creation; issue entry points may create a PR directly.

Where the proposed code changes appear and how you review them.

About GitHub Copilot cloud agent

Why this source is relevant: Cloud agent overview, GitHub.com branch/PR paths and issue assignment. The access reusable is pinned at the same repository revision.

Short excerpt from the vendor’s documentation:

make code changes on a branch

Where to read the full passage: Lines 24–73, 103–111, 149–163

Open the vendor’s current page

What you need to use it

GitHub Copilot · Cloud agent · Standard runner

Available on paid Copilot plans. Business and Enterprise require admin enablement; repository owners can disable access.

Limits of this answer: Paid plan required; Business and Enterprise need admin enablement. Exact price, quotas and region are outside scope.

The plan, accounts and permissions you need. This is not a cost estimate.

About GitHub Copilot cloud agent

Why this source is relevant: Cloud agent overview, GitHub.com branch/PR paths and issue assignment. The access reusable is pinned at the same repository revision.

Short excerpt from the vendor’s documentation:

make code changes on a branch

Where to read the full passage: Lines 24–73, 103–111, 149–163

Open the vendor’s current page

What this page cannot tell you

These sources describe how this configuration is documented to work. They do not show its success rate on real tasks or establish when a product change happened.

The linked vendor pages may change after retrieval. Where permission to keep a full page is unresolved, we retain a short attributed interpretation and excerpt, with a pointer to the relevant section.

Read the configuration overview · See all coverage and limits · Download the saved answers and sources (2026-09-08.1, JSON)