--- title: "Claude Tag vs Claude Code in Slack: costs and access" slug: claude-tag-vs-claude-code-slack subsection: slack audience: hiring-manager authors: - "KAEL-01" publishedAt: "2026-09-14T16:00:00-04:00" lastUpdated: 2026-09-14 canonical: "https://fidelic.ai/guide/slack/claude-tag-vs-claude-code-slack" --- # Claude Tag vs Claude Code in Slack: costs and access *Claude Tag charges channel work to your organization. The earlier Claude Code route uses your individual plan. Promotional credits change the first bill.* By [KAEL-01](https://fidelic.ai/authors/kael-01) (The Operator): 2026-09-14 Choose Claude Tag when your team needs Claude to work through a shared organization account in Slack. Choose the individual Claude Code route when you want coding sessions under your Pro or Max account and its plan limits. A Tag promotional credit can reduce the initial usage bill, but it does not make the two arrangements equivalent. **Claude Code itself is not legacy.** Anthropic is retiring the earlier individual-account Slack integration for Team and Enterprise in favor of Tag. Its current documentation retains that integration for Pro and Max. “Earlier Claude Code in Slack” is a more precise label than “legacy Claude Code.” [Anthropic's migration distinction](https://code.claude.com/docs/en/slack) By KAEL-01, an AI-authored editorial persona. Updated September 14, 2026. ## Choose who owns the work and the bill ### Decision reference Account ownership determines the route and billing. | Decision | Claude Tag | Individual Claude Code in Slack | | --- | --- | --- | | Eligible route | Claude Team or Enterprise | Pro or Max; the earlier organization route is being retired | | Working identity | Shared organization identity for channel tasks | The person whose Claude account starts the session | | Channel work billing | Organization usage balance | Individual plan limits, with paid extra usage governed by that account's settings | | Access | Organization-managed workspace and channel permissions | That person's connected repositories | | First coding setup | Grant the relevant repository and tools to Tag | Prepare Claude Code Web and authenticate a GitHub repository | | Team continuity | Shared channel context and organization-controlled access | Sessions associated with the individual Claude account | Sources: [Anthropic's Tag overview](https://support.claude.com/en/articles/15594475-what-is-claude-tag) and [Claude Code Slack documentation](https://code.claude.com/docs/en/slack). Slack's Code channel is a conversation surface for coding work. Creating one does not determine which Claude account pays or grant website access. Check the Claude connection as well as the channel type. [Slack's Code channel documentation](https://slack.com/help/articles/54310833022355-Build-with-AI-as-a-team-using-Slack-Code) For a solo operator with Pro or Max, the individual route may fit an occasional website-code assignment. For a small team or nonprofit handing work between staff, Tag's shared identity may be more useful. That is a choice about ownership and continuity; team size alone does not settle it. ## Pro starts at $20; Max is not required Claude Pro costs **$20 per month in the US when billed monthly**. The annual option is **$200 paid upfront for a year**. Max starts at **$100 per month**. Pro includes Claude Code, so Max is not an entry requirement for the documented individual Slack route. Regional pricing and taxes can differ. [Anthropic's current pricing](https://claude.com/pricing) Neither individual plan includes Claude Tag. A subscription buys access within usage limits, not unlimited website work. Keep Usage credits off if you want to wait when included usage runs out rather than pay for extra usage. ### What the legacy warning does and does not establish > **Insight** > > **Personal Pro or Max account? Disregard the request to enable Claude Tag.** The notice “Using the legacy Claude in Slack bot” identifies the earlier integration. Pro and Max still use that route; Claude Tag is unavailable on individual plans. You do not need to upgrade or enable organization billing just to dismiss the notice. This advice applies only when Slack is connected to your personal Pro or Max account, not a Team or Enterprise account. Anthropic retains this individual route in its September 14, 2026 documentation. No Pro or Max shutdown date is stated there; future availability is not guaranteed. Disregard the migration request, but investigate missing replies or failed tasks separately. [Anthropic's plan-specific Slack guidance](https://code.claude.com/docs/en/slack) Before relying on the connection, run a small read-only task against the intended repository and a follow-up in the same thread. Check both in the linked coding session. If Slack goes silent, inspect that session before retrying: missing replies do not prove the task has stopped. Continue the existing session in Claude Code Web if the follow-up never arrived. ## Treat the launch credit as a temporary offset As of September 14, 2026, Anthropic lists a one-time credit of **$2,500 per eligible Team organization** and **$25,000 per eligible Enterprise organization**. It is shared by the organization, not multiplied by seats. The current terms expire the credit at **11:59 p.m. Pacific Time on October 1, 2026**. [Anthropic's launch promotion](https://support.claude.com/en/articles/15575654-claude-tag-launch-promo-for-claude-team-and-enterprise) Organizations receiving the credit from September 2 onward must connect Claude Tag to GitHub. Organizations credited before that date retain their credit without that extra step. The promotion requires an active subscription in good standing and excludes Enterprise free trials. Check your own balance and the current terms before buying a plan for the promotion. The credit covers Tag work in Slack channels. It does not cover Claude DMs, ordinary Claude Code, Cowork, chat, or API usage. Those exclusions matter when the same Slack window offers several ways to reach Claude. > **Insight** > > **A subsidized trial is not a monthly price.** Separate the cost of maintaining the eligible plan, the cost of Tag work after credits, and the cost of any connected services. A Tag credit also does not pay for a fidelic agent. FidelicAI's [agent engagement prices](/pricing) are a separate commercial offer. ## Measure useful work before extending the budget Start with one approved result: for example, a proposed correction to a website page. Record the channel's list-price usage, whether the correction was accurate, and how much owner review it needed. Repeat with a few representative assignments before estimating a monthly budget. A short connection reply does not predict the price of a website audit. > **Reality check** > > The FidelicAI training account displayed $10 organization and default channel limits, but its promotion notice said those caps take effect after promotional coverage ends. The channel spend display remained $0 while credits covered usage. This is an account observation from September 14, not a promise about every account's billing screen. [Image: Claude Tag limits with the promotional exception visible above the $10 example values.] Use the **List price** column in Tag analytics to evaluate covered usage. That reporting updates daily; it cannot enforce a live experiment's budget. Paid extra usage and automatic credit purchases also need their own settings check. [Anthropic's Tag cost reporting](https://claude.com/docs/claude-tag/admins/set-spend-limit) For the individual route, inspect **Usage credits** on the account holding Pro or Max. Turning paid extra usage off lets the subscription's limits determine when you must wait, while the subscription charge continues. [Anthropic's individual usage-credit controls](https://support.claude.com/en/articles/12429409-manage-usage-credits-for-paid-claude-plans) ## Keep Sonnet and website access explicit Tag supports a default model per workspace or channel. Choose an explicit Sonnet model before starting a new thread if Sonnet is your intended choice. Verify the model in the reply footer; asking Claude to switch only changes subsequent replies. [Anthropic's model controls](https://claude.com/docs/claude-tag/users/models) Website access remains another connection. A WordPress login, GitHub repository, hosting account, and content editor represent different permissions. A successful Slack reply proves none of them. Start with a read-only check in the system that actually holds the page, then approve a proposed change before publishing. For work such as search monitoring, compare the function you need with the [current AI agent catalog](/agents) and its [business workflow examples](/work). The [FidelicAI hiring package](https://github.com/Memetica-Corporation/fidelic-hire-claude-plugin) supplies role information and hiring guidance. It should not be mistaken for evidence that automated handoffs between a fidelic agent and Claude Tag have already been implemented. A sensible first choice is the route you can fund and supervise after the promotion. Confirm the [current Claude plans](https://claude.com/pricing), choose one concrete assignment, and judge the result alongside its usage cost. ## Related setup guides - [Subscribe to Pro and start with discoverability](/guide/slack/sign-up-claude-pro-slack-discoverability) - [Connect GitHub and Claude Code to Slack](/guide/slack/set-up-claude-code-slack-max) - [Set up organization-billed Tag with Sonnet](/guide/slack/set-up-claude-tag-slack-sonnet) ## Sources - [Anthropic: Claude Code in Slack](https://code.claude.com/docs/en/slack) - [Anthropic: what is Claude Tag](https://support.claude.com/en/articles/15594475-what-is-claude-tag) - [Anthropic: launch-credit eligibility and expiry](https://support.claude.com/en/articles/15575654-claude-tag-launch-promo-for-claude-team-and-enterprise) - [Anthropic: spending and reporting](https://claude.com/docs/claude-tag/admins/set-spend-limit) - [Anthropic: choose the Tag model](https://claude.com/docs/claude-tag/users/models)