Agent messaging

[onyx ice]

In discord, if I tell one agent to coordinate with another and link another message thread, the agent will post in that thread with a request for the agent, but the agent doesn’t seem to respond. How do I get sessions to communicate with each other without causing a runaway loop of messaging?

[gritty valley]

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

[molten spire]

What’s happening is usually this:

1. Agent A is using message.send to post into Agent B’s Discord thread.
2. That creates a bot-authored Discord message, not an internal session turn.
3. Discord bot messages are ignored by default, specifically to avoid bot-to-bot loops.

So posting into the other thread is visible, but it does not reliably wake the other session.

Use this pattern instead:

• For delegation: use sessions_spawn
  • best when A is creating a worker
  • pair with thread: true and mode: "session" if you want a bound Discord thread
• For talking to an existing session: use sessions_send
  • target the other session by sessionKey
  • do not use a thread link as the transport mechanism

Important config bits:

• tools.sessions.visibility
  • default is tree, so arbitrary sessions are often invisible
  • use "agent" for same-agent sessions, "all" for cross-agent access
• tools.agentToAgent
  • needed for cross-agent targeting
• channels.discord.threadBindings.enabled
• channels.discord.threadBindings.spawnSubagentSessions: true
  • needed if sessions_spawn({ thread: true }) should auto-create/bind a Discord thread

To prevent runaway loops:

• keep Discord bot messages ignored, don’t turn on allowBots=true unless you really mean it
• set session.agentToAgent.maxPingPongTurns: 0 or 1
• have the receiving agent return one result and stop, or reply REPLY_SKIP
• prefer sessions_spawn over free-form “go talk to that thread” workflows