Good habits for working with Claude Tag changedclaude-tag/users/good-habits
Nearest release: v2.1.246, published 6 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+4added
Lines−0removed
From line
20
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits22to this page, all time
### Mentioning people who aren't in the channel
The whole hunk
from line 20, old and new numbered
/
from line 20
2020* **Give Claude the destination, not the route.** State the outcome you want and let Claude work out the steps; the [definition of done](#give-every-task-a-definition-of-done) below makes that concrete.
2121* **Tolerate the mess.** A first draft posted in the thread is more useful than a polished one in a DM. The thread is the workspace, not the deliverable.
2222
23### Mentioning people who aren't in the channel
24
25Claude 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.
26
2327## Write tasks that close
2428
2529The 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.
No line in this hunk matches that.