agent-slack CLI
Shares rank 73 of 86 privilege escalation tools by recommenders
Lets AI agents work with Slack by reading its local data instead of the API or MCP, which people find works better for a Slack-only setup. Critics warn that accounts may be flagged as hijacked and sessions killed.
Lets AI agents work with Slack by reading its local data instead of the API or MCP, which people find works better for a Slack-only setup. Critics warn that accounts may be flagged as hijacked and sessions killed.
6 people gave an opinion
- recommend it
- 5
- criticize it
- 1
- approval share
- 83%
Recommended in 2 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 5 people recommend itNeeds 10 or more, not met.
- 5 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 2 of 13 monthsNeeds 4 or more, not met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Reads local Slack data, not the API
“Oh this is smart! Reading where Slack stores the local data in your filesystem instead of using their API/MCP”
Comment from 6 Feb 2026 in “Slack CLI for Agents (OSS)” CLI preferred over MCP
“We started using it when we realized that CLI would win over MCP.”
Comment from 23 Aug 2026 in “SlackCLI” Specialized tool works better for Slack
“a specialized tool like this will almost certainly work better if Slack is the only service”
Comment from 6 Feb 2026 in “Slack CLI for Agents (OSS)” Existing tools did not fit their needs
“couldn't find anything out there that worked for us, so we coded our own agent-slack CLI”
Comment from 5 Feb 2026 in “Slack CLI for Agents (OSS)”
What people warn about
Each mark is one comment
Account may be flagged as hijacked
“your account will likely be flagged as hijacked, and all of your sessions will be killed”
Comment from 7 Feb 2026 in “Slack CLI for Agents (OSS)”
Other privilege escalation tools people recommend
The four most recommended other privilege escalation tools, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
See all 86 privilege escalation tools, rankedWhat people said
5 of the 6 comments that mention it, newest first. Each links to the original comment.
“We started using it when we realized that CLI would win over MCP.”
“your account will likely be flagged as hijacked, and all of your sessions will be killed”
“a specialized tool like this will almost certainly work better if Slack is the only service”
“Oh this is smart! Reading where Slack stores the local data in your filesystem instead of using their API/MCP”
“couldn't find anything out there that worked for us, so we coded our own agent-slack CLI”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.