I was using Claude wrong for six months
I lost ninety minutes per newsletter for half a year. Here is what I missed.
For months, editing one issue of this newsletter took me two hours.
Now it takes about twenty-five minutes.
The fix was not a better prompt or a faster typing speed. The fix was opening the right tool.
Most people are using one Claude. There are three.
If you open Claude in your browser and ask it questions, you are using one Claude.
There are three.
Claude Chat. Claude Cowork. Claude Code.
Each one is built for a different kind of work, and the one you reach for makes more difference than the prompt you write.
What each one is actually for
Claude Chat
This is the one you already know. You open claude.ai, type a question, and get an answer. It works in your browser, on your phone, and in the desktop app, and the conversation syncs across all three.
Chat is for thinking out loud once. A new idea you want to test. A single email you need to draft. A topic you want to understand quickly before a meeting.
When you close the window, the work is gone. That is the point.
Claude Cowork
This is the one most people have not heard of. It only lives in the Claude desktop app, and it is the one that changed how I run my week.
Cowork can see the actual files on your computer. It can open them, edit them, save new ones, and run a task you set on a schedule. Instead of you copying text in and pasting answers out, Cowork works on the files directly.
It also remembers your preferences across sessions, so the second time you ask it to do something, you do not have to re-explain who you are or how you want it done.
Claude Code
This one is for building real things. Web apps. Automations. Integrations. The kind of work that needed a software engineer eighteen months ago and now does not.
You can run Code in your terminal or inside the desktop app. Either way, it is built around how developers work, and if you have ever thought “I would build this if I knew how,” that is the room you have been missing.
All three run the same Claude underneath. They are not different intelligences. They are different capabilities sitting on top of the same model.
How the newsletter editing went from two hours to twenty-five minutes
I write Growsembly every week. For months, I was running drafts through Chat because Cowork did not exist yet.
The workflow was awful. I would copy a paragraph into Chat, ask for the edit, paste the result back into my document, and then catch the things Chat had silently changed that I did not want changed. Eight or nine passes per issue, twenty minutes a pass.
That is two hours of pure shuffle work per issue. The chat usage was so heavy that it forced me onto the Max plan.
When Cowork shipped, I rebuilt the editing process inside it.
Cowork edits the file directly, so the entire copy-paste loop disappeared. I read what changed, keep what I want, push back on what I do not.
Same writing work, about twenty-five minutes per issue. I dropped back to the Pro plan the following month.
The two-question test for picking the right one
You do not need to memorize anything. You need two questions, asked in order, and you stop at the first one that lands you on a tool.
Question one: does the work need to live in a file you will keep using?
If yes, that is Cowork. If no, that is Chat.
Question two: does it need to run on its own when you are not there?
If yes, that is Code. If no, Cowork still works.
Two questions, three tools, and no more guessing about which window to open.
A small experiment if you want to feel the difference
Download the Claude desktop app if you do not have it. Pick a task you actually do every week. Something boring is best.
Ask Chat to do it. Then ask Cowork. Then ask Code.
Pay attention to what clarifying questions each one asks you and what approach each one takes. They will arrive at similar answers, but the way they get there is the part that tells you which one belongs in your week.
What I am taking away
The tool you reach for first becomes the tool you reach for always. That habit calcifies inside a couple of weeks, and after that you stop noticing what it costs you.
I lost about ninety minutes per newsletter for half a year before I noticed.
If you are running the same task in Chat for the fourth time this month, the question is not how to write a better prompt. The question is whether you are in the right window.
See you next time.
— Guney