Claude Cowork + Claude in Chrome: AI That Works Alongside You

What This Section Is About

There are two ways to use AI. The first is switching to it: you open a chat window, ask something, copy the answer back into your actual work. The second is working with it: the AI operates inside your environment, seeing what you see, acting on files you already have, automating things you'd otherwise do manually.

Claude Cowork and Claude in Chrome are Anthropic's bet on the second model. Cowork handles your file system and documents. Chrome handles your browser. Neither is a chat interface you switch between tasks to reach. They work in the environment where your work already lives.

Most people still treat AI as a lookup tool: ask a question, get an answer, move on. These tools change that relationship. Claude handles tasks, not just questions. This is what "agentic AI" actually means in practice, stripped of the hype.

What you'll know after reading this:

• What Cowork does, how it works architecturally, and whether it's relevant to your work
• What Claude in Chrome does and how it differs from a browser sidebar
• When to reach for each tool and when to skip them entirely
• What the real limitations are (the marketing does not tell you)
• How these tools work together as part of a broader ambient-Claude workflow

Who this is for: People with repetitive file, document, or browser-based workflows who are on a paid Claude plan. If you mostly need help writing emails or answering questions, regular Claude chat already serves you well. These tools are for people with batch work, repetitive document operations, or web-based tasks they want to stop doing manually.

Claude Cowork: The Office Agent

What Cowork Actually Is

The honest one-line description: Cowork is Claude Code for non-developers. It gives Claude the ability to autonomously operate on files and applications on your computer, without requiring you to use a terminal or write code.

The backstory worth knowing: when Anthropic launched Claude Code in 2024 for developers, users immediately started using it for non-development tasks — organizing files, writing reports, batch-converting documents. Anthropic noticed. Cowork is the response: the same underlying capability, wrapped in an interface anyone can use.

Simon Willison, one of the most credible technical observers in the AI industry, put it clearly at launch: he'd been saying for a while that Claude Code was really a general agent in developer clothing. Cowork was the first AI assistant explicitly positioned as a coworker, not a tool.

The visual setup: Cowork lives in the Claude Desktop app as a third tab alongside Chat and Claude Code. You point it at a folder. You give it tasks in plain language. Claude plans, executes, and reports back.

Key architectural point: Cowork runs inside a sandboxed Linux virtual machine. This is different from Claude Code, which operates directly in your terminal. The sandbox is both a safety feature (Claude cannot roam your filesystem without your permission) and a constraint (you have to explicitly grant folder access, and Claude cannot see your entire computer by default). For a deeper look at the agentic AI shift this represents, see The New Wave of Agentic AI.

The Cowork Workflow

Here is what using Cowork actually looks like, step by step:

1. Setup

Install Claude Desktop (macOS or Windows 10/11 x64). Open the Cowork tab. Click "New task." Grant folder access by pointing Cowork at a working directory. That's it.

2. The task and plan loop

Cowork shows you a visible to-do list of every step it intends to take before it starts. You can review the plan and adjust before execution begins. As it works, steps get checked off in real time. You are watching the reasoning, not waiting for a black-box result.

This separation matters. You are not sending a request into a void. You see the work happening, and you can intervene if anything looks off before it's done.

3. Skills

Cowork has built-in "skills" — reusable instruction sets that load automatically when relevant. Say "create a Word doc" and it loads the docx skill. Say "make a presentation" and it loads pptx. Built-in skills cover: pdf, docx, pptx, xlsx, canvas-design, and more. You can also create custom skills by recording a workflow once and saving it.

4. Scheduled tasks

As of February 25, 2026, Cowork supports scheduled recurring tasks. Write a prompt once, set a cadence (hourly, daily, weekly, weekdays only, on-demand), and Cowork runs it automatically whenever your computer is on and the desktop app is open. Morning briefings, weekly report generation, recurring data pulls: these run without you touching anything.

One caveat worth knowing: scheduled tasks only run when your computer is awake and the app is open. This is not a cloud service that runs while you sleep unless your machine is also running.

5. Persistent agent thread

