#I’m seeing a discord update can u fill me in

1 messages · Page 1 of 1 (latest)

bold otter
#

??

honest pawnBOT
#

What Discord “update” are you seeing (and where)?

If you paste the exact text from the popup/notification (or drop a screenshot), I can tell you what it means and whether it affects anything here (OpenClaw / Discord bots / permissions).

A couple quick pointers so I can narrow it down:

  • Is it an app update (desktop/mobile), a server feature notification, or a bot/API related warning?
  • Does it mention anything like “Apps”, “Commands”, “permissions/intents”, “message content”, or “linked roles”?

Send whatever you’ve got (text or screenshot) and I’ll translate it.

bold otter
#

Discord components v2? Or some shi

honest pawnBOT
#

That channel isn’t a “Discord app update” — it’s OpenClaw release announcements, including a couple Discord-specific upgrades.

Most recent highlight (OpenClaw 2026.2.15):

  • Discord Components v2: your agent can send native Discord UI elements (buttons, dropdowns/selects, modals/forms) and OpenClaw can receive what you click/submit.
  • Telegram message streaming (replies show up live as they’re generated)
  • Nested sub-agents
  • Major security hardening + 40+ bug fixes

The previous release (2026.2.14) was also heavily security-focused (50+ hardening fixes) plus general bugfixes/perf.

If you tell me what you’re trying to do (just curious vs. you want to upgrade your own setup / bot), I can point you to the exact release notes + what changes you’ll actually notice on Discord.

bold otter
#

Why isn’t my agent using the ui elements?

honest pawnBOT
#

“UI elements” only come into play when the agent is actually using a UI automation tool (typically the browser tool / Control UI). If you’re just chatting to the agent in Discord, it can’t “click Discord UI” (buttons/menus/etc) — it can only send messages/reactions/polls via the Discord API.

A few common reasons it won’t use UI elements even for web pages:

  1. No active browser/control session
    The agent needs a connected browser session (via the Dashboard/Control UI) to “see” elements and act on them.

  2. Model/tool-calling issue
    Some models are flaky with tool calling (esp. the browser tool) and will just keep replying in text instead of clicking/typing.

  3. Prompting / mode mismatch
    If you don’t explicitly ask it to “use the browser tool and click/type”, it may try to answer conversationally.

To narrow it down, can you paste:

  • openclaw --version
  • what model you’re running
  • where you expect UI usage: Discord UI vs a website in the Control UI/browser (a screenshot is fine)
#

Then I can tell you the exact fix for your setup.

bold otter
#

Also what’s the /model command to switch to sonnet 3.5

#

??

#

Anthropic/xxx?

honest pawnBOT
#

To switch to Sonnet 3.5, you’ve got two “levels”:

1) Switch just for the current chat/session

In the chat with the agent, try:

  • /model list
  • then pick it with /model <number>

If Sonnet 3.5 is available/configured, it should show up in that list.

Docs: https://docs.openclaw.ai/concepts/models

2) Make Sonnet 3.5 the default for your whole Gateway

Use the CLI to find the exact model id string your install/provider uses, then set it:

bold otter
#

I just want to know the proper string for sonnet so I can put it in the /model command

honest pawnBOT
# 
openclaw models list --all --provider anthropic
openclaw models set <provider/model-from-the-list>
openclaw models status

(That avoids guessing the exact spelling of the Sonnet 3.5 model ref.)

Docs: https://docs.openclaw.ai/concepts/models • https://docs.openclaw.ai/gateway/configuration

If it says “Model … is not allowed”

That means you’re using a model allowlist (agents.defaults.models). Either add Sonnet 3.5 to that allowlist or remove the allowlist. (The models doc calls this out explicitly.)

If you paste your openclaw --version + the output of openclaw models status, I can tell you exactly which step you’re hitting.

#

Which part are you “??” on — the UI elements thing, or the Sonnet 3.5 switch?

Here’s the quick clarification for both:

A) “Why isn’t it using UI elements?”

  • If you mean clicking Discord buttons/menus: it can’t. A Discord bot can only interact via the Discord API (send messages, react, etc.), not drive the Discord client UI.
  • If you mean clicking elements on a website: you need to be using the browser tool (usually via the Control UI/Dashboard), and the model must be reliably tool-calling.

Tell me which UI you meant (Discord UI vs website UI), and paste:

  • openclaw --version
  • openclaw models status

B) “What’s the to switch to Sonnet 3.5?”

In chat:

  1. /model list
  2. /model <number> (choose the Sonnet entry)
#

Yep — the format is provider/model.

For Anthropic the provider prefix is:

  • anthropic/<something>

But the exact <something> (Sonnet 3.5) depends on what your OpenClaw version/provider catalog exposes, so don’t guess it—just list and pick it:

In-chat (fastest)

  1. Run: /model list
  2. Pick the Sonnet 3.5 entry: /model <number>

CLI (to see the exact anthropic/xxx string)

openclaw models list --all --provider anthropic
#

If Sonnet isn’t listed, run:

openclaw models status
openclaw models list --all --provider anthropic

…and paste the output so I can tell you the exact model ref to set.