Issue: Ollama not working in cron agentTurn sessions

[brazen steeple]

Setup:

OpenClaw 2026.3.23-2
Ollama running locally with qwen2.5:7b
Works in main session, fails in cron isolated sessions

Config tried:

Added auth.profiles.ollama:default
Set OLLAMA_API_KEY env var
Tried "qwen" alias and "ollama/qwen2.5:7b" full path

Result:
Cron always silently falls back to claude-sonnet-4-5 instead of using Ollama.
Question:
Do isolated sessions need different Ollama config than main session?

[agile bay]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[light bolt]

No — isolated cron sessions should not need a separate Ollama config.

This looks like the known isolated-cron bug: cron said the model override was applied, but the actual run used the default Claude model instead. That exact issue was closed by PR #71340, merged Apr 25, 2026, which fixed stale model/auth/runtime state leaking into fresh isolated cron runs. (github.com)

For your version (2026.3.23-2), I’d update to a build containing that PR, then verify:

openclaw models list --provider ollama
openclaw cron show <job-id>
openclaw cron runs --id <job-id> --limit 20
openclaw logs --follow

Expected config shape:

• local Ollama: OLLAMA_API_KEY=ollama-local
• model ref: exact discovered model, e.g. ollama/qwen2.5:7b
• no /v1 in baseUrl; use native Ollama URL if explicit. (docs.openclaw.ai)