Skip to content

Feature request: per-channel responsePrefix #8857

@mudrii

Description

@mudrii

Feature Request

Is your feature request related to a problem?

Currently messages.responsePrefix is applied globally to all outbound replies across all channels. When running multiple channels (e.g., Telegram + WhatsApp), there's no way to apply a prefix to only one channel.

Use case:

With multi-account WhatsApp, when the user messages between their own accounts (e.g., ONE number → TWO number), the bot replies in the same conversation. It becomes confusing who sent which message — the human or the bot. A responsePrefix like [BotName] solves this for WhatsApp, but applying it globally also prefixes Telegram replies where it's unnecessary (since Telegram already shows the bot's name/avatar clearly).

Describe the solution you'd like:

Support per-channel responsePrefix override, e.g.:

{
  channels: {
    whatsapp: {
      responsePrefix: "[Bot] "
    },
    telegram: {
      responsePrefix: ""  // no prefix
    }
  }
}

Or alternatively at the account level for WhatsApp multi-account:

{
  channels: {
    whatsapp: {
      accounts: {
        business: { responsePrefix: "[Bot] " },
        default: { responsePrefix: "[Bot] " }
      }
    }
  }
}

Current workaround:

Using the global messages.responsePrefix which applies to all channels.

Additional context:

  • OpenClaw v2026.2.2-3
  • Running Telegram + 2x WhatsApp accounts
  • dmScope: per-account-channel-peer

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions