feat: attach ts to listener context

Author: zimeg

slack_bolt/context/base_context.py

@@ -18,6 +18,7 @@ class BaseContext(dict):
         "actor_team_id",
         "actor_user_id",
         "channel_id",
+        "ts",
         "thread_ts",
         "response_url",
         "matches",
@@ -110,6 +111,11 @@ def channel_id(self) -> Optional[str]:
         """The conversation ID associated with this request."""
         return self.get("channel_id")
 
+    @property
+    def ts(self) -> Optional[str]:
+        """The message timestamp associated with this request."""
+        return self.get("ts")
+
     @property
     def thread_ts(self) -> Optional[str]:
         """The conversation thread's ID associated with this request."""

slack_bolt/kwargs_injection/async_utils.py

@@ -89,10 +89,18 @@ def build_async_required_kwargs(
     if "agent" in required_arg_names:
         from slack_bolt.agent.async_agent import AsyncBoltAgent
 
+        # For thread_ts, we check multiple sources:
+        # 1. context.thread_ts - populated for assistant events
+        # 2. event.thread_ts - for non-assistant events in a thread (e.g., app_mention in thread)
+        # 3. context.ts - fallback to the message timestamp
+        # We read from event directly to avoid changing context.thread_ts which would affect say() behavior
+        event = request.body.get("event", {})
+        thread_ts = request.context.thread_ts or event.get("thread_ts") or request.context.ts
+
         all_available_args["agent"] = AsyncBoltAgent(
             client=request.context.client,
             channel_id=request.context.channel_id,
-            thread_ts=request.context.thread_ts,
+            thread_ts=thread_ts,
             team_id=request.context.team_id,
             user_id=request.context.user_id,
         )

slack_bolt/kwargs_injection/utils.py

@@ -88,10 +88,18 @@ def build_required_kwargs(
     if "agent" in required_arg_names:
         from slack_bolt.agent.agent import BoltAgent
 
+        # For thread_ts, we check multiple sources:
+        # 1. context.thread_ts - populated for assistant events
+        # 2. event.thread_ts - for non-assistant events in a thread (e.g., app_mention in thread)
+        # 3. context.ts - fallback to the message timestamp
+        # We read from event directly to avoid changing context.thread_ts which would affect say() behavior
+        event = request.body.get("event", {})
+        thread_ts = request.context.thread_ts or event.get("thread_ts") or request.context.ts
+
         all_available_args["agent"] = BoltAgent(
             client=request.context.client,
             channel_id=request.context.channel_id,
-            thread_ts=request.context.thread_ts,
+            thread_ts=thread_ts,
             team_id=request.context.team_id,
             user_id=request.context.user_id,
         )

slack_bolt/request/async_internals.py

@@ -15,6 +15,7 @@
     extract_actor_team_id,
     extract_actor_user_id,
     extract_thread_ts,
+    extract_ts,
 )
 
 
@@ -45,6 +46,9 @@ def build_async_context(
     channel_id = extract_channel_id(body)
     if channel_id:
         context["channel_id"] = channel_id
+    ts = extract_ts(body)
+    if ts:
+        context["ts"] = ts
     thread_ts = extract_thread_ts(body)
     if thread_ts:
         context["thread_ts"] = thread_ts

slack_bolt/request/internals.py

@@ -215,9 +215,14 @@ def extract_channel_id(payload: Dict[str, Any]) -> Optional[str]:
 
 
 def extract_thread_ts(payload: Dict[str, Any]) -> Optional[str]:
-    # This utility initially supports only the use cases for AI assistants, but it may be fine to add more patterns.
-    # That said, note that thread_ts is always required for assistant threads, but it's not for channels.
-    # Thus, blindly setting this thread_ts to say utility can break existing apps' behaviors.
+    # This utility only extracts thread_ts for assistant events to avoid breaking existing say() behavior.
+    # For non-assistant events, thread_ts is intentionally NOT extracted into context because:
+    # - say() uses context.thread_ts to decide where to post messages
+    # - Existing apps may expect say() to post to the channel, not the thread
+    # - Changing this would be a breaking change for existing apps
+    #
+    # The BoltAgent class handles non-assistant thread_ts separately by reading from the event directly,
+    # allowing it to work correctly without affecting say() behavior.
     if is_assistant_event(payload):
         event = payload["event"]
         if (
@@ -242,6 +247,18 @@ def extract_thread_ts(payload: Dict[str, Any]) -> Optional[str]:
     return None
 
 
+def extract_ts(payload: Dict[str, Any]) -> Optional[str]:
+    """Extract the message timestamp from an event payload."""
+    event = payload.get("event", {})
+    # Direct ts on the event (e.g., app_mention, message)
+    if event.get("ts") is not None:
+        return event["ts"]
+    # message_changed events have ts in the message
+    if event.get("message", {}).get("ts") is not None:
+        return event["message"]["ts"]
+    return None
+
+
 def extract_function_execution_id(payload: Dict[str, Any]) -> Optional[str]:
     if payload.get("function_execution_id") is not None:
         return payload.get("function_execution_id")
@@ -292,6 +309,9 @@ def build_context(context: BoltContext, body: Dict[str, Any]) -> BoltContext:
     channel_id = extract_channel_id(body)
     if channel_id:
         context["channel_id"] = channel_id
+    ts = extract_ts(body)
+    if ts:
+        context["ts"] = ts
     thread_ts = extract_thread_ts(body)
     if thread_ts:
         context["thread_ts"] = thread_ts