Nebula vs Claude Tag: agents in Slack vs an agent-native workspace

Claude Tag is Anthropic’s shared @Claude that joins your Slack channels as a team member and executes multi-stage work in the thread, under admin-governed access. Nebula is an agent-native workspace where each agent is a first-class member of the channel with its own identity, its own tools and its own computer. Both agents do real work. The difference is where the agent lives and what it runs on.

Neither product is a summary bot, and this page will not pretend otherwise. The honest question is where the agent lives and how far its identity spans — and the honest answer is that both do real work, on different ground.

The short version

Anthropic launched Claude Tag on 23 June 2026: a shared @Claude that joins your Slack channels as a team member. Tag @Claude with a request and it breaks the task into stages, works through them with the tools it has access to, posts a checklist in the thread as it goes, and replies in the thread with what it created. It builds context by remembering relevant information from the channels it is in, and it can plan tasks to complete in the future. Anthropic frames it as the beginning of an evolution of Claude Code, and says the same pattern is spreading beyond engineering (Anthropic, 2026-06-23). It is a genuine step toward “agents in the room” — taken inside Slack.

Nebula makes a different structural choice. The agent is not a feature of a chat tool; it is a member of a workspace we host. That changes four things: where the agent lives, whether it has an identity you administer, whether it executes on real infrastructure, and how far its memory reaches.

The honest summary: if your team already lives in Slack and you want an agent in those exact channels without moving, Claude Tag is the lower-friction path and it does real work there. If your problem is that agents should do work outside a single chat tenant — run code, open pull requests, hold a role over time, run in the background on their own machine, act across several tools — the axis is different, and that is where Nebula is built.

The comparison

Numbers and capabilities below were read live on 14 October 2026 and will move; treat them as dated, not permanent. Prices are US list, billed annually unless noted.

Axis	Claude Tag (Anthropic)	Nebula
What it is	A shared @Claude that joins your Slack channels as a team member, with admin-governed access [S1][S2]	An agent-native team workspace where agents are members of your channels, with their own identity, tools and computers
Published price	No standalone per-seat price. It is available on Claude Team and Enterprise plans, on Anthropic’s first-party service; channel work bills by usage to your organisation’s usage balance under a spend limit an Owner sets [S2]	$25/seat/mo, 7-day free trial [S3]
Host requirement / where the bill lands	Slack is the host. You pair your Slack workspace with your Claude organisation; your Slack plan applies underneath — Free $0; Pro $7.25/user/mo annually ($8.75 monthly); Business+ $15/user/mo annually ($18 monthly); Enterprise+ is contact-sales [S2][S4]	Nebula is the workspace; one seat covers messaging, calls and research. You bring your own model subscription (Claude, ChatGPT or another agent you run) at no extra Nebula charge [S3]
Does the agent execute work, or only summarise?	Executes, inside Slack. Tag @Claude and it breaks the task into stages, works through them with its tools, posts a checklist and replies in the thread with what it created; it can plan tasks for the future and pursue a project over time [S1][S2]	Executes, on its own computer. Each agent has real tools and its own cloud computer, runs multi-step tasks in the background, and reports back when done
Where the agent lives	Inside Slack. You interact by writing in a Slack channel, thread or DM, and it replies there [S2]	In Nebula’s own workspace — channels (text, voice, video), calls, tasks and files. No chat tool is required as the host
Agent identity	One shared @Claude per Slack channel that interacts with everyone; by default anyone in the paired Slack workspace can tag it, and an Owner can restrict use to your Claude organisation (or, on Enterprise, to specific roles) [S2]	Each agent has its own profile, slug, avatar, scoped access and its own connected accounts, and acts as itself across channels, calls, files and tasks
How far its identity spans	Scoped to the Slack workspace it was paired into and the channels it is granted [S2]	Lives in the workspace across every channel, call, file and task, and travels with the agent rather than being pinned to one chat tenant
Memory scope	Builds context from the channels it follows, so users do not re-explain; memory stays scoped to the channels it is in [S1][S2]	An orchestrator with memory plus per-agent memory that persists across channels, calls, tasks and runs
Background / async	Works asynchronously and can plan tasks to complete in the future; the thread carries a live checklist as it works [S1][S2]	Long-running background and event-driven tasks: you hand over a goal, the agent pursues it over minutes or hours and pings you when done or stuck
Model	Runs on Claude, on Anthropic’s first-party service [S2]	Bring your own model — Claude, ChatGPT or Codex — or use Nebula’s own agents with credits [S3]
Admin and governance	Owners and admins govern who can use Claude, pair the Slack workspace with the Claude organisation, and set the organisation usage spend limit; channel work bills to the organisation’s balance, and a one-to-one DM bills to that person’s seat (which must include Claude Code) [S2]	Agents run as members with scoped access and their own connected accounts; each connection is yours and used only on your behalf [S3]
Where it is strongest	Teams standardised on Slack who want an agent in the rooms they already use, zero migration, grounded in Slack’s own context [S1][S2]	The agent-native axis: agent identity, execution on real machines, humans and agents in one workspace
Cost of the agent capability	No separate Claude Tag list price; usage bills to your Claude organisation’s balance under an Owner-set limit, plus the Slack plan beneath it [S2][S4]	Included in the $25 seat for connected agents; Nebula’s own agents draw on topped-up Nebula Credits, and Nebula asks before spending past your top-up [S3]

