Skip to content
← newsletter

Nori vs Claude Tag: Jiro or any agent, or Claude in Slack (October 2026)

Claude Tag is Anthropic's polished way to put Claude in Slack. Nori ships its own AI engineering teammate, Jiro, and runs any coding agent you prefer, on your own models, from Slack, Discord, the web, or the CLI. Here is where each one wins.

Which is better, Nori or Claude Tag?

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, and wants a polished @Claude with admin-governed access and default-deny egress. Pick Nori if you want more than one model vendor: Jiro, Nori's own agent, or any harness, Discord as well as Slack, your own Claude or ChatGPT subscription, keys, or gateway, and flat plans with no token charges. Claude Tag bills channel work to an org usage balance; Nori charges per runtime.

This page compares the two as of October 2026, using Anthropic's Claude Tag documentation. It is part of our comparison of cloud coding agents; see also Nori vs Devin and Nori vs Cursor cloud agents.

What is Claude Tag?

Claude Tag is Anthropic's Slack product for teams. In Anthropic's words, it “puts Claude in your Slack channels with admin-governed access.” Anyone in a channel can mention @Claude and hand it work — reproduce a bug and open a pull request, turn a thread into a doc, assemble a project status — and Claude posts its progress and results in the thread. As of October 2026 it is in public beta and available on Claude Team and Enterprise plans, on Anthropic's own service only.

Under the hood, each Slack thread gets an ephemeral sandbox running the same engine as Claude Code on the web. An Owner pairs the Slack workspace with the Claude organization, funds a usage balance, and sets a spend limit. Admins add connectors scoped to all of Slack, one workspace, or one channel. Credentials never enter the sandbox: according to Anthropic's security documentation, an Agent Proxy injects them at request time, and outbound traffic from Anthropic-hosted sessions is default-deny. Code work goes through the Claude GitHub App as draft pull requests, and routines run work on a schedule, a channel watch, or a repository event.

What is Nori?

Nori ships Jiro, its own AI engineering teammate, and also runs any harness you prefer. Each session is a cloud machine where you run Jiro or another harness — Claude Code, Codex, Gemini CLI, Cursor, OpenCode, pi, or ACP agents such as Droid, Goose, Amp, or Copilot CLI — on your own Claude or ChatGPT subscription, API keys, or LLM gateway. You drive it from Slack, Discord, the web UI, or the CLI, and you schedule work with cron and webhook automations. Teams have merged 100,000+ PRs with it.

We never charge for tokens: plans are per runtime, with no metering or markup, so you are free to move between model providers and we have no reason to want your agent to spend more. Everything is customizable, and on Enterprise that extends to your compute, IdP (SAML, SCIM, OIDC), LLM gateway, token provider, and memory provider, in your cloud or on-prem. The defaults are opinionated: a workflow skillset for plans, TDD, worktrees, and review, plus org skillsets, memories, automations, and checkpoints.

Meet Jiro

Jiro is Nori's own AI engineering teammate, and the Nori counterpart to tagging Claude in a channel. It runs on Claude Code or Codex under the hood, on your own Claude or ChatGPT subscription or API key, so there are no token charges. It follows an opinionated engineering workflow: planning, test-driven development, review, and worktrees. You work with it in Slack or the browser, and on its first day it reads your repos, asks the team how you ship, and sets up the workspace. See jiro.bot.

Nori vs Claude Tag, head to head

