,

Claude’s Interfaces Explained: Browser, Desktop, and Terminal

What it is: A plain-English map of Claude’s three interfaces (browser, desktop app, terminal) — what each one does, what it can’t do, and how to pick.
Who it’s for: Anyone who’s seen “Claude Desktop,” “Claude Code,” “Cowork,” and “Claude for Chrome” mentioned in the same breath and isn’t sure what’s different.
Best if: You want orientation before you pick a subscription or install anything.
Skip if: You already run all four daily.

Also available as a visual one-pager

Prefer a full-bleed, dark-theme guide you can read in one sitting, print, or share as a link? The visual version lives at beginnersinai.org/claude-guide — same content, standalone design.

Claude is one AI, but Anthropic packages it three very different ways: inside your web browser, as a desktop app, and as a tool in your terminal. The features overlap — but not evenly. This guide explains what’s what, what each one can actually do, and how to pick the right one for the job.

1-on-1 Coaching

Claude AI Crash Course

1-hour private video session with James. Walk through Claude Desktop, Claude Code, Cowork, Skills, Projects, file setups, and plugins. Best for owners who want a coach while rolling out workflows. No technical background required.

$75

1-hour live

Book session →

Group Format

AI Workshops for Teams

Team-format workshops for businesses rolling Claude out to staff. Best for businesses with 3+ people who all need to use the new workflows. Custom-built around your team’s actual tools and goals.

Custom

pricing

Get a quote →

Table of Contents

The whole picture in one paragraph

Claude.ai in the browser is for talking with Claude — asking questions, drafting, brainstorming. The Claude desktop app does all of that plus lets Claude take action on your computer — read your files, open your browser, click through tasks (this mode is called Cowork), and run Claude Code (a dev-mode coding agent) all from a single window. Claude Code in the terminal is the power-user command-line version of that coding agent — same engine, no GUI, built for developers and automation. Pick one based on what you’re trying to do, not on what sounds coolest.

What you’ll find below

  1. The three surfaces at a glance
  2. Feature matrix — what works where
  3. Deep dive — Claude in the browser
  4. Deep dive — Claude Desktop app (Chat + Cowork + Code)
  5. Deep dive — Claude Code in the terminal
  6. Decision tree — which should I open right now?
  7. Overlap & confusion
  8. FAQ — the 10 questions everyone asks
  9. Starting paths — new user, writer, developer
  10. Third-party alternatives

The three surfaces at a glance

Same Claude, three doors. Here’s what’s behind each.

🌐
Browser
claude.ai + “Claude for Chrome” extension
  • Chat with Claude (the main thing)
  • Projects — chat with your own docs
  • Claude for Chrome — clicks websites for you
  • No file access on your computer
Pricing: Free tier, Pro ($20/mo, $17/mo billed annually), Max. Claude for Chrome needs Pro+.
🖥️
Desktop app
Mac & Windows · installs as a regular app
  • Chat (same as the browser chat)
  • Projects (same as browser)
  • Cowork — multi-step work across your computer
  • Claude Code (built in, with a visual interface)
Pricing: Free download; Cowork & Code need Pro or Max.
Terminal
Claude Code CLI · command-line tool
  • Claude Code — a coding & automation agent
  • Works in any terminal (Mac, Linux, Windows WSL)
  • Reads & writes files, runs commands, edits code
  • Built for developers and power users
Pricing: Needs Pro, Max, or API credits. Free trial available.
The single most useful thing to know: the model is the same across all three — same Claude, same intelligence. What changes is what Claude can touch (just words, or also your browser, or also your files) and how you talk to it (chat box, app window, or command line).

Feature matrix — what works where

If you’re deciding which to use for a task, skim this table. ✓ means it’s built in. — means it’s not available.