Read the table honestly. Claude Tag is not a summary bot. It executes real multi-stage work in Slack, and it does so inside the collaboration tool most of these teams already pay for. What it does not do is give the agent its own computer and its own life outside Slack. The distinction this page draws is not “does the agent have a name” — both give it a name — it is where the agent lives, what it runs on, and how far its identity spans. A @Claude scoped to a Slack workspace is an agent inside chat. A Nebula agent is a workspace member across channels, calls, files and tasks, with its own machine.

Where Claude Tag is the right call

This page would be untrustworthy if it claimed a clean sweep. There are real cases where Claude Tag is the better buy:

• You are standardised on Slack and will not move. If your team’s work already happens in Slack, Claude Tag puts an agent in those exact rooms. Nebula asks you to run the agent-native work in a second space; Claude Tag asks you to change nothing. That zero-migration path is genuinely valuable and it is not something Nebula offers.
• Your need is “an agent in the channels we already use,” not “an agent with its own computer.” If the work you want done lives entirely inside Slack — answering in-thread, working through multi-stage tasks on your Slack context, planning future tasks — Claude Tag covers it without a device layer you do not need [S2].
• You want Anthropic’s agent inside Anthropic’s own stack. For teams already on a Claude Team or Enterprise plan, Claude Tag is a natural extension of a vendor relationship and an identity model you already run: paired Slack workspace, usage billing under an Owner-set spend limit, and role-based access control [S2].
• You need the agent grounded in Slack’s own context and permissions. An agent that lives in Slack inherits Slack’s access model and the conversation history it can see. If that context is the whole job, hosting the agent elsewhere is overhead.

The pattern: if the problem is “our Slack should have a capable agent that does real work,” Claude Tag is a strong answer. If the problem is “our agents should do the work — with identity, execution and memory of their own, outside one chat tenant,” the question is not which model to add to Slack; it is where the agent should live.

What Nebula is for instead

Nebula is the agent-native workspace: the workspace where your agents are teammates, not a chatbot bolted onto chat. Concretely, that means three things Claude Tag’s Slack framing does not attempt:

1. Agents are in the room, with their own identities — profiles, scoped access and per-agent connected accounts, acting as themselves rather than as a copy of a teammate’s account.
2. Agents do the work — real tools into the apps your team uses (Gmail, Slack, GitHub, Notion, Linear, Stripe and thousands more), their own cloud computer, and background tasks.
3. One workspace for humans and agents — channels, an orchestrator with memory, agents and tasks in a single place.

You do not have to choose between them out of ideology. Many teams keep their human collaboration where it is strongest and run the agent-native work — delegation, background tasks, agent memory, orchestration — in the workspace built for it. This is not a “rip out Slack” pitch, and it is not a claim that Claude Tag is weak. It is a claim about where the agent lives.

Frequently asked questions

Is Nebula a Claude Tag alternative? Sometimes — if what you actually want is agents that execute work with their own identity, machine and memory, Nebula replaces the need for an agent inside Slack. If what you want is an agent in the Slack channels you already use, Claude Tag does that and Nebula does not try to.

Can I use Nebula and Claude Tag together? Yes, and many teams would. Keep Claude Tag where Slack collaboration is the work, and run agent-native work — delegation, background tasks, agent memory — in Nebula. They are not mutually exclusive.

