Claude Cowork vs Claude Code: Which to Use After the Merge

What "Claude Cowork" means now

Cowork was Anthropic's agent for office work, a separate place next to chat. You picked Cowork in the message box, described a multi-step job, and Claude worked through it and handed back finished files. On September 16, 2026, Anthropic started merging Cowork and chat into one Claude.

In the merged Claude there is no mode to pick: Claude decides whether to answer or run a task, and bigger work comes back as editable files, says Anthropic's help article on the change. So the old Claude Cowork vs chat question has a new answer: on Pro and Max accounts the rollout has reached, they are the same conversation.

Chats, projects, connectors and skills carried over, and the Code tab did not move, so Claude Code is unchanged. Our news story on the merge has the full timeline.

Claude Cowork not showing up? Check your message box

What is the difference between Claude Code and Claude Cowork?

The difference between Claude Code and Claude Cowork is where the work lands. Cowork returns a finished file or a completed chore; Claude Code changes files in a folder you chose, and you review each change. If you searched for Claude vs Claude Code vs Claude Cowork, the first and the last are merging into one Claude.

New to the coding side? Read what Claude Code is first. Here is Claude Code vs Claude Cowork side by side:

Claude Cowork vs Claude Desktop is not a real choice: Desktop is the app, and both Cowork tasks and the Claude Code tab live inside it.

Claude Cowork vs Claude Code: route the job, not the tool

For a non-coder, the Claude Code vs Cowork decision rarely needs more than three questions:

1. Do you read the result or run it? A report, deck or summary goes to Claude. A page, script or tool you will reuse goes to Claude Code.
2. Will you keep changing it? Ongoing projects, such as a website or a price list tool, belong in Claude Code, where every change is reviewable.
3. Do you want to approve each step? Both can ask first; Claude Code adds diffs, Plan mode and checkpoints to roll back to.

Here are ten Claude Cowork use cases next to Claude Code jobs:

Hand-offs between the two

A recent Claude Desktop update added a Hand off to Claude Code option to the menu under a design's name, which opens Claude Code with a prompt to build that design in your project's code. There is no button for the other direction, but the two work well in turn: Claude Code builds a script that cleans your weekly export, and Claude writes the report from the clean file every week.

Claude Cowork tutorial: your first task in Claude

Getting started with Claude Cowork takes about as long as writing a good email. Below is how to use Claude Cowork in the merged Claude, with the one difference on the old layout noted in step 1: Claude Cowork for beginners, in five steps.

Before you start

Run the task

1. Open Claude on the web, in Claude Desktop or on your phone. On the old layout, select Cowork in the message box.
2. Keep the permission setting on Manual for your first run.
3. Describe the outcome, format and inputs as you would to a colleague, and attach the file or name the connected app.
4. Approve or deny each action. Files Claude creates appear alongside the conversation.
5. Check and download the result. You can also follow and answer a running task from the mobile app.

Use [THE FILE, FOLDER OR CONNECTED APP] to produce [THE OUTCOME, FOR EXAMPLE A ONE-PAGE SUMMARY OF LAST MONTH].
Deliver it as [A WORD DOCUMENT, A SPREADSHEET OR A SHORT DECK] that a busy owner can read in two minutes.
Show me your plan before you start. If something is missing or unclear, ask instead of guessing.
Do not send, delete or share anything without asking me first.

Make it repeat with a scheduled task

In the merged Claude, say in any conversation what to do and how often, answer Claude's questions, review the name, schedule and instructions, and click Schedule. Anthropic's scheduled tasks guide says tasks run hourly, daily, weekly, on weekdays or on demand, and fire with your computer asleep unless they need local files. On the old layout, click Scheduled in the sidebar, then New task, or type /schedule in a Cowork task.

Our merge story walks through setting up a weekly scheduled task on a Google Drive sheet. Handing recurring lead, email and marketing jobs to AI is what our AI automation course teaches.

Claude Code tutorial for non-coders: a first task with no terminal

Claude Desktop includes Claude Code, so the Code tab needs no extra install and no terminal, only a paid plan (Free accounts see an upgrade prompt).

1. Install Claude Desktop (Mac, Windows, or Linux in beta) and sign in.
2. Click the Code tab at the top of the sidebar.
3. Pick Local and open a small folder in the row under the prompt box, such as a copy of last month's exports.
4. Check the permission mode in that row: Manual makes Claude propose each change and wait.
5. Ask something safe first, like "tell me what the files in this folder are", then one small change. Click the line count (it looks like +12 -1) to see what changed.

Here is the same kind of job in the terminal version, on a test folder of made-up bakery orders:

Prefer the terminal?

On Mac, Linux or WSL:

$ curl -fsSL https://claude.ai/install.sh | bash
# then, in a new terminal window:
$ claude --version
$ cd ~/Desktop/my-project
$ claude
$ 

On Windows, in PowerShell:

PS> irm https://claude.ai/install.ps1 | iex
PS> 

The first claude run asks you to log in, and you finish the login in your browser. Our guide on how to install Claude Code covers the common errors, and how to use Claude Code walks you through a first weekend project.

Is Claude Cowork safe? Approvals side by side

Both start from the same idea: Claude asks before it acts. The settings differ, though, and Claude Code's permission modes page says Cowork does not use Claude Code's modes.

In the terminal, Shift+Tab cycles through the modes. In the Desktop Code tab, the selector under the prompt box remembers your choice for each folder.

Scheduled tasks in Claude and Claude Code, compared

There are three schedulers worth knowing (Claude Code's /loop command also repeats a prompt, but only while that session stays open). Two of them share one setup dialog: if you create one of Claude Code's cloud scheduled tasks with no repository and no GitHub or API trigger, it becomes a claude.ai chat task instead.

Use Claude's scheduler for reports and inbox summaries, a cloud task for work on a GitHub repository (until recently called routines), and a local task for files that live only on your computer.

Plans, price and plugins: is Claude Cowork free?

No. Cowork tasks, scheduled tasks and Claude Code all need Pro, Max, Team or Enterprise (Claude Code can also bill pay-as-you-go API credits instead). On Claude's pricing page, Pro costs $20 a month, or $17 a month when you pay $200 for the year, and Max starts at $100 a month.

Our Claude Code pricing guide compares every plan. The Free plan does get Docs, Slides and Design, which left beta for every plan on October 8, 2026.

claude.com/pricing

It all comes out of one allowance: Claude's pricing page says activity on the web, desktop, mobile and in Claude Code "draws from the same pool".

Plugins, skills and connectors: what carries over

• Account installs travel: a plugin added in Customize > Plugins also appears in Claude Code when your next session starts.
• Command-line installs stay put: a plugin installed with /plugin stays on that computer, and Claude's tasks do not read Claude Code's ~/.claude folder.
• Not every part works everywhere: skills load everywhere, hooks and agents only in Cowork and Claude Code, and plugins with their own programs only in Claude Code.

Deciding what to install? See our pick of the best Claude Code and Claude Cowork plugins.

What to do next

Pick one office job from the ten above and run it in Claude this week, with Manual on. Then start one thing you will keep changing, such as a landing page or a price list, in the Code tab of Claude Desktop. Our Claude Code course teaches that second half step by step, for people who have never written code.