What you want to doBrowserDesktop appTerminal (Code)
Chat with Claude, ask questionskind ofgeared toward coding
Upload files into a conversationvia drag-drop or file paths
“Projects” — chat with a doc library
Click through websites for youadd-onneeds Claude for Chrome extensionCowork uses your real browserPlaywright spins up a clean browser
Read and edit files on your computerCowork & Code modes
Run commands & scripts
Write and refactor codecopy-pasteyou paste, Claude rewritesCode mode, with file viewits specialty
Run multiple tasks in parallelsplit panesmultiple terminal sessions
Use Claude inside VS Code / Cursor / JetBrainssomedepends on IDEvia IDE extension
Works on mobileiOS & Android apps
Works offlineevery one needs the internet

🌐 Claude in the browser

The original and most common way to use Claude. Two distinct experiences live in the browser.

1. claude.ai — the main chat

Open claude.ai, sign in, type. That’s it. Same conversation model as ChatGPT or Gemini. Best for:

  • Asking questions, research, brainstorming
  • Drafting writing, email, documents
  • Explaining unfamiliar topics
  • Uploading a file (PDF, image, spreadsheet) and asking about it
  • Projects — a workspace where you attach a set of documents and per-project custom instructions (tone, format, rules). Claude follows the instructions and can reference the documents across every chat inside the project.

2. Claude for Chrome — the browser extension

A Chrome extension that puts Claude in a side panel of your browser. The key difference from claude.ai: this Claude can see and act on whatever website you’re currently on — click buttons, fill forms, extract data, summarize pages.

When to use it

  • “Summarize these 5 tabs I have open”
  • “Fill out this form with my details”
  • “Find the pricing on each of these competitor sites”
  • “Book this flight for me” (with your oversight — Claude asks before taking action)

Limitations

  • Only works in Chrome
  • Needs a Pro plan ($20/mo, or $17/mo billed annually) — no free tier
  • Still in research preview; doesn’t work reliably on every site
  • Can’t touch files on your computer — only knows what’s in the browser

Mental model: claude.ai = Claude that talks. Claude for Chrome = Claude that clicks. They’re usually both open at the same time; the extension just adds an action layer over any site.

🖥️ Claude Desktop app

A regular Mac or Windows app you install. The chat is the same as the browser, but underneath it’s a much larger toolbox. Think of it as a container holding three distinct modes.

Mode 1: Chat (same as claude.ai)

If all you ever use is the chat, the desktop app is basically the website in a dedicated window. Useful to keep Claude out of your browser tabs; otherwise identical.

Mode 2: Cowork — the computer-use agent

Cowork is the feature that lets Claude do multi-step work on your actual computer: open your browser, move files, click inside apps, fill in spreadsheets, paste into Google Docs. It’s the most agentic Claude gets today. For a full walk-through, see our Claude Computer Use guide.

Good Cowork jobs

  • “Research the top 10 competitors and put the findings in a new Google Doc”
  • “Go through my downloads folder, rename all the screenshots by their content, file them by month”
  • “Pull my calendar for next week and draft prep notes for every meeting into Notion”
  • “Take this CSV, clean it, and update the spreadsheet I have open”

What to know

  • Officially released, but still maturing — Anthropic recommends watching it the first few times on any unfamiliar task
  • Needs Pro or Max
  • You can pause it any time; it asks before doing anything destructive
  • It runs on your computer — your files, your browser, your permissions. Not a cloud server.

Mode 3: Claude Code (inside the desktop app)

The desktop app also bundles Claude Code — the same coding agent that runs in the terminal — but with a visual interface. File tree on one side, chat in the middle, terminal on the other. Useful for people who want a proper GUI instead of a CLI. For the full setup, see our Claude Code Beginner’s Guide.

Good Code jobs

  • Pair-programming on a project: “add a dark mode toggle to this site”
  • Refactoring: “rename this variable everywhere it’s used”
  • Running and debugging scripts
  • Managing 2-5 Claude sessions side-by-side, each working on a different task

Mental model for the desktop app: one window, three jobs. Chat for talking, Cowork for “go do this across my computer,” Code for programming projects. You pick which mode per task, not per app.

⌘ Claude Code in the terminal

The command-line interface. If you’re not already a developer, this probably isn’t your starting point — but it’s the most powerful version for anyone who lives in a terminal.

What it actually is

