Guide: Platforms and Modes

Claude Cowork · Feature primer

Overview

Claude runs in several places and in several modes. They are not interchangeable — each has different capabilities, different limits, and different use cases. Understanding which surface to reach for saves a lot of frustration.

The short version for this recipe library: almost everything here runs in Claude Desktop → Cowork mode. The other surfaces are useful to know, but Cowork on the desktop is where the work happens.

The Surfaces — Where Claude Lives

Browser (claude.ai)

Access Claude from any web browser without installing anything.

What it’s good for:

• Quick questions and conversations
• Writing, editing, and brainstorming
• Research and analysis
• Uploading individual files for Claude to read
• Projects (persistent context across conversations)
• Remote connectors (Google Drive, etc.) — these work in the browser once connected

What it can’t do:

• Access files on your computer directly
• Run Cowork tasks
• Execute scheduled automation
• Use local plugins or local MCPs (desktop-only connectors)

When to use it: Anything that doesn’t require touching your local files or running a multi-step task. The browser is Claude’s most accessible surface — great for one-off tasks, drafting, and conversations.

Desktop App — Chat Mode

The Claude Desktop app installed on macOS or Windows, in standard chat mode.

What it adds over the browser:

• Local plugins and desktop-only connectors (MCPs that run on your machine)
• Tighter integration with your computer

What it still can’t do:

• Access your file system directly
• Run Cowork tasks
• Schedule automation

When to use it: When you need a local connector or plugin that isn’t available in the browser, but the task is still conversational rather than agentic.

Desktop App — Cowork Mode

The same desktop app, switched to Cowork. This is a fundamentally different mode — Claude shifts from responding to executing.

What Cowork adds:

• Full access to your local file system (folders you connect)
• Multi-step agentic task execution — Claude plans, acts, and delivers a finished result
• Scheduled tasks — set recurring automation that runs automatically
• Projects with folder connections — persistent workspaces with live file access
• Sub-agent coordination — Claude can break complex work into parallel workstreams
• Computer use — Claude can see and control your screen (research preview, Pro/Max)
• Plugins with connectors — bundles of skills and integrations that extend what Claude can do

The tradeoffs:

• Uses your usage allocation faster than Chat — complex tasks are compute-intensive
• The desktop app must stay open while Claude is working
• Your computer must be awake for scheduled tasks to run

When to use it: Any time you need Claude to work with your files, run a multi-step workflow, or automate something on a schedule. This is the primary mode for all recipes in this library.

Desktop App — Code Mode (Claude Code)

A developer-focused mode for software engineering work. Available from the desktop app or directly from the terminal as a command-line tool.

What it’s for:

• Writing, editing, and reviewing code
• Running tests, managing git, navigating codebases
• Building and debugging software

When to use it: If you’re a developer building software. Not the primary surface for the business workflows in this recipe library — but worth knowing it exists if you ever want to build or customize Claude tooling yourself.

Mobile App (iOS and Android)

Claude on your phone.

What it’s good for:

• Quick questions and conversations anywhere
• Voice input
• Remote task dispatch (Pro and Max): send a task to Claude from your phone and it runs on your desktop in Cowork mode — your phone is a remote control for your desktop’s resources

What it can’t do:

• Access local files directly
• Run Cowork tasks independently
• Use local connectors or plugins

The remote dispatch caveat: For mobile task dispatch to work, your desktop must be on, awake, and have the Claude Desktop app open. Claude works on your desktop; you just don’t have to be sitting in front of it.

When to use it: On-the-go access for conversations and quick tasks. For Cowork workflows, use it to kick off or check on tasks running on your desktop.

Claude in Chrome

A browser extension that puts Claude in a side panel while you browse the web.

What it’s for:

• Getting help with what’s on screen — summarizing pages, drafting emails, answering questions in context
• Having Claude navigate and interact with websites on your behalf
• Research while staying in the browser

What it’s not: A replacement for Cowork. Claude in Chrome is a browsing companion, not a task automation tool.

Modes at a Glance

The Decision: What to Reach For

“I have a question or need something written” → Browser or Desktop Chat. Fast, no setup, works anywhere.

“I need Claude to read or create files on my computer” → Desktop Cowork. Only Cowork has local file system access.

“I want this to run automatically every day/week” → Desktop Cowork. Scheduled tasks only exist in Cowork.

“I’m away from my desk and want a task done” → Mobile (dispatches to Desktop Cowork). Your desktop must be on and open.

“I’m building software” → Desktop Code / Claude Code CLI.

“I need help with something I’m looking at in the browser” → Claude in Chrome.

For These Recipes

Every recipe in this library assumes Claude Desktop → Cowork mode. That’s where file access, Projects with folder connections, scheduled automation, and plugins all live together.

If you’re using the browser or mobile, you can still follow the prompting guidance in each recipe — but you’ll be uploading files manually rather than connecting a folder, and you won’t be able to schedule anything to run automatically.

See also: Subscriptions guide for which plan unlocks Cowork.