As of March 17, 2026, Cowork has a persistent agent thread accessible from both Claude Desktop and the Claude mobile apps (iOS and Android). This lets you assign tasks, check progress, and manage ongoing work from your phone without sitting at your computer. The thread rolled out to Max plan subscribers first, then Pro over two days.

What Cowork Is Actually Good At

Generic categories are useless here. Specifics are what tell you whether this applies to your work.

Document and file workflows:

• "Take the 40 PDFs in my client-reports folder, extract the summary section from each, and create a single master doc organized by client name"
• "Go through my Downloads folder, figure out what everything is, and sort it into subfolders by type and project"
• "Take this folder of expense screenshots, pull out the amounts and vendors, and put them in a spreadsheet"

Report generation:

• "Pull data from these three weekly spreadsheets and create a standardized monthly summary in our usual format"
• "Generate a Friday status update from the notes files in this project folder"

Office document work:

• Cross-app workflows between Excel and PowerPoint (added in the February 2026 enterprise update)
• Document formatting standardization across a folder of files
• Batch find-and-replace or reformatting across multiple documents

What doesn't work well:

• Complex, nested spreadsheets where the structure is non-obvious
• Tasks that require judgment calls Claude can't make without more context
• Anything requiring multi-device sync (Cowork is desktop-only)

Who Cowork Is For

Cowork earns its subscription cost if you:

• Deal regularly with batches of files — 20, 50, 100+ documents at once
• Have repetitive document workflows that follow a consistent pattern every week or month
• Spend meaningful time on tasks like: organizing downloads, extracting data from PDFs, converting file formats, generating reports from existing data
• Want to offload administrative work without learning to write scripts or automations

Cowork is probably not worth your time if you:

• Mostly do one-off writing or analysis tasks
• Rarely work with files in bulk
• Are already comfortable using scripts, macros, or tools like Zapier for automation
• Need something that works without the Desktop app open

The honest usage picture: reviewers who tested Cowork extensively report saving 6-8 hours per week on document management across small teams. That is a real number, but it requires having the right kinds of tasks: repetitive, file-based, batch-oriented work. If your work doesn't fit that pattern, you will spend more time setting up tasks than they save.

Availability and Pricing Reality

Current status (as of April 2026): Cowork is generally available on all paid Claude plans, having exited research preview on April 9, 2026.

• Pro: $20/month (or $17/month billed annually)
• Max: $100-200/month
• Team and Enterprise: available in research preview

Free plan users cannot access Cowork.

The token consumption problem: This is the limitation the marketing glosses over. Cowork burns through your usage quota much faster than regular chat. Every step Claude takes — reading a file, writing a file, taking a screenshot, running a verification — consumes tokens. A single moderately complex task can consume the equivalent of 50-100 chat messages worth of quota.

On the Pro plan, heavy Cowork use will hit limits within a few serious tasks per day. If you are planning to use Cowork as a core part of your daily workflow, be honest with yourself about whether Pro's limits are sufficient, or whether you need a Max plan.

Platform requirements:

• macOS: full support
• Windows: launched February 11, 2026 (Windows 10 v1909+ or Windows 11, x64 only — no ARM64 support yet)
• Web, mobile, Linux: not supported

Still in research preview: No cross-device sync. Memory does not persist between sessions (each session starts fresh). Projects, artifact sharing, and memory features from regular Claude are not available in Cowork.

Cowork vs. Claude Code: Clearing Up the Confusion

People who have heard of both get confused about the difference. Here it is clearly:

If you're a developer: You will likely use both. Claude Code for programming work, Cowork for the documentation, reports, and administrative tasks around your projects. They complement rather than compete.

If you're not a developer: Cowork gives you the same "hand off a task and come back" experience as Claude Code, without requiring you to touch a terminal. This is the right entry point.

One important caveat: Cowork is less powerful than Claude Code for complex, multi-step tasks. Claude Code gives you precise control over context. Cowork abstracts that away, which makes it easier to start but harder to fine-tune for demanding work.

Computer Use and Dispatch

As of March 23, 2026, Cowork supports computer use on Pro and Max plans (currently in research preview). Claude can open files, run dev tools, point and click, navigate the screen, and complete tasks that previously required you to be sitting at your desk.