Grok Installation and Setup

To use Grok through Passion8, you need a Passion8 API key, an enabled model ID and https://passion8.cc/v1. Use Cline for VS Code; official Grok Build and existing Codex users can follow the configuration-file guides on this page. An xAI account or official OAuth login is not required for this gateway setup.

#Choose your workflow

Cline is a third-party editor client. The verified xAI official coding entry is Grok Build with TUI, headless and ACP. A marketplace extension sharing the Grok name does not establish xAI authorship.

There are two ways to connect Grok models through Passion8:

Both use https://passion8.cc/v1. Examples use grok-4.7; select an ID actually available in the console model catalog.

#Method 1: official Grok Build CLI

This guide preserves the original Grok Build v0.2.93 integration steps and updates them against official installation, custom-model and Grok 4.7 documentation checked on 2026-10-11. Check your version with grok --version. If fields change, use grok inspect to see discovered configuration, model and authentication sources.

#Install Grok CLI

curl -fsSL https://x.ai/cli/install.sh | bash

irm https://x.ai/cli/install.ps1 | iex

Open a new terminal and check the command:

which grok
grok --version

On macOS / Linux / WSL, which grok usually points to ~/.local/bin/grok, linked to ~/.grok/bin/grok. On Windows use Get-Command grok instead of which.

echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc
source ~/.zshrc

Update with:

grok update

#Prepare the connection

Check your executable and version:

which grok
grok --version

Paths under ~/.local/bin/grok or ~/.grok/bin/grok are typical for Grok Build; check the version and installation source as well.

#Recommended configuration

Store the key in api_key:

[model.passion8-grok]
model = "grok-4.7"
base_url = "https://passion8.cc/v1"
name = "grok-4.7"
context_window = 500000
api_key = "sk-YOUR_PASSION8_API_KEY"

[models]
default = "passion8-grok"

#Use an environment variable instead

To keep the key out of config.toml, set env_key to the variable's name:

[model.passion8-grok]
model = "grok-4.7"
base_url = "https://passion8.cc/v1"
name = "grok-4.7"
context_window = 500000
env_key = "PASSION8_API_KEY"

[models]
default = "passion8-grok"

Then configure your shell:

echo 'export PASSION8_API_KEY="sk-YOUR_PASSION8_API_KEY"' >> ~/.zshrc
source ~/.zshrc

#Test the gateway

Check the key, endpoint and model availability with curl:

curl -s https://passion8.cc/v1/models \
  -H "Authorization: Bearer $PASSION8_API_KEY"

Then make a short request:

curl -s https://passion8.cc/v1/chat/completions \
  -H "Authorization: Bearer $PASSION8_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "grok-4.7",
    "messages": [{"role": "user", "content": "reply with OK"}],
    "max_tokens": 10
  }'

If curl works but grok opens browser OAuth, inspect ~/.grok/config.toml.

#Verify Grok CLI

grok -p "Reply with exactly: RELAY_OK"

After receiving the answer, check the matching timestamp, model and usage in Passion8. The answer alone does not prove which endpoint handled the request.

#Common errors

#Authentication precedence

The original version's troubleshooting record observed:

model.api_key > model.env_key > current login session > XAI_API_KEY

If api_key is missing and env_key is incorrect, the client may fall back to a login session or open browser OAuth. Recheck behavior after client upgrades.

#Common commands

grok                         # Interactive TUI
grok "Explain this project"  # TUI with an initial instruction
grok -p "Explain auth"       # Run once, print and exit
grok logout                  # Sign out to remove an old session
grok inspect                 # Inspect configuration sources
grok --version               # Show version

#Method 2: use Grok through Codex CLI / App

You can retain the Codex workflow and select Passion8's enabled Grok model. The client remains Codex while requests target Grok.

#Configure through CC-Switch

Select the GPT / Codex provider area, add a provider and enter:

Check that CC-Switch manages the Codex files:

Manual and CC-Switch configurations should use the same verified fields. No machine-specific model_catalog_json path is needed here.

#auth.json

{
  "OPENAI_API_KEY": "sk-YOUR_PASSION8_API_KEY"
}

#config.toml

model_provider = "custom"
model = "grok-4.7"
model_reasoning_effort = "high"
model_context_window = 500000
model_auto_compact_token_limit = 475000

[model_providers]
[model_providers.custom]
name = "custom"
wire_api = "responses"
requires_openai_auth = true
base_url = "https://passion8.cc/v1"

#Manual configuration

Without CC-Switch, write the same auth.json and config.toml files with the same verified budget.

~/.codex/auth.json
~/.codex/config.toml

codex "Reply with: GROK_RELAY_OK"

$env:USERPROFILE\.codex\auth.json
$env:USERPROFILE\.codex\config.toml

codex "Reply with: GROK_RELAY_OK"

Codex App uses the same configuration. After saving the provider, reopen the app or start a new session and test.

#Accounts, charges and troubleshooting

Create an account and token through the quickstart. See billing; official client subscriptions and Passion8 API balances are separate. For authentication, endpoint and model errors, see the FAQ. Actual models and rates follow the console.

#Verified sources

Checked 2026-10-11. The official catalog contains grok-4.7, with low, medium, high and xhigh reasoning efforts. Gateway access follows the console.

• Grok Build installation and custom models
• Grok 4.7 fields and context

The current overview confirms model, base_url, name, env_key and [models].default. The direct api_key setting, authentication order and 200k display default come from the original version's integration record; verify them with grok inspect after upgrades.