#How to make agent send message/request to other agent

6 messages · Page 1 of 1 (latest)

amber tangle
#

So I got few agents on my setup on discord and I was wondering how people manage the
“Main chat bot,orchestrator,coder” type of structured agent stuff
Because rn although o tell them what they’re
Purpose is and they know that but when a specific agent needs help of the admin or when it needs to pass down a message to other agents, it doesn’t do it or at least I don’t think it’s doing it
English isn’t my first language so it might’ve been a nightmare reading this but please help
Thank you

shrewd folioBOT
#

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

dusky duneBOT
mortal oliveBOT
#

Your English is totally fine 🙂

Short version: giving agents a role is not enough. If you want them to actually coordinate, they need the right tools + routing, not just instructions.

What usually works best in OpenClaw:

  • 1 main user-facing agent
  • it uses sessions_spawn to create worker agents
  • workers return results back up
  • the main agent is the one that talks to you most of the time

A few important gotchas:

  • If an agent needs to message you/admin, it needs the message tool (group:messaging)
  • If it needs to talk to another session/agent, it needs sessions_send or sessions_spawn
  • Cross-agent messaging is off by default. If these are separate agent IDs, enable:
    • tools.agentToAgent.enabled: true
#
  • tools.agentToAgent.allow: [...]
  • Session visibility defaults to tree, so agents often cannot even see other sessions unless you widen tools.sessions.visibility
  • Default leaf subagents do not get orchestration tools
    • if you want main → orchestrator → coder, set agents.defaults.subagents.maxSpawnDepth: 2
  • On Discord, if you want spawned work to stay in threads, enable:
    • channels.discord.threadBindings.enabled: true
    • channels.discord.threadBindings.spawnSubagentSessions: true

Also, tool profile matters a lot:

  • tools.profile: "messaging" = has chat/message stuff, but not sessions_spawn
  • tools.profile: "coding" = has session tools, but not message

That mismatch is a super common reason this feels “broken”.

So my recommendation is: