GitHub Copilot Complete Installation Guide: VS Code Extension Setup, Copilot Business Organization Config & Multi-Editor Setup for JetBrains and Neovim

GitHub Copilot Complete Installation Guide: From VS Code to Enterprise Multi-Editor Setup

GitHub Copilot has fundamentally changed how developers write code. Whether you’re a solo developer on the Individual plan or an engineering lead rolling out Copilot Business across your organization, this guide walks you through every installation step — covering VS Code, JetBrains IDEs, and Neovim in a single, actionable resource.

Prerequisites

• An active GitHub account (free tier or higher)
• A GitHub Copilot subscription (Individual, Business, or Enterprise)
• Node.js 18+ installed (required for some CLI operations)
• Git 2.30+ configured with your GitHub credentials

Step 1: Subscribe to GitHub Copilot

• Navigate to github.com → Settings → Copilot.
• Choose your plan:

Step 2: Install GitHub Copilot in VS Code

VS Code is the primary supported editor and offers the richest Copilot experience.

• Open VS Code and press Ctrl+Shift+X to open the Extensions panel.
• Search for GitHub Copilot and click Install.
• Also install GitHub Copilot Chat for the inline chat experience.
• Alternatively, install via the CLI: code —install-extension GitHub.copilot code —install-extension GitHub.copilot-chat
• After installation, VS Code prompts you to sign in to GitHub. Click Sign in to GitHub and authorize the extension in your browser.
• Verify activation by opening any code file — you should see ghost text suggestions as you type.

VS Code Settings for Copilot

Fine-tune behavior in your settings.json:

{ “github.copilot.enable”: { ”*”: true, “markdown”: true, “plaintext”: false, “yaml”: true }, “github.copilot.advanced”: { “inlineSuggest.enable”: true, “listCount”: 5 }, “github.copilot.chat.localeOverride”: “en” }

Step 3: Configure Copilot Business for Your Organization

If you're an organization owner setting up Copilot Business:

• Go to github.com → Your Organization → Settings → Copilot.
• Click Enable GitHub Copilot and select the Business plan.
• Choose your seat assignment policy:

gh api -X POST /orgs/YOUR_ORG/copilot/billing/selected_teams
-f selected_teams[]=“engineering”
-f selected_teams[]=“data-science”

• Set content exclusion rules to prevent Copilot from accessing sensitive repositories:

# In your organization settings → Copilot → Content Exclusions
# Add patterns like:
repositories:
  - "your-org/secret-repo"
  - "your-org/compliance-*"
paths:
  - "**/.env"
  - "**/secrets/**"

• Enable or disable Suggestions matching public code under the policy settings to control IP risk.

Audit and Monitor Usage

# Check seat assignments
gh api /orgs/YOUR_ORG/copilot/billing/seats --jq '.seats[] | {login: .assignee.login, last_activity: .last_activity_at}'

# Export usage report
gh api /orgs/YOUR_ORG/copilot/usage --jq '.[] | [.day, .total_active_users, .total_suggestions_count] | @csv'

Step 4: Install Copilot in JetBrains IDEs

Copilot works across all JetBrains IDEs including IntelliJ IDEA, PyCharm, WebStorm, GoLand, and Rider.

• Open your JetBrains IDE and navigate to File → Settings → Plugins (or Preferences → Plugins on macOS).
• Search the Marketplace for GitHub Copilot and click Install.
• Restart the IDE when prompted.
• After restart, go to Tools → GitHub Copilot → Login to GitHub.
• Copy the device code shown, open the authorization URL in your browser, paste the code, and authorize.
• Verify by opening a code file — suggestions appear as gray inline text. Press Tab to accept.

JetBrains-Specific Configuration

Navigate to Settings → Languages & Frameworks → GitHub Copilot:

• Toggle auto-completions per language
• Set keyboard shortcuts for accepting, dismissing, or cycling suggestions
• Enable or disable Copilot Chat from the same panel

Step 5: Install Copilot in Neovim

Neovim users can access Copilot via the official Vim/Neovim plugin. Requires Neovim 0.6+ (0.9+ recommended).

• Install using your preferred plugin manager. With lazy.nvim: — In your lazy.nvim plugin spec (lua/plugins/copilot.lua) return { “github/copilot.vim”, event = “InsertEnter”, config = function() vim.g.copilot_no_tab_map = true vim.api.nvim_set_keymap(“i”, "", ‘copilot#Accept("")’, { expr = true, silent = true, noremap = true, }) — Disable for specific filetypes vim.g.copilot_filetypes = { [“markdown”] = false, [“text”] = false, } end, }
• Restart Neovim, then run the authentication command:

:Copilot auth

• Follow the on-screen prompt to authenticate via your browser.
• Verify the setup:

:Copilot status

Expected output: Copilot: Ready

Alternative: copilot-lua + copilot-cmp

For tighter nvim-cmp integration, use the Lua-native alternative:

return { { “zbirenbaum/copilot.lua”, cmd = “Copilot”, event = “InsertEnter”, opts = { suggestion = { enabled = false }, panel = { enabled = false }, }, }, { “zbirenbaum/copilot-cmp”, dependencies = { “copilot.lua” }, config = function() require(“copilot_cmp”).setup() end, }, }

Pro Tips for Power Users

• Use inline chat effectively: In VS Code, press Ctrl+I to open inline Copilot Chat. Describe what you want directly in the editor context for more accurate results.
• Copilot CLI for terminal: Install gh copilot for AI-powered command suggestions:

gh extension install github/gh-copilot
gh copilot suggest "find all files modified in the last 24 hours"
gh copilot explain "git rebase -i HEAD~5"

• Custom instructions file: Create a .github/copilot-instructions.md file at the root of your repository to provide project-specific context that Copilot Chat will use automatically.
• Keyboard shortcut mastery: Use Alt+] and Alt+[ in VS Code to cycle through alternative suggestions without dismissing the current one.
• Prompt engineering in comments: Write detailed comments describing the function you need before the function signature — Copilot uses these as context for dramatically better completions.

Troubleshooting Common Issues

Proxy and Firewall Configuration

For enterprise environments behind firewalls, ensure these endpoints are accessible:

# Required domains for Copilot copilot-proxy.githubusercontent.com api.github.com github.com *.githubcopilot.com

{ “http.proxy”: “http://your-proxy-server:8080”, “http.proxyStrictSSL”: true }

Frequently Asked Questions

Can I use GitHub Copilot across multiple editors simultaneously with the same subscription?

Yes. A single GitHub Copilot subscription is tied to your GitHub account, not to a specific editor. You can install and use Copilot in VS Code, any JetBrains IDE, and Neovim at the same time. Your suggestions and chat history are not shared between editors, but the authentication and billing are managed at the account level. There is no additional cost for using multiple editors.

How does Copilot Business differ from Copilot Individual in terms of data privacy?

With Copilot Business and Enterprise plans, GitHub guarantees that your code snippets are not retained after a suggestion is delivered and are not used to train models. On the Individual plan, you can opt out of telemetry in your settings, but the default allows GitHub to use your data for product improvements. Business plans also provide organization-level policy controls, audit logs, content exclusion rules, and IP indemnity coverage.

What should I do if Copilot suggestions are consistently low quality or irrelevant?

First, ensure you have relevant files open in your editor — Copilot uses open tabs as context. Add a .github/copilot-instructions.md file with project-specific guidelines such as coding style, preferred libraries, and architectural patterns. Write descriptive function names and comments before the code you need generated. For Copilot Chat, be specific in your prompts and reference files with @workspace or #file tags. Finally, verify you are on the latest extension version, as suggestion quality improves with updates.