← Learn
Playbook · 10 steps · checked 4 October 2026 · 0 adopted

Claude Tag

At most ten steps, in order of how much they help. Each step is from Anthropic's own pages, linked. Re-checked against those pages every week; anything that can't be confirmed is marked unverified rather than removed.

  1. 01

    Set it up once, as an Owner, and pilot in one channel

    Setup needs the Owner role in a Team or Enterprise Claude organisation, Routines turned on (Admin settings > Capabilities), a Slack workspace admin, and one public channel. Go to claude.ai/admin-settings/claude-tag and click Start setup. Install the Claude app from the Slack Marketplace, run /invite @Claude in a channel, then send @Claude connect with no other text. Paste the pairing code on the setup page within 15 minutes. Pick your pilot channel, then click Launch Claude Tag. Check it works with @Claude what can you access from this channel?. Organisations with Zero Data Retention or customer-managed encryption cannot use it. (set up Claude Tag, overview, get started)

  2. 02

    Fund it and cap the spend before anyone tags Claude

    On a Team plan, nothing runs until you buy usage credits at claude.ai/admin-settings/usage. Then set a monthly spend limit at claude.ai/admin-settings/usage/claude-tag; you can add per-channel limits too. There is no published per-task cost, so start with a limit you are comfortable with and watch the per-channel breakdown. Claude reading a channel is not billed, but work it starts on its own is; turn off Respond automatically in a channel to stop that. Fast mode (@Claude !fast) is quicker but costs more per token, so keep it for urgent threads. When the limit is reached, Claude stops and says so in the thread. (set a spend limit, restrict where Claude Tag operates, models and fast mode)

  3. 03

    Name the outcome and say what "done" means

    Put the result you want in the first sentence, for example "post the project status and tag me when it's up", not "look at this". If the background is already in a thread or a connected tool, link it rather than retelling it. Give a check Claude can see ("done when CI is green") or a result you approve, and ask for proof such as a link, test output or diff. Say which decisions it may make alone and which come back to you. For costly changes, write the rules it must keep and what it must not touch. (good habits, prompt library)

  4. 04

    One task per thread, steered in the thread

    Each thread is its own session. Keep follow-ups in the same thread, and start a new thread for a new task; a crowded thread can grow too long. You do not need to re-mention Claude once it is in a thread: reply to correct it. A quiet thread usually means it is still working; @Claude !status checks, @Claude !restart replaces a stuck session, and @Claude !help lists commands. Files that exist only in the sandbox are lost when the thread goes quiet, so ask Claude to post them in the thread or push a branch. (good habits, commands, security and data handling)

  5. 05

    Give Claude its own narrow accounts, attached only where needed

    In channels Claude acts as itself, not as you, and starts with access to Slack only. For each tool, create an account for Claude (for example a dedicated email address), give it the narrowest role, read-only where possible, and add its key as a connection in an Access bundle. Do one tool end to end before the next. Anyone in a channel can use what that channel's bundle allows, so attach a sensitive bundle to one private channel, not the whole workspace. Keys are never shown again and never enter the sandbox, and outbound traffic only reaches hosts you allow. (set up Claude Tag, security and data handling)

  6. 06

    Connect GitHub, grant only the repositories you need, and name the repo

    An owner of both your GitHub organisation and your Claude organisation links GitHub at claude.ai/admin-settings/github; then grant repositories on the bundle's Repositories tab. A session starts with no code checked out, so name the repository in the first message of a code task. Once cloned, the repo's CLAUDE.md, .claude/rules/ and .claude/skills/ load; hooks and .mcp.json do not. Put install steps for extra tools in CLAUDE.md. Claude opens pull requests as the Claude GitHub App, so the person who asked can approve alone; require two approvals in branch protection if you want a second reviewer. (configure GitHub access, Claude Tag for Claude Code users)

  7. 07

    Enforce hard limits outside the chat, and check work by its stakes

    Instructions in a message steer Claude but do not stop it; use repository permissions, branch protection and required checks for anything it must never do. Text Claude reads, such as a web page, a pull request comment or a Slack thread, can contain prompt injection; Claude is designed to treat it as material, not orders, but keep that in mind. Skim a summary; read carefully anything going to a customer or changing a system. Pages Claude publishes can be opened by anyone with access to the channel, which in a public channel means the whole workspace. (good habits, get started, personal connectors, security and data handling)

  8. 08

    Teach each channel once, in memory or channel instructions

    Say "@Claude remember for this channel: keep replies short and link the source". Anyone in the channel can save, read and correct memory; check it with "what do you remember about this channel?" and prune stale entries. Keep entries short and link longer runbooks instead. For rules that outrank memory, use the Channel instructions field on the channel's Configure page (the footer link, or @Claude !configure). Note that workspace notes saved from a public channel are read in every channel of the workspace. (what Claude Tag remembers, good habits)

  9. 09

    Decide who can use it and where

    By default anyone in the paired Slack workspace can use Claude, even without a Claude account. An Owner can turn on Restrict to your organization (Team) or restrict by role (Enterprise). Claude is off in channels with Slack guests by default and does not work in Slack Connect channels. To stop it, ask it to stay quiet in a thread, /remove @Claude from a channel, or turn it off in admin settings. Removing a channel's scope, uninstalling the app or disconnecting the workspace deletes data. On Team, use blocked channel patterns to keep it out of named channels. Owners can also turn off DMs. (restrict where Claude Tag operates, security and data handling)

  10. 10

    Turn a task that works into a routine

    In one message, say the schedule, the work and the format, for example "every weekday at 9am London, post one line per open thread; skip anything with a ✅". Always name the timezone, because schedules run in UTC and shift with daylight saving. Claude can also watch named channels or follow one pull request. Anyone in the channel can list routines with @Claude !routines and pause or stop them. Routines use the channel's connections and spend from the same balance (as "Scheduled" in analytics). (set up routines, good habits, set a spend limit)

Unverified

What Anthropic's own pages disagree on, or could not be confirmed.

  • The Claude Code commands page lists /install-slack-app as "Install the Claude Slack app. Opens a browser to complete the OAuth flow" (commands). None of the Claude Tag pages mention it. They say setup starts at claude.ai/admin-settings/claude-tag, with the app added from the Slack Marketplace and paired with @Claude connect. Whether /install-slack-app gives you Claude Tag or the earlier app is not stated, so step 1 does not rely on it.
  • The support article says only a Primary Owner or Owner can set up Claude Tag and that admins cannot configure it. The docs describe a delegated "Claude Tag Admin" permission and channel managers. Step 1 follows the setup page (Owner) and does not rely on delegation.
  • The support article mentions spend alerts at 75% and 95%, a right-hand AI assistant panel in Slack, and deletion within 30 days after disconnecting or uninstalling. These were not found on the docs pages read, so they are not steps.
  • A search result said Claude in Slack switched to Claude Tag on 3 August 2026. This was not confirmed on a fetched page. Team and Enterprise workspaces on the earlier app should ask their account team for the cutover date, per the Claude Code in Slack page.
  • Anthropic publishes no per-task cost. Step 2 gives only the pilot approach the docs recommend.
  • Claude Tag is in public beta; Anthropic says features and behaviour may change before general availability.
  • "Limit Claude Tag to specific channels" needs per-scope switches. On Team you may have a single on/off switch instead, so step 9 points to blocked channel patterns; that section was not read in full.