Claude Code in Slack changedslack
Nearest release: v2.1.319, published under an hour after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 6 Nov 2026 00:08 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 6 Nov 2026 00:37 UTC.
Upstream edited
Recorded here
Lines+8added
Lines−11removed
From line
16
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits18to this page, all time
The whole hunk
from line 16, old and new numbered
/
from line 16
1616
1717## Use cases
1818
19* **Bug investigation and fixes**: Ask Claude to investigate and fix bugs as soon as they're reported in Slack channels.
20* **Quick code reviews and modifications**: Have Claude implement small features or refactor code based on team feedback.
21* **Collaborative debugging**: When team discussions provide crucial context (for example, error reproductions or user reports), Claude can use that information to inform its debugging approach.
19* **Bug investigation and fixes**: Describe a bug and ask Claude to investigate and fix it.
20* **Quick code reviews and modifications**: Have Claude implement small features or refactor code.
2221* **Parallel task execution**: Kick off coding tasks in Slack while you continue other work, receiving notifications when complete.
2322
2423## Prerequisites
from line 86
8786
8887### Context gathering
8988
90**From threads**: When you @mention Claude in a thread, it gathers context from all messages in that thread to understand the full conversation.
89* **From threads**: when you first @mention Claude in a thread, it gathers context from your messages and its own in that thread.
90* **From channels**: when you @mention Claude directly in a channel, it looks at your recent messages and its own in that channel, and at the channel's name, topic, and description.
9191
92**From channels**: When mentioned directly in a channel, Claude looks at recent channel messages for relevant context.
92This context helps Claude understand the problem, select the appropriate repository, and inform its approach to the task. To give Claude something a teammate wrote, such as an error report, paste its text into the message where you @mention Claude.
9393
94This context helps Claude understand the problem, select the appropriate repository, and inform its approach to the task.
95
9694> [!WARNING]
9795>
9896> When @Claude is invoked in Slack, Claude is given access to the conversation context to better understand your request. Claude may follow directions from other messages in the context, so users should make sure to only use Claude in trusted Slack conversations.
from line 156
158156### Writing effective requests
159157
160158* **Be specific**: Include file names, function names, or error messages when relevant.
161* **Provide context**: Mention the repository or project if it's not clear from the conversation.
159* **Provide context**: Mention the repository or project.
162160* **Define success**: Explain what "done" looks like. Should Claude write tests? Update documentation? Create a PR?
163* **Use threads**: Reply in threads when discussing bugs or features so Claude can gather the full context.
164161
165162### When to use Slack vs. web
166163
167**Use Slack when**: Context already exists in a Slack discussion, you want to start a task asynchronously, or you're collaborating with teammates who need visibility.
164**Use Slack when**: You want to start a task asynchronously, or you're collaborating with teammates who need visibility.
168165
169166**Use the web directly when**: You need to upload files, want real-time interaction during development, or are working on longer, more complex tasks.
170167
No line in this hunk matches that.