GitHub · Setup guide
How to set up GitHub Copilot
Add Copilot to the editor your team already uses, then validate inline suggestions, IDE agent mode, and the cloud agent on small tested changes before broader rollout. Neovim is completions-only; Chat and Agent mode require another supported surface.
GitHub Copilot
editor plugin · checked August 14, 2026
The “Open GitHub Copilot” link goes to the vendor site. It is not an affiliate-tracked link on this page — no commission is claimed for that click. Affiliate disclosure.
Before you begin
- A supported IDE such as VS Code, JetBrains, Visual Studio, Xcode, Eclipse, or Neovim.
- Copilot access through Copilot Free or a paid plan.
- A GitHub account governed by the right personal or organisation policy.
- For cloud-agent work, a repository where the account has the required branch, issue, and pull-request permissions.
Authentication
GitHub sign-in inside the IDE
Account: GitHub account with Copilot access
For managed organisations, access, policy, and model controls may be administered centrally.
Install or open it
1. Get the harness ready
These steps are written for beginners. On Mac, Terminal is the black/white text window where you type commands. On Windows, use PowerShell or Terminal. Use the OS tabs to hide steps that are not for your computer, then copy one command at a time.
- 01
Open your editor
Start VS Code, JetBrains, Visual Studio, Xcode, or Neovim — whichever your team already uses. Copilot installs inside that app; you do not download a separate Copilot IDE.
- 02
Use VS Code’s automatic Copilot setup
In VS Code, click the Copilot icon in the title bar or Status Bar → Use AI Features, then sign in with GitHub. VS Code installs the required Copilot extensions automatically on first setup; do not start by searching the Marketplace unless this flow is unavailable in your version.
VS Code Copilot setup - 03
Other editor paths
JetBrains: Settings → Plugins → Marketplace → GitHub Copilot. Visual Studio 17.10+ includes Copilot setup in the IDE; Xcode and Eclipse use their documented extension flows. Neovim uses copilot.vim for completions only — it does not provide Copilot Chat or Agent mode.
GitHub Copilot extension setup - 04
Check network requirements
Enterprise networks may need the Copilot allowlist or a custom certificate before sign-in and suggestions work.
GitHub Copilot setup
Repository or project
2. Start in the right place
Keep the first repository small, clean, and easy to roll back while you learn the harness’s permissions and context model.
- 01
Open a tracked repository
Open a project in the supported IDE and confirm the active GitHub account before accepting suggestions.
- 02
Set repository instructions
Add the project’s conventions and test command to the supported instruction mechanism used by your IDE and organisation.
GitHub Copilot quickstart
First run
Use a small, tested suggestion
Use this task to test the workflow before handing over a larger repository or production responsibility.
- 01Ask Copilot to explain one existing function and its edge cases.
- 02Request a unit test for one missing case.
- 03Review and run the test yourself before accepting the suggestion.
- 04For an eligible plan, try IDE agent mode or a cloud-agent task on a disposable branch and review the resulting diff and checks.
Why this is safe: A narrow test change gives the team a visible diff and a quick correctness signal without delegating repository-wide changes.
Stop and review if
- The suggestion includes code copied from an unrelated context or an unexplained dependency.
- The organisation’s policy does not permit the repository to be indexed.
- The generated test passes without exercising the intended edge case.
The operating boundary
Privacy, data, and cost
The setup is incomplete until you know what the harness can see, what account pays for it, and who approves a risky action.
Privacy
Individual Copilot can allow suggestions improvement / training depending on settings; Business/Enterprise generally exclude training on your code and add admin content exclusions — confirm live GitHub policy for your plan.
Training on code: tier dependent
Enterprise and managed-account controls should be checked with the current GitHub documentation and organisation policy.
Sensitive repos: Confirm content exclusion and organisation policy before enabling Copilot on proprietary or regulated repositories.
Pricing
Seat plans (Free / Pro / Pro+ / Max / Business / Enterprise) plus monthly GitHub AI Credits for chat, agent, CLI, cloud agent, and code review since June 2026. Completions remain included on paid plans. Individual Pro+ and Max add flex credits (Max is 10,000 base + 10,000 flex = 20,000 total). Business/Enterprise promo pools are 3,000 / 7,000 through 2026-09-01; standard pools after that are 1,900 / 3,900 per user per month (pooled).
Model: hybrid
Watch out: Business/Enterprise promo credit allowances (3,000 / 7,000) end 2026-09-01 — after that, expect the standard 1,900 / 3,900 pools. Annual Pro plans are retired for new buyers. Agent-heavy work burns AI Credits and may add Actions minutes for cloud agent / review. MAI-Code-1-Flash retires 2026-09-10 (GitHub recommends MAI-Code-1.1-Flash). Gemini 3.7 Flash has been rolling out since 2026-08-13 at provider list rates and is not the Copilot default.
When setup goes wrong
The extension is installed but suggestions are unavailable.
Check GitHub account access, IDE compatibility, network allowlists, and whether the current file type is supported.
A managed repository is excluded.
Ask the organisation administrator to review content exclusions and the applicable Copilot policy.
Suggestions are too broad or generic.
Add the repository’s conventions and tests to the prompt context, then ask for a smaller change with explicit acceptance criteria.
Next steps
After the first successful run
Keep the pilot small, then compare surfaces and budget before a team rollout.
Setup details change quickly. The page was checked August 14, 2026; use the official source below before installing in a managed or production environment.