Using slack makes me so depressed. The interactions we have today pale in comparison to what we had in IRC 30 years ago.
Of course I accept we're stuck with slack. I just have no clue what to write with such a limited interface. The above posted link is a great example of making the most of a tiny interface and coming up short compared to... 30 years ago
impulser_
I'm glad more people are catching onto lightweight CLI tools and using skills to give llms more tools. It's way better than MCP. I been doing this for awhile now and it's just the best way to gets LLMs to do things with APIs built for humans.
show comments
Wuzzy
I believe in an MCP-less future of agent-service interactions and have recently submitted this general alternative (which also supports Slack) based on curl: https://github.com/imbue-ai/latchkey
With that said, a specialized tool like this will almost certainly work better if Slack is the only service you want your agents to interact with. I like that the auth is transparent.
Hansenq
Oh this is smart! Reading where Slack stores the local data in your filesystem instead of using their API/MCP (which they charge for).
Very clever; similar to OpenAI launching Atlas when websites start blocking bot requests--just build your own browser so your bot becomes an actual user.
apimade
Warning: in Enterprise (Grid) your account will likely be flagged as hijacked, and all of your sessions will be killed.
Slack implemented session hijacking detection a while ago, and using LLM’s without throttling will very likely result in alerts. If you’re on Enterprise; I’d suggest re-slopping a re-implementation of this with ghost Chrome puppeteer.
show comments
BlueOrigin50
Oh nice. I just installed and it works pretty well. It wasn't able to find the user names on the thread though.
show comments
slopusila
how about support for "auth import-token" so you dont need to keep SLACK_TOKEN in env
Using slack makes me so depressed. The interactions we have today pale in comparison to what we had in IRC 30 years ago.
Of course I accept we're stuck with slack. I just have no clue what to write with such a limited interface. The above posted link is a great example of making the most of a tiny interface and coming up short compared to... 30 years ago
I'm glad more people are catching onto lightweight CLI tools and using skills to give llms more tools. It's way better than MCP. I been doing this for awhile now and it's just the best way to gets LLMs to do things with APIs built for humans.
I believe in an MCP-less future of agent-service interactions and have recently submitted this general alternative (which also supports Slack) based on curl: https://github.com/imbue-ai/latchkey
With that said, a specialized tool like this will almost certainly work better if Slack is the only service you want your agents to interact with. I like that the auth is transparent.
Oh this is smart! Reading where Slack stores the local data in your filesystem instead of using their API/MCP (which they charge for).
Very clever; similar to OpenAI launching Atlas when websites start blocking bot requests--just build your own browser so your bot becomes an actual user.
Warning: in Enterprise (Grid) your account will likely be flagged as hijacked, and all of your sessions will be killed.
Slack implemented session hijacking detection a while ago, and using LLM’s without throttling will very likely result in alerts. If you’re on Enterprise; I’d suggest re-slopping a re-implementation of this with ghost Chrome puppeteer.
Oh nice. I just installed and it works pretty well. It wasn't able to find the user names on the thread though.
how about support for "auth import-token" so you dont need to keep SLACK_TOKEN in env