Claude's Chat, Cowork and Code: Cowork Merged Into Chat — How to Use Each Now

Claude had three separate entrances for a long time: Chat, Cowork, and Code. On September 16, 2026, two of them — Chat and Cowork — were merged into one. You no longer have to decide which one to work in, and everything Cowork could do is now available from any conversation.

Does that mean it is all the same thing now? Not quite. The Claude app and Claude Code, which runs in your terminal, are still separate. And even inside the app, there is a clear split between asking on the spot and handing off a job and letting it run.

In this article, I'll lay out what Claude looks like after the merge, and where you should do what. So that anyone who learned the name "Cowork" isn't left guessing, it also includes a map of where the old Cowork features went.

The Big Picture — What's Left After the Merge

Let's start with the big picture. After the merge, Claude has two entrances.

• The Claude app (web, desktop, mobile): there is one conversation, and that's it. Getting an answer on the spot and handing off a substantial job both happen in that same conversation
• Claude Code: the developer tool that runs in your terminal. This one was not merged

So the choice is no longer "which tab" but simply "the app, or Claude Code." Inside the app, you just say whether you want an answer or a finished piece of work, and Claude picks the way it needs to work.

Landing alongside the merge were three creation features in beta: Claude Docs, Claude Slides, and Claude Design. These can also be called up from any conversation, and the results hand off as a single shared link. Slides export to PowerPoint and PDF.

Let's dig into each one.

Asking on the Spot — Claude as a Conversation Partner

This is the most straightforward feature. It works just like ChatGPT or Gemini — you ask, it answers.

What You Can Do

• Get answers to questions (research, brainstorming, translation, etc.)
• Draft, edit, and summarize text
• Analyze images and PDFs
• Generate and review code
• Have in-depth, extended discussions

When Chatting Shines

Chatting is perfect for those "I have a quick question" or "let me bounce some ideas around" moments. It's ideal when you want to develop your thinking through back-and-forth dialogue.

For example, it's great for open-ended questions like "What do you think about the direction of this proposal?" — the kind where there's no single right answer.

Things to Keep in Mind

Chatting isn't well-suited for processing large batches of files or handling tasks that take a long time to complete. Since it's fundamentally based on a conversational back-and-forth, you need to be at your screen to keep things moving.

Handing Off the Run — Where the Old Cowork Way of Working Went

Cowork launched in 2025 as the first tab to give shape to a way of working where Claude moves the job forward on its own. On September 16, 2026 it was merged into Chat and stopped being a separate tab — but the way of working itself did not go away. The same thing now happens from any conversation.

From here on, read "what you used to do in Cowork" as "how you ask for it after the merge."

The Key Difference from Chatting

While chatting works on a "one question, one answer" basis, Cowork lets Claude work autonomously on tasks for you.

Here's what a typical workflow looks like.

1. Tell Claude what you need done
2. Claude starts working on it in the background
3. It only checks in with you when it needs a decision
4. Once finished, it presents the deliverable

In other words, you can hand off work to Claude and focus on something else in the meantime.

When Cowork Shines

• Research tasks ("Look into X and put together a summary")
• Document creation ("Turn these specs into a design document")
• Data analysis ("Analyze this CSV and report on the trends")
• Any substantial task you want to delegate from start to finish

Things to Keep in Mind

Because Cowork operates autonomously, it can sometimes head in a direction you didn't intend. The key is to be specific with your initial instructions and check in on progress from time to time.

Claude Code — A CLI Tool Built for Development

Claude Code is a tool built specifically for software developers. It looks and feels completely different from a typical chat interface.

How It Fundamentally Differs from the App

While the app runs in your browser and on your desktop, Claude Code operates in the terminal (command line). And its standout feature is the ability to directly read and write actual files.

That means if you say "fix this bug," Claude will read through your repository, locate the problem, apply the fix, and even run the tests — all on its own.

What You Can Do with Claude Code

• Develop with full awareness of your existing codebase
• Investigate and fix bugs
• Implement new features
• Write and run tests
• Refactor code
• Handle Git operations (commits, pull requests, etc.)

When Claude Code Shines

For anyone doing serious software development, this is hands down the most powerful option. Especially when you want to add to or modify an existing project, it's far more efficient than copying and pasting code snippets back and forth in the app.

Things to Keep in Mind

If you're not used to working in a terminal, it might feel a bit intimidating at first. That said, you can give instructions in plain language, so you rarely need to memorize any commands.

Comparison Table — Where to Do What

The merge removed the need to pick between Chat and Cowork. What you pick now is the app or Claude Code. Inside the app, though, asking on the spot and handing off a run still behave differently, so the table splits them into three columns. The two left-hand columns are the same place — the only difference is how you ask.

Where the Old Cowork Features Went

Here is where the things you knew by their Cowork names live after the merge.

Recommended Use Cases by Scenario

For Business Professionals

After the merge, the app on its own covers it. What you switch between is no longer a tool but the way you ask.

Keep it short for quick questions and brainstorming. For bigger tasks like "Summarize the action items from these meeting notes," state the goal and hand it off. Because the switch happens inside the same conversation, the whole question of where to do it largely disappears. For more on the importance of mastering AI, check out our article on jobs at risk from AI and how to stay ahead.

For Engineers

When you're actively developing, Claude Code is the clear winner. It understands your entire codebase before making changes, which is worlds apart from pasting code fragments back and forth in the app.

That said, the app is still the better choice for discussing architecture decisions or hashing out design approaches. It's easier to organize your thoughts through real-time dialogue.

For Students and Beginners

Start by simply asking questions in the app. The interface is simple and there's something reassuring about being able to ask anything. Once you're comfortable, try handing over a slightly bigger task like "Draft an outline for my essay" — that's when you'll start to see what Claude is really capable of. There's no separate place to switch to.

Tips for Getting the Most Out of Claude

1. Decide Up Front: Ask, or Hand Off?

This is the single most important habit. You no longer have to pick a tab, but you do have to decide how to ask. If all you want is an answer, keep it short; if you want a finished piece of work, state the goal and the format and hand it off. Simply staying conscious of that switch changes the quality of what comes back.

2. When You Hand Off, Give a Clear End Goal

Vague instructions like "put something nice together" tend to produce disappointing results. Be specific about what you want: "Compare these from three angles in a table format, and include one recommendation at the end." The clearer your vision for the deliverable, the better the result.

3. Use CLAUDE.md with Claude Code

If you place a file called CLAUDE.md in your project root, Claude will understand your project's context before it starts working. Write down rules like "This project uses TypeScript" or "Tests are written in Jest" — it makes a remarkable difference in accuracy.

Conclusion

With the merge of September 16, 2026, Claude now has two entrances.

• The Claude app: quick questions and substantial jobs you hand off both live in the same conversation. The old Cowork way of working was absorbed here
• Claude Code: for serious software development work. This one stays separate

There's less to remember, not more. The one judgment left is "ask, or hand off?" — keep it short when you want an answer, state the goal and hand it off when you want a finished piece of work. Staying conscious of just that will change how you work with Claude.

Frequently Asked Questions