Nori vs Claude Tag, as of October 2026. Claude Tag facts from Anthropic's documentation, listed under Sources.
CategoryNoriClaude Tag
HarnessJiro (Nori's own agent) or any harness: Claude Code, Codex, Gemini CLI, Cursor, OpenCode, pi, plus ACP agents (Droid, Goose, Amp, Copilot CLI, Qwen, Kimi, Cline, and more)Claude only; the same engine as Claude Code on the web (source)
SubscriptionsBring your own Claude or ChatGPT subscription (OAuth)Requires a Claude Team or Enterprise plan on Anthropic's own service; not on Free, Pro, or Max, or third-party deployments. One-to-one DMs run on the member's own seat
API keys / gatewaysYour own API keys, or an LLM gateway: OpenRouter, Fireworks, Cloudflare, or any OpenAI- or Anthropic-compatible endpointAnthropic's first-party service only; no third-party keys or gateways documented
Token charges / pricing modelNone. A per-runtime subscription; no usage metering, no token resale, no markupNo per-seat charge for adding Claude to Slack; channel work draws on an org usage balance funded by an Owner, under a spend limit
Plans & pricesFree 30-day trial (5 runtimes, no card); Developer $99/mo; Team $250/mo; Enterprise customIncluded with Claude Team and Enterprise plans; channel usage billed from the org balance (rates not published on the Claude Tag pages)
Deployment / your infrastructureHosted by Nori; Enterprise runs in your cloud or on-prem on your compute (AWS EC2, Docker, Modal, or Sprites)Ephemeral sandbox per Slack thread on Anthropic's infrastructure; self-hosted environments run sessions on runners in your network, but admin-added connectors are unavailable there
Control plane (where the agent loop runs)Your AWS VPC, Azure VNet, or on-prem (Enterprise); a dedicated single-tenant control plane and data store per organization (hosted)Anthropic-hosted; with self-hosted environments, the control plane, transcripts, and by default inference stay at Anthropic
Identity / accessEnterprise: bring your own IdP. SAML, SCIM, and OIDCUses your Claude organization; Owners can restrict use to organization members (Team) or to roles (Enterprise). Claude acts under its own service accounts
Automations / triggersCron and webhook automationsRoutines on a schedule, a channel watch, or a repository event (source)
IntegrationsDriven from Slack, Discord, the web UI, and the CLISlack only (no Discord); admin-added connectors, plugins, and skills; code work through the Claude GitHub App as draft PRs
Memory / customizationOpinionated defaults: workflow skillset (plans, TDD, worktrees, review), org skillsets, memories, checkpoints; Enterprise can bring its own memory providerChannel memory and workspace notes; retains memory and transcripts, so not available with ZDR, CMEK, or HIPAA configurations

Enterprise deployment: where does the control plane run?

The control plane is the part that orchestrates sessions, holds transcripts and org state, and runs the agent loop. Claude Tag is hosted by Anthropic. Its self-hosted environments, a public beta that is off by default, run sessions on runners in your network, but the control plane, transcripts, and by default inference stay at Anthropic. Nori Enterprise deploys the full stack — control plane, agents, and data — into your own AWS VPC, Azure VNet, or on-prem environment. On hosted plans, Nori gives each organization a dedicated, single-tenant control plane and data store, and every session runs on its own isolated machine.

When to choose Claude Tag

  • Slack polish matters most. Claude Tag is built by the model vendor for Slack: anyone in a channel can tag Claude with no per-user setup, and it reports progress as a checklist in the thread.
  • You want strict, documented egress control. Anthropic documents a default-deny Agent Proxy that injects credentials at the boundary so the sandbox never holds them, with credentials scoped down to a single channel. Nori does not document an equivalent egress proxy.
  • You are already on Claude Team or Enterprise and only want Claude models. There is no per-seat charge for adding Claude to Slack; channel work draws on your org balance.
  • Your work is not only code. Anthropic's use cases include triaging requests, answering data questions, and turning threads into docs, alongside fixing bugs.

When to choose Nori

  • You want an engineering workflow, not just a mention. Jiro plans, works test-first, reviews its changes, and uses worktrees; on day one it reads your repos and asks how you ship. 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 ACP agents. Claude Tag runs Claude only.
  • You want to use subscriptions you already pay for. On Nori, a developer's Claude or ChatGPT subscription can power cloud sessions. Claude Tag channel work bills to the org usage balance.
  • You route models through a gateway or your own keys. Claude Tag is Anthropic's first-party service only. Nori works with OpenRouter, Fireworks, Cloudflare, or any OpenAI- or Anthropic-compatible endpoint.
  • Your org has ZDR, CMEK, or HIPAA requirements. Claude Tag is not available with those configurations because it retains channel memory and transcripts.
  • You want your connectors on your own machines. Claude Tag's self-hosted runners cannot use admin-added connectors. Nori Enterprise runs the whole runtime in your cloud or on-prem.
  • Your team uses Discord. Claude Tag is Slack only; Nori supports Slack and Discord.
  • You want a fixed bill. Nori's plans are flat per runtime, and we never charge for tokens.

Subscribe to the newsletter

Weekly updates and long-form essays from the Nori team on AI agents and the agent ecosystem.

How to switch from Claude Tag to Nori

  1. List your routines and connectors. Note each routine's trigger (schedule, channel watch, or repository event) and the services Claude reaches in each channel.
  2. Start the free trial. Thirty days, five runtimes, no card.
  3. Keep Claude. Run Claude Code on Nori with your Claude subscription or Anthropic keys, so the model and much of the behavior stay familiar.
  4. Recreate routines. Schedules become cron automations; repository events become webhook automations.
  5. Move channel instructions into skills. Standing guidance and team conventions belong in your org skillset and memories.
  6. Connect Slack (or Discord) and run both in separate channels for a week before you remove Claude Tag.

Plan details are on our pricing section.

Frequently asked questions

How much does Claude Tag cost?

As of October 2026, Claude Tag requires a Claude Team or Enterprise plan. Adding Claude to Slack has no per-seat charge; channel work draws on an organization usage balance funded by an Owner, under a spend limit, and one-to-one DMs bill to the member's own seat. Nori has a free 30-day trial, Developer at $99/mo, Team at $250/mo, and custom Enterprise pricing, and never charges for tokens.

Can Claude Tag use models other than Claude?

No. Claude Tag runs Claude only, on the same engine as Claude Code on the web. Nori runs Claude Code, Codex, Gemini CLI, Cursor, OpenCode, and ACP agents on your own subscriptions, keys, or gateway.

Does Claude Tag work in Discord?

No. As of October 2026, Claude Tag works in Slack only. Nori is driven from Slack, Discord, the web UI, and the CLI.

Can Claude Tag run on my own infrastructure?

Partly. Anthropic documents self-hosted environments where sessions run on runners inside your network, but admin-added connectors are not available in those sessions. Nori Enterprise runs in your cloud or on-prem with your own compute, IdP, LLM gateway, token provider, and memory provider.

Is Claude Tag available with zero data retention?

No. Because Claude Tag retains channel memory and session transcripts, Anthropic says it is not available to organizations with Zero Data Retention, a customer-managed encryption policy, or the HIPAA configuration.

Sources

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

Subscribe to the newsletter

Weekly updates and long-form essays from the Nori team on AI agents and the agent ecosystem.