Discussion about slack bot in 🧵 cc @limited-student-10747 @calm-artist-7206 I didn't want to pollute the other thread

Sounds good to me, it would use slack bolt?

Sorry, I’m not very sure what you mean by in-house solution?

I think, as of now, automation repo doesn’t support an outbound socket connection (option 3), though it’s likely the best for a Slack agent. No permanent polling when events don’t happen; no exposure to the world either. So in my understanding, if we want to make it here, we could start with implementing it, and we can see later how to integrate it?

A small summary to make things clear: What I did was to migrate our Slack bot from polling Slack every minute to reacting instantly when mentioned. The old setup checked Slack ~1,440 times/day and it was not so effective, i.e., it had blind spot in the mentions. So now we have: - Opened a persistent connection to Slack (Socket Mode) so Slack pushes mentions to us directly. Note that no public endpoint here, which matters since ours is locked behind a login page - Built a small bridge process that forwards those mentions into Agent Canvas's existing "event trigger" feature (the bridge is my in-house solution, we can incorporate that in the agent-canvas potentially. Perhaps in-house was the wrong word 🫣 I wanted to say a solution which is not in canvas). - Rewrote the bot script Now it seems that the reply time is down to ~6–12s, and polling traffic is gone. Tested live in both workspaces including thread follow-ups. You are welcome to test it and see if it is robust and works properly. You just need: • to invite the oss-openhands app into the channel you want to use it. • having your slack mail whitelisted (@calm-artist-7206 if you want to test it, you should send me your mail. For instance, just me, Graham and everyone with openhands.dev mail are in the list)

OK, sounds good. We can consider what would need to change in the core software too