Bug type
Regression (worked before, now fails)
Summary
After upgrading from v2026.3.24 to v2026.3.28, any explicitly configured provider with api ollama fails immediately with:
Error: No API provider registered for api: ollama
This worked perfectly on v2026.3.24.
Environment
- OpenClaw: 2026.3.28 (f9b1079)
- OS: Windows 10 (x64) build 26200
- Node: v22.16.0
- Install method: npm global
- Previous working version: 2026.3.24
Steps to Reproduce
- Configure an explicit Ollama provider in openclaw.json with api set to ollama
- Select the model (e.g. ollama-cloud-native/qwen35-cloud-native)
- Send any message
Expected Behavior
Model responds normally, as it did on v2026.3.24.
Actual Behavior
Immediate failure: No API provider registered for api: ollama
Root Cause Analysis
register-builtins.js registers 10 API providers (anthropic-messages, openai-completions, mistral-conversations, openai-responses, azure-openai-responses, openai-codex-responses, google-generative-ai, google-gemini-cli, google-vertex, bedrock-converse-stream). ollama is NOT among them.
The changelog entry 'Models/plugins: move Ollama, vLLM, and SGLang onto the provider-plugin architecture' moved Ollama registration into the plugin system. However, the plugin-based registration does not cover all code paths. When a user explicitly configures api ollama in models.providers, resolveApiProvider(ollama) in stream.js fails because the plugin has not registered it in the global API registry.
A related changelog entry confirms this gap: 'Ollama/compaction and summarization: register custom api ollama handling [...] so native Ollama models no longer fail with No API provider registered for api: ollama outside the main run loop.' This fix addresses compaction/summarization paths but does not cover the primary chat/streaming path for explicitly configured providers.
Workaround
Downgrade to v2026.3.24.
Additional Notes
- The proxy at 127.0.0.1:11436 responds correctly to /health and /api/tags
- Multiple models affected (qwen35-cloud-native, nem3-super-cloud, deepseek-v32-cloud, kimi-k2.5:cloud, minimax-m2.7:cloud)
- All configured with api ollama
- Issue is purely on OpenClaw side - Ollama API provider not registered in global API registry for explicit provider configs
Bug type
Regression (worked before, now fails)
Summary
After upgrading from v2026.3.24 to v2026.3.28, any explicitly configured provider with api ollama fails immediately with:
Error: No API provider registered for api: ollama
This worked perfectly on v2026.3.24.
Environment
Steps to Reproduce
Expected Behavior
Model responds normally, as it did on v2026.3.24.
Actual Behavior
Immediate failure: No API provider registered for api: ollama
Root Cause Analysis
register-builtins.js registers 10 API providers (anthropic-messages, openai-completions, mistral-conversations, openai-responses, azure-openai-responses, openai-codex-responses, google-generative-ai, google-gemini-cli, google-vertex, bedrock-converse-stream). ollama is NOT among them.
The changelog entry 'Models/plugins: move Ollama, vLLM, and SGLang onto the provider-plugin architecture' moved Ollama registration into the plugin system. However, the plugin-based registration does not cover all code paths. When a user explicitly configures api ollama in models.providers, resolveApiProvider(ollama) in stream.js fails because the plugin has not registered it in the global API registry.
A related changelog entry confirms this gap: 'Ollama/compaction and summarization: register custom api ollama handling [...] so native Ollama models no longer fail with No API provider registered for api: ollama outside the main run loop.' This fix addresses compaction/summarization paths but does not cover the primary chat/streaming path for explicitly configured providers.
Workaround
Downgrade to v2026.3.24.
Additional Notes