7 replies

Discord Components Route Interactions to Channel Session Instead of Originating Session?

✅Solved

hey! discovered some unexpected session routing behavior with Discord components and i wanted to know if this was intended behavior or not:

what happens:
context: DM'ing agent with

dmScope

dmScope

set to

main

main

, so conversation is routed to

agent:main:main

agent:main:main

when DM'ing discord bot

1. agent sends discord DM from

agent:main:main

agent:main:main

→ message delivers fine, sent from

agent:main:main

agent:main:main

2. agent include

components

components

(buttons) in that DM → message still delivers
3. user clicks button → interaction routes to

agent:main:discord:channel:ID

agent:main:discord:channel:ID

instead of

agent:main:main

agent:main:main

the issue:
the button click response lands in a completely different session than where the original message was sent from. this breaks continuity - the webchat session never sees the interaction.

repro:
- session A: send DM with buttons to user
- user clicks button in Discord
- response goes to session B (discord channel session)
- session A is unaware the button was clicked

expected behavior:
1. agent sends discord DM from

agent:main:main

agent:main:main

→ message delivers fine, sent from

agent:main:main

agent:main:main

2. agent include

components

components

(buttons) in that DM → message still delivers
3. user clicks button → interaction routes to

agent:main:main

agent:main:main

so result of button press stays within the context of the original session key

question:
is this intended behavior? if so, is there a way to have component interactions route back to the originating session, or a config to change this routing?

misc info:
openclaw version v2026.2.19-2

thanks!

Solution

Yep — and the gotcha is: for Discord component interactions in DMs, the inbound event context often has:

-

ChatType: "direct"

ChatType: "direct"

(so it is a DM)
- but

To: "channel:<dmChannelId>"

To: "channel:<dmChannelId>"

(because Discord interactions are tied to the channel the interaction happened in)

So if your agent “replies to whatever

ctx.To

ctx.To

is”, it’ll drift back to using the DM channel id.

Best way to make this “default” (no config change)

Put a rule in your agent’s system prompt / AGENTS.md (whatever you use to instruct the agent) like:

ctx.Provider == "discord"

ctx.Provider == "discord"

and

ctx.ChatType == "direct"

ctx.ChatType == "direct"

, always send replies to

user:${ctx.SenderId}

user:${ctx.SenderId}

(or derive user id from

ctx.From

ctx.From

), not

ctx.To

ctx.To

Concrete logic:

- If Discord + direct:
-

to = "user:" + ctx.SenderId

to = "user:" + ctx.SenderId

- Else (guild channels/threads):

Jump to solution

FotC�

Friends of the Crustacean 🦞🤝•3w ago•

7 replies

November

Discord Components Route Interactions to Channel Session Instead of Originating Session?

✅Solved

hey! discovered some unexpected session routing behavior with Discord components and i wanted to know if this was intended behavior or not:

what happens:
context: DM'ing agent with

dmScope

dmScope

set to

main

main

, so conversation is routed to

agent:main:main

agent:main:main

when DM'ing discord bot

1. agent sends discord DM from

agent:main:main

agent:main:main

→ message delivers fine, sent from

agent:main:main

agent:main:main

2. agent include

components

components

(buttons) in that DM → message still delivers
3. user clicks button → interaction routes to

agent:main:discord:channel:ID

agent:main:discord:channel:ID

instead of

agent:main:main

agent:main:main

agent:main:main

agent:main:main

→ message delivers fine, sent from

agent:main:main

agent:main:main

2. agent include

components

components

(buttons) in that DM → message still delivers
3. user clicks button → interaction routes to

agent:main:main

agent:main:main

Solution

Yep — and the gotcha is: for Discord component interactions in DMs, the inbound event context often has:

-

ChatType: "direct"

ChatType: "direct"

(so it is a DM)
- but

To: "channel:<dmChannelId>"

To: "channel:<dmChannelId>"

(because Discord interactions are tied to the channel the interaction happened in)

So if your agent “replies to whatever

ctx.To

ctx.To

is”, it’ll drift back to using the DM channel id.

Best way to make this “default” (no config change)

Put a rule in your agent’s system prompt / AGENTS.md (whatever you use to instruct the agent) like:

ctx.Provider == "discord"

ctx.Provider == "discord"

and

ctx.ChatType == "direct"

ctx.ChatType == "direct"

, always send replies to

user:${ctx.SenderId}

user:${ctx.SenderId}

(or derive user id from

ctx.From

ctx.From

), not

ctx.To

ctx.To

Concrete logic:

- If Discord + direct:
-

to = "user:" + ctx.SenderId

to = "user:" + ctx.SenderId

- Else (guild channels/threads):

Jump to solution

Discord Components Route Interactions to Channel Session Instead of Originating Session?

Best way to make this “default” (no config change)

Discord Components Route Interactions to Channel Session Instead of Originating Session?

Best way to make this “default” (no config change)

Similar Threads

Similar Threads

Similar Threads