Meet NanoCo, maintainers of NanoClaw: we raised $12M to give every member of your team a professional assistant →
Add to Slack

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.

1

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.

2

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.

3

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.

4

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

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.

Terminal
$ 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?

Yes. Agents are standard Slack apps connecting over Socket Mode, which works on every Slack plan. There’s no paid Slack feature involved.

What do workspace admins see?

Two things. First, the NanoClaw manager app requesting approval — a one-time, per-workspace step. Second, each agent appears as its own app in the workspace’s app list, with its bot scopes visible for review. If your workspace requires admin approval for new apps, that flow applies to every install — nothing bypasses it.

Can an agent read every message in my workspace?

No. Agents hold bot scopes only, so they can read messages solely in the channels, group DMs, and direct messages they’ve been invited to — the same visibility as any Slack bot.

How do I revoke access?

From NanoClaw, delete an agent’s app or disconnect the whole workspace from setup. From Slack, admins can remove any of the apps directly in workspace settings at any time — removing the manager app also removes NanoClaw’s ability to provision new agents there.

Does my computer need to be reachable from the internet?

No. Everything is outbound: your agents connect to Slack over Socket Mode, and your install talks to NanoCo’s app-manager service when provisioning. No public URL, no port forwarding.

Where do my agents actually run?

On your machine, same as always. NanoClaw agents run in containers on your own hardware. Add Agent to Slack only automates the Slack app creation — the agents, their memory, and their tokens stay local.

How accurate are the agents’ responses?

NanoClaw agents are powered by large language models, so their responses can be inaccurate, incomplete, or confidently wrong. Review agent output before acting on it — especially for decisions, code, or anything consequential. Agents can also take actions on your behalf, which is why sensitive operations route through human approval.

Need help?

Email us at support@nanoco.ai — no account needed, and we respond within two business days.