Bug type

Regression (worked before, now fails)

Summary

• Slack messages create isolated sessions instead of persistent per-channel sessions
• Downgrade to 2026.2.26 resolves it

Steps to reproduce

1. Upgrade OpenClaw from 2026.2.26 to 2026.3.1
2. Configure Slack with Socket Mode enabled, groupPolicy: "open", historyLimit: 20
3. Send a message to a Slack channel (with bot mentioned)
4. Wait for bot reply
5. Reply to the bot in the same channel
6. Observe bot has no context of previous message

Expected behavior

• Slack channel messages should create/maintain persistent sessions with key format: agent:main:slack:channel:
• Each channel should have one continuous session that preserves conversation context across messages
• Bot should remember previous messages within the same channel (up to historyLimit)

Actual behavior

• Each Slack channel message creates a new isolated session with random UUID (e.g., c83eee8f-5863-4260-b11d-d7473755f1e2)
• No conversation context is preserved between messages
• Bot cannot remember confirmations, previous questions, or any prior conversation in the channel
• Session files show random UUIDs instead of expected agent::slack:channel: format

OpenClaw version

2026.3.1

Operating system

OS: Linux 6.8.0-101-generic (x64) Node: v22.22.0

Install method

npm global

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response