openclaw - 💡(How to fix) Fix Beta blocker: ollama-provider - plugin appends /v1 to baseUrl in models.json overriding correct config [1 participants]

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

Yes

Summary

The bundled Ollama provider plugin writes baseUrl: http://host:11434/v1 to models.json regardless of the correct baseUrl: http://host:11434 specified in openclaw.json, silently breaking native Ollama tool calling per the documentation's own warning.

Steps to reproduce

1. Configure openclaw.json with remote Ollama: models.providers.ollama.baseUrl: "http://192.168.40.22:11434" models.providers.ollama.api: "ollama"
2. Start OpenClaw gateway
3. Inspect ~/.openclaw/agents/main/agent/models.json
4. Observe /v1 appended to baseUrl by the plugin

Expected behavior

Per docs.openclaw.ai/providers/ollama: "Do not use the /v1 OpenAI-compatible URL with OpenClaw. This breaks tool calling and models may output raw tool JSON as plain text. Use the native Ollama API URL instead: baseUrl: http://host:11434 (no /v1)." The plugin should write the baseUrl exactly as specified in openclaw.json.

Actual behavior

openclaw.json specifies: "baseUrl": "http://192.168.40.22:11434"

Plugin writes to models.json: "baseUrl": "http://192.168.40.22:11434/v1"

Confirmed via: grep "baseUrl" ~/.openclaw/agents/main/agent/models.json

"baseUrl": "http://192.168.40.22:11434/v1"

openclaw models status --json confirms models.json is the active source: "source": "models.json: ~/.openclaw/agents/main/agent/models.json"

OpenClaw version

2026.4.22

Operating system

Ubuntu 24.04 (running as Unraid VM)

Install method

npm global

Model

ollama/qwen3.5:27b

Provider / routing chain

openclaw -> ollama (remote host 192.168.40.22:11434)

Additional provider/model setup details

Plugin: @openclaw/ollama-provider v2026.4.22 (stock bundled) Remote Ollama at http://192.168.40.22:11434 openclaw.json models.providers.ollama.api: "ollama" (native, not openai-completions) Workaround: sed -i 's|:11434/v1|:11434|g' ~/.openclaw/agents/main/agent/models.json Workaround is temporary — plugin regenerates /v1 on every gateway restart

Logs, screenshots, and evidence

Impact and severity

Affected: All users with remote Ollama using native api: "ollama" mode Severity: High — silently breaks native tool calling for all remote Ollama users Frequency: 100% reproducible — happens on every gateway start Consequence: Tool calls may fail or return raw JSON as plain text; user has no indication this is happening

Additional information

The /v1 path routes through OpenAI-compatible mode instead of native Ollama API. Per docs, this breaks tool calling — models output raw tool JSON as plain text. The plugin owns models.json (marked "plugin-owned") so manual edits are overwritten. Fix must be in the plugin's baseUrl generation logic.