You install a small program. You cd into a project folder. You run claude. Claude reads the folder, understands the code, and works with you from there. It can:

  • Read and edit any file in the project
  • Run shell commands (builds, tests, git operations, server starts)
  • Drive a web browser via Playwright (see below)
  • Take multi-step tasks: “refactor auth to use the new library, update the tests, run them, commit”

Also runs outside the terminal now. Claude Code is bundled into the Claude desktop app (launch Claude, click the Code tab), available as a VS Code / JetBrains extension, runs on the web at claude.ai/code, and is part of the Claude iOS app. Same engine under all of them.

Yes — Claude Code can control the browser too

Using Playwright (Microsoft’s free browser-automation library), Claude Code can launch a web browser, navigate to URLs, click, type, fill forms, and scrape the page. It does this in a clean, fresh browser it spins up — not the Chrome you have open on your desktop. Handy for:

  • Scraping data from sites as part of a scripted job
  • Writing automated tests that click through your own web app
  • Building automations you want to save as code and run on a schedule
  • Research-style web tasks where you don’t want your personal browser involved

This is distinct from what Cowork does and from Claude for Chrome. See the comparison in the next section.

Why some people prefer the terminal over the Desktop app

  • Speed. Keyboard-only, no mouse. Faster once you know it.
  • Scripting. You can pipe other commands in and out; run Claude as part of a bigger automation.
  • IDE integration. Hooks into VS Code, Cursor, JetBrains, Vim.
  • Less overhead. Just a terminal process; no app window.
  • SSH / remote servers. Works over a remote connection where a desktop app can’t.

Why some people prefer the Desktop app over the terminal

  • They don’t like typing commands
  • They want to see the file tree, the terminal output, and the chat at once
  • They run several sessions in visual split panes
  • They’re not developers but want coding-style power for other tasks

Important: the engine behind “Claude Code in the terminal” and “Claude Code inside the desktop app” is the same program. Same capabilities, same behavior. The desktop app is a GUI wrapper on top of the same Claude Code CLI.

Decision tree — which should I open right now?

Start at the top. Read downward.

What are you trying to do right now?
Talk / Ask
question, draft, explain, brainstorm
→ Browser: claude.ai
or the Desktop app’s Chat tab
Do work
take action on something — where?
In a browser
click sites, fill forms, scrape pages
→ Claude for Chrome
Across my computer
files, apps, research-to-doc
→ Desktop app · Cowork
Code / Projects
write, refactor, build, ship software
→ Terminal · Claude Code
or Desktop · Code mode

Overlap & confusion — wait, isn’t that the same thing?

A lot of capabilities exist in more than one surface. Here are the ones that trip people up most.

Isn’t the Desktop chat just claude.ai in a window?

Basically, yes — for chat. Same conversations, same history, same Projects. The Desktop app isn’t a new chat product; it’s a container that also includes Cowork and Code. If you’ll never use Cowork or Code, the browser is fine.

What’s the difference between Claude for Chrome and Cowork?

Both let Claude click through websites. Key differences:

  • Claude for Chrome only knows about the browser. It can click sites; it cannot touch your files or desktop apps.
  • Cowork can use your browser and your files and your apps. It’s a superset.

In plain terms: if the job is “click this website for me,” either works. If the job is “research on the web AND save the result to a doc AND email it,” only Cowork can do the whole thing.

Wait — Claude Code can also control the browser? How is that different?

Yes. All three can drive a browser, but they do it in meaningfully different ways. Same end result (a page gets clicked), different mechanics — which changes which one you should actually pick.

Claude for Chrome Cowork (Desktop) Claude Code + Playwright
Which browser is Claude using?The Chrome tab you’re onYour real browserA clean, fresh browser it launches
Does it have your logins / cookies?✓ yes, whatever you’re signed into✓ yesNo — fresh each time (unless you set it up)
Can you watch it happen?Yes, it’s in your tabYes, you see every clickOptional — often runs hidden (headless)
How it “decides” what to doAI reads page, decides each clickAI reads page, decides each clickWrites code that drives the browser
Saves as a reusable script?NoNot really✓ yes — the output is code
Best forQuick one-off actions on the page in front of you“Do this whole task for me” across browser + files + appsRepeatable, scheduled, or scripted web tasks

