Environment
- OpenClaw version: 2026.4.27 (also tested after update to 2026.5.5)
- OS: WSL2 (Ubuntu)
- Model: grok-4.3 (correct ID from xAI console)
Problem
The xai provider is not registering the x_search and code_execution tools, even after:
- Correcting the model list in
models.json (removed invalid grok-4.3-fast)
- Full gateway restart (
systemctl --user restart openclaw-gateway)
- Using a valid model (
grok-4.3) that exists in the xAI account
After restart, web_search still falls back to SearXNG instead of using the native xai tool.
Logs observed
chokidar@^5.0.0 installs correctly on every startup
- No more
model_not_found errors for grok-4.3
- No errors related to xai provider failing to load
- Gateway reports normal startup, but x_search tool is never available
Expected behavior
When using a valid Grok model (grok-4.3), the xai provider should register x_search and code_execution tools.
Workaround
Currently using SearXNG + web_fetch as fallback.
Additional info
- API key is correctly configured
- Other providers (deepseek, codex) work normally
Can someone confirm if this is a known limitation or if there's additional configuration needed to enable xai tools?
Environment
Problem
The xai provider is not registering the
x_searchandcode_executiontools, even after:models.json(removed invalidgrok-4.3-fast)systemctl --user restart openclaw-gateway)grok-4.3) that exists in the xAI accountAfter restart,
web_searchstill falls back to SearXNG instead of using the native xai tool.Logs observed
chokidar@^5.0.0installs correctly on every startupmodel_not_founderrors for grok-4.3Expected behavior
When using a valid Grok model (grok-4.3), the xai provider should register
x_searchandcode_executiontools.Workaround
Currently using SearXNG + web_fetch as fallback.
Additional info
Can someone confirm if this is a known limitation or if there's additional configuration needed to enable xai tools?