← AI 101

Intermediate training

Choosing Your Claude Surface

Chat, Cowork, or Code: pick the right Claude surface for any task in thirty seconds, know what each one can and can't reach, and move work between them without losing the thread. The foundation for every Level 3 module that follows.

18 minutes Builds on Level 2 Includes surface workflow walker

Start here

What you'll be able to do after this lesson

Pick a surface in thirty seconds

Match any task in front of you to Chat, Cowork, or Code using a reusable mental algorithm — not a guess.

Know each surface's reach

Understand what files, web access, code execution, and persistent context each surface offers — and what each one cannot do.

Move work between surfaces cleanly

Hand off context from one surface to another without re-explaining the world. Most real work crosses surfaces; the skill is in the handoff.

Three surfaces, three strengths

Same model, different workspaces

Chat

Conversational, fast, no file system access. The right place for thinking, drafting, asking, and exploring — anywhere the work doesn't need to land in a file on your computer.

Cowork

A workspace with access to your folders and the ability to produce real deliverables — .docx, .pptx, .xlsx, .pdf. The right place for any task that produces or modifies a file you'll actually open later.

Code

Developer-grade tool use — terminal, codebase, real test runs. The right place for software development and infrastructure work. Overkill for anything that isn't software.

Trainer note: The surface is the workspace, not the model. The same Claude that brainstorms with you in chat is the one that opens your .pptx in Cowork. The difference is what the workspace lets it do — not how smart it is in there.

Where each surface wins

The tell-tale signals that say "use this one"

Chat wins when…

You're thinking out loud, generating options, asking a quick factual question, or drafting something you'll move to a file later. No attachments yet, no real deliverable.

Quick thinking

Cowork wins when…

A file on your computer is part of the work — to open, to modify, to produce. Decks, memos, spreadsheets, PDFs. Anything you'll save and reuse.

Real files

Code wins when…

The work is software — writing or modifying code, running tests, configuring infrastructure, working in a real repo. Don't use it for anything that isn't development.

Software only

Surface choice

Five rules for picking the right one

Start in chat for any new question

If the task is "what should I do about X" or "help me think through Y," chat is almost always the right opening surface. Promotion to Cowork or Code comes later, if the task grows.

Move to Cowork the moment files enter the work

The instant you find yourself describing a file instead of attaching it, switch surfaces. Cowork is where actual deliverables get produced — chat is where you talked about them.

Stay in chat for thinking and drafting that won't land in a file

Don't open Cowork just because Cowork exists. Quick reality checks, framing conversations, and short drafts live in chat. Speed is a feature.

Use Code only when the task is software

Code is a developer surface — terminal, repo, tests. If the task is "write a memo" or "build a deck," Code is the wrong tool. Cowork covers everything that isn't development.

Don't fight the surface

If the work feels awkward — Claude keeps asking for things it can't see, you're pasting around, the conversation is stalling — you're in the wrong surface. Switch instead of forcing it.

Prompt upgrade

Wrong-surface prompt

Hey can you open my Q3 board deck and rewrite slide 3 to be sharper?

Right-surface prompt

Work-ready prompt

(In Cowork.) Q3-board-deck.pptx is in this folder. Read slide 3 — the revenue summary. Rewrite the three bullets to lead with the number and drop weasel words. Save the file in place. Show me the before/after of just those bullets.

Cross-surface patterns

Four workflows that earn the handoff

Brainstorm → Build

Chat for the outline and options. Cowork for the real deck, memo, or spreadsheet. The chat surfaces the idea; Cowork ships the artifact.

Review → Debrief

Cowork to read a real file and produce a structured critique. Chat to discuss what the critique implies about the underlying brief, writer, or strategy.

Research → Package

Chat for the long-form thinking that lands on a conclusion. Cowork to package the conclusion into the actual deliverable in the actual template.

Brainstorm → Implement

Chat for architecture discussions and trade-off framing. Code for the actual implementation, tests, and infrastructure changes. Don't write code in chat.

Wrong-surface signs

Five signals you're in the wrong workspace

You're describing a file instead of attaching it — the file is on your computer, the conversation isn't You're pasting code into chat that should run in Code (or worse, that needs to run somewhere) You're trying to produce a real deliverable in chat — drafting a paragraph is fine, building a deck is not You're losing context every time you switch surfaces — copy-pasting whole threads is a tell Claude keeps asking for things it can't see in the current surface — that's the surface's answer, not yours

Employee rule: The surface is part of the brief. A perfectly written prompt in the wrong surface produces a worse result than an okay prompt in the right one. Pick the surface first; brief it second.

Map your week to surfaces

Six exercises to build surface fluency

The goal isn't to memorize. It's to feel — within five seconds of seeing a task — where it belongs.

Open the workflow walker in this lesson. Click each of the four workflows and read what carries over between steps. That handoff is the actual skill.
List five tasks from your week and assign each to a surface. Note any you're not sure about — those are the ones to test.
Run the same task in two surfaces. Same brief, same intent. Feel the difference in what works and what stalls.
Build one task that flows cleanly across two surfaces. Brainstorm in chat, build in Cowork. Carry the right amount of context across — not the whole conversation.
Find one task you've been doing in the wrong surface and switch it. The cost of switching once is small; the cost of staying wrong is repeated.
Draft a personal "which surface for what" cheat sheet — six bullets, no more — and share it with one teammate.

Completion standard

You've finished this module when you can name the right surface for any task in five seconds, move work between surfaces without losing the thread, and recognize a wrong-surface signal the moment it shows up.