Edit user config.toml in Grok Build

Use ~/.grok/config.toml (or $GROK_HOME/config.toml) for defaults the /settings modal does not cover — models, MCP servers, feature flags, and sampling. Official: Settings, Settings reference.

Prefer the modal for UI toggles

Day-to-day UI, notifications, and in-app options belong in /settings (alias /config). Edit TOML when you need keys the modal does not expose.

Minimal user config

Copy into ~/.grok/config.toml when GROK_HOME is unset:

[models]
default = "grok-build"
web_search = "grok-4.6"

[ui]
compact_mode = false
theme = "auto"
show_thinking_blocks = true

Add MCP servers under [mcp_servers.<name>] — see Add MCP servers in Grok Build. Custom / BYOK models use [model.<id>] tables — see Add a custom model in Grok Build.

Project vs user scopes

Scope	Path	Allowed sections
User	~/.grok/config.toml	Full user config
Project	.grok/config.toml	MCP, plugins, permission rules only
Managed / requirements	managed_config.toml, requirements.toml	Fleet defaults and pins

Confirm what loaded:

grok inspect

Full key list: Settings reference. Env overrides: Set Grok Build environment variables. Fleet pins: Deploy Grok Build for enterprise.

Pitfalls

• Putting [ui] or [models] in project .grok/config.toml does nothing useful — those sections belong in the user file.
• Managed requirements.toml pins win over user TOML and env vars on enterprise fleets.
• Restart the TUI (or start a new session) after editing so the new defaults apply.