Claude Cowork is for handing Claude a piece of finished work: a report, a deck, a cleaned spreadsheet. Claude Code is for building: it works inside a codebase or a folder of files with a terminal and git. Both run on the same agent engine. Most marketers should start in Cowork and move to Claude Code when they want a system they own and can version. Product details below come from Anthropic's own pages as of November 13, 2026, and they change often.
What is Claude Cowork?
Claude Cowork is the part of Claude that does the task instead of describing it. You point it at folders and connected apps like Google Drive, Gmail or Slack, describe the outcome, and it plans the steps, works through them and hands back a document, deck or spreadsheet. It runs on web, desktop and mobile, keeps going when your laptop is closed, and can run a task on a schedule.
Anthropic's own one-line split is the clearest: chat is for thinking with Claude, Cowork is for delegating to Claude, Code is for building software with Claude. Since September, Cowork and chat have been merging into one Claude app. You ask in a normal conversation, and Claude brings in Cowork when the task needs your files or tools. Anthropic says the unified app reached Team plans on November 12; until it reaches your account, Cowork sits in its own tab next to Chat.
What is Claude Code?
Claude Code is Anthropic's agent for software work. It runs in your terminal, a desktop app, the web, IDEs like VS Code and JetBrains, and connects to GitHub. It reads and edits files in a project, runs commands, and commits changes. Anthropic describes Cowork as using the same agentic approach as Claude Code, aimed at knowledge work instead of code.
For marketers, "code" undersells it. A marketing knowledge base, a content pipeline, or a set of brand files is a folder of text. Claude Code works well in any folder of files you want kept under version control, which is why we run this site's blog and SEO work through it. Our Claude Code for marketing guide covers what that looks like day to day.
What is the difference between Claude Cowork and Claude Code?
The difference is the output and who maintains it. Cowork delivers finished work for you to review: a report, a deck, a memo. Claude Code builds and changes the system that produces work: files, scripts, templates and site pages, tracked in git so every change can be reviewed and undone. Cowork needs no terminal. Claude Code assumes you are comfortable reading what it changed.
| Claude Cowork | Claude Code | |
|---|---|---|
| Built for | Knowledge work: research, analysis, documents | Software and file-based systems |
| Where it runs | Claude app on web, desktop and mobile | Terminal, desktop app, web, IDEs |
| Typical output | A deck, report, spreadsheet or memo | Changed files, commits, a pull request |
| Works with | Chosen folders, connectors, a built-in browser | A project folder, terminal, git, GitHub |
| Runs unattended | Yes, scheduled tasks keep going with the laptop closed | Yes, through cloud sessions and automation |
| Who maintains the result | You review each deliverable | The repo keeps the history |
Which one should a marketer use?
Use Cowork when the job ends in a deliverable someone reads: the Monday performance readout, a competitor scan, a campaign recap deck, a cleaned list. Use Claude Code when the job is to build something that keeps producing: a brand knowledge base, a content pipeline, landing pages, or the rules every AI tool reads before it writes. If you are not sure, start in Cowork. You will feel the moment you want version history and a reusable setup, and that is the moment to move a workflow into Claude Code.
- Weekly report from GA4, Search Console and a sheet: Cowork, on a schedule.
- Twenty blog briefs from one keyword plan: Cowork for a one-off batch, Claude Code if briefs become a pipeline.
- Brand voice rules every tool follows: Claude Code, as a CLAUDE.md and skills in a repo. See the CLAUDE.md setup guide.
- A second brain in Obsidian: Claude Code, pointed at the folder. See the Claude Code + Obsidian setup guide.
- Publishing pages on your own site: Claude Code, with a pull request you review before it goes live.
Is Claude Cowork included in Claude Pro?
Yes. Anthropic's Cowork page lists it in Pro, Max and Ultra, and in Team and Enterprise. Agentic tasks use more of your limit than chat, and Anthropic says so directly: Cowork coordinates several sub-agents and tool calls per task. Pro suits short tasks like organizing a folder or a short report. If you hand Claude long jobs every day, Max is the plan Anthropic points to.
Can you use Claude Cowork and Claude Code together?
Yes, and that is how a working setup tends to settle. Claude Code builds and maintains the files: brand guidelines, the knowledge base, templates, the skills that tell Claude how your team works. Cowork uses that context to produce the week's deliverables. Skills and connectors work in both, so a skill written once in a repo can shape what Cowork produces. The knowledge base is the shared layer. Whatever Claude reads about your brand decides how good both outputs are.
What should you set up first?
Pick one recurring deliverable you build by hand every week and hand it to Cowork with the sources named and the format spelled out. Run it for two weeks and fix the instructions each time. Then put your brand context somewhere both tools can read it, as plain files you own. Our guide to Claude skills for marketers covers packaging your methods so Claude follows them. If you want to turn your Claude Code skills into a service you sell, the Claude Code Service OS is a downloadable workflow that walks you through the offer, pricing, outreach and a website for it.
Cowork and Claude Code both write better with your brand in front of them. In Brand Architect, Ophelia builds a knowledge base from your website or materials that any AI tool can read. Build your knowledge base →