Bug: Multi-agent Discord setup fails in v2026.2.12
Bug: Multi-agent Discord handler fails in v2026.2.12 with “Session file path must be within sessions directory” (bots stop responding)
Version OpenClaw: v2026.2.12 (regression)
Works after downgrade: v2026.2.9
Channel: Discord
Setup: Multi-agent setup (3 agents)
Each agent bound to its own Discord channel
Previously working; then 2 agents stopped responding, then the 3rd also stopped
Observed behavior:
Bots stop replying in their bound channels.
Logs show repeated Discord handler failures: error gateway/channels/discord ... handler failed: Error: Session file path must be within sessions directory
Workaround: Downgrade OpenClaw to v2026.2.9 via:
npm i -g openclaw@2026.2.9
After downgrade, all Discord agents resume responding normally.
Version OpenClaw: v2026.2.12 (regression)
Works after downgrade: v2026.2.9
Channel: Discord
Setup: Multi-agent setup (3 agents)
Each agent bound to its own Discord channel
Previously working; then 2 agents stopped responding, then the 3rd also stopped
Observed behavior:
Bots stop replying in their bound channels.
Logs show repeated Discord handler failures: error gateway/channels/discord ... handler failed: Error: Session file path must be within sessions directory
Workaround: Downgrade OpenClaw to v2026.2.9 via:
npm i -g openclaw@2026.2.9
After downgrade, all Discord agents resume responding normally.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
