AI Tool Profile
GitHub Copilot
GitHub introduced an asynchronous coding agent for GitHub Copilot, embedded in GitHub and accessible from VS Code.
Coverage describes this profile, not a product score or a current price guarantee.
Kingy AI Product Facts
GitHub Copilot
Current statusUnknown
- Company
- Not yet reviewed
- Primary job
- AI coding assistance that helps people write code faster and with less effort.
- Audience
- Not yet reviewed
- Free plan
- Available
- Evidence
- Source-backed; review due
- Latest source check
- October 20, 2026
See all tracked product factsPricing, platforms, dependencies, data claims, regions, and timeline
Sources and checks
- Coverage
- 7 of 87 tracked fields currently verified
- Sources
- 4
Source-check dates apply to the tracked facts. Editorial updates elsewhere on this page may have a different date.
Plans and pricing units
- Pro+ 39 USD per user per month
- Max 100 USD per user per month
- Pro 10 USD per user per month
Where it runs
- Availability
- Not yet reviewed
Stack and integrations
- Model / provider dependencies
- Not yet reviewed
- Integrations
- Not yet reviewed
Data and regions
- Vendor data-use claim
- Not yet reviewed
- Vendor retention claim
- Not yet reviewed
- Regions
- Not yet reviewed
Launch and latest material update
- Launch
- Not yet reviewed
- Latest material update
- Not yet reviewed
Review history
- GitHub Copilot — Verification refreshed
Kingy reconfirmed the published facts against the cited sources.
View published revision - GitHub Copilot — Verification refreshed
Kingy reconfirmed the published facts against the cited sources.
View published revision - GitHub Copilot — Verification refreshed
Kingy reconfirmed the published facts against the cited sources.
View published revision - GitHub Copilot — Verification refreshed
Kingy reconfirmed the published facts against the cited sources.
View published revision - GitHub Copilot — Verification refreshed
Kingy reconfirmed the published facts against the cited sources.
View published revision - GitHub Copilot — Verification refreshed
Kingy reconfirmed the published facts against the cited sources.
View published revision - GitHub Copilot — Verification refreshed
Kingy reconfirmed the published facts against the cited sources.
View published revision - GitHub Copilot — Verification refreshed
Kingy reconfirmed the published facts against the cited sources.
View published revision
Current source update — September 7, 2026
GitHub’s current individual plans page lists Copilot Free at US$0, Pro at US$10 per user per month, Pro+ at US$39 per user per month and Max at US$100 per user per month. Free lists 2,000 completions per month and Copilot CLI; Pro adds cloud agent, code review, model selection and US$15 monthly total credits; Pro+ lists US$70 monthly total credits; Max lists US$200. Those are provider-listed individual-plan facts, not a prediction of a particular workflow’s consumption.
The same page says AI credits are consumed by chat, agent mode, code review, cloud agent, Copilot CLI and Copilot Apps, and that the Free plan supports CLI and agent mode. Availability across GitHub, editors and organization-managed accounts remains product-, policy- and feature-dependent. A plan listing does not establish access to every third-party agent, a fixed model list, enterprise billing or a safe autonomous workflow.
This is a source update, not a Kingy hands-on test. It preserves the existing billing-boundary explanation and does not replace its historical source anchors.
Current first-party source
- GitHub Copilot plans — retained successful capture 2026-09-07
Earlier source assessment — 2026-08-10, with the accepted September 6 plan note
Retained for context. The current update above covers the facts rechecked on September 7; other statements below have not been revalidated by that update. Use the dates and account scopes attached to each statement.
Warning: This is not a general GitHub Copilot pricing guide. It covers only the legacy annual Pro/Pro+ boundary in the cited source.
Answer first: GitHub’s cited request page applies only to legacy annual Copilot Pro and Pro+ subscribers who remained on request-based billing after June 1, 2026.
What this page establishes
Premium request use can vary by feature and model; do not generalize this page to every Copilot account or current plan.
What it does not establish
This is a billing-boundary explainer, not a pricing recommendation or usage estimate.
FAQ
Is this a recommendation?
No. This is source-bound editorial context; selection needs a task, account, data, permission, cost and human-review boundary.
What should be tested before adoption?
Use a disposable or approved environment, record product/version/account, define allowed tools and data, inspect diffs and logs, and keep a human approval step.
Sources, testing and correction
Product documentation: What is GitHub Copilot? — GitHub
Primary source: GitHub Copilot legacy request-based billing documentation.
Testing limit: Kingy has not created an account, connected a repository, submitted code, run a model, benchmarked output, or tested security.
Correction: replace only the affected claim with dated primary evidence; retain the prior source and correction note.
Current plan check
As observed on 2026-09-06, GitHub lists Copilot Free for individuals and lists Copilot Pro at US$10 per user per month. These individual-plan statements do not establish access, limits, or billing for every Copilot agent feature or organization policy.
Source: GitHub Copilot plans (retained successful capture: 2026-09-06T03:13:08.000Z).
The Kingy Brief
Get The Kingy Brief.
AI changes, original tests and one practical thing to try. Fridays at 09:00 Vancouver time.
Free · Double opt-in · Unsubscribe anytime
Sign up for The Kingy Brief on Beehiiv.
Signup help and newsletter schedule
Signup form provided by Beehiiv. After submitting, check your inbox for "Confirm your subscription to The Kingy Brief" and open its confirmation link. Check Spam or Promotions if you cannot find it.
Fridays at 09:00 Vancouver time: source-checked AI changes, original tests and one practical thing to try. We skip a week when there is not enough verified material. Free. Unsubscribe anytime.
Tool Links
Launch History
GitHub Copilot cloud agent for Linear reaches general availability
GitHub made its Copilot cloud agent integration for Linear generally available, allowing teams to assign Linear issues to an asynchronous coding agent.
Copilot cloud agent for Linear addresses a concrete need: The integration moves agent assignment into an issue tracker that many software teams already use,…
GitHub Copilot in VS Code June 2026 releases
GitHub summarized Copilot changes across Visual Studio Code 1.123 through 1.127, including integrated browser interaction, parallel agent sessions, chat organization, AI-credit visibility, model-provider discovery and Autopilot behavior.
The June roundup shows VS Code becoming an orchestration surface for multiple agents, browser checks and model choices rather than a single coding chat.…
Codex as an agent provider in GitHub Copilot for JetBrains
GitHub added Codex as an optional public-preview agent provider in GitHub Copilot for JetBrains IDEs and shipped related agentic enhancements including hooks support, richer MCP server management and…
Provider choice inside JetBrains can reduce tool switching, but Codex, Claude and Copilot modes should not be treated as equivalent harnesses. The release is…
GitHub Copilot Cost Centers AI Credit Pools
GitHub added AI credit pools to cost centers on July 2, 2026 so eligible enterprises can cap how much included Copilot AI credit usage a group draws from…
- Launch readiness
- 6.8 / 10
- Demo evidence
- Not scored yet
- Creator-story fit
- Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.
- Scale
- 0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
- Assigned by
- Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
- Rubric and check date
- Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-07-09.
- Confidence and missing data
- Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
- Freshness
- Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
- Disputes
- Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.
GitHub added AI credit pools to cost centers, letting eligible enterprises cap how much included Copilot usage a group draws from the shared pool…
GitHub Copilot AI Credits Usage Metrics API
GitHub added the ai_credits_used field to enterprise and organization Copilot usage-metrics API reports, exposing an overall per-user total in the one-day and 28-day user endpoints.
Per-user AI-credit totals give administrators a practical way to spot consumption concentration and build internal reporting. The field is deliberately coarse: GitHub says it…
GitHub Copilot Agent Finder
GitHub released Agent Finder for Copilot, which accepts a plain-language task, searches a selected public or private Agentic Resource Discovery registry, and returns ranked MCP servers, skills, canvases,…
Agent Finder addresses a real scaling problem: agents should not carry every possible integration in context. Its strongest controls are registry choice, managed settings…
GitHub Copilot Chat agent-session search
GitHub updated Copilot Chat so it can search and query past Copilot cloud agent sessions in chat.
- Launch readiness
- 6.5 / 10
- Demo evidence
- Not scored yet
- Creator-story fit
- Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.
- Scale
- 0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
- Assigned by
- Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
- Rubric and check date
- Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-12.
- Confidence and missing data
- Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
- Freshness
- Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
- Disputes
- Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.
GitHub updated Copilot Chat to search and query past Copilot cloud agent sessions, per the June 10, 2026 changelog (github.blog). Developers and Engineering Teams…
GitHub Copilot CLI security review command
GitHub added a dedicated security review command to Copilot CLI.
- Launch readiness
- 6.7 / 10
- Demo evidence
- Not scored yet
- Creator-story fit
- Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.
- Scale
- 0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
- Assigned by
- Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
- Rubric and check date
- Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-12.
- Confidence and missing data
- Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
- Freshness
- Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
- Disputes
- Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.
GitHub added a dedicated security review command to Copilot CLI in its June 10, 2026 changelog (github.blog). Developers and Security-Minded Engineering Teams get an…
GitHub Copilot coding agent
GitHub introduced an asynchronous coding agent for GitHub Copilot, embedded in GitHub and accessible from VS Code.
Important because distribution inside GitHub may matter more than standalone agent novelty for enterprise adoption.
Introducing GitHub Copilot Extensions
GitHub introduced Copilot Extensions so partners and developer tools could connect into Copilot Chat experiences.
- Launch readiness
- 6.5 / 10
- Demo evidence
- Not scored yet
- Creator-story fit
- Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.
- Scale
- 0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
- Assigned by
- Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
- Rubric and check date
- Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-08.
- Confidence and missing data
- Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
- Freshness
- Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
- Disputes
- Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.
GitHub introduced Copilot Extensions in May 2024. Its GitHub App-based Copilot Extensions were disabled on November 10, 2025; new server-side extensions had already been…
Kingy coverage
Kingy AI articles about GitHub Copilot, newest first.
- NewsGitHub Copilot Can Control Desktop Apps: Setup and Permission Limits
- NewsGitHub Copilot’s June 2026 VS Code Update: Browser Agents, Parallel Sessions, and AI Credit Visibility
- NewsGitHub Copilot Adds Codex as a JetBrains Agent Provider: Setup, Pricing, and Preview Risks
- NewsKimi K2.7 Code in GitHub Copilot Business and Enterprise: Access, Billing, and Governance
- NewsGitHub Copilot AI Agent Session Limits: What the Launch Means for AI Platform Teams
- NewsGitHub Copilot Agent in JetBrains AI Assistant: pricing, KALI evidence, and buyer risks
- NewsGitHub Copilot for Jira: permissions, costs, and rollout tests
- NewsHow GitHub Copilot App BYOK Could Change AI Coding Workflows
More coverage (7)
- NewsHow GitHub Copilot AI Credits Usage Metrics API Could Change AI Coding Workflows
- NewsGitHub Copilot Auto Mode Routes Chat Requests Across Models
- NewsGitHub Copilot App: What the Launch Means for AI Platform Teams
- NewsGitHub Copilot Chat Can Search and Explain Agent Sessions
- NewsGitHub Copilot Code Review Controls: What the Launch Means for AI Platform Teams
- NewsThe Party’s Over: GitHub Copilot Is Charging You for Every Token You Burn
- NewsA Detailed Analysis of AI-Powered Coding Assistants: Google Jules vs. OpenAI Codex vs. GitHub Copilot