Key takeaways
- 'Language model unavailable' means Copilot cannot reach or use the selected model from VS Code.
- Common causes are sign-in or subscription problems, outdated VS Code or extensions, network or proxy blocks, policies and quotas.
- Fix it by updating, re-signing in, switching models, checking GitHub's status and reading the Copilot output logs.
- Organisation policies can disable specific models, which makes them appear unavailable.
- Choose models by task: stronger reasoning models for complex coding, faster ones for quick edits and documentation.
The "language model unavailable" message in VS Code's GitHub Copilot means the extension cannot use the selected AI model right now, usually because of a sign-in or subscription problem, an outdated VS Code or Copilot Chat extension, network or proxy blocking, an organisation policy, an exhausted quota, or a GitHub service incident. Updating, re-signing in and switching models fixes most cases. I use AI coding assistants daily, so this page explains each cause, step-by-step fixes, and which Copilot models suit coding and documentation.
What does "language model unavailable" mean in VS Copilot?
It means Copilot in VS Code tried to send your request to a language model and could not, because the model is not accessible to your account, client or network at that moment. The editor still works; Copilot's AI features do not respond until the issue is resolved.
Also asked as: vs copilot language model unavailable
The message is generic, covering several underlying problems: authentication failures, unsupported client versions, models not enabled for your plan or organisation, rate limits, connectivity issues and outages. The Copilot output logs in VS Code usually reveal the specific reason, which tells you which fix to apply rather than trying everything blindly.
Why is the Copilot language model unavailable in VS Code?
The most common causes are an outdated VS Code or Copilot extension, an expired sign-in, an inactive Copilot subscription or trial, network restrictions such as corporate proxies or firewalls, and organisation policies that disable certain models.
Also asked as: vs code copilot language model unavailable · vs code copilot language model unavailable error · vs code github copilot language model unavailable · vs code copilot chat language model unavailable
Other causes include reaching your plan's premium request limit for a particular model, selecting a model that is in preview or not available in your plan, and temporary GitHub incidents. If Copilot worked yesterday and fails today without changes on your side, check GitHub's status page first. If it fails only on one network, suspect the proxy or firewall. College and office networks sometimes block the domains Copilot uses, so testing on a mobile hotspot is a quick way to confirm a network cause.
How do I read the "language model unavailable" error details?
Open VS Code's Output panel, choose "GitHub Copilot Chat" or "GitHub Copilot" from the dropdown, and look for error lines around the time of the failure. Messages often mention authentication, quota, policy, network or model errors with status codes.
Status codes help: 401 or 403 suggest authentication or policy problems; 429 indicates rate limits; 5xx codes point to service issues; and connection or certificate errors suggest network or proxy problems. Copy relevant log lines, without tokens, when asking for help in GitHub Community discussions or reporting issues, since they speed up diagnosis.
Why does GitHub Copilot say the language model is unavailable?
From GitHub's side, the model may be unavailable because your account lacks an active Copilot plan, your organisation has not enabled that model, the model requires a higher plan, or your premium requests for the period are used up.
Check your Copilot settings on github.com: subscription status, which models are enabled, and usage. Students and teachers may have free access through GitHub Education, which must be verified and renewed. Organisation members should ask administrators whether policies allow the model. Switching to a model included in your plan often restores Copilot immediately. If you recently changed GitHub accounts, make sure VS Code is signed in with the account that actually holds the Copilot licence.
Why is the Copilot Chat language model unavailable?
Copilot Chat often fails when the Copilot Chat extension version does not match your VS Code version, since the extension depends on recent VS Code APIs. Updating VS Code and both Copilot extensions to their latest versions resolves many chat failures.
Also check that chat is enabled in your settings and organisation policy, that you are signed in with the correct GitHub account in VS Code's accounts menu, and that conflicting extensions are not interfering. Reloading the window with the "Developer: Reload Window" command clears transient extension problems. Insiders builds sometimes need the pre-release Copilot Chat extension.
Why is a Copilot language model not available in the model picker?
A model may be missing or greyed out because your plan does not include it, your organisation disabled it, it is not supported in your client version, or it was retired or renamed. Model availability changes as GitHub adds and removes models.
Also asked as: vs code copilot language model not available
Update VS Code and extensions to see current models, check GitHub's documentation listing supported models by plan and client, and ask administrators about policies. If a preferred model disappears, choose a comparable alternative. Some models require opting in through settings on github.com before they appear in the editor. After enabling one, reload VS Code so the model list refreshes.
How do I fix "Copilot language model unavailable"?
Work through these steps in order, testing after each:
Also asked as: how to fix copilot language model unavailable
- Check GitHub Status for Copilot incidents.
- Update VS Code and the GitHub Copilot and Copilot Chat extensions.
- Sign out of GitHub in VS Code and sign back in.
- Confirm your Copilot subscription and model settings on github.com.
- Select a different model in the chat model picker.
- Reload the VS Code window.
- Check proxy settings, certificates and firewall rules on your network.
- Read the Copilot output logs for specific errors.
If nothing works, try another network or a fresh VS Code profile to isolate configuration problems, then contact GitHub Support with logs.
Which Copilot model is best?
There is no single best model; GitHub Copilot offers models from several providers, such as OpenAI, Anthropic and Google, each with strengths. The best choice depends on the task, your plan's included models and premium request budget.
General guidance: use faster, included models for quick completions and simple questions; use stronger reasoning models for complex refactoring, debugging and agent mode tasks; and compare models on your own codebase for a week. Model line-ups change frequently, so check GitHub's model documentation and changelog for current options and their premium request costs.
Which Copilot model is best for coding?
For complex coding and agent mode, developers often prefer the strongest available reasoning and coding models, with Claude Sonnet-class and recent GPT models popular choices; for quick edits and completions, faster models work well and save premium requests.
Test with real tasks: implement a feature, fix a bug with a failing test, and refactor a module, then compare correctness, diff quality and how much you had to fix. Results vary by language and framework. Provide good context with instruction files and open relevant files, which improves any model's output more than switching models does.
Which Copilot model is best for documentation?
For documentation, such as READMEs, docstrings, API docs and explanations, fast models that write clearly are usually enough, and reasoning-heavy models add little. For documenting complex architecture, a stronger model that reads more context helps.
Give clear instructions: audience, format, tone and examples of good documentation from your project. Ask Copilot to document one module at a time and to flag anything it is unsure about. Always review generated documentation for accuracy, since models can describe behaviour the code does not actually have, which is worse than no documentation.






