#Bug: Only showing 1 or 2 Ollama models on Dashboard

1 messages · Page 1 of 1 (latest)

limber glen
#

I am running claw version 2026.4.15. I need help figuring out why sometimes I see a huge list of models to select from and then other times I only see two Ollama models to choose from.

I think this is a bug or something. Does anyone have a solution for this?? It’s frustrating to only have one or two models to go between. Thank you 🙏

smoky mortarBOT
coral bobcatBOT
#

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

smoky mortarBOT
proud daggerBOT
#

This usually is not random, and it’s often not a dashboard bug.

What’s happening is there are effectively two model views:

  1. Full catalog = the huge list
  2. Allowed/configured models = the smaller picker

A big clue from the docs/code is:

  • openclaw models list shows configured models by default
  • openclaw models list --all shows the full catalog
  • The dashboard picker uses models.list, and if agents.defaults.models is set, it gets filtered to that allowlist

So if your config currently only allows 2 Ollama models, the dashboard will only show those 2.

There’s also a second Ollama-specific gotcha:

  • If you explicitly set models.providers.ollama, auto-discovery is disabled
#
  • Then OpenClaw will only show the Ollama models you manually defined there

Can you paste these 4 outputs?

openclaw models list
openclaw models list --all
openclaw config get agents.defaults.models --json
openclaw config get models.providers.ollama --json

If you’re running the gateway as a service, also paste:

openclaw status --all
limber glen
proud daggerBOT
#

Yep, but the key is agents.defaults.models (plural defaults).

Also, small but important distinction:

  • agents.defaults.model = your selected default model + fallbacks
  • agents.defaults.models = the allowed model catalog / picker list

So yes, agents.defaults.models can contain multiple models. Example:

{
  agents: {
    defaults: {
      model: {
        primary: "openai/gpt-5.4",
        fallbacks: ["anthropic/claude-sonnet-4-6", "ollama/gemma4"],
# 
      },
      models: {
        "openai/gpt-5.4": { alias: "GPT-5.4" },
        "anthropic/claude-sonnet-4-6": { alias: "Sonnet" },
        "ollama/gemma4": { alias: "Gemma 4" },
        "ollama/qwen3:14b": { alias: "Qwen 3 14B" },
      },
    },
  },
}

If you set agents.defaults.models, the dashboard picker is usually limited to those entries.

So if you want:

#
  • more choices → add more models there
  • the huge full picker → remove agents.defaults.models entirely

Docs:

If you want, paste your current agents.defaults.models block and I’ll help clean it up.

limber glen
# proud dagger - **more choices** → add more models there - **the huge full picker** → remove `...

This is what it says:
openclaw config get agents.defaults.models --json
{
"ollama/gemma4:31b-cloud": {}
}

I really want to have access to all of my available Ollama models which are:
kimi-k2.6:cloud a90cd0d1590c - 51 minutes ago
qwen3.5:397b-cloud a7bf6f7891c3 - 8 days ago
ministral-3:latest 1922accd5827 6.0 GB 9 days ago
gemma4:31b-cloud c382fbfbc73b - 9 days ago
kimi-k2.5:cloud 6d1c3246c608 - 9 days ago

proud daggerBOT
#

Yep, that’s the cause.

Right now you’ve explicitly allowlisted only one model:

{
  "ollama/gemma4:31b-cloud": {}
}

So the dashboard picker is doing exactly that, it’s only showing the allowlisted model(s).

If you want all 5 of your Ollama models, make agents.defaults.models look more like this:

{
# 
  agents: {
    defaults: {
      models: {
        "ollama/kimi-k2.6:cloud": {},
        "ollama/qwen3.5:397b-cloud": {},
        "ollama/ministral-3:latest": {},
        "ollama/gemma4:31b-cloud": {},
        "ollama/kimi-k2.5:cloud": {}
      }
    }
  }
}

A couple gotchas:

#
  • use the exact Ollama model id
  • keep the ollama/ prefix in OpenClaw
  • tags matter, so ministral-3:latest is different from just ministral-3

If you want the picker to show the huge full catalog again, remove agents.defaults.models entirely.

If you want, I can help you turn that into the exact openclaw config command(s) next.

limber glen
proud daggerBOT
#

Yep, you can do this from the CLI without manually editing the file.

Run these:

openclaw config set 'agents.defaults.models[ollama/kimi-k2.6:cloud]' "{}" --strict-json
openclaw config set 'agents.defaults.models[ollama/qwen3.5:397b-cloud]' "{}" --strict-json
openclaw config set 'agents.defaults.models[ollama/ministral-3:latest]' "{}" --strict-json
openclaw config set 'agents.defaults.models[ollama/gemma4:31b-cloud]' "{}" --strict-json
openclaw config set 'agents.defaults.models[ollama/kimi-k2.5:cloud]' "{}" --strict-json

Then verify:

openclaw config get agents.defaults.models --json
#

You should end up with those 5 Ollama models in the allowlist, which means the picker should show those Ollama models instead of the giant full catalog.

After that:

  • refresh the dashboard tab
  • if it still looks stale, do:
    openclaw gateway restart

One important gotcha: once agents.defaults.models is set, new Ollama models will not auto-appear there. If you pull another model later, you’ll need to add another entry the same way.

Docs:

If you want, I can also give you the one command to set your default model to one of those 5.

limber glen
proud daggerBOT
#

Heck yes, glad that did it! 🎉🦐

If this fixed it, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow can index it for the next person who hits the same weird model-picker behavior.

And if the picker gets weird again later, the first thing to check is still:

openclaw config get agents.defaults.models --json

Happy to help! 🦐