I used to believe that Claude Code was just for the top [engineers], but trust me it's not. I don't have a development background, and I've built three live websites with it. The one you're reading right now is built with it too.
If "just use Claude Code" makes you picture a black terminal window full of text you can't read, that picture is out of date. In the Claude desktop app, Claude Code is a tab. My take: all you gotta do is switch the tab and it looks almost the same.
You need a paid plan, one folder, and about 15 minutes.The site you're reading, built with Claude Code by a non-coder. Live on September 25, 2026.
One honest note before you start: I work in the terminal, because that's how I learned it. You don't have to, and the last section says why.
What you need (as of September 25, 2026)A paid plan. Claude Code is on Pro and up, not Free. Pro is $20 a month, or $17 a month billed annually, per Claude's pricing page.
The Claude desktop app on a Mac or Windows PC (Linux is in beta), per Anthropic's desktop quickstart. Nothing else to install.
One folder you don't mind it touching. A new empty one is perfect.
Work laptop? Ask IT before you point it at company folders. On Team and Enterprise plans, your admin controls what it can do.
Skip for now: the terminal, VS Code, and every "20 settings you need" list.Claude's pricing page, September 18, 2026.
If you're still on Free, what Claude's free plan actually includes shows what you'd be upgrading from.
Step 1: Click Code, one tab over from chat
Claude desktop app → sign in → Code (at the top of the window). If Code asks you to upgrade, you're on Free.Anthropic's desktop quickstart, captured September 25, 2026.
Cowork and chat merged on September 16, 2026, and people worried the tab went with it. It didn't. Anthropic's merge note says "The model picker and the 'Code' tab are where they were." If you don't see it, open the sidebar, and Code shows up in the top bar.
Step 2: Point it at one new folder, not your whole drive
Code tab → Local → Select folder. Make a new folder first (I'd call it claude-first-run) and pick that.
This is the one real difference from chat. In my words: the only thing is you can pick your repo or your folder and that's it. "Repo" is just the coder word for a project folder.Anthropic's desktop quickstart, captured September 25, 2026.
Why a new folder: Claude Code can create, edit and move files inside whatever you give it. Anthropic says its checkpoints are "not a replacement for version control." A fresh folder, or a copy of one, is your undo button.
Step 3: Leave it on Manual so you approve every change
Prompt box → the mode button next to Send → Manual. Manual is the default, so on a first run you usually just leave it alone.Anthropic's Claude Code desktop docs, captured September 25, 2026.
On Manual, Claude asks before it edits a file or runs a command, and shows you the change to accept or reject, per Anthropic's desktop docs. Ignore Accept edits, Auto and Bypass permissions on day one, and on a work laptop, ignore anyone who tells you to skip permissions.
Step 4: Give it your first job, which is you
The first thing I'd do is the thing I say all the time. Spend time riffing: I am a non-coder, I run a one-person operation, I manage a bot team. Tell it everything about you.
Then have it save that to a file, so every future session starts knowing who you are. Paste this and fill in the brackets (talk as long as you want):
I don't code. I work full time as [your job]. I [manage a team of 4 / work solo].
Outside work I [side project, goals, what eats my week].
Here's a normal week for me: [ramble for two minutes].Save what you learned about me into a file called about-me.md in this folder.
Then read it back and give me the 3 biggest opportunities where you could
save me time this month, smallest first.Time box: 15 minutes. Applicable for: anyone with a job and a to-do list (ops leads, HR, teachers, managers, people with a side business).
Step 5: Check the folder, not the chat, to know it worked
Chat can tell you it did something. Code actually does it, so the proof is a file.You saw a change to approve. On Manual, Claude shows you about-me.md before it writes it. Accept it.
The file is in your folder. Open the folder in Finder or File Explorer. If about-me.md isn't there, it only talked, and nothing happened.
The opportunities sound like your week, not a generic productivity list. If they're generic, tell it more and ask again.If something reads wrong, ask it why in plain English. That's the whole fix-it skill on day one.
Step 6: When it breaks, paste the error into a fresh chat
Something will break eventually, usually a long red error message. My fix is boring. Open a new chat window, paste it on another Claude Code chat window, ask it to fix it. That's the worst thing that can happen.
Then ask what went wrong in layman's terms. Most of the time the answer is "this thing was missing, I already fixed it."
The bigger risk is scope creep. Before you build something real, write down what "done" looks like, or you'll keep building forever.
I'm guilty of it right now. I've been editing an emulator game, a Pokemon game, for days, well past 24 hours of my own input, and I'm still adding customizations. Ironically, scope creep.
Step 7: Give it a to-do list so the ideas don't pile up
Once it knows you, the ideas start coming, and they get messy fast. I used to leave notes files scattered everywhere. Now I keep the ideas in a free Linear account, which is like a Trello board for your AI, and knock them down like a checklist.My Claude connectors menu, September 2026. Linear is already in there.
Claude has a Linear connector, and Anthropic's desktop docs list Linear among the tools the Code tab can connect to. Treat this as week two, not day one.
You don't have to be an expert to build real things
This is what Code gives you that chat doesn't: it builds actual stuff in a real folder. This site is built with Claude Code too, on Astro, Tailwind and Vercel. Those names sound scary, and it's a lot at first, but once you learn it, it becomes second nature.My three Claude Code sites, on camera (6 min). The "free" is the hosting; Claude Code still needs Pro.Before you build something big, know the basics of what you're making: what the app needs to do, at a high level. You don't need a course, just a plan on one page.
Other people coming from Cowork land in the same place. After moving projects over from Cowork, u/Jefferheffer wrote on r/ClaudeAI: "It's not that much harder than cowork and dang it did a much better job at finding missing pieces of context."
Nolen Jonker, a non-coder testing it for XDA, put it this way: "Turns out I didn't need to use or even understand half of the coverage on Claude Code to actually benefit from it."
Stay in chat if you're not building anything
Be honest with yourself first. Are you gonna build an app? Are you gonna build anything serious? If you can do your work in chat, Cowork tools included, you don't need Claude Code.
That's a change from what I used to say. In July I told people to start with Cowork because Claude Code was the big brother. My view now: you don't need it, but there's no reason not to try it, because it's a tab.
It's not all or nothing. You can toggle between the tabs.
If you're still deciding, Claude Cowork vs Claude Code draws the line between the two doors, and Claude guides maps the rest of what Claude does on a normal workday.
Should you learn the terminal? Not on day one
Would I tell a regular person to use the terminal? No.
That's gonna slow you down. It's gonna take you months. You're gonna have to learn the shortcuts, the tricks, the interface, and if you've never used a terminal, trust me, it's terrible.
I only use it because I started when Claude Code was terminal-only, and it took me weeks to get comfortable. I work in the terminal and VS Code because I like seeing the folders. That's just me being used to it.
You don't need to see them. Ask it to be your eyes: "Can you tell me the list of the folders in this directory? Let's do some spring cleaning." Most days, the app I actually open is Codex, not a terminal, because it looks simpler.
You lose nothing by starting in the app. Anthropic says the desktop app and the terminal run the "same underlying engine" and can work on the same project. A few power features (like agent teams) are terminal-only. If you want the Codex side, Codex vs Claude Code covers which one to open first.
My rule: you don't have to be an expert, you just gotta get over the fear.
Where this comes from
The plan, tab and permission facts come from Anthropic's pricing page, its Claude Code docs and the September 16 merge note, all checked September 25, 2026. The app and connector screenshots are mine.
What I haven't done: run this exact first job in the desktop Code tab, since I work in the terminal, or test it on Windows.
Published September 25, 2026. Last reviewed September 25, 2026 against Anthropic's docs and pricing page.
Quick answer: one question decides it. Does this task need a file that lives on your laptop's hard drive? If no, fire it off from your phone and shut the lid. If yes, your desktop app has to stay open, and the laptop has to stay plugged in.
That second half is the part that bites. The task does not stop when your laptop sleeps or your battery dies, and it does not error out when it loses your files. It just gets worse without telling you.
If you searched "claude cowork on phone," "how to use claude cowork mobile," or "claude cowork dispatch vs cloud," this page settles the decision first, then untangles the two different things both called "Cowork on your phone."
The one question that decides everything: does it touch a local file?
Everything else on this page is a footnote to this rule.
Anthropic's cross-device help article states it in one sentence: "A session in the cloud can read and write files in folders you've connected on your computer only while the desktop app is open on that computer. If the app is closed, the session keeps running but can't reach your local files."
Notice that the session keeps running. It does not stop, and it does not tell you.What the task needs
Laptop can be shut?
WhyEmail, calendar, Slack, Drive (connectors)
Yes
Cloud session reaches them over the internetWeb research and summarizing
Yes
Nothing local involvedWriting, drafting, restructuring text you paste in
Yes
The context is in the promptA folder on your hard drive (Downloads, a local vault, project files)
No
Needs the desktop app open on that machineAnything editing a video, a design file, or a local export
No
The file only exists on your machineLive artifacts and browser/computer use
No
Desktop-only per the help centerThe shorthand I already use for scheduled tasks holds here too: cloud in, cloud out; local files, local machine. That is my rule, and the surface you start from does not change it.
I unpacked the scheduling half of it in Claude Cowork scheduled tasks; this page is the same rule applied to which device you are holding.The 60-second version, from my Shorts: 5 Claude Cowork connectors that do your boring work for you.Keep the laptop plugged in, or the run dies mid-task
This is my actual hack, and nobody writes it down.
When I take work on the go, it is light tasks. The heavy stuff, editing my shorts and long-form videos, takes a long time and I am on it, so I let that run and step away. But I still take it with me, because Claude hits judgment calls.
It will stop and ask something like "Chris, you don't have the screenshot, do you want to use this," and then just sit there. Not running. Waiting.
That is why I go mobile at all. I don't do the work from my phone. I just make sure I am not the bottleneck when it needs a decision.
Anthropic frames the same thing in the Cowork web and mobile launch post: "When Claude reaches a call only you can make, it asks, and the question reaches your phone."
So here is the hack: have the computer on and plugged in.
If it fades away, if it goes to sleep, you are done. If the battery dies, you are done. Power is the whole thing.
What goes wrong for me is simple: I come back and the session is dead. I have not had it hand me a confidently wrong answer.
And the mechanics back the hack up. Anthropic's Dispatch help article lists the requirements plainly: "Your computer must be awake and the app must be open for Claude to work on tasks." The setup flow even offers a toggle to keep your computer awake. Anthropic built a button for it, so it's a real problem.
One more trick worth stealing, because it is the thing that surprised me most: ask it for the file path. When it finishes a video render, I ask for the link and it hands me the path from the laptop.
Click it, and I can watch the output on my phone. You do not need the file to be in the cloud to check the work.
The silent failure: your phone task looks finished and used none of your documents
The ranking pages skip this part, and it's the expensive one.
A normal software failure announces itself. This one does not. Your session keeps running with its connectors and skills, and hands you a polished, confident answer built on none of your actual files.
u/Secure_Sorbet_8671 named it in a PSA thread on r/ClaudeCowork: "The big one is local files.
You connect folders on the desktop and a session only reaches them while the desktop app is open, so if your context lives in a local vault like mine, anything you fire off from the phone with the laptop shut has your connectors and skills but none of your files."
The interface does not save you either. u/Gh0stw0lf on the same subreddit put it bluntly: "They have projects on your computer that have local files be unable to do that and the UI doesn't clearly point that out."
So the defensive habit is simple and it costs you nothing.Before you shut the lid, ask yourself which folder this task will open. If you can name one, leave the desktop app running.
If you fire something off from the phone and the output feels generically correct, check whether it ever named one of your real files.
For anything pointed at a local folder, treat "laptop plugged in and app open" as part of the prompt.That's the trap. It looks finished, and it did the wrong job.
Dispatch and cloud sessions are two different products, and only one survives the lid
Half the pages ranking for this query describe a world that ended on July 7, 2026. Here is the current split.Dispatch
Cowork cloud sessionWhere the work runs
Your own desktop
Anthropic's serversLaptop can be asleep?
No, must be awake with the app open
Yes, work continues in the backgroundPlans
Pro or Max
Max, Team, Enterprise; rolling out to ProThreads
One continuous thread, no way to start or manage a second
Normal sessions you start and resumeBest mental model
Remote control of your machine
A machine you do not ownDispatch is remote control. Per the Dispatch help article, it needs an awake computer, an open app, a Pro or Max plan, and an active internet connection on both devices.
It also has a limit you should know before you build a habit on it: "There's no way to start a new thread or manage multiple threads." It is one long conversation you keep messaging.
Cloud sessions are the opposite. The Cowork launch post says it directly: "Work continues in the background. Close your laptop and Claude keeps going."
I had a hunch about this and asked to be fact-checked on it, and the hunch was right. With Dispatch you invoke a session on the machine and then walk away from it. Starting fresh from the phone gives you a new cloud session. That's a separate thing from what is on your desk.
That gap is exactly what bugs me about it, and it is why I have been leaning on Codex and GPT's remote work for on-the-go sessions lately. I do not have to invoke anything first. I can just say I want to start something new and start.
That is my preference, not a benchmark. If your work is knowledge work sitting in connectors, Cowork cloud sessions handle it fine and you never touch Dispatch.
Anthropic's own line for the split, from the Dispatch doc: "Development tasks run in Claude Code; knowledge work runs in Cowork." If you are still deciding which cockpit you belong in, Claude Cowork vs Claude Code is the upstream decision.
If Cowork isn't on your phone, it's your plan, not you
A lot of people are doing nothing wrong and still seeing nothing.
u/tenaciousdweeb, on r/ClaudeCowork: "I have the Pro plan and I've tried everything and still no Cowork for me on mobile. I feel like I'm the only one who can't use it. I'm so frustrated."
That is the rollout, not a settings problem. Anthropic's help center, as of August 7, 2026: "Claude Cowork is in beta on web and mobile for Max, Team, and Enterprise plans, and will be rolling out to Pro plans over the next several weeks."
Three things to stop doing while you wait.Stop looking for a separate app. There isn't one. Cowork lives inside the regular Claude mobile app.
Stop expecting desktop sessions to appear on your phone. u/jaylan101 hit this: "Also my desktop cowork sessions don't show up on mobile so I don't see how pass off works." Resume behavior across surfaces is improving but is not a guarantee today.
Stop shopping for a second computer. The "buy a Mac Mini as your always-on host" advice still ranks and still gets repeated, and for cloud-eligible work it is now an expensive answer to a solved problem. You need an awake machine for local files. That is it.If you do have Dispatch on Pro but not mobile Cowork, that mismatch is documented, not a bug. Different features, different plan requirements.
The doubled limits ended August 5, so a phone habit costs more than it did last week
Know this before you get comfortable firing off tasks all day.
Anthropic's launch post extended doubled Cowork usage limits "through August 5." That window closed two days before this was published. Whatever consumption felt like in late July is not what it feels like now.
This matters more on mobile for a boring reason: your phone makes it way too easy to fire off another task while you wait in line. And each one is multi-step agent work, not a chat message.
You don't have to use it less. Just stop re-firing.
Ask for a status update on the session that is already running instead of starting a parallel one. If you want the full picture of what burns capacity and how the tiers actually behave, Claude usage limits explained covers it.
What Anthropic's own page promises, and what it quietly requires
Here is the pitch, straight from Anthropic's Cowork page, captured on July 9, 2026:"Steer from anywhere" is true, but it leaves a lot out.
Steering from anywhere is real: you can watch progress, answer the judgment calls, and redirect from your phone. u/strraand described exactly this on r/ClaudeCowork: "I can close the lid, go for a walk with my dog and still be able to follow the progress and adjust from my phone."
Working from anywhere comes with a condition. The condition is the local-file rule at the top of this page, and the small print for it lives in the help center, not on the marketing page.
What I would actually send from my phone first
Do not start with your most important task. Start with one where you would notice immediately if it went sideways.Best first phone task: something built entirely on connectors. Have it read your inbox and calendar and tell you what actually needs you today. Nothing local, so the lid can be shut the whole time.
The one I run most: a heavy job I started at the desk, that I then babysit from my phone so I can unblock it the second it hits a judgment call. Laptop open, plugged in, sleep off.
The trick worth copying: when it produces a file, ask for the path or link. You can open it on your phone and check the work without going back to the desk.
What I would not send from the phone: anything pointed at a local folder that I am not physically near. The problem is it doesn't fail loudly.
Skip entirely for now: anything that depends on a live browser login or a desktop-only artifact. Those still want you at the machine.For the full menu of jobs worth handing over in the first place, 20 real Claude Cowork use cases has the list, and the connector-driven ones are your phone-safe candidates.
How this was checked
Product facts come from Anthropic's own pages, linked inline at each claim: the cross-device help article, the Dispatch help article, and the Cowork web and mobile launch post. User reports are public Reddit threads, linked where quoted.
The plugged-in rule, the judgment-call babysitting pattern, and the file-path trick are my own working habits, labeled as mine.
I have not personally been handed a wrong answer by the local-file trap, so that section is built from Anthropic's documented behavior and named community reports, not from a story of mine. My failure mode has been the session dying with the machine, which is why the power hack is the part I actually enforce.
Things Anthropic does not document, so this page does not claim them: exact rollout dates by country or plan, what happens to an in-flight local-file task at the moment you close the app, and whether the doubled-limit promo affected anything beyond the Cowork limit.
Published and last reviewed August 7, 2026. Product facts checked against Anthropic's support center and launch post on that date. Cowork on web and mobile is in beta for Max, Team, and Enterprise with Pro rolling out; doubled Cowork usage limits ended August 5, 2026. These products change often, and the linked official pages are the source of truth.This post is part of Claude Guides, the hub with every plan decision, task comparison, and setup guide for using Claude without code.
Quick answer: pick by billing model, not by features. Claude Cowork draws from the Claude plan you already pay for, $17/month annual or $20 monthly on Pro, with nothing extra to buy. ChatGPT Work bills as metered credits from a pool it shares with three other agents.
Feature-wise they do the same job. The differences that will actually bite you are the ones nobody on this search result page has written down yet.
My rule for the four surfaces: Chat answers. Cowork and ChatGPT Work do your office work. Claude Code and Codex build software.
That extends the split from Claude Cowork vs Claude Code, where the rule was "Chat answers. Cowork does your office work. Claude Code builds software." OpenAI has now shipped its own version of the same three-lane structure, which is why this comparison exists at all.
Four things people get wrong about these two, then my pick.
The comparison in one tableClaude Cowork
ChatGPT WorkWhat it is
Agent for non-coding knowledge work
"An agent designed for longer, multi-step work and finished deliverables"Announced
Early 2026, GA on paid plans
July 9, 2026, rolling out over "the coming days"Where it executes
Remotely, on Anthropic's servers
Cloud, same as CodexLocal file access
Through the Claude Desktop app only
Desktop app only. Web and mobile cannotHow you pay
Included in your plan allocation. No separate SKU
Metered credits from a shared agentic poolShares its budget with
Nothing. It is your plan
Codex, ChatGPT for Excel, Workspace AgentsEntry price
Pro $17/mo annual, $20 monthly. Max from $100/mo
Included with eligible paid accounts, per OpenAI's rollout note. Credits meteredSibling surfaces
Chat, Cowork, Claude Code
Chat, Work, CodexCompliance API coverage
Not captured, per Anthropic's docs
Follows standard ChatGPT workspace controlsTwo products, same job, four corrections needed before the table above means anything.
Correction 1: ChatGPT agent mode is retired, so most comparisons are describing a dead product
Search this topic today and you will get a stack of articles comparing Claude Cowork to "ChatGPT agent mode."
That product is gone.
OpenAI's help center says it in one line: "ChatGPT agent is no longer available. Use ChatGPT Work for longer, multi-step tasks and finished deliverables." The same page notes that Operator, the earlier browser-driving agent, was folded into agent mode before that, and "the Operator website is no longer accessible."
So the lineage runs Operator, then agent mode, then ChatGPT Work. Two renames in about a year.
The product you are actually comparing against Cowork is ChatGPT Work, announced July 9, 2026. ChatGPT now has three surfaces: Chat for conversation, Work for multi-step deliverables, Codex for software. If that structure sounds familiar, it is the same three-lane split Anthropic shipped with Chat, Cowork, and Claude Code.
One practical note before you go looking for it: OpenAI says ChatGPT Work "is gradually rolling out to eligible accounts over the coming days." If it is not in your account yet, that is why.
Correction 2: the local vs cloud story is backwards in both directions
You will see this claim everywhere, including in the AI summaries at the top of this search: Claude Cowork is the local-first one, ChatGPT is the cloud one.
It is backwards.
Anthropic's own getting-started documentation states that "Cowork runs your tasks remotely (in beta). Claude's work runs on Anthropic's servers, in an isolated environment."
The local part is a bridge, not the execution: "When a task needs something on your computer, like a local file or your browser, Claude reaches it through the Claude Desktop app on that computer."
Meanwhile OpenAI's documentation is equally blunt about its own limit: ChatGPT "Work on web and mobile cannot directly access files on your computer." Local file access requires the desktop app, and on the free and Go tiers it is listed as "Limited (desktop app)" on OpenAI's pricing page.
Read those two side by side and the real picture is boring: both products execute in the cloud and reach your local files through a desktop app. Neither one is running on your laptop.
A dated correction to my own earlier post
This is where I have to correct my own page, because the same mistake is on it.
Claude Cowork vs Claude Code, published July 9, 2026, closes with the line that Cowork's "home-field advantage is working directly on your local files and folders." That line needs an update as of July 2026.
Anthropic's current documentation describes remote execution on their servers with the desktop app acting as the bridge to local files. That's a very different setup from "works directly on your local files."
What that means in practice: tasks built on connectors run in the cloud without your machine, and tasks pointed at a local folder still need an awake desktop. Same for ChatGPT Work.
If a comparison tells you one of these is the "local" option, it has not read either company's docs this month.Correction 3: the billing models are structurally different, and that is the actual decision
Everything above is small stuff next to this. The two products charge you in really different ways.
Claude Cowork draws down the plan you already have. Anthropic's Cowork docs list it as "available for paid plans (Pro, Max, Team, Enterprise)" with no separate purchase.
There is no Cowork SKU. What there is, printed in the same docs: "Working on tasks with Cowork consumes more of your usage allocation than chatting with Claude," and specifically that "auto mode consumes more of your usage limit than the other modes."
That matches the verdict from Claude Cowork vs Claude Code: "Claude Cowork consumes limits faster than Chat," and Claude Pro caps you two ways, a 5-hour session limit plus a separate weekly cap. The plan-sizing conclusion there still holds.
The $20 tier is sized for chat-first use with some agent work on the side. If Cowork becomes your daily workhorse, that is what the Max tiers from $100/month are for, which is the same upgrade trigger covered in Claude Max vs ChatGPT Pro.
ChatGPT Work meters credits from a shared pool. OpenAI's Codex plan-usage article states that "usage from Codex, ChatGPT Work, ChatGPT for Excel, and Workspace Agents draws from the same agentic usage and credit pool when those features are available on your plan." Work follows the same usage structure as Codex.
Stop on that for a second, because it's the biggest practical difference on this page.
If you use Codex for a build, ChatGPT for Excel on a spreadsheet, and ChatGPT Work on a report, all three are eating the same budget. Heavy use of any one starves the other two. Cowork doesn't have that problem. The only thing it competes with is your own Claude chat usage.
So skip "which is cheaper." The question to ask: do you want one metered pool shared across four agents, or one plan allocation that agent work drains faster than chat?
Nobody has published a real usage number, including me
Somebody on r/ClaudeCowork asked the exact right question and got nothing back. u/Proper_Club8511:As per title, does anyone have any information on the effective difference in usage between these two? I would like to know which is more efficient in general tasks. i.e. given the same task, and the same tier of plan (Pro), which would use more/less and by how much.That thread produced no useful answer.
That's the question this page is here to answer, and the answer is that no public number exists. Neither company publishes numeric quotas. The metering units are not even comparable: Cowork burns a plan allocation, ChatGPT Work burns credits from a shared pool. There is no exchange rate.
Anyone handing you a "Cowork uses 2x more" figure invented it.
What the burn actually feels like on the Claude side
I cannot give you a Cowork-vs-Work efficiency number (nobody honestly can yet; the Reddit thread asking got zero useful answers).
What I can tell you from daily use: Cowork burns more than chat because it does more. It is interactive, it reads reference files, it reads my wiki before it acts. That's the work you are paying for.
I don't really feel Cowork chores. Where I feel a dent is heavy coding sessions in Claude Code, like editing my video-editing pipeline. If you are on a $20 plan, the efficiency rule that matters: plan with the big model, execute with the cheaper one (Opus to plan, Sonnet to execute).
I skip that dance because I am on the $200 Max plan and just run Opus. And watch the open-ended autonomous runs: telling an agent "here's a goal, go" on something vague is the fastest way to torch a week's allocation on any plan.
Where ChatGPT Work genuinely wins
This page leans Claude, so read this section as me arguing the other side. ChatGPT Work has real advantages, and two of them are structural.
One: the agent budget is portable across the whole stack. That shared pool is a downside when four agents fight over it and an upside when you want flexibility. A week where you do no coding means all of it goes to Work. Cowork cannot borrow budget from anywhere.
Two: it lands inside an account most workplaces already have. ChatGPT's enterprise footprint is bigger. If your company already pays for ChatGPT, ChatGPT Work arrives on your existing account with your existing admin controls and your existing Workspace Agents, no new vendor review. That matters a lot when procurement is what's actually slowing you down.
Three: three surfaces, one login. Chat, Work, and Codex live in one product with one billing relationship. Running Claude means Chat, Cowork, and Claude Code plus, if you also pay for ChatGPT, a second subscription.
There is also a real argument that Cowork's agent behavior is less predictable. u/jmillionair3 put it well on r/AI_Agents:Seems like GPT is going for more of a build and agent and deploy it places, and cowork deploys agents at its own discretion to carry out tasks but more or less similar in nature. What am I missing?They're not missing much, and that's a fair read.
ChatGPT's model leans toward agents you configure and place. Cowork's leans toward describing an outcome and letting Claude decide the steps. Neither one is better on paper. If you want to see exactly what the second style produces in practice, 20 real Claude Cowork use cases has the community receipts.The 60-second version, from my Shorts: What to hand ChatGPT Work first (OpenAI's own advice).Where Claude Cowork genuinely wins
No separate meter to think about. Cowork is in the plan. You are not watching a credit balance while deciding whether a task is worth running, and you are not rationing between four agents. For someone who just wants the Monday report to happen, not having to think about it matters more than it sounds.
A more mature scheduled-task story. Cowork's recurring tasks run remotely on their schedule, hourly through weekly, even with the laptop closed, with the local-files exception noted above.
It is generally available, not rolling out. Cowork is live on Pro, Max, Team, and Enterprise today. ChatGPT Work is still arriving on eligible accounts, with Cowork's own web and mobile beta rolling out starting with Max.
And a caution against over-committing to either: portability is worth something. u/backhand_snipe on r/ClaudeCowork, writing about switching to ChatGPT Work:Because my workflows and historical decisions lived in plaintext on my machine rather than locked deep inside Claude's proprietary backend, I was completely platform-agnosticThat's the lesson I'd take from this whole page: keep your prompts, context files, and standard operating procedures in plain text you own. Then switching costs you an afternoon instead of a year.
Their stated reason for leaving was not features either:The real catalyst for me jumping ship today was growing frustration with Anthropic. The constant teasing of Fable 5's availability, the moving target dates (July 9th, then the 12th, now the 19th), and the resetting limits just felt like being dragged along as a customer.Trusting the roadmap is a real reason to pick one. I'm calling it out because this page otherwise leans Claude.Cowork winning on the desk: I recorded the task once, and it drafted the repeatable version.
Correction 4: Cowork activity is not captured in the Compliance API
If you are evaluating this for a team rather than yourself, stop here first.
Anthropic's own Cowork documentation states it plainly: "Cowork activity is not captured in the Compliance API at this time."
For an individual professional, that is a footnote. For anyone in a regulated industry, or anyone whose security team requires an audit trail of what AI touched which documents, it could be a dealbreaker, and it is the first question a reviewer will ask.
It does not mean Cowork is unsafe. It means the audit surface your organization may require does not exist for it yet. Check before you roll it out to a team, not after.
None of the pages currently ranking for this comparison mention it. It matters more than anything else on this page.
How this comparison was built
Here's how I built it, because it changes how much you should trust the verdict.
No head-to-head first-party test was run, and I will not fake one. I live in Claude Cowork and Claude Code daily; I have not run ChatGPT Work on anything real.
So read it for what it is: a comparison built on the docs and real users, from someone with a lot of hours on one side only. ChatGPT Work also only started rolling out on July 9, 2026, and a real test needs both products in one account doing identical work.
What this page is built from:Primary documentation, linked inline at every claim that matters: Anthropic's Cowork help articles and pricing page, OpenAI's help center for ChatGPT Work, the retired agent mode notice, and the agentic billing article.
Real user threads, named and linked, from r/ClaudeCowork and r/AI_Agents.
My own published Cowork verdicts, linked to their source posts, including the correction to one of them above.What it is not: a benchmark. When a usage number gets published or I run both against the same task, this page gets updated and the date at the bottom changes.
Pick your lineYou already pay for Claude Pro or Max and mostly do document, email, and report work: Cowork. It is included, it is generally available, and the scheduled tasks are the feature that makes it stick.
Your company already runs on ChatGPT and procurement is your real bottleneck: ChatGPT Work. Same job, no new vendor review.
You code and do office work in roughly equal measure: ChatGPT's shared pool across Work and Codex is more flexible than paying for Claude twice over.
You are on a $20 plan and agent work is becoming daily: the plan is your constraint, not the product. Read Claude Max vs ChatGPT Pro before switching tools, because switching will not fix a sizing problem.
You are evaluating for a regulated team: start with the Compliance API gap above. Feature comparisons are premature until that clears.
You have never used either: start with whichever subscription you already have. They do the same job, and the cost of picking wrong is one afternoon, provided you keep your prompts and context in plain text.For what it is worth, here is how the split actually shakes out in my week, across the two ecosystems: ChatGPT is my well-rounded everyday generalist (general questions, quick lookups, and QA-ing Claude's output), and Claude is where the real work happens: creative work, scripts, content, building and refining the systems.
Cowork does the office work, Claude Code builds the software. Pick the ecosystem that matches the bulk of YOUR week and you will not be far wrong.
Common questions
Is ChatGPT Work the same as ChatGPT agent mode?
No. Agent mode is retired. OpenAI's help center states that ChatGPT agent is no longer available and points users to ChatGPT Work for longer, multi-step tasks. Operator was absorbed into agent mode before it was retired, so both older names now resolve to ChatGPT Work.
Does Claude Cowork run on my computer or in the cloud?
In the cloud. Anthropic states that Cowork runs tasks remotely on their servers in an isolated environment. When a task needs a local file or your browser, Claude reaches it through the Claude Desktop app on that machine, which makes the desktop a bridge rather than the place the work happens.
Do I have to pay extra for Claude Cowork or ChatGPT Work?
Neither has a separate subscription. Cowork is included on all paid Claude plans, starting at $17/month annual or $20 monthly for Pro, and draws from that plan's allocation. ChatGPT Work is included with eligible paid ChatGPT accounts but meters credits from an agentic pool shared with Codex, ChatGPT for Excel, and Workspace Agents.
Which uses fewer credits for the same task?
No public number exists. Neither company publishes numeric quotas, and the two products meter in non-comparable units, a plan allocation versus a shared credit pool. Anthropic does say that Cowork's auto mode consumes more of your limit than its other modes, which is the one concrete lever you control.
Should I switch from Claude Cowork to ChatGPT Work?
Only for a structural reason: your company already runs on ChatGPT, you want one agent budget shared with Codex, or you need an audit trail Cowork's Compliance API gap cannot provide. Feature parity is close enough that switching for features alone is not worth the setup cost.Published July 18, 2026. Checked against Claude pricing, OpenAI's Work help article, agent notice and billing article. No head-to-head test.This post is part of Claude Guides, the hub with every plan decision, task comparison, and setup guide for using Claude without code.
Every guide ranking for this query teaches you to build a skill in the first five minutes. Folder, frontmatter, ZIP, done. That order is backwards. It's why most non-coders try Skills once and then just stop.
The build step is the last step.
My rule for this one: you are going to change your mind, so run the task manually until you stop changing it, and only then write it down.
That is the rule I landed on in the Claude vs ChatGPT for Excel breakdown. Here's the cool part: Anthropic's own docs agree with it, not with the tutorials. More on that in a second.I walk through this on camera in The 5 Levels of Claude Code Skills (Most People Are Stuck on Level 2) (17 min).A Skill Is a Folder of Instructions Claude Picks Up Only When It Needs Them
Anthropic's definition is one sentence: Skills are folders of instructions, scripts, and resources that Claude loads dynamically to improve performance on specialized tasks.
The key word is dynamically. Per the same page, when you ask Claude to complete a task, it reviews available skills, loads relevant ones, and applies their instructions.
So a skill is not always-on. It sits there until a task matches, then fires.
That is also why the description field matters more than anything else you write. A skill needs two things in its frontmatter: a name capped at 64 characters and a description capped at 200.
Anthropic's skill-creation docs call the description critical, because Claude uses it to decide when to invoke your skill. A perfect procedure with a vague description never runs.
Skills, Projects, and Custom Instructions Do Three Different Jobs
Most of the confusion on this query is people building a skill when they wanted a Project. Anthropic draws the line themselves in the Skills doc: Projects provide static background knowledge that is always loaded, while Skills provide specialized procedures that activate dynamically.What it is
When it loads
Use it forCustom instructions
Standing preferences
Every conversation, always
Tone, format defaults, how you want to be addressedProjects
Static background knowledge
Always, inside that Project
Client docs, brand guide, product spec, past reportsSkills
A procedure with steps
Only when a task matches the description
A repeatable process you run the same way every timeThe quick test: if the answer is stuff Claude should know, that is a Project. If it is how Claude should do a thing, that is a skill. If it is how you like to be talked to, that is custom instructions.
Getting this wrong costs you weeks, because a badly-scoped skill fails silently. It just never triggers.
Anthropic's Own Trigger for Building a Skill Is Retrospective
This is the line that should end the "build your first skill in 5 minutes" genre. From Anthropic's skills documentation: create a skill when you keep pasting the same instructions, checklist, or multi-step procedure into chat, or when a section of your standing instructions file has grown into a procedure rather than a fact.
Look at the tense. When you keep pasting. That means repetition you already lived through.
The tutorials teach it the other way around: have an idea, encode it, ship it. Anthropic's trigger needs you to have already done the thing enough times to be annoyed by doing it again.
And that difference matters. If you encode a procedure you haven't tested, you didn't save time. You installed a wrong answer that fires on its own and looks confident every time. You won't catch it, because the output will look fine.
Anthropic's own doc backs this up. So build the skill second.
Why You Can't Find Skills in Your Settings (the Code Execution Gate)
If Skills is missing from your Claude settings, you almost certainly have not turned on code execution, and no tutorial mentions this.
Skills are available for users on Free, Pro, Max, Team, and Enterprise plans, per Anthropic, so the plan is rarely the problem. The gate is a setting you have to flip.Free, Pro, and Max: open Settings, go to Capabilities, turn on "Code execution and file creation." Then Skills appears under Customize.
Team and Enterprise: an Owner has to enable it first in Organization settings under Skills. If you are not an Owner, you can't turn this on yourself. Ask.Yes, a non-technical person has to turn on something called code execution. That's just what it's called, and flipping it is the whole job.
Where skills work once it is on: claude.ai on web, desktop, and mobile; Claude Code; Claude Cowork; the Microsoft 365 add-ins for Excel, PowerPoint, Word, and Outlook; and the API.
One trap before you plan around Cowork. Cowork is paid only, on Pro, Max, Team, and Enterprise per the Cowork docs, which is a narrower list than Skills itself.
And per Anthropic's skills docs, Cowork sessions and cloud sessions, including routines, do not read the skills folder on your machine. Both interactive and scheduled Cowork sessions load the skills enabled for your claude.ai account, synced at session start.
Translation: a skill saved locally will not show up in your scheduled Cowork run. It has to live on your account.
Start With the Skills Anthropic Already Built for You
You can get real value out of Skills without ever writing one. For a non-coder, that changes the whole question.
Anthropic ships built-in claude.ai skills for Excel spreadsheet creation and manipulation, Word document creation, PowerPoint presentation generation, and PDF creation and processing. Partner skills from Notion, Figma, and Atlassian sit in the Skills Directory.
That covers a large share of what actually lands in a normal work inbox. Deck, doc, spreadsheet, PDF.
So your first week looks like this: turn on code execution, browse the directory, use the bundled skills on real work, and author nothing. If you never get past this step, Skills still paid for itself.The 60-second version, from my Shorts: Stop installing random Claude skills. These 5 actually hand you the file.The Graduation Ladder: Manual Chat, Then Reps, Then Encode, Then Schedule
The right order is a ladder with four rungs, and every rung has to earn the next one.Run it manually in chat. Paste the input, describe what you want, read the output.
Do it again, several times, and change your mind out loud. This is the rung people skip.
Stop changing your mind. When the format holds across runs, you finally know what the procedure is.
Write it down as a skill, then automate it.My inbox automation is the worked example, and I published the sequence in the Claude Cowork scheduled tasks breakdown. I ran the inbox summary manually first.
I started by asking for what I wanted without really knowing what I needed. Then I changed the format run by run: I need this, I do not need this, I like this format. Only once it kept doing the job right did I move it onto a schedule.
The manual reps weren't wasted time. They told me what the automation had to do.
My other rule from the Excel breakdown works the same way: start with one simple skill and keep doing everything else manually until you trust it. One skill you trust beats five you're babysitting.
If you are still deciding where any of this fits in your week, the Claude Guides pillar lays out which lane each task belongs in before you automate anything.
The Signal You're Done Iterating
The real tell is having a clear goal and knowing what good looks like. And the only way you know what good looks like is that you've done the work by hand yourself.
With my own skills, I judge it like this: I use the product, so I can read an output and place it. This is good enough. This is on par with what I would have done.
This is better than I would have done it. That scale only exists in your head because of the manual reps. Skip them and you literally cannot know when the skill is done, because you have no standard to judge against.
In practice: after each manual run, note whether you edited the output. When runs stop surprising you and you catch yourself saying "on par with mine," you have the green light.
And be practical about it. You are not going to spend five weeks perfecting a skill while shipping nothing. Get it good enough to use, ship with it, and keep refining.
Realistically that's a week or two of tweaking when you have time. Either way the work keeps moving. Run it manually while the skill catches up, or keep refining until it clears your bar. Once it's in use, it pays for itself on real output you're QA-ing anyway.
What Actually Goes in Your First Skill
Your first skill should be the most boring repeatable thing you do, not the most impressive.
Good first candidates share a shape: same input type every time, same output format every time, and a judgment call you have already made and settled.The weekly status update you write from the same three sources
The way you reformat a client's messy export before you look at it
The specific structure your boss wants meeting follow-ups in
The checklist you run before sending anything externalWrite it as instructions, not an essay. Steps, the format you want, and one line about what to do when input is missing. Then spend real effort on the description field, because that line decides whether the skill ever fires.
Three No-Code Ways to Actually Create One
There is a terminal-free upload path, a skill whose job is writing skills, and since July 21, 2026, a way to record yourself doing the task and let Claude write the skill from the recording.
The upload path. Create the skill folder, package it as a ZIP, then go to Customize, Skills, the plus button, Create skill, Upload a skill.
One thing that trips people up: the skill folder must be the ZIP root, and per Anthropic's skill guide, files should not sit directly in the ZIP root. Folder in the ZIP, not loose files.
skill-creator. Anthropic maintains a skill that authors skills. Its own description reads: create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill. If writing structured instructions is the part you dread, hand that part to it.
Record a skill. This one landed on July 21, 2026, after this page first went up, and it is the most non-coder path of the three.
In Cowork on Claude for Mac, click the plus button in the composer and pick "Record a skill" (or go to Customize, Skills, Add, "Record your screen"). Do the task the way you normally do it, talk through it if you want, click Done.
Per Anthropic's skill guide, Claude then "starts a Cowork task and reviews the recording, then proposes a skill" for you to approve before it is saved. It is Pro, Max, and Team only, Mac only, and a recording runs about 10 minutes.A test run on my Mac mini: I recorded myself turning a Monday brief into a three-line summary in TextEdit, and Claude watched the 15 steps and proposed a skill that does the same thing with file reads and writes instead. That is the part that matters for this page: it built the skill from a task I had already done by hand, which is exactly the order I am arguing for.
Two cautions from the same doc. Everything on your screen is captured while you record, so no passwords, no private tabs. And the video is not kept; what is saved afterward is a set of screenshots from the session, which you can open under the "Recorded demonstration" step in the task.
One correction while you are here. The tip going around LinkedIn, where you open an old Cowork chat and prompt Claude to turn the conversation into a Skill, is not documented by Anthropic anywhere in its support material. It may work. It is not a supported path, so do not build your plan on it.
After the Skill Exists, Verify It Like You Do Not Trust It
When a skill runs on its own, nobody reads it closely. That's exactly when wrong output sticks around the longest.
The habit I keep from the Excel breakdown is trust but verify: run the automated version in parallel with your manual process until it matches your answers, and when a number matters, paste the output into a second tool and ask it to QA the first.
Spot-check numbers against the source. Read the whole thing on the first few automated runs even when you are sure it is fine.
Skills take the typing off you. The review step is still yours.
If you want to see what the finished automated versions look like in practice, the 20 real Claude Cowork use cases page is the catalog of what people actually run on a schedule.
When a Skill Is the Wrong Tool
Skills are the wrong call more often than the tutorials admit, and knowing when saves you the most time.One-off tasks. If you will do it twice this quarter, just prompt it. Encoding costs more than the task.
Anything still changing. New process, new client, new format the team is still arguing about. Encode it and you will be maintaining a stale procedure inside a folder you forget exists.
Judgment calls. Deciding what to include is not a procedure. Formatting what you already decided is. Skills automate the second one.
Stuff that is really reference material. If you want Claude to know things, put them in a Project. Skills hold procedures, not facts.
Work where being wrong is expensive and unreviewed. Anything financial, legal, or client-facing that would go out without a human reading it. Keep a person on that.It always breaks the same way: you encode too early, then trust output that slowly drifted from what you meant.
Frequently Asked Questions
Do Claude Skills require coding?
No. Anthropic ships built-in skills on claude.ai for Excel, Word, PowerPoint, and PDF work, plus partner skills from Notion, Figma, and Atlassian in the Skills Directory, and using them requires no authoring at all.
Creating a custom skill also has a no-terminal path, and since July 2026 a record-your-screen path in Cowork on Mac: package the skill folder as a ZIP and upload it through Customize, Skills, Create skill.
Why is Skills missing from my Claude settings?
Skills sit behind the code execution capability. On Free, Pro, and Max, open Settings, go to Capabilities, and enable "Code execution and file creation," after which Skills appears under Customize. On Team and Enterprise, an Owner has to enable Skills in Organization settings before any individual user can see it.
When should I create a Claude Skill instead of just prompting?
Anthropic's stated trigger is repetition you have already experienced: create a skill when you keep pasting the same instructions, checklist, or multi-step procedure into chat.
If you have not run the task manually enough times that two consecutive runs need no edits, prompting is still the right tool and a skill would just lock in a guess.
Are Claude Skills available on the free plan?
Yes. Skills are available for users on Free, Pro, Max, Team, and Enterprise plans, though code execution must be enabled first. Claude Cowork is stricter and paid-only, on Pro, Max, Team, and Enterprise, so a free user can use skills in chat but not run them on a Cowork schedule.
Do my local skills work in Claude Cowork?
No. Anthropic states that Cowork sessions and cloud sessions, including routines, do not read the skills folder stored on your machine. Both interactive and scheduled Cowork sessions load the skills enabled for your claude.ai account, synced at session start, so a skill has to live on your account to run there.
Do This in This OrderThis week: enable code execution, then use the bundled Excel, Word, PowerPoint, and PDF skills on real work. Author nothing.
Weeks two through four: pick your single most repetitive task and run it manually in chat every time it comes up, changing the format whenever it annoys you.
When two runs in a row need no edits: write it down as one skill, with real effort spent on the description field.
Only then: put it on a schedule, and read the first few automated outputs like you do not trust them.
If the process is still changing, or the call is a judgment call: do not build the skill. Keep prompting.The tutorials sell you the last step first because it's the only step that looks like progress. The point is, the reps are the work. The skill comes last.
Published and last reviewed July 18, 2026. Product capabilities, plan tiers, and setup paths checked that day against Anthropic's official support and developer documentation, all linked inline. The claim that a Cowork conversation can be converted into a skill in one click is explicitly not documented by Anthropic and is flagged as unverified above. These products change often; the official pages are the source of truth.
Until late August 2026 this page opened with "Claude cannot send your email." That is no longer true. Anthropic's Gmail connector now sends, replies and forwards, and asks for your approval before each one by default.
ChatGPT has worked that way for a while. So both can hit send and both ask first.
Every page ranking for this query is arguing about tone. That is the wrong argument.
My rule for this one: tone is the cheapest thing to fix and the loudest thing in search results. What matters is which tool can touch your inbox, and how it treats the words you put in it.
Whether you searched "claude vs chatgpt for email," "chatgpt vs claude for gmail," or "can claude send emails," the answer starts with what each tool can do and what happens to your data. Tone comes after. Below is the split, with the official docs behind each line.
The Split in One Table (updated September 2026)Claude
ChatGPTReads your inbox
Yes, via Google Workspace connector
Yes, via connectorsCreates a draft
Yes, in Gmail
YesSends the email
Yes, since August 2026. Asks for approval first by default
Yes, gated as an "important action"Reads attachments
Metadata only, not content
See OpenAI's connector docs per appTrains on connector-retrieved email
No, stated explicitly
Not by default on Business, Enterprise, EduTrains on email you paste in
Possible on Free, Pro, Max if chat training is on
Possible on Free, Plus, Go, Pro if the setting is onAvailable on the free tier
Yes, connectors are on all tiers
Connector behavior varies by tierIn-browser help
Claude in Chrome, beta, paid plans, labeled risky
Not covered hereSaved email voice
Projects with project instructions
Projects and custom GPTsThe third row is the one most pages still get wrong.
Claude Can Send Now (It Could Not Until August 2026)
Until late August 2026 the Google Workspace connectors documentation said "Claude creates drafts in your Gmail account, but cannot send emails on your behalf," with an FAQ line that read "Can Claude send emails on my behalf?
No." That is the version most comparison pages still quote. It changed in late August 2026. The same FAQ line now reads:Yes. Claude can send, reply to, and forward emails from Gmail, and asks for your approval by default before each of these actions.The approval step is the important part. Ask Claude to reply to a thread and it drafts the reply, shows it to you, and waits. On Team and Enterprise plans an owner decides whether members can let those actions run without asking each time. I covered the switch the week it landed:The 60-second version, from my Shorts: Claude just got a send button for your Gmail.The setup screen makes more sense now too. Google's OAuth screen mentions email sending permissions, and Claude actually uses them. The setting to leave on is the approval prompt.My own connector list in Cowork. Gmail is on, which is all the setup the send path needs; the approval prompt does the rest.
One more limit before you build a habit on this. Claude can't open attachments through Gmail. It only sees the metadata. So "read the contract Sarah sent and reply" does not work end to end. You get the filename, not the file.
Connectors are available on all Claude tiers including free. On Team and Enterprise, an Owner has to enable them for the organization first.
ChatGPT Can Send, But It Has to Ask First
ChatGPT has sent email for a while, and its gate works the same way Claude's does now. Sending isn't silent. The useful detail is what OpenAI calls it. From the connectors documentation:An important action is an app action that could have a meaningful effect outside ChatGPT... Examples may include: Sending or editing an email, message, comment, post...The default behavior is spelled out on the same page: ChatGPT "uses Important actions, which allows reading from apps automatically but asks before actions that may have a meaningful effect outside ChatGPT."
So it runs at two speeds. Reading your inbox is automatic. Sending stops and waits for you.
One catch the other pages on this skip. OpenAI's Outlook email and calendar app documentation lists mail sending scopes while describing retrieval as read-only. So OpenAI's own doc contradicts itself. On Outlook, test it on a low-stakes message before you trust it with a client thread.
The Privacy Question Is Not "Which Tool," It Is "How Did the Email Get There"
This should change what you do tomorrow morning. On both platforms, copy-pasting an email into the chat is the worst option for your data.
Anthropic's connector page states the protection clearly: "We do not train our models on your Gmail, Drive, or Calendar connector data." Then it draws the line that matters.If you are using our consumer products (e.g. Claude Free, Pro, and Max)... and you have chosen to allow us to use your chats... then any content you copy/paste from your Gmail, Drive, Calendar... may be used to improve our models.Anthropic's model training policy page says the same thing. Email Claude pulls through the connector is never trained on. The same email, pasted into a chat box on a consumer plan with training allowed, can be.
OpenAI draws its line by plan instead of by how the email got there. From the connectors doc: for ChatGPT Free, Plus, Go, and Pro users, OpenAI may use information accessed from apps to train models if your "Improve the model for everyone" setting is on.
For Business, Enterprise, and Edu customers, OpenAI does not use information accessed from connectors to train models by default.
So here's the rule for both:Connector, on a work plan: the safest setup on either platform.
Connector, on a consumer plan: protected on Claude for retrieved data; on ChatGPT, check your training setting.
Copy-paste into a chat window on a consumer plan with training on: the riskiest setup, and it's the one most people are using right now.If your inbox contains client names, salary figures, legal threads, or anything under an NDA, that last bullet is why this section exists. Turn the setting off, or connect the account instead of pasting.
The Verdict Spine: Email Is Generalist Work, Not Creative Work
This is where you actually decide. It's the same question the Claude Guides pillar is there to answer: which tool owns which job in your week.
My split across my own week, published in Claude Cowork vs ChatGPT Work, runs like this. ChatGPT is the well-rounded everyday generalist, and it doubles as the QA layer for Claude's output. Claude is where the real work happens: creative work, scripts, content, building and refining.
Email is correspondence. Most of it is generalist work.
One more thing from my own week. Almost every comparison out there assumes "AI for email" means writing emails. My biggest AI email win isn't drafting at all.
It's management: my inbox system organizes, archives the junk, unsubscribes, and pings me on the stuff that matters, like a person reaching out or a bill that needs to be paid.
Drafting responses is the smaller half. If your inbox is cluttered, the most useful email automation you can build has nothing to do with writing (the full setup is in Cowork scheduled tasks).
Confirming a meeting, chasing an invoice, answering a vendor, summarizing a thread for your manager: that is ChatGPT's lane by that split, and either tool can now carry it through to send.
The exception is real, though. Some email is writing. The resignation note, the pitch to a decision maker, the apology to a client who is already annoyed, the message where the wrong word costs you something.
Those are Claude tasks by the same split. And the approval prompt helps you there. Nothing you can't take back goes out until you've read it.
Run the Cross-Check Before Anything Important Leaves Your Outbox
The rule I landed on in the Excel breakdown works here too: run the output past the other model before it goes out. If you are using ChatGPT, paste it into Claude and ask it to QA it.
For email, the trigger is easy to state.
Anything going to a client, your boss, or anyone who can fire you gets a second-model read before send.
It takes about thirty seconds, and it catches where AI email really goes wrong. That's usually not grammar. It's a confident tone that drifts, or a draft that agrees to a deadline you never agreed to.
Ask the second model one question: does this commit me to anything I did not intend to, and does the tone match a message to this person.
One catch. Pasting the draft into the second tool is exactly the copy-paste path from the privacy section, so on a consumer plan check your training setting first, or run the cross-check on a work account.
Save Your Email Voice Once Instead of Re-Explaining It Every Week
Both tools have the same fix for "it does not sound like me," and it is a container you set up once.
Claude has Projects, where you can define project instructions for each project, including instructing Claude to use a more formal tone. The free tier is capped at 5 projects, so an "Email" project is a reasonable use of one of them.
ChatGPT has Projects too, with one rule to know, per OpenAI's Projects doc: project instructions only apply inside the respective project and will override your global custom instructions. Your email project can be more formal than your default without you editing your global settings back and forth.
Custom GPTs go one step further, and OpenAI's guide to creating a GPT spells out the split better than most people use it.Use knowledge for reference material, not rules or behavior. Put rules, tone, and workflow guidance in instructions.So here's what you build. Your voice rules go in instructions: sentence length, greeting and sign-off, whether you use exclamation points, what you never say. Then 5 to 10 of your actual sent emails go in knowledge as reference material.
Building GPTs is paid-only and web-only, so plan around that.
If you want the longer comparison of those two containers, it is in Claude Projects vs custom GPTs.
One timing warning before you spend an evening on this. My manual-reps rule, also from the Excel breakdown, says don't lock in a workflow before you have run it manually enough times to stop changing your mind.
So do not write your email voice instructions on day one. Draft emails the slow way for two or three weeks, keep the corrections you make by hand, and then turn those corrections into the instruction block.
Where Claude Genuinely Wins on Email
Now that both tools send and both ask first, the capability table is close to a tie. So the difference comes down to the writing.
Claude reads a hard email better. It holds your tone across a long reply, it doesn't slide into the hedge-everything tone that gives AI email away, and when you tell it "shorter, and drop the apology" it actually does that instead of rephrasing the apology.
Leave the approval prompt on. That is your pause: nothing leaves your account until you have read it, no confirmation dialog you clicked past at 4:50 on a Friday. For anyone whose email carries legal, financial, or relationship weight, that prompt is worth more than the two seconds it costs.
Add the editing and refining edge from my split above, and it's pretty clear: if your hard emails are the ones that matter, Claude is the better email tool for you.
How This Comparison Was Built
I didn't run a side-by-side test for this page, and there are no screenshots of private inboxes on it.
What it is built on instead:Official vendor documentation, linked at every capability claim: Anthropic's Google Workspace connectors page, model training policy page, Projects page, and Claude in Chrome page; OpenAI's connectors page, Outlook app page, Projects page, and GPT creation guide.
Verbatim quotes rather than paraphrase wherever the exact wording is the point, especially on sending and on training data.
My published verdicts on adjacent questions, linked at each claim: the daily-driver split from the Cowork vs Work comparison, the cross-check rule and the manual-reps rule from the Excel breakdown.One flagged inconsistency: OpenAI's Outlook app documentation lists mail sending scopes while describing retrieval as read-only. Outlook users should verify behavior on a test message. Both companies change things often, so if their pages disagree with this one, trust theirs.
Updated September 5, 2026: Anthropic's connector page flipped its FAQ from "Can Claude send emails on my behalf? No." to "Yes," with approval required by default. The title, table, and the two sections on sending were rewritten to match. I covered the change in a Short on August 25.
Frequently Asked Questions
Can Claude send emails from Gmail?
Yes, since late August 2026. Anthropic's Google Workspace connector documentation now answers it directly: "Yes. Claude can send, reply to, and forward emails from Gmail, and asks for your approval by default before each of these actions." Before that it was draft-only, and most pages on this topic still say so.
Can ChatGPT send an email without asking me?
Not by default. OpenAI classes sending an email as an "important action," which it defines as an app action that could have a meaningful effect outside ChatGPT. The default configuration reads from connected apps automatically but asks before actions like sending, so the message is shown to you first.
Is it safer to paste an email or connect my account?
Connecting is safer on both platforms. Anthropic states it does not train on Gmail, Drive, or Calendar connector data, but says pasted content from those sources on Free, Pro, or Max may be used to improve models if you allowed chat training.
OpenAI may use information accessed from apps for training on Free, Plus, Go, and Pro when "Improve the model for everyone" is on, and does not by default on Business, Enterprise, and Edu.
Can Claude read my email attachments?
No. Anthropic's connector documentation states that attachment content is not directly accessible through Gmail, metadata only. Claude can see that a file was attached and what it is called, but it cannot open the contents, so "read the attached contract and draft a reply" does not work end to end.
Do I need a paid plan to connect Claude to Gmail?
No. Google Workspace connectors are available on all Claude tiers including free. On Team and Enterprise plans, an Owner has to enable connectors for the organization before individual users can set them up.
Why does the Google consent screen mention email sending permissions?
Because Claude now uses them. Anthropic's documentation says the OAuth screen mentions sending permissions and that Claude can send, reply to, and forward emails, but only with your explicit approval by default. On Team and Enterprise plans, owners decide whether members can let those actions run without asking each time.
Can Claude write directly inside my Gmail compose window?
Claude in Chrome, in beta on paid plans (Pro, Max, Team, and Enterprise), has built-in knowledge of how to navigate Gmail and other popular platforms, and Anthropic still labels it risky even with safety classifiers enabled.
Treat in-browser assistance as an experiment rather than the reliable path. The dependable Claude email surface is the Google Workspace connector, which drafts, and with your approval, sends.
Pick By What You Need the Tool to Actually Do
There's no one winner here. It depends on your inbox.You want the whole loop handled, drafting through to send: either one now. Both send, both ask first by default, so pick by the rest of this list.
Most of your email is routine correspondence: ChatGPT, per the generalist half of the daily-driver split.
Your hard emails are the ones that matter: Claude. Better at voice and refining, and the approval prompt is your pause before anything irreversible.
You handle confidential threads: connect the account instead of pasting, and check your training setting.
You are on a free plan: Claude connectors work on free tiers, which is the cheapest real path into an AI-assisted inbox.
You want it to sound like you every time: a project with instructions on either tool, built after two or three weeks of manual reps, per the Excel breakdown.So decide how the email gets into the tool and who reads it before it goes out. Tone comes after that.
Published July 18, 2026. Updated September 5, 2026, when Anthropic's Gmail connector gained send, reply and forward with approval required by default. Capabilities, permissions, and training-data policies checked against Anthropic's and OpenAI's official support documentation, all linked inline. No first-party head-to-head test was run for this page. These products change often; the official pages are the source of truth.
Claude will not take your recording. Not "handles it worse." It does not accept audio or video files at all. ChatGPT will, through record mode, but only on the macOS desktop app, capped at 4 hours, auto-joining Google Meet and nothing else.
So the real question is not which one writes prettier summaries. It is whether you can record at all.
My rule for this one: capture is a hardware problem, minutes are a writing problem, and only one of these two tools can do the first.
That is the answer. Here is the evidence, the official limits, and a verdict split by whether a recorder is allowed in your room.
The Split in One Table (July 2026)Claude
ChatGPTAccepts an audio file
No. 10 supported file types, none audio
Yes, via record modeNative transcription
None
Yes, with speaker labelsWhere recording works
Nowhere
macOS desktop app onlyRecording length cap
n/a
4 hours per recordingAuto-joins your calls
No
Google Meet only, not Zoom/Teams/WebexWhich plans
n/a
Plus, Pro, Business, Enterprise, Edu (not Free or Go)Turning messy notes into minutes
Stronger
CompetentScheduled, recurring processing
Claude Cowork
Scheduled tasksEntry price
Pro $17/mo annual, $20 monthly
See OpenAI's pricing pageRead that top row again, because it is the row nobody writes down.
Claude Does Not Accept Audio Files, Full Stop
Anthropic publishes the supported upload list, and it is short: PDF, DOCX, CSV, TXT, HTML, ODT, RTF, EPUB, JSON, XLSX, plus images. Ten document types and pictures.
No mp3. No m4a. No wav. No mp4.
There is no asterisk, no "coming soon," no premium tier that unlocks it. If you drag a recording of your Tuesday standup into Claude, there is nowhere for it to go.
The near-miss that confuses people is voice mode. Claude has one, and it is genuinely useful, but it is conversational input and output: you talk to Claude, Claude talks back. It is not a recorder pointed at a conference table.
To be fair to both apps: talking TO them on mobile is in good shape now. Claude's mobile voice input was a little buggy a few weeks back, and in my use it has caught up; both transcribe what you say to them just fine.
That is dictation. It is a different capability from handing the app a recording of a meeting, and the upload list above is still the wall for that.
This is the wall. Somebody pays $17 a month for Claude Pro after reading a listicle that called it "more structured for meeting summaries," opens the app with an hour of audio, and discovers the product will not take the file.
ChatGPT Is the Only One of the Two That Can Capture a Meeting
Credit where it is due, and this is the section where ChatGPT wins outright.
OpenAI's own Record mode doc says it plainly: "ChatGPT can transcribe and summarize audio recordings like meetings." Record mode transcribes, labels who said what, and hands you a summary. On the capture question, Claude is not in second place. It is not on the field.
Now the limits, because every ranking page skipped these too.macOS desktop app only. Not the web app, not Windows, not iOS or Android.
4-hour cap per recording. Your all-day offsite does not fit in one file.
Google Meet auto-join only. Zoom, Microsoft Teams, and Webex are not supported for auto-join.
Plus, Pro, Business, Enterprise, and Edu. Not on Free, not on Go.
Off by default on Enterprise and Edu, so your admin has to turn it on before you can use it.
Audio is deleted after transcription, and it works best in English.Read that list as a filter, not a feature spec. A Windows-based project manager running Teams calls gets nothing from record mode, and no comparison post on this query says so.
Every Ranking Page Is Answering the Second Question First
Search this topic and you get summary-quality opinions. Claude is more structured. ChatGPT is more conversational. Pick your favorite prose style.
That is the second question.
The first question is whether the tool will accept your input, and one of these two answers no. Writing quality only becomes the deciding factor after capture is solved, which is exactly why so many people buy the wrong subscription for this job.
I have written the writing-quality comparison, and the verdict there holds.
In Claude vs ChatGPT for writing the pattern from months of real user reports is that Claude holds voice and follows constraints like "one sentence only" more reliably by default, while ChatGPT wins on volume, versatility, and tasks that mix files and data. That is a real advantage for turning a transcript into minutes.
It is just not the advantage you should shop on first.
The Pain Is in the Write-Up, Not the Recording
The people asking this question are not confused about what a summary is. They are drowning in the after-part.
A project manager, u/folkarlow93 on r/projectmanagement, laid out the math: "a 1 hour meeting can take me anywhere from 2-4 hours (sometimes more) to type up minutes for... my manager seem to be able to take minutes and get them sent out 30 minutes after the meeting which I find is insane, almost like I'm doing something wrong."
Four hours of write-up for one hour of meeting, against a manager who ships in 30 minutes. That gap is the whole product category.
An executive assistant, u/AmMF808 on r/ExecutiveAssistants, named the other half of it: "I can take notes during the meeting, but then I feel like I'm only half listening... Some meetings are online, but a lot are in person meetings or quick follow ups where setting up a full meeting bot feels weird."
Two different problems hiding under one search query. One is transcription. The other is attention, etiquette, and what happens to the scribbles afterward.The 60-second version, from my Shorts: Never Write Up a Meeting Again: The 2-Minute AI Workflow After Every Call.The Handoff Between Tools Is Where the Time Actually Goes
Even people who solved capture are still doing manual labor, and they know it.
From r/ObsidianMD, u/Interesting-Post4178 put it better than any vendor page: "The issue is not really capturing the meeting anymore.
There are already good tools for transcription and summaries. The part that still feels manual is what happens after... Right now this still feels like a lot of copy/paste between a meeting tool, Claude/ChatGPT, notes, and email."
That is the honest 2026 state of things.
Heads up: the Fireflies links below are affiliate links: a small kickback to me at no cost to you. I only recommend tools I've actually run.
Transcription is a commodity. Otter, Fireflies, Tactiq, and Granola all do it well, and several will sit in a Zoom or Teams call that ChatGPT record mode will not auto-join. The unsolved part is the chain from transcript to decisions to owners to the email that actually goes out.
What I actually do after a call
My path is deliberately boring, and it sidesteps the whole wall: I record and transcribe on the phone itself, with Voice Memos or Apple Notes transcription on the iPhone, and then paste the TEXT into the AI.
Easiest thing you can do. Text uploads work everywhere, the transcript is on-device in one step, and I never have to care which chatbot accepts which file type.
I also do not lean on in-app recording for any of these tools.
The recording windows are short in my experience (ChatGPT's felt like roughly a ten-minute window when I tried it) and the apps can freeze mid-capture, which is exactly the failure you cannot afford in a meeting. Capture on the device, process in the AI.
For the processing itself, my split: everyday summarize-and-draft work goes to ChatGPT, which is my well-rounded daily generalist, and anything that has to become real content (a script, a post, a doc with my voice in it) goes to Claude.
When a summary really matters, I paste one tool's output into the other and ask it to QA it.
The Cohort Nobody Writes For: You Are Not Allowed to Record
Every article on this query assumes a bot is in the room. For a lot of professional life, it cannot be.
In-person meetings. Board meetings where recording is prohibited by policy. Legal, healthcare, and security-restricted workplaces. Two-party consent states. And the case u/AmMF808 named, where spinning up a meeting bot for a five-minute hallway follow-up just feels weird.
If that is you, the Claude no-audio limitation is completely irrelevant.
You are never uploading audio anyway. You have a page of hurried notes, a few half-sentences, three names, and a decision you are pretty sure was made. Your problem is processing, not capture, and processing is exactly where Claude is strongest.
Here is the workflow, and it takes about five minutes.Take rough notes during the meeting. Bullets, fragments, initials for people. Do not try to write minutes live. That is the trap that makes you half-listen.
Paste the mess into Claude within the hour, while you can still fill gaps from memory.
Ask for four things in one prompt: a structured summary by topic, decisions made, action items with an owner and a due date, and open questions that were not resolved.
Make it flag its own gaps. Add "list anything ambiguous or missing that I should confirm" so you get a checklist instead of confident invented detail.
Ask for the follow-up email in a second message, addressed to the attendees, short, decisions and owners only.Step 4 is the one people skip, and it is the one that keeps the output honest.
For meetings you have every week, do not run this by hand forever. That processing step is Cowork's job.
Route It With the Chat, Cowork, Code Rule
The rule I give everyone, from Claude Cowork vs Claude Code: Chat answers. Cowork does your office work. Claude Code builds software.
Pasting one set of notes into a chat window is a Chat task. Fine, do it, it works.
Turning every Monday's notes into a brief without you asking is a Cowork task. Anthropic's own getting-started documentation names this exact use: Cowork can "extract themes, key points, and action items from meeting notes, interviews, or lecture recordings."
This is not theoretical. In 20 real Claude Cowork use cases, use case 9 is people dumping Teams chats, meeting notes, emails, and scattered docs into Cowork on a schedule and getting one readable brief back.
Use case 15 is podcast host Aakash Gupta running Cowork across years of his own transcripts to find where guests contradicted each other, then building the ten most quotable insights into a deck.
That is the after-capture lane, already documented, already working.
Two caveats before you go build it. Cowork is on paid plans only (Pro, Max, Team, Enterprise) with no separate SKU, and it burns your usage allowance faster than chat does.
Claude also has a Google Calendar connector that can view and create events, which is how you get "schedule the follow-up we agreed to" without leaving the app.
The Third Answer: Do Not Make These Two Your Only Options
The way this comparison is set up is a little rigged, so let me break it.
A dedicated transcription tool plus Claude is a legitimate, often better answer than either chatbot alone. Otter, Fireflies, Tactiq, and Granola exist because capture is a real product problem with real requirements: joining Zoom, Teams, and Webex, running on Windows, handling recurring calendar invites, storing transcripts you can search a year later.
None of that is what a chatbot is for.
Let the recorder record. Then hand the transcript to the tool that writes better, and store the output wherever your work lives, whether that is Notion, Obsidian, or a Claude Project you keep for a given client. That chain beats a purist "one AI does everything" setup almost every time.
How This Comparison Was Built
Straight up: I did not run a head-to-head first-party test for this page. No side-by-side of the two tools summarizing the same meeting, and no screenshots of my own runs.
Fabricating those would be the actual failure, so here is what this page is built on instead.Official vendor documentation, linked inline at every capability claim: Anthropic's file upload list, voice mode page, Cowork getting-started page, and Google Workspace connector page; OpenAI's record mode help article.
Real user threads, named and linked: r/projectmanagement, r/ExecutiveAssistants, and r/ObsidianMD, quoted verbatim above.
My own published verdicts on adjacent questions, linked at each claim so you can check the reasoning.One honest gap: exact dollar figures for ChatGPT's Plus and Pro tiers could not be verified against OpenAI's pricing page at publish time, so this page names tiers instead of prices and links the pricing page for the current numbers. Claude's are on claude.com/pricing: Pro at $17/month billed annually or $20 monthly, Max from $100.
Both companies ship changes constantly. Their pages win over this one.
Frequently Asked Questions
Can Claude take meeting notes?
Claude cannot record or transcribe a meeting. Its official upload list covers 10 file types plus images, with no audio or video format anywhere on it. Claude can turn notes or a transcript you already have into clean minutes and action items, but something else has to capture the meeting first.
Is there a Claude AI note taker?
Not in the sense most people mean when they search that. There is no Anthropic-built bot that joins your call and takes notes for you. Claude is the processing layer that runs after capture, either in chat or on a schedule through Claude Cowork.
Which is better for note taking, Claude or ChatGPT?
For turning raw notes into structured minutes that follow your format rules, Claude. For getting the raw material in the first place, ChatGPT, because record mode is the only native capture path between the two. Many people end up using ChatGPT or a dedicated recorder for capture and Claude for the write-up.
Can ChatGPT join my Zoom or Teams meeting automatically?
No. Record mode auto-joins Google Meet only. For Zoom, Microsoft Teams, or Webex you either record locally with the macOS desktop app in the room, or use a dedicated meeting tool like Otter, Fireflies, or Granola that supports those platforms.
Does record mode work on Windows?
No. ChatGPT record mode is macOS desktop app only as of July 2026. Windows users have no native capture path in either Claude or ChatGPT and should pair a dedicated transcription tool with whichever chatbot they prefer for the write-up.
Pick By Whether You Can Record
There is no universal winner here, only a fork based on your room.You are on macOS, meetings are on Google Meet, recording is allowed: ChatGPT. Record mode is the only native path between the two, and it is included on your Plus or Business plan already.
You are on Windows, or your calls are Zoom, Teams, or Webex: neither chatbot captures for you. Pair Otter, Fireflies, Tactiq, or Granola with Claude for the write-up.
You cannot record at all (in person, board, regulated, or it just feels weird): Claude. Capture stays manual, and the five-step notes-to-minutes workflow above is the whole win.
You have the same meeting every week: Claude Cowork on a schedule. Stop doing the processing step by hand.
Your write-up has to match a strict template or house format: Claude, per the instruction-following pattern in Claude vs ChatGPT for writing.
You are only paying for one and this is a real part of your job: decide capture first, then read the $20 tier breakdown before you enter a card, because the plan you pick changes how much of this work you can actually get done.Solve capture. Then argue about prose.
Published and last reviewed July 18, 2026 against Anthropic's and OpenAI's help pages, linked inline. Quotes from public Reddit threads. No head-to-head test.This post is part of Claude Guides, the hub with every plan decision, task comparison, and setup guide for using Claude without code.
You have a 90-page contract, report, or policy PDF and one question you actually need answered. Every ranking page on this query hands you a context-window spec sheet and calls it a decision.
That doesn't help you with the actual job.
Three things decide this, and none of them is the size of the context window: where you put the file, whether the PDF is a scan, and whether you are summarizing or judging.
My rule for this one: the bigger window does not read your document, and when being wrong is expensive, run both models against each other before you trust either one.
One note on the window itself, since every other page leads with it. Anthropic's context window doc states that Claude Sonnet 5 supports a 1M token context window on all paid plans.
Opus 4.8, Opus 4.7, Opus 4.6, and Sonnet 4.6 support 500K. Outside of these models the window is 200K, and there's no free-tier number published anywhere.
OpenAI does not clearly publish context window sizes for its consumer tiers at all.
So the "bigger window" argument compares a published number to an unpublished one. That just means one vendor is more open than the other. Useful to know, but it's not what those pages think they're proving.
What will actually break your afternoon is file size caps, image handling, and retrieval behavior. All three are documented. None of them show up in those search results.
Where You Put the File Changes the Rules More Than Which Brand You Picked
So the table that actually helps here compares chat to project knowledge, on both platforms.Claude chat
Claude project files
ChatGPT chat
ChatGPT project knowledgeFile size cap
500MB per file
30MB per file
512MB per file, 2M tokens
512MB per file, 2M tokensFile count
Up to 20 per chat
Unlimited, must fit context window
80 files per 3 hours (Free: 3/day)
10 uploaded at a timeWhat gets read from a PDF
Text and visuals under 100 pages
Text extraction only, except multimodal PDFs
Text and visuals (Enterprise: visual retrieval)
Text only, images discardedWhen it flips to search
Automatically at context limit (RAG)
Automatically at context limit (RAG)
Not documented for consumer tiers
Not documented for consumer tiersStorage
Not published per-user
Not published per-user
25GB per user, 100GB per org
25GB per user, 100GB per orgSources: Anthropic's upload documentation, OpenAI's file uploads FAQ, and OpenAI's Projects documentation.
Look at the first row. That's the one this whole post is about.
The Popular Advice About Big Files Is Backwards on File Size
The standard advice, including the top-voted Reddit answers on this, is that large files belong in the knowledge base rather than in chat. If you mean lots of files, that's right. For one big file, Anthropic's own numbers say it's backwards.
Anthropic's upload doc puts chat uploads at 500MB per file, up to 20 files per chat. The same page documents project files at 30MB per file.
That is a 16x gap running the opposite direction from the advice.One enormous PDF, used once: drop it straight into a chat. The project will reject it long before the chat does.
Forty documents you will query for months: project knowledge. Unlimited file count there, and the chat's 20-file ceiling is what would stop you."Knowledge base for big stuff" sounds obviously right. It only holds up when you have lots of files, not one huge one.
There's a second catch too. Anthropic specifies project files as "Text extraction only (except for multimodal PDFs)." File your chart-heavy quarterly report in the project, the spot you'd assume is more thorough, and it can lose its charts.
The Scanned PDF Trap Is the Most Expensive Surprise in This Comparison
If your PDF is a scan or a photo of a document, this section decides your answer by itself.
OpenAI's file uploads FAQ states it directly: "ChatGPT Enterprise supports Visual Retrieval for PDF files... All other plans and document files only support text-based retrieval. This means that ChatGPT will extract digital text from the file and discard any images."
Their dedicated visual retrieval page repeats it: "This capability is available only to ChatGPT Enterprise customers. It is not supported for ChatGPT Free, Pro, Team, or Edu accounts."
A scanned document has no digital text. So if ChatGPT pulls the text and throws out the images, there's nothing left.
Claude's documented behavior on the same input: "Claude models can analyze both text and visual elements (like images, charts, and graphics) in PDFs that are under 100 pages." And that applies on every tier.
Neither vendor uses the word OCR in their consumer docs, so I'm not going to guess whether either one does it. What they do document is what gets read and what gets thrown out. That's enough to make the call.
But there's a gap in Claude's docs. PDFs over 1000 pages get text only, and for anything between 100 and 1000 pages the docs say nothing.
That range covers most real contracts, annual reports, and policy manuals. In other words, the exact document that brought you here. Any page that tells you what happens in that range is making it up.
So test your own file: ask Claude to describe a specific chart or signature block on a specific page. If it can, visuals are being read. If it can't, you're only getting the text, so plan around that.
The nested version of this trap that will genuinely catch you
Same PDF, same ChatGPT account, two different behaviors depending on how it got there.
OpenAI documents it: "PDFs uploaded as GPT Knowledge or Project Files are processed using text-only retrieval. PDFs uploaded by users during interactions with a published GPT or within a Project conversation are processed using visual retrieval."
So filing a PDF into your project's knowledge strips its images. Dragging the identical file into that project's chat window does not. The tidy habit is the one that costs you the images. Know that before you build a workflow around it. Same argument as Claude Projects vs Custom GPTs.
Claude has the same problem, in the project-files line quoted above. On both platforms, the knowledge base is the worse place for anything visual.
Why Claude "Forgot" Something That Was Definitely in Your Project File
This is the most common complaint with long documents, and there's a documented reason for it.
Anthropic explains that when retrieval augmented generation is enabled, "Claude uses a project knowledge search tool to retrieve relevant information... Instead of loading all project content into memory at once, Claude intelligently searches and retrieves only the most relevant information needed to answer your questions."
The trigger is the part that matters:RAG automatically activates when your project approaches or exceeds the context window limits. You'll see a visual indicator.It reverses if the project drops back below the threshold, and Anthropic says it can expand capacity by up to 10x.
In practice: below the threshold, everything you filed gets loaded. Above it, Claude searches instead of reading, and it only finds what its search thinks matches how you worded the question.
So it's the same project with two behaviors, and it switches on its own.
That's why the clause you know is in there comes back as "I don't see that in the documents." Claude isn't making things up there. Its search just missed the clause. Ask again using the exact wording from the document, not your paraphrase.
One caveat. Anthropic's RAG page says "RAG for projects is available for all Claude plans (free, Pro, Max, Team, and Enterprise)," while their Projects article describes enhanced project knowledge with RAG as paid-plans-only.
So two Anthropic pages from the same period say opposite things. Check your own account for the indicator rather than trusting either page.
Summarize This and Find the Clause Are Two Different Jobs With Two Different Risk Levels
Every page on this query treats "work with a PDF" as one task. It is two, and only one can hurt you.
Summarize and orient is low stakes. What is this report about, what are the main findings, what do I need before the meeting. If the model flattens a detail, you find out in the meeting and correct it. Both tools are fine here.
Find the clause and judge it is not. What is the termination notice period, does this indemnity cap cover third-party claims, does this policy apply to me. Being wrong has a dollar figure attached.
That second job is where my trust-but-verify rule from the Claude vs ChatGPT for Excel breakdown applies without exception: the fully autonomous agent does not exist yet. Run the AI in parallel with your manual process until its answers match yours, and keep QA-ing after they do.
My cross-check is what I'd do with documents: if you are using ChatGPT, paste the output into Claude and ask it to QA it. Then reverse it. AI is already smarter than us at plenty of things and it can still be wrong.
For a contract, that means a concrete loop:Ask model A for the clause, requiring it to quote the exact passage and give the page number.
Open the PDF and read that page yourself. Everyone skips this and it takes ninety seconds.
Paste model A's answer into model B and ask it to QA the interpretation against the same document.
Where the two disagree, that is your list for a human who is paid to be right.Step one does most of the work. A model forced to quote and cite cannot hand you a smooth paraphrase of a clause that is not there.
Two setup habits from that same breakdown make either job go better:One job per session. Do not dump 20 files covering 20 topics and fire off 10 questions. The exception that works is grouping files that belong together. Four contracts from one vendor relationship is one job. Four unrelated policies from four departments is four jobs, and merging them is how you get answers that mix up documents without telling you.
Decide the output format before you upload. That choice is the real skill. It's the difference between "summarize this contract," which gives you prose you have to re-read, and "give me a table with clause, page number, plain-English meaning, and risk to me."Capture and processing are separate problems here, same as they are in meeting notes. Whether this work belongs in a chat, a project, or something scheduled is the routing question covered in the Claude Guides pillar.
Where Each One Genuinely Wins
Neither is the universal answer, and pages that pick a winner outright are not being straight with you.
ChatGPT wins on volume and throughput. 80 files every 3 hours is a generous documented allowance, and the 2M token per-file cap does not apply to spreadsheets at all.
If you work with CSVs alongside your PDFs, that matters. Storage is published too, at 25GB per user and 100GB per org, which is more than Anthropic tells you.
ChatGPT's free tier is honest about being a trial. 3 file uploads per day tells you immediately whether it fits your week.
Claude wins on scanned and image-heavy documents on any tier. Anthropic documents visual analysis of PDFs under 100 pages with no tier condition, while OpenAI restricts visual retrieval to Enterprise. That's the biggest documented difference between the two for this job.
Claude wins on published transparency. Context windows by model and plan, page thresholds, per-destination file caps. You can plan against numbers instead of guessing.
Both share one weak spot: non-PDF documents. Anthropic states that for DOCX, TXT, and the rest, "Claude extracts text only from these files. If they contain embedded images, Claude won't be able to read or interpret them."
Same for Google Drive: "Claude extracts text content only from Google Drive files. Images embedded in documents are not processed." A Word doc full of screenshots is a bad input on either platform.
Frequently Asked Questions
Is Claude or ChatGPT better for PDFs in 2026?
For one large PDF, especially a scanned or image-heavy one, Claude. Anthropic documents that Claude analyzes both text and visual elements in PDFs under 100 pages on any tier, while OpenAI documents that visual retrieval for PDFs is Enterprise-only and all other plans extract digital text and discard images.
For a large library of documents you query repeatedly, both handle it, and the deciding factor is where you put the files rather than which brand you picked.
What is the maximum PDF size Claude can handle?
Anthropic documents 500MB per file for chat uploads, up to 20 files per chat. Project files are capped much lower at 30MB per file, with unlimited file count as long as total content fits the context window.
Separately, Claude analyzes text and visuals in PDFs under 100 pages and processes text only for PDFs over 1000 pages.
Can ChatGPT read a scanned PDF?
Not on consumer plans. OpenAI documents that visual retrieval for PDFs is available only to ChatGPT Enterprise customers and is not supported for Free, Pro, Team, or Edu accounts.
On those plans ChatGPT extracts digital text from the file and discards any images, so a scanned or photographed document has no extractable text and yields nothing usable.
Why did Claude miss something that was in my project file?
Anthropic documents that retrieval augmented generation activates automatically when a project approaches or exceeds context window limits. Below that threshold everything is loaded at once.
Above it, Claude switches to searching and retrieving only what it judges relevant, which means the same project can behave two different ways depending on how full it is. A visual indicator appears when the switch happens.
How many PDFs can I upload to ChatGPT?
OpenAI documents up to 80 files every 3 hours, with free users limited to 3 file uploads per day. Individual files are capped at 512MB and 2M tokens, spreadsheets at roughly 50MB.
Inside Projects, only 10 files can be uploaded at the same time, and the project count per plan runs from 5 on Free to 40 on Edu, Pro, Business, and Enterprise.
The Verdict, By What Is Actually on Your Desk
There's no single winner. It depends on the document, not the brand.One huge PDF you need answers from today: either tool, dropped into a chat window, not filed into a project. Chat takes 500MB on Claude and 512MB on ChatGPT. The project route caps at 30MB on Claude and strips images on both.
A scan, a photo, or anything image-heavy: Claude, unless you are on ChatGPT Enterprise. Consumer ChatGPT discards the images, and images are the entire document.
A library you will query for months: project knowledge on either platform, with the images caveat understood, and know that Claude switches to search once the project outgrows the window.
A contract you are going to sign: neither one alone. Make the model quote and cite the page, read that page yourself, then cross-check with the other model per the Excel breakdown's verify rule.
You are only paying for one: ask whether your documents are born digital or scanned. That question decides it faster than any context window number.Put the file in the right place and check whether the visuals are being read. After that, sure, argue about which one writes prettier summaries.
Published and last reviewed July 18, 2026. Limits verified that day against vendor documentation linked inline: Anthropic's upload page (itself dated April 22, 2026), Anthropic's context window and RAG for projects pages, OpenAI's file uploads FAQ, visual retrieval FAQ, and Projects documentation. No first-party head-to-head test was run for this page. These numbers drift, and both vendors ship changes constantly, so check the official pages before relying on any figure here.
Both make real, editable .pptx files. The first page of Google gets that wrong.
Several of the slide-tool vendor pages ranking for this query still say the chatbots do not produce slides at all. A MindStudio page dated May 4, 2026 puts it plainly: Claude "is in the same boat as ChatGPT for visual design. It doesn't produce slides."
That was roughly true when it was written. It is not true now, and Anthropic's and OpenAI's own documentation is where you can check.
This happens a lot. The products change fast and the comparison pages don't. MindStudio itself published a newer piece on June 3, 2026 comparing ChatGPT PowerPoint, Claude, and Gamma that references the PowerPoint add-in and editable decks. The claim got updated. The older page is the one still ranking.
So before you trust any AI comparison, including this one, check the date on it.
Once you know both make files, the real decision is the tier gates, and they flip.
So here's my split for slides: the tool makes the file, you make the argument.
The premise of the question is out of date. My take: don't use PowerPoint. It's silly. It's like you have an assistant who does it better than you and faster.
Below is what each one actually makes, which plan gets you which one, and what to do when you have a deck due Thursday and a company template you have to match.
Both Tools Generate Editable .pptx Files as of July 2026
This changes the whole comparison, so here are the vendors' own pages.
Anthropic's file-creation doc: "Claude can create Excel spreadsheets (.xlsx), PowerPoint presentations (.pptx), Word documents (.docx), and PDF files." It does this by executing code to create files directly in your conversations, inside an isolated, sandboxed container.
OpenAI describes ChatGPT for PowerPoint as "a PowerPoint-native AI experience that lives in a sidebar inside Microsoft PowerPoint. It can help you create, edit, understand, and polish presentations directly, while preserving editable slide structure."
Editable slide structure. Not an image of a slide, not a wall of HTML. A file you open, click into, and fix.
Both of those pages are dated. Hold this one to the same standard.
There Are Four Mechanisms Here, Not Two Tools
The mistake is comparing "Claude" to "ChatGPT" as if each has one slide feature. Claude now has three separate ones with different plan requirements, and that third one is two days old.
Claude Slides, new on September 16, 2026. Anthropic launched it alongside the Cowork merge.
It drafts a presentation inside a normal conversation, you edit the slides directly, and you present from Claude or download PowerPoint or PDF. It is in beta, and per Claude's pricing page it is available on Pro and Max and not on Free.
This is the one that breaks every other comparison on this search, including the last version of this page. Keep reading for the corrected gate table.Anthropic's pricing page, September 18, 2026: Slides sits in the Pro column. Max adds usage, not Slides.
Claude, in-chat file creation. Claude writes code in a sandbox and hands you a .pptx. Anthropic states that "code execution and file creation is available to all Claude users (Free, Pro, Max, Team, and Enterprise)" on web, desktop, and mobile. Files can save to Google Drive. The cap is 30MB per file.
Claude for PowerPoint, the add-in. An add-in that integrates Claude into your PowerPoint workflow, running in PowerPoint on web, Windows, and Mac. Anthropic states it "is available to Pro, Max, Team, and Enterprise plans." Free is excluded.
ChatGPT for PowerPoint, the add-in. The sidebar described above. OpenAI states it "is available globally to Free, Go, Plus, Pro, Business, Enterprise, ChatGPT Edu, and K-12 users. Free and Go include limited usage access."
Put those four tier lists side by side and you can see them flip.
The Tier Gates Invert, and That Is the Actual Decision
A free Claude user can get a .pptx file but cannot get the sidebar. A free ChatGPT user can get the sidebar but is metered.Claude, in chat
Claude Slides
Claude for PowerPoint
ChatGPT for PowerPointFree plan included
Yes, all users
No. Pro and up
No. Pro, Max, Team, Enterprise
Yes, limited usageWhere it runs
Web, desktop, mobile chat
Inside a Claude conversation
PowerPoint on web, Windows, Mac
Sidebar inside PowerPointOutput
A .pptx file you download
Editable slides, export .pptx or PDF
Slides in your open deck
Slides in your open deckEdits an existing deck
Not documented
Not documented
Yes, pinpoint slide edits
Yes, add or revise slidesReads your slide master
Not documented
Not documented
Yes, stated explicitly
Hedged, "may not always match"Metered by credits
No
No, but spends normal usage
No
Yes, roughly 20 to 110 per taskStatus
Stable
Beta
Stable
StableOther file types
.xlsx, .docx, .pdf too
Slides only
Slides only
Slides onlyOne caution on that credit row. OpenAI conditions its credit figures on flexible pricing being effective, which makes it rollout-dependent. Check the current help page before you plan a week of deck work around a number from a blog post, including this one.
Only the Add-Ins Have a Verified Claim to Edit an Existing Deck
If your Thursday deck already exists and needs revisions, this is the row that decides it.
Claude for PowerPoint is documented to "make pinpoint edits to specific slides without regenerating entire decks." You select a slide and tell Claude what to change. ChatGPT for PowerPoint is documented to "add or revise slides in an existing deck."
Claude's in-chat file creation is documented for creating files. There is no equivalent published claim that it will take your uploaded .pptx and edit it in place.
That matters more than it sounds. Making a fresh deck and fixing slide 7 of an approved deck are different jobs. Only one of them is what most people are actually doing at 4pm on a Wednesday.
If you need the second one, you need an add-in, which means a paid Claude plan or a metered ChatGPT session.
Every Vendor Says the Same Thing About Company Templates: Start From the File
Anthropic, OpenAI, and Microsoft all agree on this one. It's also the move that actually works.
Microsoft's Copilot documentation is the bluntest: "Start with your organization's template. If your organization uses a standard presentation template, start with this file before creating a presentation with Copilot. Starting with a template will let Copilot know that you'd like to retain the presentation's theme and design."
OpenAI's Work documentation says to ask ChatGPT to match an existing file, master deck, or reusable template, and draws a useful line: a reference file applies to one request, a template can be used again.
One catch, though: OpenAI's Work documents article says PowerPoint is not included in that Work desktop flow at launch.
So whichever tool you pay for, do this:Open the approved company template file first. Do not start from a blank prompt and hope.
Work inside that file with the add-in, so the tool can see the master, layouts, and theme colors already in it.
Give it the argument, not the design. It has the design.
Check the first two generated slides against a known-good deck before you let it produce twenty.Nobody is going to praise your gradient. They will notice immediately if the logo is in the wrong corner.
Claude Makes the Confident Template Claim, ChatGPT Makes the Honest One
Each tool wins something different here.
Anthropic's is the strongest sentence either company publishes on this topic, from the add-in doc: "Claude reads the slide master, layouts, fonts, and color scheme in your deck and uses them when generating or editing slides." That's a clear, specific claim about the exact stuff a company template is made of.
One more nice detail: skills you have enabled in your Claude settings are available inside the PowerPoint add-in too, so any house style rules you have already written travel with you.
OpenAI hedges, in writing, on the same question: "Template adherence: The product is designed to work within existing presentation templates where possible, but generated or edited slides may not always match a preferred style perfectly."
It goes further and flags that "some advanced PowerPoint editing, chart, shape, formatting, and slide-management capabilities may be limited or still in development."
That hedge actually helps you.
A vendor telling you up front that formatting might drift beats a confident claim that turns out to be loose at 11pm. Plan a formatting check either way. ChatGPT just told you to.
ChatGPT's real win is reach. It is in the sidebar on Free, in a product your employer already licenses, on a plan you may already have. Claude's sidebar requires Pro or above.
What Neither One Knows Is What Your Audience Needs to Believe
This decides whether the deck lands, and no docs page covers it.
In Claude vs ChatGPT for Excel, my argument is that being technical stopped mattering. Nice-looking output and reading the data are cheap now. What matters is taste, plus the way you already know things should be done.
Slides are the clearest case of that. Both tools will produce a clean, on-brand, well-spaced deck. Neither knows that your VP kills any recommendation that appears before the cost slide, or that the number on slide 4 is the one the whole room came to argue about.
I handle this the same way on the content side. In my write-up of Claude Cowork scheduled tasks, I describe trying to fully automate long-form content and watching it fail: you sound robotic reading it, you lose track of what you're talking about.
What works instead is that the system generates the outline and I supply the substance.
Same shape for a deck.
Let the tool build the structure and the file. You own the argument, the order, and the cut. It fails the same way in both cases. You get something that reads smooth but says nothing you would defend in a room.
One more rule worth stealing from that Excel piece: one job per session. Do not dump twenty files on twenty topics and ask ten questions at once. One deck, one audience, one decision you want made.
If you are still deciding how much of your work belongs in these tools at all, the Claude Guides pillar lays out the lanes.
Deck Due Tomorrow, You Pay for Both? Research in ChatGPT, Design in Claude
If you pay for both and you have a deck due, do not agonize. Here's the split I would run. It's two steps.
Step one: ChatGPT, for the thinking. Get the raw ideas, the text, and the research hashed out first. ChatGPT is phenomenal at this part.
Use Astra if your plan has it, or a mid reasoning level on the $20 tier if that is still what you are offered, which is plenty for this. One warning: Astra burns your usage fast, so do the research pass and get out. Come away with an outline and the actual words.
Step two: Claude, for the deck. Then open Claude and tell it you are designing a presentation. Give it three things first:Your audience. Who is in the room and what they need to believe.
Your colors. Say them explicitly.
A reference deck you like, and ask it to reverse engineer why it works. The composition, the font choices, the psychology of how the thing is laid out. Most people can't explain why a deck looks good. This step lets you borrow that judgment instead of guessing.Then let it come back with topics, colors, and layout options.
For PowerPoint, I say open Claude. That's it. ChatGPT thinks, Claude builds the slides. That's my split on this one.The 60-second version, from my Shorts: Claude or ChatGPT? Wrong question. Here's when to use each..And do not use PowerPoint by itself. I know that sounds a little much, but I mean it. You have an assistant that does this faster and better than you will by hand. Using the bare app is picking the slow path on purpose.
In my opinion, the bolted-on Copilot experience is a downgrade from just going to Claude or ChatGPT directly and bringing the file back.
Is the beta label on Claude Slides a reason to wait?
Beta doesn't mean anything, bro. Use the feature and just try it out. It might be buggy, but it is not useless. Anthropic shipped it because it is usable. Try it, find out where it breaks on your work, and keep the old route in your pocket for the deck that actually matters.
How to Actually Build the Thursday Deck
No feature list here, just the order to do it in.Write the argument first, in plain text. Five to eight bullets, in the order you want the room to accept them. You can't hand this part off.
Open the approved template file. Not a blank deck, not a theme you picked. The file your company sends around.
Open the add-in you have access to. Claude for PowerPoint if you are on Pro or above, ChatGPT for PowerPoint otherwise.
Ask for structure from your bullets, one section at a time, not the whole deck in one shot.
Check slides one and two against a known-good deck before generating the rest. Fonts, logo placement, color, title case.
Revise slide by slide. Both add-ins support targeted edits. Use them instead of regenerating.
Read it out loud as an argument. If you cannot say why each slide exists, cut it.Step 1 is the one people skip, and it is the one the tools cannot do.
If you want the free-tier path instead: ask Claude in chat for a .pptx built from your bullets, download it, then paste your content into the company template manually. Slower, but it costs nothing and you keep the template intact.
Frequently Asked Questions
Can Claude make PowerPoint presentations?
Yes. Anthropic's documentation states Claude can create PowerPoint presentations (.pptx), along with Excel, Word, and PDF files, by executing code in a sandboxed container inside the conversation. This file creation is available to all Claude users including Free, on web, desktop, and mobile, with a 30MB per-file limit.
Does ChatGPT work inside PowerPoint?
Yes. ChatGPT for PowerPoint is a sidebar that lives inside Microsoft PowerPoint and can create, edit, understand, and polish presentations while preserving editable slide structure. It is available globally to Free, Go, Plus, Pro, Business, Enterprise, Edu, and K-12 users, with Free and Go getting limited usage access.
Which one matches my company template better?
Claude makes the stronger documented claim. Anthropic says Claude for PowerPoint reads the slide master, layouts, fonts, and color scheme in your deck and uses them when generating or editing slides.
OpenAI hedges, stating that generated or edited slides may not always match a preferred style perfectly. Either way, start from the template file rather than a blank prompt.
Can AI edit an existing PowerPoint deck?
Yes, through the in-PowerPoint add-ins. Claude for PowerPoint can make pinpoint edits to specific slides without regenerating entire decks. ChatGPT for PowerPoint can add or revise slides in an existing deck. Claude's in-chat file creation is documented for creating files, not for editing an uploaded .pptx, so use the add-in when you need to edit.
Do I need a paid plan for AI slides?
It depends which mechanism you want, and the gates invert. Claude's in-chat .pptx creation includes Free users, but Claude for PowerPoint requires Pro, Max, Team, or Enterprise. ChatGPT for PowerPoint includes Free and Go with limited usage, but it is credit-metered, with a typical task consuming roughly 20 to 110 credits.
Where this comes from
I do not make decks, and nothing on this page pretends I do. Every capability claim links to Anthropic, OpenAI or Microsoft's own pages, checked July 18 and again September 18.
The MindStudio quote is word for word from a page dated May 4, 2026. I didn't run a head-to-head test. Prices and credit numbers move, so the linked pages win over this one.
Pick By Which Mechanism You Need
There's no one winner here. It depends on your plan and your deck.You are on a free plan and just need a deck to exist: Claude, in chat. It is the only free path to an actual .pptx file, and it also does .xlsx, .docx, and .pdf.
You are on a free plan and need to work inside PowerPoint: ChatGPT for PowerPoint. It is the only sidebar that includes Free, though usage is limited and metered.
You already pay for Claude Pro or above: Claude for PowerPoint. The slide master claim is the most specific one either vendor publishes, and your enabled skills come with you.
You must match a strict corporate template: open the template file first, then use an add-in inside it. That advice comes from Anthropic, OpenAI, and Microsoft alike.
You need to revise an existing approved deck: an add-in, not in-chat generation. Only the add-ins have a documented edit-existing-deck capability.
You want the new Claude Slides specifically: it needs Pro or above, it is in beta, and I wrote up what it is and what it cannot do at Claude Slides.
You are deciding which subscription to hold for work generally: read Claude vs ChatGPT for writing and Claude vs ChatGPT for Excel before you pick, because slides are rarely the only thing on the list.Making the file is the easy part now. The argument is still your job.
Correction Log
This page's whole point is "check the date on it," so here are this page's own dates.July 18, 2026. Published with two Claude mechanisms and one ChatGPT mechanism, and the tier-inversion argument.
September 4, 2026. Reviewed, no mechanism changes.
September 18, 2026. Wrong, in the same way I accused everyone else of being wrong. Claude Slides launched on September 16 and the previous version of this page did not know it existed. Added it as a third Claude mechanism, rebuilt the gate table around it, added the beta row, and added the two-step workflow. The tier-inversion thesis survives: Free still gets in-chat .pptx from Claude and still cannot get Claude Slides.This stuff just moves that fast.
Published July 18, 2026. Updated September 18, 2026 for Claude Slides. The correction log above has the dates.
Quick answer: yes, Claude Cowork scheduled tasks now run remotely, which means they fire on their schedule even when your laptop is asleep and the app is closed. The one exception is a task that needs your local files or apps, which still has to run on your awake machine.
That one fact is what makes recurring Cowork tasks dependable. It's also the thing half the articles on this page still get wrong.
If you searched "claude cowork scheduled tasks," "do cowork tasks run when my computer is closed," or "how to schedule a task in claude cowork," this page settles it: the closed-laptop question first, then the 60-second setup, then what to schedule so the feature earns its keep.I walk through this on camera in 8 Claude Routines That Run My Business While I Sleep (20 min).Yes, they run with your laptop closed (with one exception)
This is the big one, so it goes first.
A lot of pages you will find on this exact search still say scheduled tasks "only run while your computer is awake." That was true at launch. It is not true now.
Anthropic's current help center is explicit. From the scheduled tasks help article: "Scheduled tasks run remotely, so they run on their cadence even when your computer is asleep or the Claude Desktop app is closed."
Their cross-device help page says the same thing a second way: scheduled tasks "no longer need your computer to be awake."
So the morning brief lands whether or not you opened your laptop. That is the difference between a nice demo and a system you can rely on.
The exception is in the same help article: "If a scheduled task requires local files or apps, it will only run locally." A remote run happens on Anthropic's servers, so it can reach your connectors (email, calendar, Slack, Drive) and files saved to your Claude account, but it cannot reach a folder sitting on your hard drive.
Point a task at your Downloads folder and it becomes a local task again, which means your machine has to be awake for it.
The clean rule: connectors and cloud files run in the cloud, your local folders run on your desk. My shorthand for it is "cloud in, cloud out; local files, local machine."
Design your recurring tasks around connectors and you get the closed-laptop magic. Design them around a local folder and you are back to leaving the lid open.
How to set one up (about 60 seconds)
You do not write any code. Two paths, both in the app.
Open the Scheduled section in the left sidebar, then click New task in the upper right. From there:Set up manually. Enter a task name, the prompt (what you want it to do), an approval mode, a frequency, and optionally a model and a folder. Click Save.
Create with Claude. Claude asks you a few multiple-choice questions, then proposes a task name, a schedule, and what it will do. You click Schedule to confirm.Frequency options, straight from the help article: hourly, daily, weekly, on weekdays, or manually. That covers almost every real recurring chore.
One detail that trips people up: each scheduled run is its own fresh Cowork session. It does not remember your last chat.
So everything the task needs to know goes in the prompt, in a connected tool, or in a file it can open. Write the instruction as if the task has never met you, because on every run, it hasn't.
You manage the whole thing from that same Scheduled screen: review upcoming and past runs, edit the instructions or schedule, pause a task, resume it, delete it, or run it on demand when you do not want to wait for the next cycle.
The first thing I scheduled: my inbox
Hands down, inbox. It organizes, archives the junk, unsubscribes, and pings me about the stuff that matters: this person reached out, this bill needs to be paid.
But the part worth copying is how I got there: I ran it manually first. I described what I wanted without fully understanding what I actually needed, let it run, and iterated. Okay, I need this part.
I do not need that. I like this format better. Once it did the job right repeatedly, and only then, I put it on a schedule and stopped babysitting it. It eventually graduated off Cowork entirely onto my always-on machine, but Cowork is where I tested it.
Run it manually until the output stops surprising you. Then schedule it. That's it.
What to actually schedule (the recurring stuff that compounds)
Don't schedule something clever. Schedule something boring that you do every week anyway. That's what turns Cowork from a tool into staff, and it's the part most articles skip.
Anthropic's own launch note put it well: "You set it up once, a morning brief, weekly spreadsheet updates, Friday team recaps, and Claude handles it automatically." Real users landed on the same handful of jobs.The recurring job
How often
Runs closed?Morning email + calendar brief
Daily / weekdays
Yes (connectors)Weekly metrics or content review
Weekly
Yes (connectors/cloud files)Monday expense report from forwarded receipts
Weekly
Yes (connectors)7am digest of your industry sources
Daily
Yes (web + connectors)Sort/rename a local Downloads folder
Weekly
No (local files, needs awake machine)Monthly LinkedIn profile health check
Weekly / monthly
Yes (web)Notice the split maps exactly to the exception above. The jobs that run with the lid closed all pull from connectors or the web. The one that needs an awake machine is the one pointed at a local folder.
For the full list of what people run, 20 real Claude Cowork use cases has the receipts, and every recurring one there is a scheduled-task candidate.The 60-second version, from my Shorts: 3 FREE Claude Tasks That Run Your Business On Autopilot.The best scheduled task: a weekly review that does the research first
The recurring task I'd copy is the one I run myself, documented in the Cowork use cases breakdown: a weekly content and metrics review. Mine answers three questions: how did the content perform, are we trending the right direction, and why or why not.
This is that weekly audit, straight from my system. Verdict first, graded against my own playbooks:The part that makes it good, the rule I gave in that post: have it do the research BEFORE proposing changes, because sometimes the right answer is "nothing is broken, keep going, put in the volume." A scheduled review that jumps straight to "here are 5 changes" every week trains you to keep changing things for no reason.
One that checks the data first and is allowed to say "no change needed" is the one you keep.
The gotchas nobody warns you about
Scheduled tasks are good. But three real snags show up in the community threads, and you should know them before you trust one overnight.
Fresh session means re-auth on some tasks. One user set up a daily task that scrapes an authenticated site in the browser and hit a wall: "because scheduled sessions start in a new chat window it prompts for browser access every time, which defeats the purpose of scheduled/automated runs."
Anything that needs a live browser login is a weak fit for unattended scheduling right now.
Silent overnight failures. Another user chaining tasks flagged the honest hard part: "what happens when a scheduled agent fails silently at 3am.
Still figuring out reliable error propagation." Anthropic's help article does not document retry behavior, so treat a critical task as "check the result," not "trust it blind." Read the past-runs list on the Scheduled screen for anything you actually depend on.
It burns your plan faster than chat. Anthropic says this directly in its consumption guide: "A single Cowork task or Claude Code debug session can consume many more tokens than chat."
A task running every morning is doing multi-step work every morning. On the $20 Pro plan, a few heavy daily tasks will meet the weekly cap. That is plan sizing, not a bug, and it is the exact signal covered in Claude Max vs ChatGPT Pro.
What I refuse to schedule: content
The place scheduling has burned me every single time is content. I used to fantasize about a fully automated content pipeline: I put everything in, it generates, and my only job is to review at the end. It does not work that way. And honestly, it is not as fun. It is mindless.
I tried scripting entire 20 to 30 minute videos. You sound robotic reading it, and you lose track of what you are even talking about. What actually works is the opposite: the system generates the outline and the research, and I riff the substance.
I wing it in a controlled way. I enjoy it more and I know what I am talking about. My newsletter gets repurposed from that long-form, so it is already in my voice. Same pattern on Substack: I pick the topic, I riff, I approve the outline and the research.
The rule that came out of all that burn: creating content has to be more me; the system's job is to help me create it faster. That is the difference between AI slop and having a ghostwriter partner who understands your vision.
Schedule the deterministic stuff (pull the analytics, scrape the competitors, prep the research) and keep the substance human.
Cowork or Claude Code for scheduling?
If you write code, you might wonder whether to rig this up in a terminal instead. For recurring office chores, you almost never should.
My take, from Claude Cowork vs Claude Code: scheduled tasks are cleaner in Cowork than anything I have rigged up in the terminal, and I live in Claude Code all day. You define the cadence once and it just runs, no cron file, no script, no install.
The simple rule: Cowork does your office work, Claude Code builds software. A weekly report is office work. Keep it in Cowork.
What I would schedule first
If you have never made one, do not overthink the first task.Easiest win: a daily or weekday morning brief that reads your email and calendar and hands you the day. It runs on connectors, so it fires with your laptop closed.
The compounding win: a weekly review that checks your real numbers and is explicitly allowed to say "nothing is broken." Research first, changes second.
The reminder that works for me: my content day is Friday, so a Friday task kicks off the first steps on its own. It pulls candidate topics and starts the research without waiting for me. I cannot forget content day, because the work is already sitting there when I show up. If you batch anything weekly, give the batch day a task that runs the boring first hour for you.
Skip for now: anything pointed at a local folder or needing a live browser login, until you are okay leaving your machine awake for it.Build one, watch its first two runs on the Scheduled screen, then add a second.
If you want ready-made prompts that make good first scheduled tasks, grab the 15 workday AI prompts at /start. Most of them run fine on the $20 tier and turn into recurring tasks in one click.
How this was checked
Product facts here are from Anthropic's official help center, linked inline at each claim: the scheduled tasks article, the cross-device article, and the consumption guide. User reports are public Reddit threads, linked where quoted.
A few things Anthropic does not document, so this page does not claim them: exact timezone/DST handling, retry behavior on a failed run, and whether scheduled-task completion pushes a notification. Where users report a gotcha, it is labeled as a community observation, not official behavior.
Published and last reviewed July 17, 2026. Product facts checked against Anthropic's support center on that date. Cowork's scheduled tasks are available on all paid plans and, per the current help center, run remotely even when your computer is asleep, with local-file tasks as the documented exception. These products change often; the linked official pages are the source of truth.This post is part of Claude Guides, the hub with every plan decision, task comparison, and setup guide for using Claude without code.
Quick answer: people use Claude Cowork for the boring work that eats their week: sorting files, triaging email, building the same report every Monday, prepping taxes, tracking home repairs, tailoring resumes.
Not science fiction. Chores.
This is a complete, organized list of 20 real use cases, pulled from what actual users report doing (linked, so you can verify every one) plus the ones I run myself.
The community's own words, from the biggest use-case thread: "No '50x your productivity' hype please, just real, everyday use cases." Agreed. If you searched "claude cowork use cases," "cowork examples," or "what do people use Claude Cowork for," this is the reference. Steal freely.I walk through this on camera in The Only 4 Claude Cowork Use Cases Worth Keeping (I Deleted the Rest) (12 min).The map: 7 categories of real Cowork workCategory
The chores
Best first pick?Files and documents
Downloads cleanup, renaming by content, pulling data out of PDFs
✅ easiest winInbox and comms
Email triage, drafts in your voice, calendar wrangling
Start day 2Recurring reports
Monday expense report, weekly metrics, morning brief
The compounding oneResearch and monitoring
Competitor watch, topic digests, multi-document synthesisMoney and admin
Receipts to spreadsheet, tax-prep summaries
Seasonal heroCareer
Resume tailoring, job radar, LinkedIn upkeep
Quiet compounderPersonal ops
Home maintenance log, personal CRM, insurance questions
Sleeper hitsEverything below runs in plain English. No terminal, no code. Cowork is included on every paid Claude plan and, as of July 2026, its scheduled tasks run remotely, even with your laptop asleep.
Files and documents: the easiest first win
1. Clean the Downloads folder. The most-reported first use case, and for good reason. One user on r/ClaudeAI had Cowork organize their Downloads folder in 5 minutes and called it a day of work saved.
A blogger stress-tested it on 2,200 files: sorted into 11 folders in about 20 minutes, including renaming 50 "Untitled" images and 17 generically named documents by reading their contents.
Honest number from that test: about 70% of the auto-names were right. So it's a great assistant, but you still want to skim what it did.
2. Rename files by what is inside them. Not by filename. It opens each file, reads it, names it properly. Users in the big use-case thread describe exactly this workflow for the "sort the chaos" problem.
3. Pull specific data out of a pile of PDFs into one table. Contracts, invoices, statements in a folder → one clean Markdown or Excel table with the fields you asked for. Same thread, multiple reports.
4. Turn messy project folders into master documents. One engineer, in an r/ClaudeAI thread, had Cowork scan a folder from a production-line commissioning, categorize everything, and produce a master bill of materials for the maintenance team. Same move works on any documentation dump.
5. The insurance folder. One user dropped four insurance policies, including a 240-page health policy, into a folder and now just asks questions against it, per the thread. Pretty much every household could use this folder.
One caution from experienced users: go folder by folder, not "reorganize my whole computer."
Inbox and comms: the daily grind, delegated
6. Email and calendar triage. One r/ClaudeAI user put it in the most relatable way possible: the fancy agentic stuff was over his head, so he just uses Cowork for handling emails and organizing calendars.
That's the right place to start. This is also my own #1: my inbox gets checked multiple times a day by the system, and it is exactly the kind of chore I hand Cowork.
7. Status updates drafted in your voice. One user has Cowork read the project folder and draft the update so all that is left is pressing send. The trick: it writes FROM your files, so the update is accurate, not generic.
8. Gmail into a tracking spreadsheet. Sales and customer-success people report having Cowork categorize emails (opportunity, lead, rejection) and update their sheet or CRM. If your pipeline lives in your inbox, start here.
9. Synthesize the noise. Teams chats, meeting notes, emails, scattered docs, dumped and synthesized on a schedule into one readable brief. One user built a Getting Things Done dashboard that pulls together overdue Asana tasks and unread email.
Recurring reports: where Cowork stops being a tool and becomes staff
This is the category most articles miss, and it is the best one. Type /schedule inside any task, set the schedule once, done. It runs even when your computer is asleep.
10. The Monday expense report. One user forwards anything resembling a receipt; Cowork stores them all week and sends an expense report every Monday morning. The same user's summary of the whole product: "It really is like a junior assistant."
11. The 7am digest. Same user gets a daily email summarizing highlights from the subreddits they care about. Swap in your industry sources.
12. Weekly analytics review. This one is mine, and my advice is: do not make it complicated. Mine answers three questions: how did my content perform, are we trending the right direction, and why or why not.
Here is a real one from this week, verbatim from my system:The one thing I have learned: have it do the research BEFORE proposing changes, because sometimes the answer is "nothing is broken, keep going, put in the volume." A flat week doesn't mean you need to change everything.
13. The auto-updating deliverable. One user maintains a revenue model that updates itself with the latest forecasts, slides included. Cowork writes real Excel, PowerPoint, and Word files, so "the deck" can just always be current.
Research and monitoring: your standing scouts
14. Watch for specific signals. One user has Cowork scan public sources for phrases that signal frustration with a product category, logging date, source, and exact wording. That is a lead machine or a product-research machine, depending on your job.
15. Deep-mine your own archive. Podcast host Aakash Gupta ran Cowork across years of his own transcripts to find where guests directly contradicted each other, then had it build the "10 most quotable insights" into a Keynote deck, edited directly in the app.
If you have an archive (calls, docs, posts), there's probably good stuff in there you've never pulled out.
16. Conference prep. Attendee list + a data source + Cowork = bios and talking points for everyone you want to meet, read on the plane.
Money and admin: the seasonal hero
17. Tax prep from raw transactions. A user in a Claude community group downloaded a year of bank and credit-card transactions, handed them to Cowork, and got back an annual summary for tax prep, in minutes instead of days.
A LinkedIn user reported the same move saving roughly 5 hours. Pair it with use case #10 and next year's version builds itself weekly.
Career: the quiet compounder (even if you are not job hunting)
18. The recurring LinkedIn health check. My favorite move for employed people. Have Cowork pull your LinkedIn profile on a schedule and grade it: is your headline current, is your bio dry, when did you last post? Simple report, monthly or biweekly.
Why bother? Recruiters find active profiles, so people reach out while you sleep.
And this is exactly the task you would forget: Cowork won't.
19. The job-search folder. Users run a folder system: resume, cover letters, and Cowork tailors per job description. Fair warning from that thread: review before sending, it can oversell you. A lighter version even if you are happy where you are: a monthly "what roles like mine are trending" radar.
Personal ops: the sleeper hits
20. The home maintenance tracker. The best "I did not know it could do that" story in the threads: a homeowner had Cowork sift 10 years of email for every repair (plumber, electrician, stucco), log dates, contractors, and costs, then build a maintenance schedule synced to Google Calendar.
That's the house admin, handed off. Honorable mentions from the same community: a personal CRM for keeping up with your network, and the insurance folder from #5.The 60-second version, from my Shorts: Claude Cowork can plan your entire trip: the 3-step setup.The move that beats all 20: reverse-prompt it
Here is what I tell everyone who asks "but what would I use it for?"
Do not guess. Tell Cowork your situation: who you are, what you are good at, what you hate doing, your goals, your roadblocks.
Then ask IT for the best opportunities to take work off your plate. Save that context as an "about me" file so it remembers, and build the top two or three suggestions as scheduled tasks.
My content chores won't match yours, but the method works for anyone. Hand off a boring task once and it keeps paying off.
If you think visually: riff out loud and have Cowork sketch and document your workflows. The old version of this was an afternoon in Canva. Now you just talk it through and the docs come out of that.
The honest limitsIt burns your allowance faster than chat. Agentic work is multi-step work. On the $20 Pro plan, heavy daily Cowork use will meet the weekly cap. That just means your plan is too small. If you are hitting it weekly, that is the exact signal covered in Claude Max vs ChatGPT Pro.
It is a strong assistant, not an infallible one. The 2,200-file test above hit ~70% naming accuracy. Skim its work, especially anything outbound.
Chat memory does not carry over into Cowork (outside projects), so give tasks their context.Facts current as of July 2026, checked against Anthropic's Cowork page: included on all paid plans, on desktop (macOS, Windows, Linux, ChromeOS) and the web with mobile in beta, scheduled tasks run remotely, and connectors cover email, calendar, Slack, Drive, and more.
Still deciding between the two cockpits? That is its own decision: Claude Cowork vs Claude Code. And if you want ready-made starting prompts for your workday, grab the 15 workday AI prompts at /start: most of them make good first Cowork tasks.
Published and last reviewed July 12, 2026. Every use case links to its source thread or article; community-reported details verified against the linked threads at publish time.This post is part of Claude Guides, the hub with every plan decision, task comparison, and setup guide for using Claude without code.
Quick answer: you cannot pick Cowork anymore. On September 16, 2026, Anthropic merged Cowork into Claude. There are two doors left: Claude, which you talk to, and Claude Code, which you point at a folder.
If you do not write code, the answer is Claude, and you no longer have to choose a tab to get agentic work done.
Searching for "cowork vs code", "Claude Code vs Cowork", or "when to use Claude Cowork vs Claude Code"? You are in the right place. Half the comparison stopped existing two days ago.
The rule on this page expired on September 16
This page used to teach a three-way fork, and I am going to retire it in public instead of just editing it away.
The old rule was: Chat answers. Cowork does your office work. Claude Code builds software.
Cowork is no longer a place you go, so that rule is dead. Here is the replacement.
Claude does the work. Claude Code builds the thing that does the work. That's my two-door rule, and it is the whole page now.
The one question that picks between them: does this job need to edit real files in a real folder on my machine? If no, stay in Claude. If yes, that is Claude Code.
Everything Cowork used to do, Claude now routes to itself. Anthropic says it decides whether your request needs a quick reply, connected tools, extended execution, or document creation, without you picking a container. Per TechCrunch's report, customers "often struggled to choose the right tab for the right task," so Anthropic removed the choice.
And nothing was deleted. Anthropic's wording: "everything is where you left it: your chats, projects, artifacts, connectors, and skills."
If you landed here because your Cowork tab vanished and you want the full story of where it went, that is Claude Cowork is now Claude. This page is about the fork that survived.
But it has not actually reached most accounts yet
Heads up before you go looking for a changed app.
The rollout is staged: Pro and Max first, on web, desktop, and mobile, "over the coming weeks," with Team and Free following.
I pay $200 a month for Max 20x, which puts me in the first wave. Here is my settings window on September 18, two days after the announcement:My Claude desktop app, September 18, 2026, version 2.2553.1. Two days after the merge was announced, Claude Code and Cowork are both still sitting there as separate sections.
So what Anthropic announced and what my app shows are not the same thing this week. The merge is announced. My paid account still shows the old shape. Both screenshots on this page are real and dated, because that is the only honest way to cover a staged rollout.
Plan for the two-door world. Do not panic when your app still shows three.
The earlier correction: the terminal fork is dead
The earlier version of this page told you the answer came down to one question: do you want to click, or do you want to type commands.
That was the whole thesis and it is no longer true.
Claude Code ships in the desktop app. From Anthropic's own Cowork FAQ: Claude Code "is available in the terminal, in the desktop..." So it has two front doors: the terminal and the desktop app.
Here is what that looks like on my own machine.My Claude desktop app, September 5, 2026, before the merge was announced. Claude Code and Cowork are sibling tabs in the same settings window. There is no terminal in this picture.
So if you have been avoiding Claude Code because you do not want to live in a command line, that reason has expired. You may still not want it. Just not for that reason.
The difference in one tableClaude (Cowork merged in)
Claude CodeWhat you hand it
A job to finish
Something to buildWhere it lives
Web, desktop app, mobile
Terminal and desktop appWhere tasks run
Anthropic's servers; the desktop app bridges your local files
SameBuilt for
Files, docs, email, reports, browser work, documents and decks
Software: code, plugins, custom systemsSetup required
None. It is the app
None on desktop; a terminal install if you want the CLIBest at
Delegated and recurring work, scheduled tasks
Complex builds, custom scripts, full step-by-step visibilityIncluded on
Every plan, including Free. The merged experience reaches Pro and Max first
Pro and Max. Not FreeSame AI engine?
Yes
YesBoth come with your paid plan, so you are not buying anything. You are just picking which door to open.
Same engine, different job
People treat Chat, Cowork, and Claude Code like a power ladder: Chat is the starter tier, Code is the pro tier, Cowork sits in the middle. That model is wrong, and it is the biggest thing I see people get confused about.
Anthropic could not be more direct about it:"Cowork and Code run on the same engine. Both are Claude Code underneath."And the replacement fork, in Anthropic's own words: "Cowork is for delegating to Claude. Code is for building software with Claude. Most knowledge workers will live in Chat and Cowork."
This gets debated constantly. u/SilverConsistent9222 on r/Anthropic put the trap well: "They're often discussed as if one is an upgrade over the other. That's not really accurate. They operate in different environments."
The loudest version of the confusion is a thread titled "What's the point of Cowork when you have Claude Code?", which pulled 316 upvotes and 149 comments on r/ClaudeAI. People keep asking because the click-versus-terminal answer never really answered it.
The cleanest rule of thumb I have seen came out of u/Talley-Ho's thread on the same question: codebase goes to Code, everything else file-based goes to Cowork.What Cowork gave you, and where it went
This list should have been on this page all along, and almost no other page that ranks for this shows it. Per Anthropic's Cowork documentation before the merge:Access local folders with no upload step
Navigate your logged-in browser through Claude in Chrome
Reach desktop apps via computer use
Delegate parallel work, several jobs at once
Run tasks on a scheduleAll of that is now just Claude. Anthropic says your connectors and skills came across untouched, and the routing that used to require picking the Cowork tab happens on its own.
So the merge was not a feature cut. Everything on that list survived. Only the Cowork tab went away.
One caveat that still holds: several of these were never only a Cowork thing anyway. Claude Code can do most of them too. The difference is that Cowork had them ready out of the box, and in Claude Code you set them up yourself.
One more bit of history: since August 26, 2026, Cowork had its own browser built into the desktop app. Three weeks later it stopped being its own thing.
The computer-use item is the one I would think about most, because it has nothing to do with avoiding a terminal.
Quick note on my own setup: I have a shorts pipeline that logs into my Mac mini, takes screenshots, clicks around and opens real apps to run experiments.
That one runs in Claude Code, not Cowork. I bring it up because it is the kind of work Cowork's computer use opened up to people who never open a terminal. Cowork did not run it.
Scheduled tasks are the least-hyped item on that list and probably the most useful. You set the schedule once and it just runs.People use this for boring, useful things. A product manager, u/RusticGroundSloth on r/ClaudeCowork, described his setup:"there's a 'director' cowork project that pulls all of my Teams and Email from the last 24 hours every morning at 6:00 a.m... Claude Cowork has essentially become my project/program manager and is saving me HUGE amounts of time... I realize a bunch of this could probably be done in Claude Code but it was extremely easy to set up in Cowork and I haven't had to think about it since."That last part is the point. It could have been done in Code. It just was not worth doing in Code.The 60-second version, from my Shorts: You don't need Claude Code. Cowork does 90% of it.Everything Cowork hands a non-coder lives behind this one plus button: files, a screen recording that becomes a skill, your skills, your connectors, plugins. None of it is a terminal.
Where Claude Code still wins
Code is for building things. That line still holds.
If you live in Claude every day, you are going to do most things. You will get your job done, you will build skills, you will run some pretty powerful workflows. That covers most knowledge work.
But if you want to code, hence the name, that is where Claude Code starts. Build a game. Build an app.
And "an app" is broader than it sounds. I have a skill that edits my videos. That is not an app in the App Store sense, but it is a real piece of software with many moving parts, and that is Claude Code work.
The other thing Code gives you is visibility into every step the agent takes. That is why developers will not give it up, and it is a fair reason for a non-developer to move over too, eventually.
What I still open it for, now that Claude handles the long jobs
Now that the merged Claude routes multi-step work by itself, this is what is still left on my side.
Coding. Complex workflows. Brainstorming that turns into something I have to build.
Stuff like an app, a plugin, a custom skill, or refining the system that edits my videos. Those are Claude Code jobs because they need something that can edit my folder, not something that can make me a document.
The biggest one right now is not a piece of software at all. I am building a second brain that is actually a second brain, and feeding it daily. Where I learn something, what I read, what I pull out of a YouTube video.
That never used to get written down. It would be an inspiration-spur moment, I would go update the system, and then it could get reversed later and the reasoning was just gone.
Unreferenceable.
Now there is a system that grows with me, and when I go to make something I have somewhere to make it from. That is a lot of work to get where I want it. It is also the thing I would not try to run out of a chat window.
The common thread in all of those: I need to see the folders. If I cannot see the file tree, I feel like I am going to end up with a lot of trash in there.
Which is why you should ignore a whole category of online takes. Developers keep posting some version of what u/gatsbtc1 wrote: "Everything cowork can do, so can code. And code is so much more robust."
That is true, but it does not matter for you. Everything a car does, a manual transmission race car also does. You still do not need to learn to heel-toe shift to get groceries.
How I actually split them, and why I am the wrong model
Here's the honest part, including the bit that does not flatter me.
I do not switch between them mid-job. I want to be straight about that, because "tell me about a job that moved from one to the other" is a great question and I do not have a story for it. I use both. I do not toggle.
For me, it is Claude Code, because it does everything I need and I am already fluent in it. Going from Claude Code back to Cowork would feel like a downgrade from what I am used to.
But that is a fact about my history, not about the products.
The reason I got good at Claude Code is that I decided to, so I could make YouTube videos about it. And getting there was rough. I would see the hype, watch technical people using it, and think: I am pretty technical, why can I not get into this?
I did not even know what Claude Code was. I knew it was in the terminal. Did I have to install something? I did not know what a CLI meant.
This was over a year ago, maybe six months after it first came out, when I was mostly living in n8n.
When it finally clicked, it clicked hard. It just made sense to me. But I am comfortable staring at a terminal window, and I do not recommend that path for everybody.
What I want you to take from this: if I were starting today, and Cowork existed, I would probably have started there. The transition I made was painful and it was only worth it because I had a specific reason.
You probably do not need to repeat it.
I think the reason for having both is pretty clear: if Claude is your main driver, Claude Code is there for when something gets serious. It is the same shape as ChatGPT Work and Codex on the other side of the market. Nobody thinks that pairing is strange.
The usage gotcha nobody warns beginners about
Anthropic printed this in plain sight on its Cowork documentation and almost no comparison article mentioned it: agentic work consumes your limits faster than plain chat does.
The merge did not change that. It removed the tab. The usage math is the same. One task that sorts a folder of 30 files is not one message; it is dozens of steps, each drawing on your allowance. Now that Claude routes those jobs itself, it is easier to start one without noticing.
Documents and decks almost certainly count too, since they are the same kind of multi-step work, but I could not find Anthropic publishing a specific rule for them, so I am not going to make one up. Check your own meters after a long deck session rather than trusting anyone's number, including mine.
Claude Pro caps you two ways: a rolling five-hour session limit plus a separate weekly cap. On the $20 plan, heavy agentic use will hit that, and it will feel like the product is broken.
It is not. The $20 tier is sized for chat-first use with some agent work on the side.
On the narrower question people keep asking, whether Cowork and Claude Code burn your plan at different rates, there is a 27-upvote thread asking exactly that.
I am not going to give you a ratio, because Anthropic publishes no multiplier and every number going around is somebody's estimate from their own usage. What is documented is that both draw from the same pool as your chat.
If either one becomes your daily workhorse, that is what Claude Pro vs Max is about.
When does a job leave the chat window at all?
A lot of people who land here are actually asking the earlier question: when does a job leave the chat window at all?I walk through that one on camera in the Chat vs Cowork video (11 min).The line Anthropic drew before the merge still helps, even though you no longer pick between them: a conversation is something you steer turn by turn, and a delegation is something you hand over.
A conversation gives you text you will read. A delegation gives you a finished file or an action taken.
The difference now is that you do not choose. You describe the outcome and Claude decides which one it is.
Which one should you open?You do not write code: Claude. Just describe the outcome. You do not pick a mode anymore.
Your work is documents, email, spreadsheets and reports: Claude. That is what the merge was for, and Docs and Slides now live in the same conversation.
You want a chore to just happen every morning: Claude. Scheduled tasks came along with everything else.
You want Claude to click around real apps or your browser: Claude. Claude Code can be driven to do this too, but you no longer need a separate surface for it.
You are building software, a plugin, an app, or a complex reusable skill: Claude Code.
The job has to edit real files in a real folder on your machine: Claude Code. This is the whole test.
You want every step the agent takes to be visible: Claude Code, terminal or desktop, your choice.
You avoided Claude Code because of the terminal: that reason is gone. Try the desktop tab before you decide.
You cannot find Cowork and thought you broke something: you did not. Here is where it went.So does a non-coder ever actually need Claude Code?
Honestly? Mostly no, and less so after the merge than before it.
The reason a non-coder used to eye Claude Code was that they wanted the long agentic jobs. Claude does those now, by itself, without you learning anything. That was the main reason, and now it is gone, which is a good thing.
What is left on the other side is real builder work. If your sentence is "I want to build a thing," that is Claude Code. If your sentence is "I want this done," that is Claude.
I am the wrong person to make the terminal sound scary, and also the wrong person to make it sound necessary. I have used it for over a year, so it is just where I am comfortable now.
I have tried living in the app and I bounce off it, which is the opposite of most people's problem. Do not copy my setup. Copy the test: files in a folder, or not.
Where this comes from
The engine and capability facts are Anthropic's pre-merge Cowork docs, read September 5, cited as history now. Merge facts are Anthropic's September 16 announcement and TechCrunch. Plan rows are claude.com/pricing, read September 18. The screenshots are my own machine on those dates.
I run both daily, so the preference is mine. I have not measured usage between the two, and I left that number out on purpose.
If you want somewhere concrete to start today, grab the 15 workday AI prompts at /start: they are built for exactly the kind of tasks you would now hand straight to Claude.
For adjacent decisions: Claude Cowork vs ChatGPT Work for the cross-vendor version, Claude Cowork use cases for what to actually run first, and Claude Cowork scheduled tasks for the recurring-work setup.
Correction log: what this page has said, and when
This page has now had its central rule replaced twice. Both times in public, with the date.July 9, 2026. The thesis was that the fork is clicking versus typing commands. Wrong.
September 5, 2026. Replaced it after Anthropic made Claude Code available in the desktop app, with a screenshot of my own settings window as proof. The new thesis was a three-way rule: Chat answers, Cowork does your office work, Claude Code builds software.
September 18, 2026. Anthropic merged Cowork into Claude on September 16, so the three-way rule lasted eleven days. Replaced with the two-door rule: Claude does the work, Claude Code builds the thing that does the work. Added a dated screenshot showing the merge had not yet reached my paid Max account, updated the comparison table and plan rows, corrected the FAQ wording that treated Cowork as a separate plan inclusion, and pointed the "where did Cowork go" intent at its own page.Not many pages show you their own rule expiring. This one has dated proof on both sides, twice.
Published July 9, 2026. Updated September 18, 2026 for the merge. The correction log above has the dates.
This post is part of Claude Guides, the hub with every plan decision, task comparison, and setup guide for using Claude without code.
Chris Alarcon 
