What is Claude Cowork? A plain-English guide

I run parts of my weekly builds in Cowork, and JotThread works inside it, so this explainer comes from daily use rather than a press release. Cowork also changes fast; everything here was checked against Anthropic's current materials before publishing, and the FAQ flags the details most likely to have moved by the time you read this.

What exactly is Cowork?

Open the Claude Desktop app and you'll find tabs: Chat, Cowork, and Code. Cowork is the middle one, and the mental model is a working session rather than a conversation. You point Claude at one or more folders, give it a goal in plain language, and it makes a plan, works through the steps, and reports as it goes. The output is real files in your real folders: a finished document, an organized directory, a spreadsheet built from a pile of screenshots. Anthropic's own examples are usefully unglamorous, like turning a folder of receipt photos into an expense report, and that's the right expectation to arrive with.

How is it different from regular Claude chat?

Access and autonomy. In chat, Claude sees what you paste or attach and hands text back; every file operation routes through you. In Cowork, Claude has permission to read, edit, and create files in the folders you've granted, and it carries multi-step tasks from start to finish instead of waiting for a prompt per step. The trade is supervision style: chat is turn-by-turn, Cowork is "here's the goal, show me the plan, go," with checkpoints where you steer. It's the difference between a very good advisor and a very good assistant.

How is it different from Claude Code?

Same family, different audience. Cowork is built on the agent foundations of Claude Code, which developers have used for years to build and debug software from the terminal. What Anthropic noticed was non-programmers adopting a terminal tool for decidedly non-code work, organizing files, compiling research, drafting documents, because nothing else could act on files the same way. Cowork is that capability without the terminal: the everything-else counterpart to Code's software engineering. If you write software, use Code; if your work is documents, folders, spreadsheets, and research, Cowork is the one aimed at you.

What do you need to run it?

A paid Claude plan and the Claude Desktop app on macOS or Windows, with web and mobile access in beta, which in practice means you can start a task at your desk and check on it from your phone. It launched in January 2026 as a research preview for Max subscribers on macOS and has since opened to every paid tier, with usage limits that vary by plan. Those specifics, platforms, tiers, and limits, are exactly the kind that shift; Anthropic's site is the source of truth on the day you read this.

What is it actually good at?

• File chores at volume: reorganizing a chaotic downloads folder, renaming and sorting by rule, batch conversions. Tedium is where it shines first.
• Documents from raw material: a report drafted from a folder of notes, a deck or spreadsheet assembled from scattered inputs, using the same document skills available elsewhere in Claude.
• Recurring work: tasks can be scheduled daily, weekly, or monthly, which turns "compile the weekly review" from a chore into a standing order.
• Connected work: connectors and plugins let a task reach the tools you've granted, and Claude chat and Cowork now share memory, so context about you carries across both.

The honest limits: it consumes usage quickly on long tasks, it's only as safe as the folder scope you grant, and supervision still matters. It's a capable junior colleague, not a vending machine.

Do skills work in Cowork? Where does JotThread fit?

Yes: skills uploaded in claude.ai settings are available in Cowork, and that's precisely why JotThread ships Cowork-ready. The fit is natural because Cowork sessions generate exactly the artifacts worth keeping: decisions about how files got organized, tasks discovered mid-job, notes on what the report still needs. /jot files them into jotthread.md, which lives in the very folder Claude is working in, and /thread renders the board. What skills are and how they load is covered in the skills guide; the wider capture workflow is in this one.

Common questions