Nori vs Claude Tag (Claude in Slack)

Quick answer

It depends on how much of your stack is already Anthropic. Pick Claude Tag if your team lives in Slack, already pays for Claude Team or Enterprise, wants only Claude, and accepts a public beta billed to an org-funded balance. Pick Nori if you want Jiro or any harness working for the whole team from Slack, Discord, schedules and webhooks, with shared memories and skillsets, on your own Claude or ChatGPT subscription, keys or gateway, with flat plans and no token charges.

What is Claude Tag?

Claude Tag is Anthropic's Slack product for teams: you mention Claude in a channel, hand it work, and it replies in the thread. It puts the model vendor's own agent where the team already talks.

As of November 2026, Anthropic's documentation establishes these points:

• Availability. Claude Tag is a public beta for Claude Team and Enterprise plans. See the Claude Tag overview.
• Billing. Slack channel work uses an org-funded balance. The plan underneath is separate: Anthropic lists the Team standard seat at $25 per month, or $20 per month billed annually. See Claude pricing.
• Memory. Channel notes and workspace notes are distinct, and public and private channels have different write rules. See what Claude Tag remembers.
• Routines. Routines are documented for recurring work. In Claude Code's cloud product, durable cloud schedules, API triggers and GitHub triggers are a research preview. See routines.

The rate at which channel work draws down the balance is not established by the pages read for this comparison, so no figure is given here.

What is Nori?

Nori is a cloud platform for coding agents, built for engineering teams. The whole team drives it from Slack, Discord, the web or the CLI. Cron schedules, one-time reminders and webhooks start the same kind of session a person would start, with run history and approval paths. Every session begins with the team's shared memories and org skillset, so the agent already knows how you ship.

Each session is an isolated cloud sandbox running the harness you choose: Claude Code, Codex, Gemini CLI, Cursor, OpenCode, Droid, Amp or any ACP agent. You connect your own Claude or ChatGPT subscription, API keys or any LLM gateway. Nori never charges for tokens, so you are free to move between model providers.

Meet Jiro

Jiro is the AI engineering teammate that Nori ships, and the Nori counterpart to tagging Claude in a channel. It runs on Claude Code or Codex under the hood, on your own subscription or API key. It follows an opinionated engineering workflow: plan, write the failing test, implement, review. On its first day it reads your repositories, asks the team how you ship and sets up the workspace. See jiro.bot.

A typical thread looks like this:

#checkout-eng
@Jiro the cart total is wrong when a coupon and a gift card are both applied.
Reproduce it, add a test in tests/cart/test_totals.py, open a PR.

Jiro: Plan posted in thread. Failing test written: discount applied after gift card.
PR: fix(cart): apply coupon before gift card balance
Tests: 96 passed. Ready for review.

If Claude is the model you want, nothing changes: run Claude Code on Nori with your Claude subscription. See Claude Code in Slack.

Nori vs Claude Tag, head to head

The memory row deserves a closer look. Claude Tag ties notes to Slack: some belong to a channel, some to the workspace, and who may write them depends on whether the channel is public or private. Nori's shared memories belong to the organization, not to a chat surface. A note such as "the orders table is partitioned by month; always filter on created_at" applies whether the session started from a Slack thread, a Discord mention, the web or a 02:00 cron run.

Enterprise deployment: where does the control plane run?

The control plane is the part that orchestrates sessions, holds transcripts and organization state, and runs the agent loop. For background, see what an agent control plane is.

Claude Tag is run by Anthropic. Anthropic also documents customer-run environments for Claude Code's cloud product: a public beta for Team and Enterprise that retains Anthropic control. Whether Claude Tag threads can use those environments is not established by the pages read for this comparison, so ask Anthropic before you plan around it.

Nori Enterprise deploys the full stack, control plane included, into your own AWS VPC or Azure VNet, or on-prem, with your identity provider (SAML, SCIM, OIDC), LLM gateway and compute. On hosted plans, Nori gives each organization a dedicated, single-tenant control plane and data store, and every session runs in its own isolated sandbox.

When to choose Claude Tag

• You are already on Claude Team or Enterprise and only want Claude. The product comes from the model vendor and sits on the plan you already hold.
• Your team works only in Slack. Claude Tag is built for Slack channels and threads.
• You want one vendor for model, agent and billing. Nobody connects credentials; an org-funded balance pays for channel work.
• Channel-level notes fit how you work. Distinct channel and workspace notes suit teams whose context divides cleanly by channel.
• A public beta is acceptable for the work you plan to hand over.

When to choose Nori

• You want an engineering workflow, not only a mention. Jiro plans, works test-first and reviews its changes, and it can run on Codex as well as Claude Code.
• You use more than Claude. Nori runs Claude Code and also Codex, Gemini CLI, Cursor and any ACP agent.
• You want to reuse subscriptions you already pay for. A Claude or ChatGPT subscription powers cloud sessions on Nori, and Nori never charges for tokens.
• You route models through a gateway or your own keys. Nori works with both.
• Scheduled and event-driven work matters as much as chat. Cron schedules and webhooks start sessions with run history and approval paths.
• You need the control plane in your environment. Nori Enterprise runs the full stack in your cloud or on-prem.
• Your team uses Discord, or wants the same agent from the web and the CLI.
• You want a fixed bill. Nori Team covers five machines and unlimited members for a flat price.

How to switch from Claude Tag to Nori

1. List your routines and notes. For each routine, write down the trigger and the prompt. Copy the channel notes and workspace notes you rely on.
2. Start the Nori trial. Thirty days, no card.
3. Keep Claude. Run Claude Code on Nori with your Claude subscription or Anthropic API key, so the model and much of the behavior stay familiar. Try Jiro on the same tickets.
4. Move notes into shared memories and the org skillset. Workspace notes become shared memories. Standing channel instructions become skills, for example a release-checklist skill for #releases.
5. Recreate routines as automations. Schedules become cron automations like the one below. Repository events become webhook automations.
6. Run both for a week. Connect Nori to Slack, use it in #eng-nori-trial while Claude Tag stays in its current channels, and compare the pull requests before you cut over.

schedule: 0 9 * * 1-5
agent: claude-code
repo: acme/checkout
prompt: Summarize pull requests merged since the last run.
        Flag any that changed db/migrate. Post in #checkout-eng.

For other options, see cloud coding agents compared, Nori vs Devin and Nori vs running Claude Code locally. To see Nori on your own repositories, book a demo.

Frequently asked questions

Sources

Competitor facts were read from these vendor pages on November 11, 2026. Vendors change plans and features often; check the source before you decide.

• Claude docs: Claude Tag overview (availability and billing)
• Claude docs: What Claude Tag remembers
• Claude Code docs: Routines
• Claude Code docs: Self-hosted environments
• Claude: Pricing
• Jiro, the agent Nori ships