Description
Description
1. Issue summary
When configuring OpenClaw’s web search provider in the sandbox, switching from Brave Search to Kimi via openclaw configure --section web leaves the old apiKey field at the top level.
Steps to reproduce:
- after connect sandnox
- openclaw configure --section web
in this step choose web search provider: Brave Search
get the config like this:
tools : {
web : {
search : {
enabled : true,
provider : brave ,
apiKey : Brave_API_Key
},
fetch : { enabled : true }
}
}
3. switch web search provider to another one :kimi
found the config like this:
Switched to another web search provider, but the previously configured API key left residual settings, causing the new configuration to fail. the answer like this:
Environment:
- NemoClaw: v0.1.0 (main branch, commit f3430c6)
- OpenShell: 0.0.10
- Colima: 0.10.1
- Docker context: colima
- Node.js: v23.10.0, npm: 11.3.0
- macOS 26.1 (Apple M4, arm64)
- Policy presets applied: pypi, npm
- Inference: NVIDIA Cloud API (nvidia/nemotron-3-super-120b-a12b)
Steps to reproduce
No steps provided.
[NVB# 5998131]
[NVB#5998131]
Description
Description
1. Issue summary
When configuring OpenClaw’s web search provider in the sandbox, switching from Brave Search to Kimi via
openclaw configure --section webleaves the oldapiKeyfield at the top level.Steps to reproduce:
in this step choose web search provider: Brave Search
get the config like this:
3. switch web search provider to another one :kimi
found the config like this:
Switched to another web search provider, but the previously configured API key left residual settings, causing the new configuration to fail. the answer like this:
Environment:
Steps to reproduce
No steps provided.
[NVB# 5998131]
[NVB#5998131]