#delete

1 messages · Page 1 of 1 (latest)

west furnaceBOT
#

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

tired hingeBOT
#

If OpenRouter’s activity log shows openrouter/auto, that usually means the actual model field in the request is openrouter/auto (or you’re failing over to it), even if your UI/alias says “MiniMax”.

A few quick checks to narrow it down:

  1. Version first (important): what does this print?
openclaw --version
  1. Confirm what OpenClaw thinks the resolved model is (on the gateway host):
openclaw models status
openclaw models status --plain

Paste the output (redact keys). This will also show if you’re silently hitting fallbacks.

  1. Discord gotcha: model overrides are per session key (per channel/thread). In Discord, channels/threads are isolated sessions, so run:
#
  • /model status in the same thread/channel where the “wrong” requests happen.
  1. OpenRouter model refs must include the OpenRouter prefix. For OpenRouter it should look like:
  • openrouter/<provider>/<model>
    So for MiniMax-via-OpenRouter it should be something like:
  • openrouter/minimax/<…>
    (not just minimax/<…>)
  1. Check your allowlist/catalog vs alias. In config, the map key is the real model id; alias is just a label. If you accidentally did something like:
models: { "openrouter/auto": { alias: "minimax m2.5" } }

then it’ll look like MiniMax in pickers but will call openrouter/auto.

If you paste your (sanitized) config snippets for:

  • agents.defaults.model
  • agents.defaults.models