#List available models of a provider

1 messages · Page 1 of 1 (latest)

fleet oar
#

How can I list all available strings for models from a configured llm provider?

fluid flameBOT
minor geyserBOT
#

Use:

openclaw models list --provider <provider> --all --plain

Examples:

openclaw models list --provider anthropic --all --plain
openclaw models list --provider openai --all --plain

A couple notes:

  • openclaw models list by itself shows configured models by default
  • add --all for the full catalog
fleet oar
#

but these are hardcoded values by openclaw or live fetched from providers? anthropic just released opus 4.7 and I don't see it in the list

minor geyserBOT
#

Mixed, not always live-fetched.

openclaw models list comes from OpenClaw’s model catalog layer, and provider plugins can augment/suppress entries. So for some providers it feels dynamic, but it is not guaranteed to be a raw live dump from the provider API every time.

For Anthropic, if you do not see the new Opus release, the two most likely reasons are:

  1. you ran models list without --all, so you only saw configured rows
  2. your OpenClaw version is a bit behind the catalog/plugin update

Try:

openclaw models list --provider anthropic --all --plain
openclaw --version

Current OpenClaw source already has Anthropic Opus 4.7 support wired in, so if you are on an older build that would explain it.

fleet oar
#

just updated to OpenClaw 2026.4.14, still no 4.7 in the list

minor geyserBOT
#

Yep, that explains it.

I checked the repo, and Anthropic Opus 4.7 landed after v2026.4.14, in v2026.4.15-beta.2.

So on 2026.4.14, not seeing it in openclaw models list is expected.

In other words:

  • 2026.4.14: no Opus 4.7 yet
  • 2026.4.15-beta.2 or newer: includes it

So if you need it right now, you need a newer build than 2026.4.14. Otherwise, wait for the next stable release.

And yep, this also confirms the earlier point: for Anthropic, the list is tied to OpenClaw’s catalog/plugin update cadence, not just a raw live fetch from Anthropic.

fleet oar
#

how to install beta one

minor geyserBOT
#

If you already have OpenClaw installed, the easiest path is:

openclaw update --tag 2026.4.15-beta.2

If you want to stay on the beta track going forward:

openclaw update --channel beta

Useful nuance:

  • --tag 2026.4.15-beta.2 = install that exact build
  • --channel beta = follow the beta channel going forward
fleet oar
#

if later I want to go back to stable channel, I just need to remove the arg, right?

minor geyserBOT
#

Not quite.

It depends which one you used:

  • If you used openclaw update --channel beta, that choice is persisted, so to go back you should run:
openclaw update --channel stable
  • If you used a one-off tag like:
openclaw update --tag 2026.4.15-beta.2

then the channel was not changed, so a later plain openclaw update will use whatever channel you already had configured.

fleet oar
#

nice, you are the best. who are paying for you to run like this?

minor geyserBOT
#

Haha, thanks 😄

In this server, the OpenClaw crew are covering the bot/runtime costs here, not you.

If you run OpenClaw yourself, then it is your own provider/API bill depending on which models and channels you use.

fleet oar
#

after using --channel beta, if I switch back to --channel stable, will it go back to the 4.14? or I keep the .15 beta2?

minor geyserBOT
#

It switches to the latest stable release, not "whatever you had before."

So right now, if stable is still 2026.4.14, then switching back with:

openclaw update --channel stable

would likely downgrade you from 2026.4.15-beta.2 back to 2026.4.14.

OpenClaw should prompt before a downgrade.

If you want to preview first:

openclaw update --channel stable --dry-run
#

So short version:

  • stable channel = latest stable
  • beta channel = latest beta candidate
  • switching back does not "keep beta" unless that same version has already been promoted to stable

Docs: https://docs.openclaw.ai/cli/update