lobster-biscuit

Summary

Slack thread replies leak to main channel when messages are queued during agent processing.

Repro Steps

1. Configure Slack with replyToMode: all
2. Send 2+ messages quickly while agent is busy
3. Messages enter followup queue, get collected/drained
4. Response appears in main channel instead of thread

Expected

Queued responses preserve thread_ts and reply in the correct thread.

Actual

typeof threadId === "number" in drain.ts drops Slack string thread_ts. Thread key becomes empty, collected reply goes to channel.

Environment

• OpenClaw version: 2026.2.6
• OS: macOS 15 (Apple Silicon)
• Install method: pnpm (source)
• Channel: Slack

Logs/Evidence

// drain.ts — broken check (only accepts Telegram numeric IDs)
const threadKey = typeof threadId === "number" ? String(threadId) : "";
// Slack thread_ts is string like "1770474140.187459" → fails → threadKey = ""

Impact

All Slack users with queue mode enabled lose thread context on queued replies. Moderate severity — messages work but land in wrong place.

Workarounds

None known.

Related

• [Bug]: Slack thread_ts lost during collect queue drain — typeof === "number" check drops string thread IDs #4380 — original report
• Slack: second thread reply routes to main channel when two messages arrive before first reply #4424 — second thread reply routes to main channel
• fix: handle string thread_ts from Slack properly #4389, fix: handle string thread IDs in queue drain for Slack #4749, [Slack] fix: preserve thread context for string threadId in queue drain #5245 — prior fix PRs (all missing empty-string edge case)
• PR fix(slack): queue drain drops string thread_ts — replies leak to main channel instead of thread #11194 — fix