openclaw - 💡(How to fix) Fix [Bug]: Slack async exec completion still escapes originating thread [2 comments, 2 participants]

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

A Slack channel-thread async exec completion reply still escapes the originating Slack thread and posts as a top-level channel message on OpenClaw 2026.4.24 (cbcfdf6).

This is the v2026.4.24+ follow-up requested in #72151 after that issue was closed as already implemented.

Steps to reproduce

1. Start OpenClaw 2026.4.24 (cbcfdf6) with Slack enabled and channel thread replies configured.

2. In Slack, send a message to the assistant inside an existing channel thread.

3. In that threaded assistant turn, start an exec command that completes after the assistant turn returns.

4. Exact command used:

   python3 - <<'PY'
   import time
   time.sleep(2)
   print('ROUTING_REPRO_MARKER_20260426_1821_V24')
   PY

   The command was started with a very short foreground wait so OpenClaw returned before completion and later injected the async completion event.

5. Wait for the async completion event.

6. Let the assistant relay the completion output back to Slack.

Expected behavior

The async completion relay should be posted in the original Slack thread that started the command.

Actual behavior

The async completion relay posted as a top-level channel message instead of staying in the original Slack thread.

Observed marker:

ROUTING_REPRO_MARKER_20260426_1821_V24

Repro evidence

• OpenClaw version: 2026.4.24 (cbcfdf6)
• Origin Slack thread timestamp: 1777136297.410919
• A normal assistant reply immediately before the async completion did post inside that thread.
• The async completion relay containing ROUTING_REPRO_MARKER_20260426_1821_V24 posted at channel root instead.
• Leaked top-level Slack message timestamp: 1777220556.388089
• Local session key shape: agent:main:slack:channel:<redacted-channel>:thread:1777136297.410919

Route metadata observed

Persisted session routing context looked correct:

{
  "channel": "slack",
  "lastChannel": "slack",
  "lastTo": "channel:<redacted-channel>",
  "lastThreadId": "1777136297.410919",
  "deliveryContext": {
    "channel": "slack",
    "to": "channel:<redacted-channel>",
    "accountId": "default",
    "threadId": "1777136297.410919"
  }
}

But the injected async completion turn metadata visible to the assistant contained only channel-level context, not the original thread route:

{
  "chat_id": "<redacted-channel>"
}

It did not include the originating Slack thread_ts / OpenClaw threadId in that visible async completion envelope, and the final relay was delivered at channel root.

Relevant config

{
  "channels": {
    "slack": {
      "replyToModeByChatType": {
        "channel": "all"
      },
      "thread": {
        "requireExplicitMention": true
      }
    }
  }
}

Related issues

• #72151 was closed as already implemented, with a request to file a fresh regression if this reproduced on v2026.4.24 or later.
• #62736 is related historical thread-routing context, but this repro is specifically async exec completion delivery.