Grok Build
~/.grok/config.toml inside a marked managed block, so every model in your Prism catalog becomes selectable in Grok Build with its real context window and reasoning support.Last updated Reviewed against Prism v0.3.26
One-click setup
Open the Agents tab
Agents. Grok Build is detected when ~/.grok/config.toml exists or the grok binary is on PATH.Click Setup
config.toml.prism-backup of your original content.Pick a model in Grok Build
What Prism writes
# >>> prism-managed >>> [model.prism-glm-5-1-cloud] model = "glm-5.1:cloud" base_url = "http://127.0.0.1:11434/v1" name = "GLM 5.1 (Ollama Cloud)" api_key = "prism" api_backend = "chat_completions" context_window = 128000 supports_backend_search = false supports_reasoning_effort = true # <<< prism-managed <<<
Fields Prism derives from your catalog
| Key | Value |
|---|---|
| model | The model's route key — the name Grok Build sends to Prism. |
| base_url | The Prism proxy's OpenAI-compatible base. |
| api_key | The fixed Prism token. |
| api_backend | responses for Codex OAuth models, chat_completions for everything else. |
| context_window | The model's configured context length, defaulting to 128000. |
| supports_reasoning_effort | Written only when the model supports reasoning. |
| supports_backend_search | Always false, so search goes through Prism instead. |
Why there is a managed block
The block is tagged with begin and end markers. On each sync Prism removes the old block and writes a new one, so syncing many times never duplicates sections or damages the rest of your file. A TOML section header correctly terminates the previous section, which is why appending is safe.
[models] default, so which model Grok Build starts with stays entirely your choice.Search behaviour
With supports_backend_search = false, Grok Build does not use its own backend search. Agent search tool calls reach Prism, where they are answered locally through your configured search provider. See Web Search.
Add MCP servers
Grok Build keeps MCP servers in the same TOML file, so Prism uses a dedicated TOML writer for it rather than the JSON writers used elsewhere. Enabling Grok Build in the MCP tab adds the gateway table to ~/.grok/config.toml. See MCP Gateway.