Which IDEs support Grok 4.6 in Copilot?

Visual Studio Code, Visual Studio, the Copilot CLI, the GitHub Copilot cloud agent, the GitHub Copilot app, JetBrains, Xcode and Eclipse.

How is Grok 4.6 billed in Copilot?

At provider list pricing under usage-based billing, which is a different cost model from the request allowances included with Copilot plans. Worth understanding before enabling it across a large organisation.

Which Copilot plans include Grok 4.6?

Copilot Pro, Pro+, Max, Business and Enterprise. The distinction that matters is not availability but the administrator policy gate on the two organisational plans.

Grok 4.6 Lands in Copilot, Switched Off

A control panel of toggle switches all flipped up and lit, with one switched off and dark — ToolsAugust 14, 2026·2 min read·By the Automation Squad Research
Grok 4.6 Lands in Copilot, Switched Off
Half the people who go looking for it will conclude it hasn't shipped. It has. Someone just needs to flip a switch.

By Robert MacKelfresh

Founder, Automation Squad · August 14, 2026

The short answer

Grok 4.6 is available in GitHub Copilot across Pro, Pro+, Max, Business and Enterprise, in eight IDEs including VS Code, JetBrains and Xcode. For Business and Enterprise plans an administrator must enable the Grok 4.6 policy in Copilot settings first — GitHub states the policy is off by default. It bills at provider list pricing under usage-based billing.

Admin checklist

Turning Grok 4.6 on for your organisation

Short, because the task is short. The value here is knowing the switch exists — most people will assume the rollout simply hasn't reached them.

Work out whether you are the person who can do this
On Copilot Business and Copilot Enterprise, only a plan administrator can enable the policy. On Pro, Pro+ and Max there is no policy gate — if you cannot see the model there, it is the gradual rollout, not a setting.
Open Copilot settings and find the Grok 4.6 policy
GitHub's wording is unambiguous: administrators must enable the Grok 4.6 policy in Copilot settings, and the policy is off by default. Nobody gets it by waiting.
Understand the billing before you enable it, not after
Grok 4.6 bills at provider list pricing under usage-based billing. That is a different cost model to the included allowances your developers are used to, so decide whether you want it on for everyone or a subset.
Tell your developers it is available and which IDEs support it
VS Code, Visual Studio, Copilot CLI, the Copilot cloud agent, the Copilot app, JetBrains, Xcode and Eclipse. A model nobody knows was enabled produces no benefit and still produces invoices.
If it still is not showing, wait before raising a ticket
GitHub says the rollout is gradual and to check back if the option is not immediately visible. Confirm the policy is on, then give it time.

Plan	Who enables it	Default state
Copilot Pro	No policy gate	Available (gradual rollout)
Copilot Pro+	No policy gate	Available (gradual rollout)
Copilot Max	No policy gate	Available (gradual rollout)
Copilot Business	Plan administrator	OFF by default
Copilot Enterprise	Plan administrator	OFF by default

Take it with you

GROK 4.6 IN GITHUB COPILOT — admin checklist
Source: https://automationsquad.com/news/grok-4-6-github-copilot/

THE ONE THING TO KNOW
On Copilot Business and Enterprise the Grok 4.6 policy is OFF BY DEFAULT.
An administrator must enable it in Copilot settings. Waiting does nothing.

BY PLAN
  Pro / Pro+ / Max ....... no policy gate, gradual rollout
  Business / Enterprise .. admin must enable, OFF by default

CHECKLIST
[ ] Confirm I am a plan administrator (Business/Enterprise only)
[ ] Copilot settings > enable the Grok 4.6 policy
[ ] Check the cost model: provider list pricing, usage-based billing
    — this is NOT the included allowance developers are used to
[ ] Decide: everyone, or a subset?
[ ] Tell developers it is on, and which IDEs support it:
    VS Code · Visual Studio · Copilot CLI · Copilot cloud agent
    Copilot app · JetBrains · Xcode · Eclipse
[ ] If still not visible after enabling — rollout is gradual, wait

GitHub announced on August 14, 2026 that xAI's Grok 4.6 is available in GitHub Copilot. It can be selected across Copilot Pro, Pro+, Max, Business and Enterprise.

The facts: the model is selectable in Visual Studio Code, Visual Studio, the Copilot CLI, the Copilot cloud agent, the Copilot app, JetBrains, Xcode and Eclipse. It bills at provider list pricing under usage-based billing rather than against Copilot's included allowances. The detail that decides whether anyone in your organisation actually sees it is in GitHub's own wording: "Copilot Enterprise and Copilot Business plan administrators must enable the Grok 4.6 policy in Copilot settings. The policy is off by default." GitHub also notes the rollout is gradual and suggests checking back if the option does not appear immediately.

Automation Squad's take: model availability announcements are usually not worth your attention, and this one is, for a reason that has nothing to do with the model. There is now a standing pattern where a vendor ships something, the announcement says "available today", and for the largest customers it is available in the sense that a switch exists. The gap between those two meanings is where a lot of quiet frustration lives — developers conclude the rollout is slow, administrators never learn there was anything to do, and the feature sits dark for months. It costs an administrator two minutes to check. The billing note is the other half: usage-based pricing on a model developers can select freely is a cost surface worth deciding about deliberately rather than discovering later.

Run this now: if you administer Copilot Business or Enterprise, open Copilot settings and look for the Grok 4.6 policy. Decide whether you want it on for everyone or a subset, enable it, and then — the step people skip — tell your developers it exists and which IDEs support it. If you are a developer rather than an admin and the model is not there, check which plan you are on before assuming it has not shipped. On Pro, Pro+ and Max there is no gate and it is a rollout question; on Business and Enterprise it is a question for whoever owns your settings.

Questions people are asking

Why can't I see Grok 4.6 in GitHub Copilot?: If you are on Copilot Business or Enterprise, the most likely reason is that nobody has enabled it. GitHub states that plan administrators must enable the Grok 4.6 policy in Copilot settings and that the policy is off by default. On Pro, Pro+ and Max there is no policy gate, so an absence there is the gradual rollout.
Which IDEs support Grok 4.6 in Copilot?: Visual Studio Code, Visual Studio, the Copilot CLI, the GitHub Copilot cloud agent, the GitHub Copilot app, JetBrains, Xcode and Eclipse.
How is Grok 4.6 billed in Copilot?: At provider list pricing under usage-based billing, which is a different cost model from the request allowances included with Copilot plans. Worth understanding before enabling it across a large organisation.
Which Copilot plans include Grok 4.6?: Copilot Pro, Pro+, Max, Business and Enterprise. The distinction that matters is not availability but the administrator policy gate on the two organisational plans.