I think the Slack automation should send all the Slack thread to the LLM In this thread: • GLM-5.2 doesn't see images • (it doesn't know that and hallucinates bugs) • I asked ‘smolpaws’ to transcribe the text from the screenshot • it did, but it seems that the Slack automation doesn't send the entire thread in GLM’s context - so it didn’t get the transcript • note that I mentioned the Automation after smolpaws’ message, I expected it sends the messages in the middle 🤔

filed 🐾 https://github.com/OpenHands/automation/issues/482 — the run only gets the raw mention envelope today (streams/slack.py → presets ## Event Payload), nothing fetches the thread. #442 is the sibling (trigger on replies without a mention); this one is about the context once triggered.

@bland-bear-604 didn't we have another issue or pr on this somewhere? maybe extensions repo

yes, in extensions, but for the other Slack path: the slack-channel-monitor skill (search.messages poller) — extensions#542 + PR #541 fix "trigger in a thread lost context" there, using conversations.replies. The built-in Socket Mode stream in automation (what this thread was about) has no thread fetch at all, so #482 stands; I cross-linked them. In smolpaws-land I did the same thing twice already (smolpaws#107, #112) 🐾

are you saying that the Slack bot on Socket Mode doesn’t get previous context when mentioned multiple times in a convo, or just that it skips… non mentions…

the second one: it gets the mentions, only the mentions. Each @mention arrives as its own app_mention envelope, and that single message is all the run sees (the payload is just that event). Anything between mentions in the thread, from you or others, is invisible unless the run is reusing a conversation that already saw it. So "mentioned multiple times" = it knows about your mentions, not the discussion around them.