Skip to content
← 最新リリース

ドキュメント / cc-doc-tracker

Claude Tag を使う

2026-11-20 に取得した公式ドキュメントです。各バージョンの公開後に追加された説明を含む場合があります。

公式ドキュメントを開く ↗
目次

英語の原文を掲載しています。

Claude Tag puts Claude in your Slack channels with admin-governed access. See what to hand it, how setup works, and where to start as an admin or end user.

Public Beta Tag @Claude in. Get results back in the thread. Anyone in a Slack channel can tag Claude into a problem and hand it work: reproduce a bug and open a pull request, turn a decision thread into a doc, assemble the state of a project. It posts a checklist in the thread as it goes, and the whole exchange stays visible to the channel.

I'm setting it up → Use it in your channel ↓

# platform-eng 38 members

Dana2:14 PMcheckout has felt slow all morning — anyone else seeing it?

Leo2:15 PMsame. @Claude can you investigate? Compare latency against this morning's deploy and find what's causing it.

ClaudeAPP2:15 PMOn it. I'll compare latency before and after the deploy, track down the cause, and report back here.

Done: Pulled p99 latency from Datadog Done: Diffed deploy 4f2c1 against main Done: Reproduced the slow query locally In progress: Opening a pull request with the fix…

Plans that include Claude Tag

Claude Tag is available on Team and Enterprise plans, on Anthropic's first-party service. It isn't available on individual plans (Free, Pro, Max, or Ultra), or for third-party deployments. To use it, your organization pairs its Slack workspace with its Claude organization; see the setup overview for the full prerequisites.

If you're choosing between Claude products for Slack-shaped work, how Claude Tag differs from Cowork and Claude Code compares them directly: team work in shared channels is Claude Tag; personal work on your own files is Cowork or Claude Code.

Who needs a Claude seat

Slack users don't each need a Claude seat to work with Claude in channels.

  • In channels: by default, anyone in the paired Slack workspace can tag @Claude in a channel, and an Owner can restrict who can use Claude to people in your Claude organization or, on Enterprise, to specific roles. Channel work bills by usage to your organization's usage balance, under a spend limit an Owner sets.
  • In group DMs: the same restriction on who can use Claude applies, and the work bills to your organization's usage balance. See Group DMs.
  • In one-to-one DMs: a DM from a member who has connected a Claude account runs on that account and bills to that person's seat. For the DM to work, that person needs either a seat that includes Claude Code or, on the Enterprise plan, Cowork access on a Standard seat or a usage-based Chat seat. A DM from a member who hasn't connected a Claude account can bill to your organization for a limited time.

Where Claude Tag runs

Claude Tag works in Slack. You interact with it by writing in a Slack channel, thread, or direct message, and it replies there. Mention @Claude in a channel to guarantee it picks the message up.

When Claude works on a task, it runs in an ephemeral sandbox, not on your computer. The sandbox is created when a conversation starts, holds any code or files Claude is working with, and is discarded when the conversation goes idle. See how Claude Tag works for the full lifecycle.

You extend what Claude can reach, like your repositories, ticketing systems, data warehouses, and custom tools, through Claude Tag connectors, plugins, and skills. An Owner or a Claude Tag admin configures these for all of Slack, for one workspace, or for one channel. Members' own claude.ai connectors are separate from that configuration; Claude can use them in a channel for the member's own requests, as personal connectors in channels describes.

For administrators Set up Claude Tag

Open

Where do I start? Pair your Slack workspace, launch, and test that it works

What can Claude Tag access? How admins set access per channel, and where credentials are stored

How do I connect each service? Credential types, allowed hosts, and what each connection lets Claude reach

For end users Put Claude Tag to work

Open

How do I hand Claude Tag a task? Mention Claude in any channel it's in, with nothing to install

What is Claude Tag good at? Use cases for coding, data, incidents, and go-to-market

How do I get good results? Good habits for scoping and reviewing work

What does Claude Tag remember? Channel memory, what's shared across the workspace, and who can see what

