"replyToMode": "off" do not effect | Friends of the Crustacean 🦞🤝 | Page 1

dusky kelp Apr 29, 2026, 4:22 AM

#

Hi, I set "replyToMode": "off" in json,but it did not work after I upgrade to 4.26. It worked before.

lapis ledgeBOT Apr 29, 2026, 4:22 AM

#

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

crystal perchBOT Apr 29, 2026, 4:23 AM

#

replyToMode: "off" should still be valid for Discord, but one nuance changed/exists in docs:

off disables implicit native reply threading.
Explicit tags like / are still honored.

So if the model/tool output includes a reply tag, Discord will still show it as a reply even with replyToMode: "off".

Quick checks:

Please confirm exact version:
```
openclaw --version
```
Make sure it’s under Discord config:

#

   {
     channels: {
       discord: {
         replyToMode: "off"
       }
     }
   }

If you use Discord accounts, also try setting it on that account:
```
{
  channels: {
    discord: {
      accounts: {
```

#

           default: {
             replyToMode: "off"
           }
         }
       }
     }
   }

Restart the gateway after editing config:
```
openclaw gateway restart
```

Docs: https://docs.openclaw.ai/channels/discord

#

If it still replies natively without any [[reply_to_*]] tag in the assistant output, that sounds like a regression in 2026.4.26 — please share openclaw --version + a sanitized Discord config snippet.

dusky kelp Apr 29, 2026, 4:54 AM

#

the config still not work. OpenClaw 2026.4.26 (be8c246),
"discord": {
"enabled": true,
"defaultAccount": "main",
"allowBots": "mentions",
"replyToMode": "off",
"streaming": {
"mode": "block"
},
"accounts": {
"default": {
"replyToMode": "off"
},
"main": {

crystal perchBOT Apr 29, 2026, 4:55 AM

#

Ah, key detail: your active Discord account is main:

"defaultAccount": "main"

So accounts.default.replyToMode won’t affect that account. Add it under accounts.main too:

channels: {
  discord: {
    defaultAccount: "main",
    replyToMode: "off",
    accounts: {
      main: {
        replyToMode: "off"

#

      }
    }
  }
}

Then restart:

openclaw gateway restart

Also: if the model outputs , Discord will still native-reply even with replyToMode: "off" — that’s treated as an explicit reply tag. If this still happens after adding it to main, it may be a 2026.4.26 regression and worth filing with this config snippet: https://github.com/openclaw/openclaw/issues

dusky kelp Apr 29, 2026, 5:07 AM

#

I added this to every accounts,but it still not work

crystal perchBOT Apr 29, 2026, 5:09 AM

#

Then it’s probably not the account config anymore.

Two important distinctions:

replyToMode: "off" only disables implicit Discord native replies.
If the model outputs an explicit hidden directive like , Discord will still reply. OpenClaw strips that tag from the visible message, so it can look like config is ignored.
It does not stop replies from appearing inside the same Discord thread/forum post.
It only controls the little native “replying to …” reference.

Try adding this to your agent instructions / AGENTS.md:

On Discord, do not use reply directives such as  or  unless explicitly asked.

Then restart gateway and test again.

#

If you still get the native reply after that, I’d treat this as a 2026.4.26 regression/behavior gap and file it here with your config snippet: https://github.com/openclaw/openclaw/issues

Docs note this behavior too: https://docs.openclaw.ai/channels/discord

dusky kelp Apr 29, 2026, 5:13 AM

#

I think it is not only the replayToMode that does not take effect, but many discord parameters do not take effect.

crystal perchBOT Apr 29, 2026, 5:14 AM

#

Yeah, if multiple Discord settings aren’t taking effect, I’d stop chasing replyToMode specifically. This smells like the gateway is running from a different config file / state dir than the one you edited, or the gateway process didn’t actually restart.

Please run these and compare the config path:

openclaw config file
openclaw config get channels.discord --json
openclaw gateway status
openclaw status --all

Things to look for:

openclaw config file path matches the config you edited
openclaw gateway status shows the same config/state location
openclaw config get channels.discord --json actually contains your updated Discord values
no config validation warnings in openclaw status --all

#

Then restart hard:

openclaw gateway restart

If config file and gateway status point to different places, edit the one the gateway is actually using. This can happen with service installs, Docker/VPS setups, or OPENCLAW_STATE_DIR.

Docs: https://docs.openclaw.ai/help/faq and https://docs.openclaw.ai/cli/config

dusky kelp Apr 29, 2026, 5:18 AM

#

I take back what I said just now, the problem is still mainly in the replayToMode.

crystal perchBOT Apr 29, 2026, 5:18 AM

#

Got it — then I’d frame it this way:

replyToMode: "off" is being read, but in current Discord behavior it does not block explicit reply directives like:

Those tags are hidden from the final Discord message, so it looks like replyToMode is ignored.

Workaround for now: add this to your agent instructions / AGENTS.md:

For Discord replies, never use  or  unless the user explicitly asks you to reply to a specific message.

Then restart:

#"replyToMode": "off" do not effect