Chat vs. Cowork: When do you use which?

I’ve seen some confusion online about the difference between “Chat” and “Cowork” in Claude or “Chat” and “Work” in ChatGPT. They look almost the same. What’s the difference? Is one better than the other? Should I only use “Cowork” now because “Chat” is old and inferior?

The actual difference between these two modes comes down to one simple question. Beyond that, there are some nuances around features and availability.

In this article I’ll give you an overview.

Chat vs. Cowork — what’s the difference?

Open Claude or ChatGPT today and you have a choice: Do you want to “chat” or do you want to “(co-)work”? But what does that actually mean? The answer is not obvious because the user interfaces of both look very similar.

The difference comes down to this:

• Chat is a conversation you steer turn by turn: You ask, Claude answers, you refine, you ask again, Claude comes back to you, and so on, until you have what you need. Importantly, you’re present the whole time. Claude, on the other hand, is waiting for your next instruction on what to do.
• In Cowork you give Claude a goal to achieve, and it will work toward it, planning the steps, looking at files or using tools where needed, and returning something finished. You check in rather than steer every move.

In a nutshell: Do you already know what the finished thing looks like, or are you still working that out? Know the shape of the output, hand it to Cowork. Don’t know yet, use a Chat to figure it out. These modes can work hand in hand.

The commonalities most people miss

This brings me to a common misunderstanding I’ve seen online: Cowork is not superior to Chat. It’s not its successor. It’s not always better. That becomes clear when you look at features like Skills and Connectors. Some people think they’re exclusive to Cowork because they encountered them there first. That’s not correct.

Skills are reusable instructions you give Claude once, so you don’t have to re-explain a workflow, a style guide or a piece of domain knowledge every time you start a new conversation. A Skill for proofreading your English, say, or one that knows your publication’s house style.

Tip: In a separate article, I explain how to set up and use Skills as a content professional with concrete examples from my own work.

Connectors link Claude to your other tools and services, like Gmail, Google Drive, Slack or Notion, so it can pull in information or take actions there directly instead of you copying and pasting.

Both live in the same place, under “Customize” in the sidebar, and both are shared across modes by default. A Skill you’ve built works in Chat and Cowork alike. So does a Connector: Once you’ve linked Google Drive, both modes can search it.

There are a few exceptions. Skills packaged inside a “plugin,” along with the plugin’s bundled Connectors, need Cowork because there is no installation option in Chat. And “Record a Skill,” where you screen-record yourself doing a task and Claude turns it into a Skill, only works in Cowork on the desktop app.

But those are the exceptions, not the rule. For the vast majority of Skills and Connectors, which mode you’re in doesn’t matter.

The practical upshot: Picking Cowork over Chat isn’t about unlocking more capability. Most of what Claude can reach, it can reach either way. The biggest difference is who’s in charge.

What’s exclusive to Cowork

Claude can access your files even in Chat. Case in point: I’m writing this article right now with Claude inside Ulysses, my writing app on the Mac. I have Claude open on the left and this article on the right. This works because Claude can read and write this file. It works because of a Filesystem connector I set up myself once, in Claude Desktop’s settings. It is available now across Chat and Cowork.

So what does Cowork actually have that Chat doesn’t?

The difference is in how you get there. In Cowork, you point at a folder, and Claude reads and writes to it immediately, no setup required. The capability is built into the mode itself. In Chat, the same access exists only if you’ve installed a connector for it first, the way I did. So it takes a few extra steps, and that’s probably where the confusion I see online comes from: It’s much more obvious and straightforward in Cowork because doing work for you on your computer is one of its strong suits.

Beyond that, a few things are Cowork-only in practice:

• Browser control. Paired with Claude in Chrome, Cowork can navigate a live, logged-in browser as part of a task: click through a website, fill out a form, pull data from a portal you’re signed into.
• Computer use. Claude can operate your screen directly, clicking and typing across apps, not just working with files.
• Parallel work. For tasks with independent parts, like researching five companies or checking every contract in a folder, Cowork can split the work into separate workstreams and run them simultaneously instead of one after another. This is inherited straight from Claude Code, which Cowork runs on under the hood. More on that later.
• Scheduled Tasks. You can set a Cowork task to repeat, such as a weekly report or a daily briefing, without starting it yourself each time.

