Good habits for working with Claude Tag changedclaude-tag/users/good-habits
Nearest release: v2.1.283, published 10 hours before 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 26 Sep 2026 05:33 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 26 Sep 2026 05:37 UTC.
Upstream edited
Recorded here
Lines+13added
Lines−1removed
From line
24
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits13to this page, all time
### Mentioning a user group
The whole hunk
from line 24, old and new numbered
/
from line 24
2424
2525Claude can't add anyone to a channel, and it doesn't decide whether a mentioned person is notified. Slack's prompt to invite or notify someone who isn't in the channel appears only for messages you type yourself; it never applies to messages Claude posts. Slack delivers Claude's mention the way it delivers any app-posted message. In a public channel, the person is notified in their Activity view even though they haven't joined. In a private channel, they aren't notified and can't see the message until someone invites them. If you want someone to follow a thread Claude is working in, invite them yourself.
2626
27### Mentioning a user group
28
29Ask Claude to notify a user group, such as an on-call rotation. Claude mentions the group, and Slack notifies its members. If Claude writes the group's @handle as plain text instead of mentioning the group, Slack notifies no one, so ask Claude to notify the group rather than to include its handle.
30
31If Claude replies with re-approval guidance instead of mentioning the group, your workspace's Claude app predates a Slack permission that group mentions need. Ask a Slack admin to re-approve the app, and send them [Slack app permissions](/docs/claude-tag/admins/troubleshooting#slack-app-permissions).
32
33Claude never pings @channel, @here, or @everyone.
34
2735## Write tasks that close
2836
2937The phrasing of a task determines whether it has a verifiable end state, what form the result takes, and how Claude responds while working on it.
from line 126
118126
119127Start a new thread for each new task. The fresh session begins with full room for the work, picks up any configuration changes made since the old thread began, and keeps each piece of work reviewable on its own. A thread that accumulates many tasks eventually [grows past what one session can hold](/docs/claude-tag/users/troubleshooting#this-conversation-is-too-long-for-me-to-process).
120128
129To start several independent tasks from inside an existing thread, [ask Claude to open a thread for each](/docs/claude-tag/users/prompt-library#fan-out-work-across-threads). To continue the current discussion in a fresh thread, run [`!fork`](/docs/claude-tag/users/commands#fork-a-thread).
130
121131### Pick the right surface
122132
123133Channel access belongs to the channel, and DM access belongs to you. A channel can also be yours alone. Create one with just you and Claude in it, and it works the same way a team channel does. The table compares the three surfaces.
from line 146
136146
137147Reading a public channel's full history, rather than what search finds, needs Claude to be a member of that channel. If it says it can't read a public channel, `/invite @Claude` from inside that channel adds it.
138148
149Claude can also post into other public channels, and the rules depend on where you ask. See [What Claude can do in other channels](/docs/claude-tag/concepts/how-it-works#what-claude-can-do-in-other-channels).
150
139151A private channel is readable only from inside it. Inviting Claude lets it work in that channel, but Claude can't read the private channel's messages from any other channel or DM. To ask about a private channel, ask in that channel.
140152
141Channels in a different workspace stay out of reach. Claude also doesn't answer in a [Slack Connect channel](/docs/claude-tag/admins/restrict-access#slack-connect-channels), one shared with another company.
153Claude can't post into a channel in a different workspace, and it doesn't answer in a [Slack Connect channel](/docs/claude-tag/admins/restrict-access#slack-connect-channels), one shared with another company.
142154
143155When more than one surface would work, prefer a channel. Work that happens there compounds, because Claude can draw on it in later threads and teammates can find it, redirect it, or build on it.
144156
No line in this hunk matches that.