GitHub Copilot Not Activating After a Plan Change: Safe Fixes
🔍 WiseChecker

GitHub Copilot Not Activating After a Plan Change: Safe Fixes

If GitHub Copilot stops working after you change plans, first check the account and entitlement. The timing does not prove that a cached token has the wrong subscription tier. Organization policy, exhausted usage, an incompatible client or a network failure can produce similar symptoms.

Refresh authentication only after confirming that the selected account should have access. You do not need to delete your IDE’s Local History or broadly erase operating-system credentials.

ADVERTISEMENT

1. Verify what actually changed on GitHub

Open GitHub in the browser and confirm the username. Under Settings → Billing & licensing → Licensing, inspect the current plan; the original billing platform uses Billing and licensing → Plans and usage. Follow the current plan-management instructions.

  • Organization access: ask the administrator to confirm the seat is assigned to this exact account and the required feature is allowed.
  • Personal plan: inspect whether the change is active or scheduled, and whether the billing page reports a payment problem. Do not repurchase the plan simply to refresh the editor.
  • Usage message: read the allowance or reset information shown. GitHub documents that a renewal or plan change does not automatically grant a fresh monthly AI-credit allowance. See license changes and allowance timing.

Check GitHub’s status page through the troubleshooting guide if multiple accounts or colleagues are affected. An outage is not fixed by repeated account resets.

2. Refresh the correct VS Code session

If you have multiple GitHub identities, first inspect Accounts → Manage Extension Account Preferences for GitHub Copilot Chat in the active workspace or profile. Select the account that has access. The VS Code setup guide describes this control.

When the account is correct but authentication still fails, save your work and use GitHub’s documented refresh:

  1. Open VS Code’s Accounts menu and sign out of the affected GitHub account. Other extensions using that account may also require sign-in again.
  2. Run Developer: Reload Window from the Command Palette.
  3. Sign back in and verify the username in the browser authorization flow before approving it.

Then test a simple request. This can renew authentication; it cannot grant an unassigned seat or override organization policy. See GitHub’s authentication troubleshooting.

ADVERTISEMENT

3. Use the Copilot plugin’s account flow in JetBrains

Check that the installed Copilot plugin is compatible with your JetBrains IDE and update it through the normal plugin mechanism where permitted. If the plugin offers a logout or account-switch control, use that targeted action rather than deleting credential-store entries by name.

For sign-in, GitHub documents Tools → GitHub Copilot → Login to GitHub, followed by the device-code authorization flow. Check the browser account carefully. A managed account on GHE.com requires the enterprise-specific setup linked from the installation and sign-in guide.

If your version has no usable account control, record the plugin and IDE versions and consult support. Do not select Clear file system cache and Local History as a Copilot sign-in fix: JetBrains confirms that option deletes Local History. A normal restart and a cache/history deletion are different operations.

4. Use the error to choose the next step

A 403 is a refusal, not proof of one specific token defect. Record the affected feature, selected account, endpoint or diagnostic message, and whether it occurs in all projects. Do not assume that waiting a fixed number of minutes resolves it.

If authentication succeeds but inline suggestions are absent in one file, check its language settings and any content-exclusion notice. If a request fails on the network, follow GitHub’s endpoint, proxy and certificate checks with the administrator. Do not disable TLS verification to test a subscription.

For unresolved cases, provide support with the change date, plan shown, IDE/plugin versions and a minimal reproduction. Redact tokens, private repository content and personal information from logs. These details are more useful than a history-clearing reset or another purchase.

Official documentation checked October 14, 2026. No account changes or credential deletion were performed for this review.

ADVERTISEMENT

Did this guide solve your problem?