HyperCLI for Slack
Your agents, where you work.
Not another tab. Your agent lives in Slack — in channels, in DMs, in threads — doing real work where the conversation already is.
Two clicks · No IT ticket · Only sees channels you invite it to
It knows how Slack works.
A good teammate has channel manners. So does your agent.
Mention it in any channel
Tag it mid-conversation and it picks up the thread's full context — no re-explaining what everyone just said.
Or keep it one-on-one
Direct message for personal delegation — your drafts, your research, your follow-ups.
It works in threads
Long tasks stay in their thread — progress updates and the final delivery, without flooding the channel.
It speaks first
When something it's watching changes — a competitor, a metric, a deadline — it posts. You don't have to ask twice.
What it looks like in #marketing.
@agent we're launching thursday — can you draft the announcement thread and make 3 image options?
On it — I'll use the positioning from Monday's doc. Drafts in this thread within the hour.
Done — thread draft (2 versions) + 3 images. Also: your competitor teased something for Wednesday. Want me to prep a response angle just in case?
It only sees what you invite it to.
Most AI apps are vague about permissions. Here's exactly how yours behaves:
Invited channels only. No access to channels it hasn't been added to — ever. Remove it from a channel and it forgets the room exists.
Minimal scopes, listed openly. Every permission it requests is documented, with why. No wildcard access.
Your data isn't training data. Conversations stay between you, your team, and your agent.
Admin-friendly plumbing. Socket mode, relay, or HTTP — your workspace admin picks the connection model. Uninstall removes everything.
Live in your workspace in two minutes.
Add to Slack. Standard OAuth install — approve the scopes, done.
Invite it to a channel. /invite @agent — start with one channel, add more when it earns them.
Hand it something real. @mention it with a task you'd give a new hire. Check the thread in an hour.
Workspace admin questions.
- What can it read?
- Messages in channels it's been invited to, DMs sent to it, and files shared with it directly. Nothing else — no workspace-wide history, no private channels it isn't in.
- Where does the work happen?
- On the agent's own cloud machine, not inside Slack. Slack is the conversation; the browsing, documents, and media generation happen on its machine and get delivered back to the thread.
- How do we remove it?
- Remove it from a channel like any member, or uninstall the app to disconnect it from the workspace entirely. Uninstalling revokes all access immediately.