Multi-agent task creation & management in Discord
Hi Krill, can you help understanding the correct/supported way to launch & manage Subagent tasks from a Main Agent Discord channel.
Setup:
- OpenClaw
- Built in Codex, trying to follow native OpenClaw Discord + ACP docs, not custom runtime code
- One bound Discord channel for the Main Agent
- Separate bound Discord channels for each Subagent in their own category
- Non-trivial Subagent work is intended to run in dedicated threads under the relevant Subagent channel
- ACP is enabled, Discord is connected,
-
Goal:
From the Main Agent command channel, we want to create a task for a Subagent, have it run autonomously in the Subagent’s own thread, complete autonomously if possible, and escalate back to the Main Agent with feedback/retry context if it gets blocked, fails, or hangs.
What works:
- Direct use of an agent in its own bound channel
- Creating a real thread under a Subagent channel
- Once explicitly woken in that thread, the Subagent can execute normally
What fails:
- Cross-channel Main Agent -> Subagent launch is unreliable
- We first tried
- We then switched to
- In several cases, posting the kickoff into the thread was not enough to auto-wake the Subagent
- We had to manually wake it with
Question:
Is there a supported native way for a Main Agent in one bound Discord channel to launch, monitor, and receive escalation/handback from a Subagent running in another bound agent channel? If so, what is the correct implementation? Are we missing required config, or is the expected pattern that task creation must happen directly inside the target Subagent channel/thread instead of from the Main Agent channel?
Setup:
- OpenClaw
2026.3.7- Built in Codex, trying to follow native OpenClaw Discord + ACP docs, not custom runtime code
- One bound Discord channel for the Main Agent
- Separate bound Discord channels for each Subagent in their own category
- Non-trivial Subagent work is intended to run in dedicated threads under the relevant Subagent channel
- ACP is enabled, Discord is connected,
threadBindings.enabled=truespawnAcpSessions=true-
spawnSubagentSessions=falseGoal:
From the Main Agent command channel, we want to create a task for a Subagent, have it run autonomously in the Subagent’s own thread, complete autonomously if possible, and escalate back to the Main Agent with feedback/retry context if it gets blocked, fails, or hangs.
What works:
- Direct use of an agent in its own bound channel
- Creating a real thread under a Subagent channel
- Once explicitly woken in that thread, the Subagent can execute normally
What fails:
- Cross-channel Main Agent -> Subagent launch is unreliable
- We first tried
openclaw gateway call sessions_sendunknown method: sessions_send- We then switched to
gateway call agent- In several cases, posting the kickoff into the thread was not enough to auto-wake the Subagent
- We had to manually wake it with
openclaw agent --agent <subagent> ... --deliver --reply-to <thread-id>Question:
Is there a supported native way for a Main Agent in one bound Discord channel to launch, monitor, and receive escalation/handback from a Subagent running in another bound agent channel? If so, what is the correct implementation? Are we missing required config, or is the expected pattern that task creation must happen directly inside the target Subagent channel/thread instead of from the Main Agent channel?
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
134,827Members
Resources
Similar Threads
Was this page helpful?
