How to Use Claude in Slack

Anthropic publishes an official Claude for Slack app that team members can @mention in channels and direct messages to ask questions, get summaries, or draft content. Once your workspace admin installs it, you do not need a separate Claude account to use it in Slack. Teams like fenbs use a shared project record to capture the decisions and action items that Claude surfaces in Slack, so they live in the project rather than disappearing into chat history.

Each conversation with Claude in Slack starts fresh. Claude does not retain memory between separate messages unless they are in the same thread. Understanding that limit helps you ask better questions and decide what to move out of Slack and into a project record that persists.

How to install Claude in Slack

1. A Slack workspace admin visits the Slack App Directory↗ (opens in a new tab) and searches for Claude.
2. Select the Claude by Anthropic app and click Add to Slack. Review the permissions it requests.
3. Once installed, any team member can invite Claude to a channel with /invite @Claude, or start a direct message with Claude from the Apps section of the sidebar.
4. In a channel, @mention Claude followed by your question. In a DM, type directly. Claude responds in the thread.

Check Anthropic's Claude for Slack documentation↗ (opens in a new tab) for current installation steps and available plans, as availability and features change over time.

What Claude can do in Slack

In a channel or thread, Claude can answer questions, draft messages, summarize what you paste into the conversation, explain technical concepts, and suggest approaches to a problem. It is most useful for tasks where a quick, knowledgeable answer or a first draft saves time.

Claude reads the thread it is in — the messages above in the same conversation — but it does not read other channels or previous messages outside the current thread. If you need Claude to know about something discussed in another channel last week, paste the relevant context into the current conversation.

Context limits and what to keep in mind

Every @mention of Claude in a new thread or DM starts a conversation with no memory of previous ones. If you asked Claude to help with a project yesterday, it does not remember that today. This is by design — Slack conversations are ephemeral, and Claude does not silently read your whole history.

This limit matters most for ongoing projects. If your team uses Claude to help with decisions and planning, the agreed decisions need to live somewhere that survives beyond the Slack thread. Otherwise each new Claude conversation gets the same question and may give a different answer.

Permissions and data handling

When installed, Claude for Slack requests permissions that let it read messages in channels it is added to and respond to @mentions. It does not silently monitor channels or read messages that do not @mention it in a public channel. In private channels, the admin controls which apps have access.

If your team discusses sensitive business, legal, or personal information in Slack, check Anthropic's privacy documentation before involving Claude in those channels. Treat Claude in Slack the same way you would treat any external AI service: do not paste information that should not leave your organization unless you have confirmed the data handling terms.

Getting better results from Claude in Slack

Claude in Slack works best for focused questions and short drafts. Long multi-part requests work less well in the back-and-forth of a channel. When you need Claude to work through a complex problem, do that in Claude.ai where you have more space; use Slack for quick questions and brief outputs that benefit from being visible to the channel.

Moving agreed decisions out of Slack

Slack is where decisions happen. Slack is not where decisions live. An important rule agreed in a channel thread is at risk the moment the thread scrolls out of view. Someone who was not in the channel when it happened has no way to find it. A new AI session has no idea it exists.

When a Slack conversation produces a decision or an action item, move it to your project record. In fenbs, that means adding a Decision with the rule, who decided it, and the date. Any connected AI app reads those Decisions and rules at the start of each session, before looking at anything else. See how it works for the full team setup.

How to do this with fenbs

fenbs does not connect to Slack directly. Its value here is as the persistent record where your team moves the things that matter from chat into the project.

1. Create a free account. Add your team as members and give each person an appropriate role.
2. Connect a supported AI app from Integrations so Claude, ChatGPT, Cursor, or another assistant can read and update the project record.
3. When a Slack conversation produces a decision, add it to fenbs as a Decision. Include who decided it and the reason, even if that reason seems obvious today.
4. When a Slack conversation creates a task, add it to the kanban board in fenbs. The task holds the action; Slack holds the conversation that led to it.
5. At the start of each new AI session, ask the assistant to read the project context — Rules first, then Where we left off. It gets the decisions from Slack without you re-explaining the thread.