openclaw - 💡(How to fix) Fix [Bug]: Slack interactive reply clicks do not show assistant status/typing [2 pull requests]

Summary

Slack interactive reply clicks (buttons/selects) are handled, but the follow-up agent turn does not show Slack native assistant status/typing.

Steps to reproduce

1. Run OpenClaw 2026.5.12 with @openclaw/slack 2026.5.12 in Slack socket mode.
2. Have OpenClaw send an interactive reply with buttons/selects in a Slack thread.
3. Click a button/select.
4. Observe that OpenClaw receives and handles the interaction, but Slack native assistant status/typing does not appear for the follow-up turn.

Expected behavior

Button/select-triggered follow-up agent turns should show Slack native assistant status/typing in the relevant assistant thread, consistent with ordinary Slack message turns.

Actual behavior

The Slack block action is received and the follow-up turn runs, but the visible Slack assistant status/typing indicator is missing for the interactive follow-up turn.

Environment

• OpenClaw version: 2026.5.12
• @openclaw/slack version: 2026.5.12
• Operating system: macOS / Darwin 25.5.0 arm64
• Install method: OpenClaw macOS/local install with external @openclaw/slack plugin
• Model: Not model-specific; observed with OpenClaw gateway Slack interaction path
• Provider / routing chain: Slack socket mode -> @openclaw/slack -> OpenClaw gateway -> configured model provider

Additional provider/model setup details

Not provider/model specific. Observed in Slack socket mode with interactive replies enabled and Slack display config using replyToMode="off", streaming.mode="partial", streaming.nativeTransport=true. No API keys or secrets included.

Logs, screenshots, and evidence

Observed versions: OpenClaw 2026.5.12 and @openclaw/slack 2026.5.12.

Upstream main checked on 2026-05-17 (commit 9b5f5b86510b87e393bff3335d0c192200412b5d) still appears to use:

threadTs: typedBody.container?.thread_ts,

in extensions/slack/src/monitor/events/interactions.block-actions.ts.

This may miss thread context when Slack provides the thread timestamp on typedBody.message?.thread_ts instead of container.thread_ts.

GitHub issue search for assistant.threads.setStatus interactive / block_action thread_ts status did not find an exact existing report.

Impact and severity

• Affected: Slack users using OpenClaw interactive replies/buttons/selects in threads.
• Severity: Low/Medium UX issue; the action still runs, but the turn looks inactive because native assistant status/typing is absent.
• Frequency: Observed for interactive button/select follow-up turns in this workflow.
• Consequence: Users cannot tell that OpenClaw is working after clicking an interactive control, which is confusing for longer follow-up turns.

Additional information

Possible fix direction: preserve Slack block action thread context with typedBody.container?.thread_ts ?? typedBody.message?.thread_ts, and ensure heartbeat/system-event-triggered Slack turns can call assistant.threads.setStatus(...) for the relevant channel/thread.

NOT_ENOUGH_INFO for last known good version.