Switching to Grok Official clears config.toml: Grok Build

Quick fix

Upgrade to 4.0. The maintainer said the new version preserves other settings in config.toml.

Symptom

Error outputCopy

切换到 Grok Official，原有 `config.toml` 内容被清空。

English translation

After switching to Grok Official, the existing `config.toml` contents were cleared.

Cause

In CC Switch 3.20.4, the Grok Official form hid the configuration area, but the switching logic still wrote the empty configuration stored in the entry (`{"config":""}`) to `~/.grok/config.toml`, overwriting its existing contents. The maintainer said version 4.0 rewrote configuration writes: switching to the Grok Build provider changes only `models.default` and the model table written by CC Switch; switching to Grok Official removes the previously written third-party model table and no longer overwrites the entire file with an empty configuration.

Fix

1. 1

   Upgrade to 4.0. The maintainer said the new version preserves other settings in config.toml; the reply did not say whether this fix was verified in later versions.

Affected Versions

ToolGrok Build

Version3.20.4（受影响版本；维护者称 4.0 重写了配置写入方式）

PlatformsmacOS

Source Issues

This page is distilled from 1 real issues

• #7724[Bug] Grok Official 没有配置编辑入口，切换后清空 config.toml

FAQ

(No FAQ yet)

Related problems

After switching, opening codex still uses the old account — CodexAfter switching OAuth accounts, fully restart the Codex background service. For CLI, run `codex app-server daemon stop`, then reopen Codex.1 issues mergedSelect Model Menu Still Shows Pre-Switch Model List - CodexClose existing Codex sessions, run `codex app-server daemon restart`, and upgrade CC Switch to v4.0.7 or later for detection and restart prompts.3 issues mergedmcode session usage import: model stays unknown, latency stays 0, and pricing failsNo confirmed user-side fix is available; update the importer to backfill model and latency from telemetry or session data.1 issues merged