Bug

On workspaces that have Slack Connect enabled (even for purely internal channels), Socket Mode message delivery fails with:

error gateway/channels/slack slack-stream: failed to stop stream: Error: An API error occurred: missing_recipient_team_id

Details

• OpenClaw version: 2026.2.17
• Slack mode: Socket Mode
• Workspace has Slack Connect enabled
• Channels are internal (not shared)
• DMs work fine
• Posting via the message tool (REST API path) works fine
• Only automatic replies to channel mentions fail

Expected behavior

OpenClaw should pass team_id in Slack API calls when the workspace has Slack Connect enabled. The team ID is available from the bot token's auth.test response.

Workaround

Using the message tool to post directly to channels works. Automatic mention-triggered replies do not.

Reproduction

1. Set up Slack integration on a workspace with Slack Connect enabled
2. Invite bot to an internal channel
3. @mention the bot
4. Agent runs successfully but reply never appears
5. Logs show missing_recipient_team_id error