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 28 Sep 2026 22:07 UTC.
Upstream edited
Recorded here
Lines+20added
Lines−20removed
From line
62
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 62, old and new numbered
/
from line 62
6262
6363Without a stated end condition, Claude can't declare the thread finished and you can't stop checking it. The end condition you write determines who can close the thread, and the table matches each kind of condition to who closes it.
6464
65| End condition | Who closes it | Example |
66| :----------------------------- | :----------------- | :---------------------------------------------------- |
67| An objective check passes | Claude, on its own | "Done when CI is green" |
68| You approve a prepared result | You, one click | "Draft the status memo and post it here for approval" |
69| You choose between options | You, one word | "Research approaches A and B and recommend one" |
70| No verifiable condition exists | No one | Reframe it as a question instead of a task |
65| End condition | Who closes it | Example |
66| :- | :- | :- |
67| An objective check passes | Claude, on its own | "Done when CI is green" |
68| You approve a prepared result | You, one click | "Draft the status memo and post it here for approval" |
69| You choose between options | You, one word | "Research approaches A and B and recommend one" |
70| No verifiable condition exists | No one | Reframe it as a question instead of a task |
7171
7272Two refinements make the table work in practice:
7373
from line 132
132132
133133Channel 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.
134134
135| | A team channel | Your own channel | A DM |
136| :---------------- | :----------------------------------------- | :---------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------- |
137| Access | The channel's connections, set by an admin | The channel's connections, set by an admin | Your own claude.ai connectors |
138| Memory | Channel memory the team builds | Channel memory you build | Outside channel and workspace memory |
139| Who sees the work | Everyone in the channel | You, plus anyone you invite | You |
140| Billing | The organization | The organization | Your seat |
141| Best for | Shared work the team should see and steer | Your own questions, digests, and follow-ups, kept where a teammate can pick them up | Personal tasks on your own connections, or data that shouldn't run through a shared channel connection |
135| | A team channel | Your own channel | A DM |
136| :- | :- | :- | :- |
137| Access | The channel's connections, set by an admin | The channel's connections, set by an admin | Your own claude.ai connectors |
138| Memory | Channel memory the team builds | Channel memory you build | Outside channel and workspace memory |
139| Who sees the work | Everyone in the channel | You, plus anyone you invite | You |
140| Billing | The organization | The organization | Your seat |
141| Best for | Shared work the team should see and steer | Your own questions, digests, and follow-ups, kept where a teammate can pick them up | Personal tasks on your own connections, or data that shouldn't run through a shared channel connection |
142142
143143[Routines](/docs/claude-tag/users/proactivity) belong to a channel too. You set standing work up in the channel where it should post, and it runs with that channel's connections. [Work from your own channel](/docs/claude-tag/users/use-cases/your-own-channel) shows what a channel of your own is good for.
144144
from line 160
160160
161161When Claude gets something wrong, or learns something worth keeping, where you put the fix decides who else benefits and whether you can do it yourself.
162162
163| You want Claude to know | Put it in | Who can write it | Reaches |
164| :---------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------- |
165| How this channel should behave: format, tone, when to respond | [**Channel memory**](/docs/claude-tag/users/memory) (say it and ask Claude to remember) | Anyone in the channel | This channel; the whole workspace only if Claude saves it as a workspace note from a public channel |
166| Conventions and setup for one repository: file layout, PR labels, dependencies to install | **`CLAUDE.md`** at the repo root ([loaded when the repo is](/docs/claude-tag/admins/configure-github#what-loads-from-a-repository)) | Anyone with repo write | Any session that works in that repo, from any channel |
167| Standing rules for this channel that outrank memory | The [**Configure** page](#configure-claude-for-a-channel), in the **Channel instructions** field | Channel members, unless an admin has [restricted it](/docs/claude-tag/admins/attach-to-scope#restrict-who-can-set-channel-instructions) | This channel |
168| How to use a tool correctly, or follow a specific process, org-wide | [**A skill**](/docs/claude-tag/admins/skills-repo) in your org's plugin marketplace | An organization Owner adds it; anyone can ask Claude to open a PR proposing the change | Every channel under the scope it's attached to |
169| Standing rules across many channels | [**Custom instructions**](/docs/claude-tag/admins/attach-to-scope#add-custom-instructions) on a workspace or organization scope | An organization Owner, in the console | Every session in that scope |
163| You want Claude to know | Put it in | Who can write it | Reaches |
164| :- | :- | :- | :- |
165| How this channel should behave: format, tone, when to respond | [**Channel memory**](/docs/claude-tag/users/memory) (say it and ask Claude to remember) | Anyone in the channel | This channel; the whole workspace only if Claude saves it as a workspace note from a public channel |
166| Conventions and setup for one repository: file layout, PR labels, dependencies to install | **`CLAUDE.md`** at the repo root ([loaded when the repo is](/docs/claude-tag/admins/configure-github#what-loads-from-a-repository)) | Anyone with repo write | Any session that works in that repo, from any channel |
167| Standing rules for this channel that outrank memory | The [**Configure** page](#configure-claude-for-a-channel), in the **Channel instructions** field | Channel members, unless an admin has [restricted it](/docs/claude-tag/admins/attach-to-scope#restrict-who-can-set-channel-instructions) | This channel |
168| How to use a tool correctly, or follow a specific process, org-wide | [**A skill**](/docs/claude-tag/admins/skills-repo) in your org's plugin marketplace | An organization Owner adds it; anyone can ask Claude to open a PR proposing the change | Every channel under the scope it's attached to |
169| Standing rules across many channels | [**Custom instructions**](/docs/claude-tag/admins/attach-to-scope#add-custom-instructions) on a workspace or organization scope | An organization Owner, in the console | Every session in that scope |
170170
171171The first three are yours to write. Skills and wider-scope custom instructions are attached by an Owner, but you can still ask Claude to draft a skill change as a pull request for an admin to review:
172172
No line in this hunk matches that.