Skip to main content
Public Beta

Tag @Claude in. Get results back in the thread.

Anyone in a 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-eng38 members
Dana2:14 PM

checkout has felt slow all morning — anyone else seeing it?

Leo2:15 PM

same. @Claude can you investigate? Compare latency against this morning’s deploy and find what’s causing it.

ClaudeAPP2:15 PM

On it. I’ll compare latency before and after the deploy, track down the cause, and report back here.

Done: Pulled p99 latency from DatadogDone: Diffed deploy 4f2c1 against mainDone: Reproduced the slow query locallyIn progress: Opening a pull request with the fix…
For administratorsProvision the identity
Where do I start?The four setup steps, what to have ready, and what to test firstWhat can Claude Tag access?Why access follows the channel, and where credentials are storedHow do I connect each service?Credential types, allowed hosts, and what each connection lets Claude reach
For end usersPut Claude Tag to work
How do I hand Claude Tag a task?Mention Claude in any channel it’s in, with nothing to installWhat is Claude Tag good at?Use cases for coding, data, incidents, and GTMHow do I get good results?Good habits for scoping and reviewing workWhat does Claude Tag remember?Channel memory, what’s shared across the workspace, and who can see whatCan Claude Tag run tasks on a schedule?Scheduled jobs, channel watching, and triggers
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 depends on the channel you’re in, not on who you are. The fastest way to find out is to ask it: @Claude what can you access from this channel? The one exception is a DM, where it runs on your own claude.ai account instead of the channel’s setup. Admins can disable DMs organization-wide; see Allow or disable direct messages. Begin with Get started, which covers your first message, what you see while it works, and how to shape its behavior in your channel.
For administrators

​
Set Claude Tag up once for everyone

Installing the Claude app in Slack is a prerequisite, not the setup. Setup is provisioning an identity. Claude Tag starts with no access to your external systems; you choose its credentials and repositories (an Access bundle), and which workspaces and channels they apply to. You configure this once, at claude.ai/admin-settings/claude-tag, and everyone in those places can use Claude Tag immediately, with no per-user setup. You must be an Owner in your Claude organization to run setup. Set up Claude Tag walks the four provisioning steps, from creating the identity to attaching it to your first channel.

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

Set up Claude Tag

Admins: provision the identity and connect your first channel

Hand Claude Tag your first task

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

How Claude Tag works

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

Use case library

Prompts to paste, by team and connection