docs: clarify xai oauth coverage · openclaw/openclaw@8bc927b
steipete
·
2026-05-16
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -38,9 +38,9 @@ OpenClaw ships a bundled `xai` provider plugin for Grok models.
|
38 | 38 | OpenClaw uses the xAI Responses API as the bundled xAI transport. The same |
39 | 39 | credential from `openclaw onboard --auth-choice xai-api-key` or |
40 | 40 | `openclaw onboard --auth-choice xai-oauth` can also power first-class |
41 | | -`x_search`, remote `code_execution`, xAI media generation, speech, and |
42 | | -transcription. `XAI_API_KEY` or plugin web-search config can power |
43 | | -Grok-backed `web_search` too. |
| 41 | +`x_search`, remote `code_execution`, and xAI image/video generation. |
| 42 | +Speech and transcription currently require `XAI_API_KEY` or provider config. |
| 43 | +`XAI_API_KEY` or plugin web-search config can power Grok-backed `web_search` too. |
44 | 44 | If you store an xAI key under `plugins.entries.xai.config.webSearch.apiKey`, |
45 | 45 | the bundled xAI model provider reuses that key as a fallback too. |
46 | 46 | Set `plugins.entries.xai.config.webSearch.baseUrl` to route Grok `web_search` |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