One-line versions:

  • Claude for Chrome = “look over my shoulder and click on the tab I’m on”
  • Cowork = “sit at my computer and click through my real browser, like a human assistant”
  • Claude Code + Playwright = “write the code that drives a clean browser, so I can run this web task again anytime”

The trade-off, in plain English: the first two are personal — they use your session, your logins, your context. They’re great for errands. The third is reproducible — it’s a clean, scriptable automation. Pick on that axis: “one-time personal” vs. “repeat / script-worthy.”

Claude Code in the terminal vs. Claude Code in the Desktop — which is better?

Same underlying tool, different presentation. Terminal if you prefer keyboard, speed, and scripting. Desktop GUI if you prefer a file tree, split panes, and visible clicks. The output and capabilities are identical.

Do I pay separately for each?

No. One Claude subscription (Free, Pro, or Max) covers all three surfaces. You sign in on each; usage counts against the same plan. The free tier on the browser gives you basic chat; Cowork, Code, and Claude for Chrome need Pro at minimum.

Is the AI model actually the same?

Yes. The brain is the same Claude model. What differs is what that brain is allowed to touch in each interface — just words (browser chat), or also your computer (Desktop Cowork), or also your code (Code mode / terminal). The intelligence does not change across surfaces. For a deeper comparison of the model itself against competitors, see our Claude vs ChatGPT and Claude AI Review.

FAQ — the 10 questions everyone asks

Do I need all three?

No. Most people use one or two. Writers and students typically stay in the browser. Anyone who wants Claude to “go do something for me” will eventually install the Desktop app. Developers often live in the terminal. It’s fine to pick one and ignore the others.

Is the Free plan enough to try Claude?

Yes — the free tier on claude.ai gives you enough chat to form an opinion. It doesn’t include Cowork, Code, or Claude for Chrome, but for “is Claude worth paying for?” it’s plenty.

What’s the cheapest path to Cowork?

Claude Pro at $20/month (or $17/month billed annually) includes Cowork. You also get Claude for Chrome and Claude Code on the same plan. One subscription, everything unlocks.

Can Claude Code read my whole computer?

Only what you give it access to. You typically run it from a project folder; Claude works within that folder and any paths you mention. It doesn’t crawl your whole drive on its own. Cowork is similar — it asks before doing something outside the immediate task.

Does my data get sent to Anthropic?

Yes — every one of these surfaces sends your prompts and any files to Anthropic’s servers so Claude can respond. Anthropic’s privacy policy covers how that data is handled (they don’t train on consumer chat data by default on paid plans). If you need local-only AI, look at tools like Ollama; Claude itself always runs in the cloud.

Can I use Claude offline?

No. All three surfaces need an internet connection to reach Claude’s servers. The desktop app and terminal tool run on your computer, but the AI brain is still remote.

I use Cursor / Copilot / another coding AI. Do I still need Claude Code?

Not necessarily. Cursor and other IDEs often let you pick Claude as the model underneath — in which case you’re using the same brain through a different interface. Claude Code is most distinctive when you want a terminal-first workflow or when you want Claude to run commands and do multi-step project work, not just suggest edits.

What about claude.ai on mobile?

There are official iOS and Android apps of claude.ai. They’re effectively the browser chat in a mobile wrapper — you get chat, Projects, and file uploads. You don’t get Cowork, Code, or the Chrome extension on mobile.

How do I install the Desktop app?

Download it from claude.ai/download. It’s a normal installer for Mac or Windows. Sign in with the same account you use on claude.ai. Your chat history and Projects sync automatically.

How do I install Claude Code in the terminal?

See claude.com/claude-code. Typical install is one command; then you run claude inside any project folder. First launch walks you through signing in. For a full walkthrough, see our Claude Code Beginner’s Guide.

Starting paths — three typical users

If you don’t know where to start, pick the profile that sounds most like you and follow that list.