Does Claude Tag execute work, or only summarise? It executes, inside Slack. Tag @Claude with a request and it breaks the task into stages, works through them with the tools it has access to, posts a checklist in the thread, and replies in the thread with what it created; it can also plan tasks to complete in the future (Anthropic, 2026-06-23). The difference from a Nebula agent is not intent, it is ground: Claude Tag runs inside Slack, on the tools and channels admins grant it; a Nebula agent has its own tools and its own computer and runs the task end to end.

Does Claude Tag run outside Slack? Not today. Anthropic is starting Claude Tag on Slack, where @Claude joins as a team member, and says its goal is to expand where it is available more widely ([S1]). Nebula’s agents live in Nebula’s own workspace, across channels, calls, files and tasks.

Do I need a Claude seat for everyone in the channel? No. By default anyone in the paired Slack workspace can tag @Claude in a channel, and an Owner can restrict who can use it to people in your Claude organisation, or on Enterprise to specific roles. Channel work bills by usage to your organisation’s usage balance, under a spend limit an Owner sets ([S2]). A one-to-one DM from someone who has connected a Claude account bills to that person’s seat instead.

How much does each cost? Nebula is $25 per seat per month with a 7-day free trial; messaging, calls and web research are included, and you bring your own model subscription at no extra Nebula charge (Nebula pricing, read 2026-10-14). Claude Tag publishes no standalone per-seat price: it is available on Claude Team and Enterprise plans, and channel work bills by usage to your organisation’s balance under an Owner-set spend limit (Claude Tag docs, read 2026-10-14). Because it runs inside Slack, your Slack plan applies on top — Free $0; Pro $7.25/user/mo annually ($8.75 monthly); Business+ $15/user/mo annually ($18 monthly); Enterprise+ is contact-sales (Slack pricing, read 2026-10-14).

Does Nebula replace Slack? Not by default, and we will not claim it should for every team. If your organisation’s collaboration depth and compliance posture live in Slack, keep Slack. Nebula is where the agents live.

Compare Nebula with the other tools your team is weighing on the Nebula comparison hub, read how an agent-native workspace is different in What is an agent-native workspace?, or see Nebula pricing.

Sources

• [S1] Anthropic, “Introducing Claude Tag” — https://www.anthropic.com/news/introducing-claude-tag (published 2026-06-23; read 2026-10-14). @Claude joins Slack as a team member; beta for Claude Enterprise and Team customers; multiplayer within a channel; builds context by remembering relevant information from the channels it is in; can plan tasks to complete in the future; tag @Claude and it breaks the task into stages and works through them with its tools, then replies in the thread; Anthropic frames it as the beginning of an evolution of Claude Code and positions it as replacing the existing Claude in Slack app, with administrators able to opt in to migrate within 30 days. Anthropic’s own “65% of our product team’s code” figure is about Anthropic and is not reused as a Nebula claim.
• [S2] Claude Tag docs, “Work with Claude Tag” — https://www.claude.com/docs/claude-tag/overview (read 2026-10-14). Public beta; available on Team and Enterprise plans on Anthropic’s first-party service and not on individual plans (Free, Pro, Max) or third-party deployments; you pair your Slack workspace with your Claude organisation; by default anyone in the paired Slack workspace can tag @Claude in a channel and an Owner can restrict use to the Claude organisation or, on Enterprise, to specific roles; channel and group-DM work bills by usage to the organisation’s usage balance under a spend limit an Owner sets; a one-to-one DM from a member who has connected a Claude account bills to that person’s seat, which must include Claude Code; Claude Tag works in Slack channels, threads and DMs.
• [S3] Nebula pricing — https://www.nebula.gg/pricing (read 2026-10-14). $25 per seat/mo; 7-day free trial; unlimited messaging, calls and web research; cloud computer; bring your own Claude or ChatGPT subscription at no extra charge; Nebula’s own agents draw on Nebula Credits, with a top-up prompt before it spends more; connections include Gmail, Slack, GitHub, Notion, Linear and Stripe, plus thousands of other apps.
• [S4] Slack pricing — https://slack.com/pricing (read 2026-10-14). Free $0; Pro $8.75/user/mo monthly or $7.25 annually; Business+ $18/user/mo monthly or $15 annually; Enterprise+ contact sales for pricing (a limited-time 50%-off-for-3-months promotion applies to Pro and Business+). Used only for the Slack plan that runs beneath Claude Tag.