-
-
Notifications
You must be signed in to change notification settings - Fork 52.6k
Closed as not planned
Closed as not planned
Copy link
Labels
close:duplicateClosed as duplicateClosed as duplicatededupe:childDuplicate issue/PR child in dedupe clusterDuplicate issue/PR child in dedupe cluster
Description
Description
openclaw doctor --fix crashes with Error: Session file path must be within sessions directory immediately after applying config migrations. More critically, the same error crashes the Discord guild message handler at runtime, preventing the bot from receiving any guild channel messages.
Environment
- Version: 2026.2.15 (npm/pnpm install, not git checkout)
- OS: macOS 26.2 (arm64)
- Setup: Multi-agent (main + secondary agent "luna"), 15 active sessions
- Install method: pnpm global
Runtime Impact
Gateway logs show:
discord channels unresolved: 823385078461497365/1465378022885429409, 823385078461497365/1466049469668790305, 823385078461497365/1467585640614068408
Error: Session file path must be within sessions directory
gateway/channels/discord handler failed: Error: Session file path must be within sessions directory
This means guild channel messages are completely broken — the Discord handler crashes on every inbound message. DMs work fine (different code path).
Steps to Reproduce
- Multi-agent setup (main + secondary agent)
- Configure Discord guild channels in allowlist
- Send a message in an allowlisted guild channel
- Handler crashes with session path error
Expected Behavior
Guild messages should be received and routed to the agent.
Actual Behavior
Handler crashes. Bot can send to channels but cannot receive messages.
Notes
- CHANGELOG references [Bug] Session file path validation failure in v2026.2.12 causing Telegram handler crashes #15141 which fixed this for "non-default agents and heartbeat/chat handlers" in reply runs — likely the same root cause in the Discord guild session resolution path.
- The "channels unresolved" log line may also be relevant — channels are listed but not resolving despite correct guild ID in config.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
close:duplicateClosed as duplicateClosed as duplicatededupe:childDuplicate issue/PR child in dedupe clusterDuplicate issue/PR child in dedupe cluster