New to Claude entirely

  1. Open claude.ai in your browser. Sign up for free.
  2. Have 5 real conversations with it. Ask the things you’d normally Google.
  3. If you like it, upgrade to Pro.
  4. Only then install the Desktop app — and only if you want Cowork or Code.
  5. Skip the terminal unless you’re a developer.

Writer / researcher / creator

  1. Start with claude.ai in the browser. Use Projects to drop in your research notes.
  2. Add Claude for Chrome for “summarize these open tabs” and research-gathering.
  3. Install the Desktop app when you want Cowork to actually write files and organize folders on your machine.
  4. Terminal only if you’re comfortable there.

Developer / power user

  1. Install Claude Code in the terminal. Run it inside a project folder.
  2. Hook Claude Code into your editor (VS Code, Cursor, JetBrains extension).
  3. Install the Desktop app as a second home — use its split panes to run parallel Claude Code sessions visually.
  4. Use claude.ai in the browser only for quick chat when you’re away from your dev setup.

A quick word on third-party alternatives

Not every Claude-like interface comes from Anthropic. If you want more control, different pricing, or to swap in a different AI model, here are the main categories people turn to. Most of these are listed in the full AI Tools Directory.

  • Browser-agent alternatives to Claude for Chrome: BrowserOS, BrowserBee, Tabstack. Free, open source, you run them. Use whichever AI model you want underneath (including Claude).
  • Terminal alternatives to Claude Code: Goose (by Block), MyCoder. Same idea, open source, multi-model.
  • Desktop alternatives to Cowork + Code: Memex, AnythingLLM. Run locally, point at any AI model.
  • “AI team” or “AI employees”: Paperclip, Cabinet, Rowboat. Hire several AI agents with different roles reporting to you. Claude is usually the brain underneath.
  • Running the AI locally (no cloud at all): Ollama. Replaces the remote Claude call with a model running on your own machine. Not as capable as Claude, but free and private.

A key point: most third-party tools can use Claude underneath if you already pay Anthropic. They give you a different package (team of agents, local browser, multi-model terminal) around the same Claude brain.

Related reading

Glossary — plain-English definitions

One sentence each, in the context of Claude.

  • Claude — The AI model made by Anthropic. Same underlying intelligence whether you reach it through a browser, desktop app, or terminal.
  • claude.ai — The website where the original chat with Claude happens. Runs in any web browser.
  • Claude for Chrome — A Chrome browser extension that lets Claude read and click the website you’re currently on.
  • Claude Desktop (app) — A Mac/Windows app containing chat, Projects, Cowork, and Claude Code in one window.
  • Cowork — A mode in the Desktop app where Claude takes multi-step action across your browser, files, and apps.
  • Claude Code — A coding & automation agent from Anthropic. Runs in the terminal and also inside the Desktop app.
  • Projects — A workspace inside Claude where you attach documents that every chat inside that workspace can reference.
  • Agent / agentic — AI that takes action (clicks, edits, runs commands), not just an AI that answers questions.
  • CLI — Command-Line Interface. A text-based way to use a program, in a terminal window.
  • GUI — Graphical User Interface. A program with buttons, windows, and menus. The normal kind of app.
  • Pro / Max — Paid Claude plans. Pro is $20/month ($17/month billed annually); Max is the higher tier.
  • Research preview — A feature that works but hasn’t been fully released. Expect rough edges.
  • API / API credits — A way to use Claude by having software call it directly. Pay per use.
  • Playwright — A free tool for automating web browsers. Claude Code uses it internally for clean browser tasks.

Want the short version of this kind of explainer in your inbox?

Join the Beginners in AI daily newsletter — one plain-English AI brief, short enough to read over coffee. Or jump into the community to ask questions and see what other beginners are building.

🚀 1-on-1 Claude AI Crash Course — $75. New to Claude? Get a personal 1-hour video call walkthrough of the Claude ecosystem from James — covers what to use, when to use it, and how to be productive on day one. View on Beehiiv →

Get Smarter About AI Every Morning

Free daily newsletter — one story, one tool, one tip. Plain English, no jargon.

Free forever. Unsubscribe anytime.

You May Also Like

Discover more from Beginners in AI

Subscribe now to keep reading and get access to the full archive.

Continue reading