Create auth file

printf '{"ollama-windows":{"apiKey":"ollama-local","baseUrl":"http://10.0.2.2:11434/v1"}}' \

~/.openclaw/agents/main/agent/auth-profiles.json chmod 600 ~/.openclaw/agents/main/agent/auth-profiles.json

Start gateway

openclaw gateway start

Send message to Telegram bot

Expected behavior

Bot connects to Ollama and responds to messages.

Actual behavior

Error: No API key found for provider "ollama-windows" Bot does not respond.

What I've tried (all fail in v2026.3.31) ✅ File exists, permissions 600

✅ Valid JSON syntax

✅ Same file works in v2026.3.8

❌ ENV variables OPENCLAW_AUTH_* also ignored

✅ Tried multiple paths

Regression evidence Version Auth works ENV works Ollama connects 2026.3.8 ✅ Yes ✅ Yes ✅ Yes 2026.3.31 ❌ No ❌ No ❌ No Environment OpenClaw: 2026.3.31

Node.js: 22.22.0

OS: Ubuntu 25.04 (VirtualBox guest)

LLM: Ollama on host Windows (http://10.0.2.2:11434)

Workaround Downgraded to v2026.3.8 — works immediately.

Related issues #13835, #18590, #27600, #31627

OpenClaw version

v2026.3.31

Operating system

Ubuntu 25.04 (VirtualBox guest)

Install method

npm global

Model

ollama-windows/glm-4.7-flash:latest

Provider / routing chain

openclaw -> ollama-windows (http://10.0.2.2:11434/v1) -> glm-4.7-flash:latest

Additional provider/model setup details

Provider: ollama-windows Base URL: http://10.0.2.2:11434/v1 Model: glm-4.7-flash:latest Auth: ~/.openclaw/agents/main/agent/auth-profiles.json (same config works in v2026.3.8, fails in v2026.3.31)

Logs, screenshots, and evidence

TL;DR

The most likely fix is to downgrade OpenClaw to version 2026.3.8, as the issue is a regression introduced in version 2026.3.31.

Guidance

• Verify that the auth-profiles.json file exists, has valid JSON syntax, and correct permissions (600) in the ~/.openclaw/agents/main/agent/ directory.
• Check if environment variables OPENCLAW_AUTH_* are set and ignored in version 2026.3.31, as this might be related to the issue.
• Try downgrading to version 2026.3.8 using npm install -g [email protected] as a temporary workaround.
• Review related issues (#13835, #18590, #27600, #31627) for potential clues or fixes.

Example

No code snippet is provided, as the issue seems to be related to a configuration or version problem rather than a code issue.

Notes

The issue is highly reproducible and affects all users of OpenClaw version 2026.3.31 who rely on auth-profiles.json for LLM authentication. The last known good version is 2026.3.8, and the first known bad version is 2026.3.31.

Recommendation

Apply the workaround by downgrading to version 2026.3.8 using npm install -g [email protected], as this is the only known solution that resolves the issue.