Can Claude Tag run tasks on a schedule? Scheduled jobs, channel watching, and triggers

Billing and spend limits

Adding Claude to Slack doesn't add a per-seat charge. Channel, thread, and group DM work is billed by usage instead: it draws from a usage balance, an amount in your organization's billing currency that an Owner funds. A spend limit caps how much of that balance Claude Tag can use each billing period.

One-to-one direct messages from members who have connected a Claude account don't draw from this balance. Such a DM runs on the sender's own claude.ai account and follows that seat's usual usage limits, so the organization spend limit doesn't apply to it. A DM from a member who hasn't connected a Claude account can draw from this balance.

To learn what your team's usage costs, run a pilot with a spend limit set and watch the per-channel breakdown on the usage page in your admin settings. Set a spend limit covers how to fund the balance on each plan, set the limit, and what happens when usage reaches it.

For end users

Put Claude Tag to work

If Claude Tag is in your channel, you can use it now. (If it isn't there yet, an Owner in your Claude organization runs setup: see Set up Claude Tag.) Anyone in the channel can hand it work, and channel work bills to the organization, not to you.

What it can reach starts with the channel you're in. The fastest way to find out is to ask it: @Claude what can you access from this channel? Or, if you're signed in to your Claude organization, click Configure in the footer of a Claude reply in the channel to see its connections, the external services an admin has connected for that channel. Replies in org-shared channels have no Configure link.

For your own requests, Claude can also use the connectors on your claude.ai account, after you allow it.

In a one-to-one DM, Claude runs on your own claude.ai account instead of a channel's setup. An Owner can turn off DMs for the whole organization; see Allow or disable direct messages.

Common uses

Each link opens a guide with the prompts to paste and the connections the task needs.

  • Watch monitors and alerts: scheduled dashboard checks, and alerts investigated as they arrive. Needs a monitoring connection like Datadog, Sentry, or PagerDuty.
  • Triage requests: an intake channel where Claude answers what it can, flags duplicates, and routes the rest. Works on Slack content alone.
  • Find answers in your docs: policy and runbook questions answered with the source. Needs a docs connection like Google Drive, Notion, or Confluence.
  • Answer data questions: a plain-language question becomes a warehouse query and a chart. Needs a data warehouse connection.
  • Track projects and chase approvals: standing status digests and follow-ups that run until an approval lands
  • Turn threads into docs and tickets: a settled discussion becomes the decision doc, the customer reply, or the filed tickets
  • Fix bugs: a bug reported in the channel comes back as a draft pull request. Needs GitHub.
  • Work from your own channel: scratch questions, digests of channels you don't follow, and follow-ups on what you said you'd do

Get started covers your first message, what you see while Claude works, and how to shape Claude's behavior in your channel.

For administrators

Set Claude Tag up once for everyone

You set up Claude Tag once, at claude.ai/admin-settings/claude-tag, and you must be an Owner in your Claude organization to do it. The setup page at that URL walks you through it:

  • Pair your Slack workspace: send @Claude connect in Slack to get a pairing code, then enter it on the setup page.
  • Set a monthly spend limit, add Claude to channels, and launch.

Once you launch, everyone in a channel Claude is in can use Claude Tag immediately, with no per-user setup.

Claude Tag starts with no access of its own to your external systems. After you launch, you connect the services Claude will work in, such as your issue tracker or data warehouse, and grant repositories to the Claude GitHub App. Members can also let Claude use their own personal connectors for their requests.

Set up Claude Tag walks through setup and connecting tools, with what to have ready, what each choice means, and how to verify Claude Tag works once you launch.

Security review Security and data handling

The security model, what admins can and can't restrict, audit trails, and network requirements.

Where to start with Claude Tag

[card] Set up Claude Tag

Admins: pair your Slack workspace and launch

[card] Hand Claude Tag your first task

It's already in your channel: send your first message

[card] How Claude Tag works

The session model, what it can read, and how memory follows places

[card] Use case library

Prompts to paste, by team and connection

変更の詳細