Paid plans include monthly AI credits; additional use and signup availability are governed by current GitHub plan terms.
Checked 2026-07-12
Privacy and code-data boundary
Copilot processes prompts, suggestions, context, engagement, and feedback data; retention and training controls differ between individual and organizational plans.
Training/data-use check: Individual subscribers can review training controls in Copilot settings; business terms should be evaluated separately.
Verification record
Installed and tested · Hands-on setup or capability check retained by RepoRadar verification harness · last checked 2026-07-13T11:47:44.798456Z
Windows 10 AMD64; Python 3.11.9; credential-stripped child environment; disposable home/cache
Install/setup time
1 minute(s)
Evidence scope
Bounded setup or capability check
Cleanup
Per-check temporary home and work directory removed. Shared cohort package cache removed.
Actions exercised
Created a disposable home, work directory, and isolated package cache with credential-like environment variables excluded.
Executed bounded check: Resolve the official GitHub Copilot CLI package and read its version in an isolated cache.
Captured the complete sanitized stdout, stderr, exit status, artifact checks, and 7.68-second wall time.
Observed results
Command exited 0 after 7.68 seconds.
The command produced a successful local process exit; complete output is retained.
Observed strengths
The pinned @github/[email protected] package resolved and launched in isolation, reporting GitHub Copilot CLI 1.0.70 and its own latest-version status.
Friction
No blocking friction was observed during this bounded local check.
Limitations
Version startup proves package resolution and local CLI launch only; no Copilot authentication, AI credit, repository access, or model request was used.
This bounded cohort check is not a production benchmark or a claim of real user-workflow adoption.
Pricing assessment: No paid plan or metered provider usage was exercised; package or licensing, hosting, and provider costs remain workflow-dependent.
Privacy assessment: No repository content, user data, or provider prompt was transmitted; broader product data handling was not assessed by this bounded run.
Windows 10 AMD64; Python 3.11.9; credential-stripped child environment; disposable home/cache
Install/setup time
1 minute(s)
Evidence scope
Bounded setup or capability check
Cleanup
Per-check temporary home and work directory removed. Shared cohort package cache removed.
Actions exercised
Created a disposable home, work directory, and isolated package cache with credential-like environment variables excluded.
Executed bounded check: Resolve the official GitHub Copilot CLI package and inspect its command and permission surface.
Captured the complete sanitized stdout, stderr, exit status, artifact checks, and 2.70-second wall time.
Observed results
Command exited 0 after 2.70 seconds.
The command produced a successful local process exit; complete output is retained.
Observed strengths
GitHub Copilot CLI's retained help exposed interactive and --prompt scripting modes, configurable permissions, and an Agent Client Protocol server mode.
Friction
No blocking friction was observed during this bounded local check.
Limitations
Help output proves the local command surface only; no Copilot authentication, permission grant, repository operation, AI credit, or model request was used.
This bounded cohort check is not a production benchmark or a claim of real user-workflow adoption.
Pricing assessment: No paid plan or metered provider usage was exercised; package or licensing, hosting, and provider costs remain workflow-dependent.
Privacy assessment: No repository content, user data, or provider prompt was transmitted; broader product data handling was not assessed by this bounded run.
History begins 2026-07-14; trends appear after a second dated snapshot. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.
RepoRadar scoreTrend begins after a second recorded point.
Momentum signalTrend begins after a second recorded point.