Claude Code, Cowork, Tag, and Routines: A Practitioner's Map to the Claude Ecosystem

Posted on Oct 22 • Originally published at revos.ai

Anthropic didn't ship one Claude product this year. It shipped four, and gave three of them names that sound like they should mean the same thing. Ask a few people on your team "what's the difference between Claude Code and Claude Cowork?" and you'll get a different answer each time. Mention "the Claude routine" and you still don't know whether they mean a cron job in the cloud, a task running on their laptop, or something set up entirely inside Slack.

This is a Claude Cowork vs. Claude Code question, but it's bigger than those two. By the second half of 2026 there are four surfaces worth knowing apart:

None of this is a rebrand of the others. Each is a different envelope around the same underlying agent, built for a different job. Here's the map.

The row that matters most for the rest of this guide: whose credentials run the work, and who can see the result. Claude Code and Cowork stay private to you. Claude Tag is visible to a whole channel by design. Routines run unattended. Keep that distinction in mind; it explains more about which tool to reach for than "how technical is the user" does. Plenty of engineers live in Cowork, and plenty of non-engineers now trigger a Claude Code Routine without ever opening a terminal. That question also generalizes well past Claude: every agent should have an identity, but not every agent should have its own authority.

Prefer video? Here's the whole map in one walkthrough:

Claude Code is an agent that reads your codebase, edits files, runs commands, and works with your existing dev tools. The important thing to understand is that "Claude Code" isn't a single app. It's one engine behind several surfaces: the terminal CLI, extensions for VS Code and JetBrains, a Code tab inside the Claude Desktop app, Claude Code on the web, and mobile. Your CLAUDE.md project memory, your settings, and your connected MCP servers (the standard way Claude reaches outside tools and data) work the same way across every one of them, because they all talk to the same underlying engine.

In practice, that means you can start a task in the terminal, hand it off to the web version so it keeps running after you close your laptop, or pull a cloud session back down locally when you want hands-on control again. It's designed to be extended: project memory, reusable skills, hooks that run on specific events, and a headless mode ( claude -p ) for piping output into scripts or CI pipelines.

Who it's for: developers and engineering teams working inside an actual repository, with their own credentials and their own machine (or a cloud session tied to their own account).

This comes up constantly, and the answer is no. They solve overlapping problems with different shapes. Cursor is a fork of VS Code: the AI lives inside the editor, suggesting and applying changes as you work, one file at a time. Claude Code is terminal-native and session-based: you describe an outcome, and the agent plans, edits multiple files, runs commands, and reports back, with or without an editor open at all.

This isn't a fringe question. Stack Overflow's 2025 Developer Survey found 84% of respondents were using or planning to use AI tools in their development process, up from 76% the year before, and 50.6% of professional developers already use one daily. It's the default way most teams now write code. Among developers who'd tried an autonomous coding agent specifically, the same survey found adoption split across ChatGPT (81.7%), GitHub Copilot (67.9%), and Claude Code (40.8%): evidence that most teams aren't choosing one tool and stopping, they're running several. The "Where Cursor still fits" section below covers how that plays out day to day.

If your team already links agentic tools to a real project, see how we structure data so AI agents can query it reliably. The agent is only half the story; what it can actually read matters just as much.

Claude Cowork is easy to misread as "Claude Code for non-engineers," and that undersells it. Cowork runs the same agentic engine that powers Claude Code, inside the Claude Desktop app, without opening a terminal, but it's organized around a different unit of work. Instead of a git checkout, you point it at Projects: local folders paired with standing instructions and a project-scoped memory that stays on your machine. Instead of responding turn by turn, Claude works toward a described outcome and you check back once it's done.

The piece that makes Cowork genuinely different from "Claude Code with a nicer UI" is Dispatch, a background planner that splits a multi-step brief into subtasks and routes each one to the surface that fits: knowledge-work pieces stay in a Cowork session, coding pieces get handed to a Code session. Ask Dispatch to "summarize the open reliability-tagged issues and draft a status update," and it can pull that off from your phone while your desktop does the actual work.

Two things worth knowing before you reach for it:

Who it's for: anyone doing file-and-document-heavy work who doesn't want to open a terminal, including engineers, since Dispatch explicitly hands coding subtasks to a Code session on their behalf.

For the bigger idea behind letting an agent own more of a workflow end to end, see our piece on agentic data engineering. Cowork's Dispatch model and the "describe the outcome, review the result" pattern it uses show up there too, just applied to data pipelines instead of documents.

If your team already has Claude working inside Slack, it's worth checking which version you're on, because there are two live right now with genuinely different account models.

Claude Tag (currently in public beta) is Claude working in your team's Slack channels under the organization's own shared credentials, not any individual's Claude account. An admin sets it up once per channel at claude.ai/admin-settings/claude-tag, and after that, anyone in the channel can just tag @Claude with no setup of their own. Each thread spins up a fresh, sandboxed working session (built when the thread starts, released when it goes quiet) running on the same engine as Claude Code on the web. It posts a live checklist as it works, and anyone in the thread can redirect it by replying, without re-tagging it.

That's the real distinction from Cowork and Code: this work is visible to the whole channel by design, and it's billed against the organization's own usage balance, not any one person's plan. It's currently available on Team and Enterprise plans. Pro and Max plans still use the older, individually authenticated Slack integration, which runs under each person's own account and their own limits. Anthropic is retiring that older integration for Team and Enterprise workspaces in favor of Claude Tag. There's no public cutover date, so ask your account team rather than assuming a timeline.

