Description

When using the message tool to send messages to a different target (e.g., from a DM session to a group chat), the message arrives with a [from #<source>] prefix that the recipient sees.

Example

Sending from main session (DM) to a WhatsApp group:

message action=send target=<group-id>@g.us message="Good morning! Here is your morning update!"

Expected:

Good morning! Here is your morning update!

Actual:

[from #+1XXXXXXXXXX] Good morning! Here is your morning update!

Also affects

• iMessage: shows [from #imessage:+1XXXXXXXXXX] prefix

Setup / Configuration

I have multiple channels configured simultaneously:

• WhatsApp: dmPolicy: pairing, groupPolicy: open, requireMention: false
• iMessage: dmPolicy: pairing, groupPolicy: open, enabled via imsg CLI
• Telegram: dmPolicy: allowlist, bot token configured

The prefix issue occurs when:

1. I'm in a WhatsApp DM session with the agent
2. The agent uses the message tool to send to a WhatsApp group or iMessage target
3. The recipient sees the [from #...] prefix on the message

It seems like cross-session/cross-target messages are getting tagged with their origin.

Version

2026.1.23-1

Desired behavior

Messages sent via the message tool should not include the originating session/channel prefix — or there should be a config option to suppress it.