Description

When OpenClaw processes messages in a Slack channel, the agent run completes successfully but the typing indicator (stream) stop call fails with:

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

Environment

• OpenClaw version: 2026.2.17
• Node: v25.6.1
• OS: macOS (arm64)
• Slack mode: socket

Reproduction

1. Configure Slack channel with requireMention: false and a system prompt
2. Send a message in the channel
3. Agent processes the message and completes (visible in lane logs)
4. The slack-stream: failed to stop stream error fires immediately after

Frequency

12 occurrences in a single session today. Fires after every agent run that processes a channel message. Does not appear to affect DM sessions.

Impact

• Message sends via the message tool still work (bot can post to the channel)
• The error appears to be specifically on the typing indicator lifecycle
• Unclear if this prevents actual message delivery when the agent does want to reply (vs NO_REPLY)

Logs

2026-02-18T19:06:56.595Z embedded run agent end: runId=1eb6712e isError=false
2026-02-18T19:06:56.896Z slack-stream: failed to stop stream: Error: An API error occurred: missing_recipient_team_id

The pattern is consistent: agent run ends → stop stream fails → next message still gets received fine.

Possible Cause

The Slack API likely requires a team_id parameter when calling the typing indicator stop endpoint for channels. This may be missing from the provider implementation.