On Tuesday, June 23, 2026, Anthropic launched Claude Tag, a new way to work with AI in Slack. Instead of opening a separate tab or tool, you simply tag @Claude in a channel. An AI shows up that behaves like a team member: it sees what gets written in the channel, can be connected to your tools, and picks up the thread where the last person left off.
Available in beta for Claude Enterprise and Team from today. Powered by Opus 4.8. Replaces the existing Claude in Slack app, with a 30-day migration window for administrators.
Anthropic uses the tool heavily itself. In the company's own framing, "tagging @Claude" is "one of the main ways we get things done at Anthropic".
What is new with Claude Tag?
The difference from the previous integration is that Claude now has a per-channel identity. In practice that means three things:
One shared Claude per channel. Everyone in the channel sees what Claude is working on, and can continue where the last person left off. Instead of each employee running a private Claude session, the team shares one with continuity.
Claude learns over time. It picks up context from channel activity, and can automatically pull information from other channels and data sources it has been granted access to. According to Anthropic, that means you do not have to repeat context every time you need help.
Asynchronous and proactive. With the "ambient" setting, Claude can flag relevant information across channels, follow up on threads that have gone quiet, and run tasks over hours or days. You can set a task and focus on something else while Claude works in the background.
Direct messages to Claude are also supported.
Anthropic cites an interesting figure: 65 percent of their own product team's code is written by their internal version of Claude Tag. That applies to an engineering team with full access and training, and shows how Anthropic uses the tool itself. An SMB should measure its own results before drawing conclusions.
What does this mean for Norwegian SMB teams?
For Norwegian businesses with 7 to 100 employees already using Slack daily, Claude Tag is a practical way to test AI agents without rolling out a separate system. If you want to learn more about how autonomous AI agents work in practice for Norwegian SMB teams, we have a dedicated service description. Three concrete workflows we can see Norwegian teams testing from day one:
1. Real-time meeting summaries. Instead of one person taking notes, Claude Tag can follow the channel during customer meetings, internal meetings, or sales calls, and deliver a short recap with action items right after. In a 15-person accounting firm, that means the partner does not have to write the recap themselves and can instead validate what Claude delivers.
2. Shared question-answer across sales and support. When a salesperson wonders about a supplier contract, or a support staffer needs a summary of a customer's history, Claude Tag can pull the answer from internal systems without that person having to email a colleague first. Especially relevant for industries with high customer churn, like automotive, tourism, and service trades.
3. Onboarding of new hires. A new employee added to a channel can ask Claude to summarize the last 30 days of discussions, find the most important customers, or explain how a specific internal tool is used. Claude Tag responds with source links to the relevant threads, so the new hire both learns and gets a path into the archive.
The biggest gain for an SMB is skipping a custom chatbot build: you tag a ready-made AI into the channel you already work in. For a 12-person accounting firm, that is the difference between a six-month project and an afternoon.
Example channel setups
Because memory and data are kept per channel, your channel structure decides what Claude can see:
- Accounting firm: In
#support, tag@Claudefor standard client inquiries based on the firm's FAQ. In#accounting, Claude extracts numbers from invoices. Sales uses#salesfor proposal drafts from the CRM, without seeing data from#accounting. Per-channel spend limits prevent overspend. - IT consultancy: One channel per project, such as
#project-acmeand#project-nordic. Claude follows each project and answers "what is the status" without consultants repeating themselves. - Health clinic:
#receptionuses Claude for scheduling, while#doctor-1and#doctor-2stay private. Patient data does not flow into the reception channel.
What should you think through before turning it on?
Claude Tag only makes sense once you have decided four things:
Which channels should Claude access? The administrator sets tokens and access per channel. A sales channel does not need to see HR data, and the other way around. Anthropic states that memories and data stay within the channels you grant access to, so a Claude set up for sales does not get insight into the engineering channel.
What are the data access boundaries? Sensitive customer data, personal data, and salary information should stay outside Claude Tag's reach in the first phase, in line with GDPR and Norwegian privacy practice. Set a policy before you let it loose. An AI consultant for Norwegian businesses can help you draw those boundaries before the app is installed.
How do you control cost? Claude Tag has per-channel and per-org token spend limits, plus an audit log that shows exactly what was used. Set a cap per channel before the pilot starts, and read the audit log weekly during the first month.
What is the success criterion? Test one use case at a time. Start with meeting summaries in one channel. Measure time saved per week. Only once you have data, can you consider expanding to other channels and workflows.
Limits and pitfalls
- Requires Slack. Teams on Microsoft Teams must move to Slack first.
- Requires Claude Team or Enterprise. The beta is not available to individual users or Pro subscribers.
- Claude Tag is an AI colleague in the channel. Agents that run whole workflows on their own are built as separate solutions, for example through AI Development.
- Know your data flows first. Before you let AI into your channels, you should know which data flows where. That is the job of an AI review.
- It is a beta. Errors happen. Start in a low-risk internal channel.
Practical setup
Claude Tag is available in the Slack Marketplace under the name Claude. You need a Claude Team or Enterprise account to activate it. The install itself takes under ten minutes: install the app, give Claude access to the channels you want, set a monthly spending cap, and test in a private channel first.
A pilot should look like this:
- Map your Slack usage. Which channels exist, and which data flows through them.
- Pick one pilot channel. Start internally with low risk, and evaluate for two to four weeks.
- Set spend limits and turn on the audit log. Caps per channel and per org, and a weekly log review during the first month.
- Train the team to use @Claude. The biggest value comes when the team actually tags Claude in daily work.
- Decide whether you need more. If the pilot covers 70 percent of the need and the rest requires autonomous agents, the next step is a custom solution.
For Norwegian businesses evaluating AI agents for the first time, Claude Tag is a low-risk path in. You do not need to replace anything you already use, and you can test on real workflows without setting up your own infrastructure. If you want help mapping which workflows in your business are ready for AI agents, an AI review is a good starting point. For an ongoing operations and development agreement around AI agents in Slack, get in touch with us for a no-obligation conversation.
Frequently asked questions
What is the difference between Claude Tag and the older Claude in Slack app? Claude Tag replaces the existing Claude in Slack app, according to Anthropic. The new version gives Claude a per-channel identity, learns over time from channel activity, can work asynchronously in the background, and lets everyone in the channel see what Claude is doing. Administrators get a 30-day migration window.
How much does Claude Tag cost? Claude Tag is included in Claude Team and Enterprise subscriptions during the beta period, and Anthropic offers an introductory credit. For Slack usage through the subscription you pay per seat as before, and token cost is controlled through per-channel and per-org spend limits. The underlying model is Opus 4.8, priced at 5 dollars per million input tokens and 25 dollars per million output tokens for direct API use.
Can Claude Tag see private channels? No. According to Anthropic, Claude Tag does not report from private channels without explicit invitation. Administrators decide which channels, tools, and data sources Claude can access, and memories and data stay scoped to the defined channels.
What does this mean for Norwegian SMB teams? Three concrete use cases from day one: real-time meeting summaries, shared question-answer across sales and support, and onboarding of new hires into channel-based workflows. Important to set clear boundaries on which data Claude can see, especially customer data and HR content.
Do I have to switch from ChatGPT Teams or Microsoft Copilot to use Claude Tag? No. Claude Tag works as an addition inside Slack, independent of other tools. For Norwegian teams already using Slack daily, the threshold is low: install the app from Slack Marketplace, connect to a channel, define what Claude can access, and try a single limited use case first.
Who can use Claude Tag? Businesses with a Claude Team or Enterprise subscription that already use Slack. The beta is not available to individual users or Pro subscribers, and teams on Microsoft Teams must move to Slack first.