Who it's for: teams that want shared, visible work a whole channel can watch and steer: incident triage, decision threads, or status rollups that shouldn't live in one person's DMs.

We cover where this fits alongside other agent categories in our rundown of enterprise AI agents, if you're mapping this against a broader agent rollout.

This is the part of the ecosystem most likely to get someone confused mid-conversation, because Anthropic uses the word "Routines" for at least three separate mechanisms, and none of them share a task list with each other.

Who it's for: anyone who wants Claude to do something without a person kicking it off in real time: an engineer scheduling nightly checks, or a channel that wants standing status updates with nobody assigned to remember it.

The practical takeaway: if a teammate says "I set up a routine," ask where. A cloud routine keeps running when their laptop is shut. A local one doesn't. A Slack routine only exists inside that one channel. They're three different systems that happen to share a name.

None of this makes Cursor obsolete. The "which one wins" framing that dominates most comparison posts online misses how teams actually use these tools together: most professional developers now use more than one AI coding tool, per the adoption figures above, rather than settling on a single winner. Cursor's strength is still the in-editor, keystroke-level loop: inline suggestions and quick edits while you're heads-down in one file. Claude Code's strength is the session-level agent loop: describing an outcome and letting it run across files, tests, and commands with less of your attention.

Worth knowing if you're evaluating either company's staying power: SpaceX fully acquired Cursor's parent company, Anysphere, in an all-stock deal finalized on August 14, 2026, per an SEC Form 8-K filing, as reported by Yahoo Finance. Cursor now operates as part of SpaceX's newly formed "SpaceXAI" division rather than as an independent startup. That's a genuinely new fact worth factoring into a build-vs-buy decision, separate from which tool writes better code today.

Most teams we talk to don't pick one. They keep Cursor open for fast, in-file edits and reach for Claude Code (or Cowork, for the non-coding half of the job) when a task is big enough to hand off entirely.

We're not writing this as outside observers. RevOS's own CLI is built specifically to be driven by AI coding agents like Claude Code and Cursor. That's a deliberate design choice, not an afterthought, because the whole point of the product is letting an agent build your data layer from plain-English intent instead of hand-written pipelines.

And the meta-example: this very post exists because of a Claude Code Routine. A label on a GitHub issue triggered a cloud routine that researched the keywords, pulled the competitive landscape, drafted this MDX file, and ran it through a validation pass: the same "Routines" mechanism described two sections up, running unattended against our own content pipeline. It's the clearest sample use case we have, because you're reading its output right now.

No. Cursor is a fork of VS Code with AI features built into the editor UI. Claude Code is a terminal-native agent that can also run inside an IDE, a desktop app, or a browser tab, the same engine either way. The practical difference is where you spend most of your time: inside an editor loop (Cursor) or handing off a full task to an agent that plans, edits, and runs commands across a session (Claude Code).

Developers and engineering teams working inside an existing repository who want to hand off a whole task, not just one line of autocomplete, and get back a plan, edited files, and a report. It fits equally well driven from a terminal, an IDE, a desktop app, or piped into a script or CI job.

Claude Cowork is an agentic workspace built on the same engine as Claude Code, designed for outcome-oriented work on local files and folders (contracts, spreadsheets, research) rather than a git checkout. You describe the outcome you want and check back once it's done, instead of responding turn by turn.

No. It's available on paid Claude plans (Pro, Max, Team, Enterprise), with no separate free tier, though it's included at no extra cost once you're on one of those plans.

An agentic workflow is a task an AI agent completes by looping through perceive, reason, act, and check steps on its own, rather than answering one prompt and stopping. In the Claude ecosystem, that loop is the same whether it runs in a terminal, a desktop workspace, a Slack thread, or on a schedule. The surface changes, the underlying agent doesn't.

A concrete one: "write tests for the auth module, run them, and fix any failures." The agent explores the codebase, writes the tests, runs the suite, reads the failures, edits the code, and reruns the tests, looping until they pass, without a person approving each individual step along the way. A single prompt in, a working result out.

It can act agentically when it uses tools, browses, or runs code across multiple steps, but its default chat mode is single-turn. "Agentic" describes a mode of operation (planning and acting toward a goal across a session), not one specific product. Claude Code, Cowork, and Claude Tag are all built around that agentic loop by default.

Neither wins outright. They're shaped for different moments. Cursor is strongest for in-editor, keystroke-level suggestions while you're heads-down in one file. Claude Code is strongest for session-level work: describing an outcome and letting an agent plan, edit multiple files, run commands, and report back. Most teams we see run both rather than standardizing on one.

Writing and fixing code inside an existing repository, running and interpreting test suites, reviewing pull requests, and automating routine engineering chores like dependency bumps or log-triage scripts piped through claude -p. Teams also use it for tasks that don't look like coding at all (refactoring config files, writing docs from a codebase, or scripting one-off data cleanups) because the same agent that edits code can just as easily edit text.

This article was originally published on the RevOS blog.

RevOS works inside Claude, ChatGPT, Slack and Teams, so agents answer from the same governed revenue data. Want to see it on your own data? Book a RevOS demo.