#The /model discord command doesn't do anything.

1 messages · Page 1 of 1 (latest)

noble star
#

Somehow the /model command has been failing lately. It always returns "Tried to see X model but current model is Y" when I use the discord UI selector. Then if I manually type /model provider/model it says Done. Yet nothing changed. If I use the openclaw control UI, models change without issue however.

split peakBOT
#

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

dense flameBOT
#

I dug through the code, and this looks like a Discord thread/session-binding regression, not a provider problem.

What I found:

  • The picker warning comes from extensions/discord/src/monitor/native-command-ui.ts when Discord applies /model ... and then rereads the model from the resolved route.sessionKey. If that reread hits the wrong session, you get:
    • ⚠️ Tried to set X, but current model is Y
  • The plain Done. reply comes from extensions/discord/src/monitor/native-command.ts as the empty fallback reply when the slash-command turn produced no renderable response. So in this case, Done. is basically “Discord command completed”, not “model actually switched”.

Why I think this is your case:

  • You’re on 0512059dd4e6d2e582393828b837c376ddc4719c (2026.4.9 stable)
  • That build is missing several later Discord fixes, including:
    • 84cd786911 fix: tolerate partial discord channel metadata (#68953)
    • dbf8fd0db7 fix(discord): read channel.parentId through safe accessor on partial thread channels
    • 42a4dee8b64daeb4154a2c543737482280c14c42 fix: prefer target entry for plugin commands
    • a8a023779d0ef027ea73763f8b5119861c5989fb fix(discord): preserve fetched thread parent for plugin commands (#69908)

Given that this is happening in a Discord thread, and Control UI switching still works, updating is the right fix.

#

What I’d do:

  1. Update OpenClaw to latest
  2. Then run:
    • openclaw --version
    • openclaw status
  3. Retest /model in the same Discord thread

Docs:

Temporary workaround:

  • Keep using the Control UI
  • Or try /model from a non-thread context, since this really looks thread-route related

If you update and it still reproduces, paste the new openclaw --version and I’ll keep digging. If this fixed it, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow can index it.