@grinich@SlackHQ search api requiring an @ and only granting a 60s token is also insane
I’ve seen one product get around this by slowly building their own index of all slack messages for them to query
@lifeof_jer humans have been accidentally wiping databases for decades, the blame in those cases was on whoever handed them prod db creds. so the blame here is on whoever left a broadly scoped api token lying around.
unfortunately our internal inspect/devin-style agent is 2-4x cheaper than devin, 2x smarter than devin, and has a much better slack communication style. it did take us a month to build (part-time) though