Summary
Running openclaw config set models.providers.ollama.apiKey "ollama-local" fails config validation. The validator errors on a missing required field models.providers.ollama.baseUrl (“expected string, received undefined”), even though the command is only setting apiKey.

This blocks configuring Ollama via CLI unless baseUrl is set first (or the CLI auto-populates it).

Steps to reproduce
Install/update OpenClaw to 2026.2.3-1 (d84eb46).
Run:
openclaw config set models.providers.ollama.apiKey "ollama-local"
Observe validation failure for models.providers.ollama.baseUrl.
Expected behavior
openclaw config set models.providers.ollama.apiKey "ollama-local" should succeed, either by:

allowing partial provider config updates without requiring baseUrl immediately, or
auto-defaulting models.providers.ollama.baseUrl (e.g. http://localhost:11434) when provider is ollama, or
providing a clearer error that baseUrl must be set first and suggesting the exact command.
Actual behavior
Command fails with:

🦞 OpenClaw 2026.2.3-1 (d84eb46) — Automation with claws: minimal fuss, maximal pinch.

Error: Config validation failed: models.providers.ollama.baseUrl: Invalid input: expected string, received undefined
Environment
OpenClaw version: 2026.2.3-1 (d84eb46)
OS: Linux (kernel 6.14.0-1017-azure, x64)
Install method: (please fill: pnpm / npm global / npx / docker / other)
Logs or screenshots
Paste the command + output (redacted), e.g.:

openclaw config set models.providers.ollama.apiKey "ollama-local"

-> Error: Config validation failed: models.providers.ollama.baseUrl: Invalid input: expected string, received undefined

but configuring manually using webui works perfects.