Chat vs Co-work vs Code

    Most people use one mode of Claude. There are three. Here's what each one actually does.

    Chat, Co-work, or Code:
    Which mode does what

    Three modes. One is a food court. One is your kitchen. One is your whole restaurant. By the end of this guide you'll know exactly which one to use and when.

    Ask

    Chat

    Do

    Co-work

    Build

    Code

    Insight 01

    Three Modes. One Cooking Show. One Kitchen. One Restaurant.

    Most people only watch the cooking show. That's where 90% of Claude's power stays untouched.

    Most people only watch the cooking show. They ask Claude questions and copy answers into their own tools. That's 10% of what Claude does.

    Cooking Show

    Chat

    You watch the chef on TV. They walk you through every step. You head to your own kitchen to cook it yourself.

    The chef talks. You do the work. Great for questions, research, and brainstorming.

    Your Kitchen

    Co-work

    The chef comes to your kitchen. Opens your fridge, cooks, plates it up. You watch.

    Claude does the task. Inside a safe sandbox. Great for documents, scheduled work, connectors.

    The Restaurant

    Code

    You hand over the keys. They run the whole place. Multiple kitchens. Multiple chefs.

    Full access, multi-agent workflows, persistent memory. Great for complex systems and projects.

    Hover a panel to go deeper. Each mode has its own job.

    Insight 02

    Chat: The Cooking Show

    Fast answers, cross-session memory, works with what you upload. Great for thinking. Limited for shipping.

    You
    Claude

    Quick questions with clear answers

    Ask anything. Get a concise answer. No setup, no files touched.

    Brainstorming and thinking aloud

    Use it as a thinking partner. Push an idea around until the shape is right.

    Research and summaries

    Pull together context on a topic. Ask follow-up questions without losing the thread.

    Getting advice before you decide

    Pressure-test a plan before you commit time and money to it.

    Superpower

    Remembers every conversation you've ever had

    Your name, your role, your clients, your preferences. Walk back in six months and it already knows you.

    Risk

    Cross-chat memory can leak across clients

    Information from Client A could quietly influence responses about Client B. Use Code or Co-work for anything sensitive.

    Insight 03

    Co-work: The Chef In Your Kitchen

    Claude does the task inside a safe sandbox. Connect your apps and step away.

    How a Co-work session flows

    01

    You ask

    "Draft my weekly client report from these 4 calls."

    02

    Claude plans

    Opens connectors, pulls transcripts, drafts the report.

    03

    You review

    Pop in, give feedback, pop out. Claude finishes.

    04

    Delivered

    Doc saved to Drive, shareable link ready.

    The Sandbox

    Safe by default. Limited by design.

    The chef works in a safe zone. They can't accidentally break anything outside the boundaries. Good for safety. Means less flexibility than Code.

    The Automatic Car

    Easier to drive. Worse fuel economy.

    Co-work uses more tokens than Code because extra orchestration runs under the hood. Fine for short tasks. Expensive at scale.

    Scheduled work

    Co-work can run on a schedule. Weekly client report every Monday. Daily LinkedIn summary. Monthly pipeline review. Set it once, it runs forever.

    Connectors you can plug in

    Google DriveGmailCalendarSlackNotionGHLDropboxGitHubAsana

    Enjoying the guide?

    Enter your details to unlock the remaining insights. We'll also send you the complete guide as a reference.

    No spam. Unsubscribe anytime.

    Insight 04

    Code: The Chef Runs The Whole Restaurant

    Full access, multi-agent workflows, persistent briefing. The most power at the best token economics.

    claude
    
    

    The Manual Car

    Harder to learn. Better fuel economy.

    Code uses tokens efficiently once configured. Best choice at scale. Not for day-one users.

    Multi-agent workflows

    Five agents for the price of one.

    Sub-agents share the prompt cache. Run research, drafting, and review in parallel without paying five times.

    IDE stack

    Where should Claude Code actually live?

    Not sure? Start with the Desktop App. Move to Antigravity if you live in Google.

    Insight 05

    The Live Scenario Switcher

    Pick a real task. See how each mode handles it side-by-side.

    Pick a real task. See how each mode handles it side-by-side.

    ChatThinking
    Best fit

    Perfect fit. Fast, conversational, no setup.

    Talks through angles, pushes back, suggests pricing ladders.

    Co-workThinking
    Overkill

    Works but slow. No real benefit over Chat.

    Would open a doc you don't need yet.

    CodeThinking
    Overkill

    Way too much machinery for a thinking session.

    Spins up a project you'll never use.

    Best fit is highlighted with a gradient border. Try every scenario. The pattern becomes obvious fast.

    Insight 06

    The Memory Difference Is The Whole Game

    Chat remembers every chat. Code and Co-work start fresh. One is a feature. The other is a risk.

    Chat

    Remembers everything across every chat

    Your name, role, clients, preferences. Walk back in six months, it already knows you.

    Client A project notes (Jan)
    Your pricing preferences (Feb)
    Client B strategy call (Mar)
    Your offer positioning (Apr)

    Risk: Client A context could leak into Client B answers.

    Co-work & Code

    Starts fresh every session

    Knows nothing about you by default. Sounds annoying. Is actually a feature for client work.

    [ clean desk on every session ]

    Feature: Client A can never leak into Client B.

    The fix for Code: CLAUDE.md

    A plain text file that lives in your project folder. Tells Claude who you are, what the project is about, where important files live, and how you like to work. Get it right and Claude walks into every session already briefed.

    CLAUDE.md

    Insight 07

    MCPs: The Power Adaptor For Your Tools

    Claude plugs into almost anything. The mode decides how much control you get over the plug.

    The power adaptor

    Your phone works in Australia. Europe needs an adaptor. An MCP is that adaptor.

    You don't need to remember the acronym. Just know that Claude can plug into your tools. Chat has built-ins. Co-work adds more. Code gives you full control over what's connected and how.

    Capability
    Chat
    Co-work
    Code
    Built-in connectors
    Some
    Most
    All
    Custom connectors
    Yes
    Yes
    Build your own MCP server
    Partial
    Yes
    Full control over what's connected
    Partial
    Yes

    Popular tools you can plug in

    GoHighLevelNotionGoogle DriveGmailCalendarLinearSlackStripeHubSpotAirtableSupabaseGitHub

    Insight 08

    The Full Comparison

    Every dimension that actually matters, side-by-side. Tap a row to go deeper.

    Click any row to expand the detail.

    Insight 09

    When To Use What

    Three job stories. One mode per job. Pick the statement that sounds like you.

    Pick the statement that sounds like you. The mode picks itself.

    I want to ask a question or think something through

    Chat

    I want Claude to actually do the task for me

    Co-work

    I'm running a system, a complex project, or a business on it

    Code

    ChatChatanswersanswersquestions.questions.Co-workCo-workdoesdoesthethetask.task.CodeCoderunsrunsthethewholewholeoperation.operation.PickPickthethemodemodethatthatmatchesmatchesthethejobjobandandstopstopusingusingClaudeClaudeatattentenpercentpercentofofitsitsrange.range.

    Chat

    Ask it anything. It talks, you do.

    Co-work

    Tell it what to do. It works while you step away.

    Code

    Build with it. You and Claude run the whole show.