As you can see: Claude can do more in Cowork than in Chat. But features like “browser control” or “computer use” would not make much sense with you sitting in front of it and watching the AI do its work. (You can do that, of course, if you feel like it, but then you don’t actually gain anything.)

The recurring theme is: Cowork can do its tasks independently of you — using your computer while you are away, for example.

Where can you use Cowork today?

Chat is available everywhere and on every plan, including Free. Cowork isn’t. Here’s the state of things as I’m writing this:

A few things worth knowing beyond the table:

• Cowork needs a paid plan everywhere. There’s no free tier for it, unlike Chat.
• Computer use, meaning Claude operating your screen directly, is its own research preview, limited to Pro and Max.
• “Record a Skill” needs Cowork specifically on the desktop app and is available on Pro, Max and Team.

Treat this table as a snapshot. Three of these four rows were still labeled “beta” or “rolling out” as I wrote this, and the status had already shifted once in the weeks I spent researching. If you’re reading this a while after publication, check Anthropic’s own documentation before planning a workflow around a specific plan tier.

And what about Claude Code?

Cowork runs on the same agentic engine as Claude Code. Cowork was in fact built on top of it. You can occasionally see that: I’ve had Cowork mention “looking at the code” while working on a plain document. A small leftover from its origins.

Code and Cowork aren’t the same tool, though, and Code can still do things Cowork can’t. The clearest illustration I’ve seen comes from Nolen Jonker at XDA Developers, who runs Claude Code as a personal productivity system without writing any code at all. Jonker’s point: Claude Code reads an entire folder as one connected system, spotting relationships and inconsistencies across every file at once. Cowork and the Filesystem connector, by contrast, move through documents more step by step.

That distinction mostly matters if you’re managing a large body of notes or reference material and want Claude to understand it as a whole. For most day-to-day content work, it’s not relevant.

ChatGPT’s fast-follow: “Chat” vs. “Work”

As much as I like to work with Claude, other vendors also have capable offerings. OpenAI ships a near-identical split in ChatGPT: “Chat” for everyday conversation, “Work” for agentic tasks and “Codex” for actual software development.

While Claude Cowork launched as a research preview on January 12, 2026, ChatGPT Work launched on July 9, 2026, roughly six months later, on the same underlying idea: a coding agent’s abilities, generalized to the rest of knowledge work. OpenAI even says as much itself, pointing to Codex’s growing non-developer usage as the trigger, the same reasoning Anthropic gave for Cowork.

The parallels go even deeper. Work needs the desktop app to access local files, use a built-in browser, and the computer as a whole. This is the same split Cowork has between cloud and machine. It has its own version of Skills and Connectors: Skills even use the same open standard Anthropic created and published, so tools built for one can, in principle, work with the other. Scheduled tasks exist on both sides too.

But this isn’t just OpenAI playing catch-up. ChatGPT has pulled ahead on a few things: All three modes are available on every plan, including Free, while Cowork, as mentioned above, stays paid-only. And its desktop app came with its own built-in browser right away, rather than depending on a separate extension the way Claude did with Claude in Chrome. Anthropic added such a browser just the other day.

One feature worth a closer look is ChatGPT Sites. At first glance, it is similar to Claude’s Artifacts: build an interactive page, publish it, share a link that works for anyone, no account required. What Sites adds compared to Artifacts is packaging. One differentiator is tiered access control: keep it to yourself, share with specific people, open it to your whole workspace or publish it to the public internet. Claude offers only “private” or “anyone with the link.” Also useful: ChatGPT has a dedicated view for managing your published sites and, on some plans, offers a custom domain. On the other hand, Sites is gated to Work or Codex, while Claude’s Artifacts work identically whether you’re in Chat or Cowork.

Where Claude still has the edge is maturity: a head start of several months, broader enterprise controls and features like Record a Skill that ChatGPT doesn’t currently match. For most of my readers, who are already working in Claude, that’s the practical takeaway: Cowork remains the more developed tool for now, but ChatGPT Work is a real alternative, not a knockoff, and worth watching.

The bottom line

Chat and Cowork complement each other. Chat is still best for developing something: an idea, an outline, an article. Cowork, on the other hand, can take over tasks for you: it works toward a given goal even without you being present.

When it comes to Skills, I have often done it like this: worked on something with Claude in Chat and at the end asked it to turn that into a Skill I can then use as the foundation for a Scheduled Task in Cowork and automate it.