Your agents, on your Slack team
One click from NanoClaw setup and your agent is a real Slack bot — with its own name, its own icon, and its own presence in your workspace. No Slack app dashboard, no copy-pasting tokens.
How it works
Slack’s app setup, automated — without your agents’ keys ever leaving home.
Connect your NanoClaw account
During setup, your NanoClaw install signs in to NanoCo’s app-manager service with your install token. Nothing to configure by hand.
Approve the NanoClaw manager app
A one-time approval per Slack workspace. You (or your workspace admin) approve the NanoClaw manager app in Slack — that’s what lets NanoClaw create agent bots on your behalf.
Agents become real Slack bots
Each agent is provisioned as its own Slack app — its own name, its own icon, its own bot identity. Not one shared bot pretending to be many.
Tokens come home
The bot tokens are handed straight to your machine, and your agents connect to Slack over Socket Mode from there. NanoCo doesn’t keep them.
Every agent is its own bot
NanoClaw agents aren’t threads of one shared bot. Each one gets its own Slack app, so your team can tell them apart at a glance.
Own name and icon
Your research agent, your ops agent, and your scheduling agent each show up under their own identity — name, avatar, profile.
DM them directly
Open a direct message with exactly the agent you need, the same way you’d DM a teammate.
Shared rooms
Invite several agents into one channel with you. Mention the one you want, or let sibling agents work a problem together in the open.
Built not to hold your keys
The same posture as the rest of NanoClaw: your machine is the source of truth.
Bot scopes only
Agent apps request a fixed, minimal set of bot scopes — read and write messages in conversations they’re part of. No user tokens, no admin scopes, no workspace-wide data export.
Admin approval respected
If your workspace requires admin approval for apps, the normal Slack approval flow applies. Admins see exactly which apps are installed and what scopes they hold.
No public URL needed
Agents connect over Socket Mode — an outbound connection from your machine to Slack. No webhooks, no open ports, no tunnel, nothing exposed to the internet.
Manager tokens encrypted
The per-workspace manager credential lives on NanoCo’s service, encrypted at rest. It can create and remove agent apps — it is not a message-reading token.
Agent tokens stay on your machine
Your agents’ bot tokens are delivered to your host and stored there. NanoCo never stores them, so NanoCo can never read your agents’ conversations.
Your host initiates everything
Your machine always makes the call — to Slack and to NanoCo’s service. Nothing on the internet can reach into your NanoClaw install.
The full scope list
The full scope list
Every agent app requests exactly these bot scopes — enough to read and respond in the conversations it’s invited to, and nothing else:
app_mentions:readchat:writechannels:historygroups:historyim:historympim:historychannels:readgroups:readmpim:readim:writempim:writeusers:readreactions:write Getting started
Install NanoClaw, run setup, pick Slack, and choose “Create it for me”. Setup walks you through the rest.
$ git clone https://github.com/nanocoai/nanoclaw.git nanoclaw-v2
$ cd nanoclaw-v2
$ bash nanoclaw.sh
# in setup: choose Slack → “Create it for me” Already running NanoClaw? Re-run setup and add Slack to an existing agent — provisioning works the same way.
Frequently asked questions
Does this work on a free Slack plan?
Does this work on a free Slack plan?
What do workspace admins see?
What do workspace admins see?
Can an agent read every message in my workspace?
Can an agent read every message in my workspace?
How do I revoke access?
How do I revoke access?
Does my computer need to be reachable from the internet?
Does my computer need to be reachable from the internet?
Where do my agents actually run?
Where do my agents actually run?
How accurate are the agents’ responses?
How accurate are the agents’ responses?
Need help?
Email us at support@nanoco.ai — no account needed, and we respond within two business days.