Unified Agent + reusable Go agent core.
Merge pull request #15 from quailyquaily/docs/slack
docs: add pending slack thread context note
+14
+14
docs/slack.md
+14
docs/slack.md
···
159
159
- Bus ordering/sharding key is `conversation_key = slack:<team_id>:<channel_id>`.
160
160
Thread is not part of sharding, so different threads in the same channel share the same serialized worker.
161
161
162
+
### Pending: Thread-Aware Context for `smart` Group Trigger
163
+
164
+
Current limitation:
165
+
166
+
- In `slack.group_trigger_mode=smart`, when a user first `@` mentions the bot inside an existing thread, the bot knows the current message is in a thread (`thread_ts` is present), but its LLM history is still channel-scoped rather than thread-scoped.
167
+
- As a result, the bot may miss earlier messages from that thread, or mix them with unrelated messages from the same channel.
168
+
169
+
Pending requirement:
170
+
171
+
- When the bot is triggered from a Slack thread, it should have a reliable way to perceive thread context before deciding or replying.
172
+
- At minimum, this means the runtime should provide thread-scoped context to addressing and main task execution, instead of relying only on channel-scoped rolling history.
173
+
- Acceptable implementations may include fetching prior thread replies on demand, maintaining thread-specific short-term history, or both.
174
+
- The goal is that when a user says "as discussed above" and then `@` mentions the bot in a thread, the bot can understand what "above" refers to within that thread.
175
+
162
176
## 11. Heartbeat Delivery
163
177
164
178
`mistermorph slack` can run heartbeat together with Slack runtime when: