and remote `code_execution`.

If you store an xAI key under `plugins.entries.xai.config.webSearch.apiKey`,

the bundled xAI model provider reuses that key as a fallback too.

Set `plugins.entries.xai.config.webSearch.baseUrl` to route Grok `web_search`

and, by default, `x_search` through an operator xAI Responses proxy.

`code_execution` tuning lives under `plugins.entries.xai.config.codeExecution`.

</Note>

| ------------------ | ------- | ------------------ | ------------------------------------ |

| `enabled` | boolean | — | Enable or disable x_search |

| `model` | string | `grok-4-1-fast` | Model used for x_search requests |

| `baseUrl` | string | — | xAI Responses base URL override |

| `inlineCitations` | boolean | — | Include inline citations in results |

| `maxTurns` | number | — | Maximum conversation turns |

| `timeoutSeconds` | number | — | Request timeout in seconds |

xSearch: {

enabled: true,

model: "grok-4-1-fast",

baseUrl: "https://api.x.ai/v1",

inlineCitations: true,

},

},

- `web_search`, `x_search`, and `code_execution` are exposed as OpenClaw

tools. OpenClaw enables the specific xAI built-in it needs inside each tool

request instead of attaching all native tools to every chat turn.

- Grok `web_search` reads `plugins.entries.xai.config.webSearch.baseUrl`.

`x_search` reads `plugins.entries.xai.config.xSearch.baseUrl`, then

falls back to the Grok web-search base URL.

- `x_search` and `code_execution` are owned by the bundled xAI plugin rather

than hardcoded into the core model runtime.

- `code_execution` is remote xAI sandbox execution, not local