xAI x_search Migration

Move xAI search settings to plugin-owned config paths

Page scope (xAI migration niche): This page covers only xAI x_search migration details. For general upgrade flow use Upgrading / Migrating. For release history use Releases.

What changed in v2026.4.2

Legacy keys under tools.web.x_search.* moved to plugin-owned keys under plugins.entries.xai.config.xSearch.*. Auth is standardized on plugins.entries.xai.config.webSearch.apiKey (or XAI_API_KEY).

Migration steps

  1. Run openclaw doctor --fix.
  2. Verify old tools.web.x_search.* keys are removed.
  3. Confirm new keys under plugins.entries.xai.config.xSearch.*.
  4. Verify API key source: plugins.entries.xai.config.webSearch.apiKey or XAI_API_KEY.

Example config shape

After migration, xAI search settings belong under the plugin block (exact keys vary by release):

Illustrative
{
  "plugins": {
    "entries": {
      "xai": {
        "config": {
          "webSearch": { "apiKey": "..." },
          "xSearch": { "enabled": true }
        }
      }
    }
  }
}

Run openclaw doctor to see warnings if legacy tools.web.x_search keys remain.

Quick verification

Commands
openclaw doctor --fix
openclaw doctor
openclaw gateway restart

If search fails after migration, review Troubleshooting and xAI provider setup.

Rollback

Keep your previous search provider keys until xAI search is stable for a week. To roll back, restore the prior tools.web.search block from backup and restart the Gateway. Document which cron jobs depended on search so you do not miss silent failures.

Test prompts after migration

Ask the agent for a time-sensitive fact and a site-specific query. If answers lack citations, search config may be wrong—not the chat model. Keep old search keys for one week for rollback.

Related