Configure a single project with settings.json
configuration
// what it does
A .grok/settings.json in the project root stores project-specific settings — the current "model" and any "mcpServers" — and is loaded automatically when you run grok from that directory. It overrides your global user-settings for that project only.
// shell
$ .grok/settings.json// gotcha
Because it is loaded by working directory, running grok from a subfolder or the wrong repo silently uses different settings. Commit .grok/settings.json to share project config with the team, but never put the apiKey in it.