Summary

Slack thread sessions inherit partial, unpredictable context from other sessions. New threads contain orphaned assistant messages and tool outputs from unrelated conversations, but NOT the user messages that triggered them. This breaks session isolation and makes it impossible to start clean conversations via threads.

Steps to reproduce

1. In a Slack channel with Clawdbot, start a conversation (e.g., ask it to browse a website — generates tool calls and assistant responses)
2. Create Thread A by posting a new message, have a multi-turn conversation including some unique identifier (e.g., a random number), and have the agent repeat back the unique identifier
3. Create Thread B by posting another new message to the channel
4. In Thread B, ask the agent: "What context do you see? Do you see [identifier from Thread A]?"
5. Observe that Thread B has partial context from earlier conversations

Expected behavior

Thread sessions should either:

• Start with clean/empty context (full isolation), OR
• Inherit complete context (all user AND assistant messages) with explicit documentation

Actual behavior

Thread sessions inherit:

• ✓ Assistant messages from other sessions
• ✓ Tool results from other sessions
• ✘ Thinking traces from other sessions
• ✘ NOT the user messages that triggered those responses

Additionally:

• Thread-starting messages go to BOTH the channel session AND create a new thread session
• Thread-internal replies only go to the thread session
• sessions_list tool exposes other sessions' full assistant content (including thinking), which then becomes part of the requesting session's context

Environment

• Clawdbot version: 2026.1.10 (c5d9b7e)
• OS: macOS (Darwin 25.2.0 arm64)
• Install method: npm global
• Slack config: groupPolicy: "open", replyToMode: "all"