Grok API for VS Code extensions
Updated:
Grok API connects to VS Code through an extension — Cline, Continue, Roo Code, or Kilo Code. All four call Grok over an OpenAI-compatible API, so one GrokAPI key is enough: Grok 4.5 and Grok 4.6 become available inside the editor, billed per token, with no subscription and at half the official rates.
Before you start
Create an account and issue an API key — the setup below starts from the key in your dashboard.
Create an accountThree values to connect
The same three values work in all four extensions.
| Field | Value | Where it comes from |
|---|---|---|
| Base URL | https://api.llm-gate.tech/v1 | Fixed. |
| API key | sk-lg-… | Issued in your GrokAPI dashboard. |
| Model ID | grok-4.6 | Any current ID: grok-4.5 or grok-4.6. |
Which extension to choose
| Extension | Installs | What it is good at |
|---|---|---|
| Cline | 4,909,518 | The largest install base and the shortest path: the OpenAI Compatible provider is picked in the extension UI, with nothing to edit by hand. The default choice for a first install. |
| Continue | 3,869,096 | The configuration is a config.yaml file, so it can be versioned with the project and give the chat, edit, and apply roles different models. Pick it when a whole team needs identical settings. |
| Roo Code | 1,907,585 | A Cline fork with per-task agent behaviour. Development stopped on May 15 and its own docs point to ZooCode and Cline, so it only makes sense on installs that already run. |
| Kilo Code | 1,399,331 | The endpoint is saved as a named provider you can switch between in one click — handy when Grok sits next to other models or several keys. |