Open settings in Grok Build

/settings (alias /config) opens the settings modal for UI, notifications, and other in-app options. Changes persist under ~/.grok/config.toml (or $GROK_HOME/config.toml). Official: Modes and Commands, Settings.

Open the modal

1. Start or resume a Build session.
2. Run either form:

/settings
/config

3. Adjust the option you need. Prefer the modal for day-to-day UI toggles; edit TOML when you need models, MCP servers, or fleet pins.

Where settings live

Scope	Path	Typical use
Environment	GROK_* variables	Session / CI overrides
User	~/.grok/config.toml	Personal defaults
Project	.grok/config.toml	Repo MCP, plugins, permission rules only
Managed	~/.grok/managed_config.toml, /etc/grok/managed_config.toml	Enterprise-served defaults
Requirements	~/.grok/requirements.toml, /etc/grok/requirements.toml	Policy pins

Confirm what loaded for this directory:

grok inspect

Full key list: Settings reference. Env-only how-to: Set Grok Build environment variables. Discovery dump: Inspect what Grok Build loads.

Related slash toggles

Some UI keys also have dedicated commands (/theme, /compact-mode, /vim-mode, /timestamps, /terminal-setup). The settings modal and those commands write the same user config.

Pitfalls

• Project .grok/config.toml does not accept full user UI sections — only MCP, plugins, and permission rules.
• Managed requirements.toml pins win over user config and env vars on enterprise fleets — see Deploy Grok Build for enterprise.