Section 9: Meet Cowork — The Agentic Desktop
Welcome to Act 2. You’ve spent eight sections building skill with Claude as a chat assistant: prompting, organizing Projects, working with documents, using connectors interactively. Cowork extends that foundation into something qualitatively different: a desktop environment where Claude can access your files, run on a schedule, receive instructions from your phone, and take actions in applications on your computer.
Why this section matters
The word “agentic” means Claude acts, not just responds. It reads your actual files. It writes to your actual folders. It can connect to your applications and operate them. The same care you bring to any tool that touches your real data and your real work applies here, with higher stakes because the actions have effects.
This section establishes what Cowork is, how it’s structured, and what you need to understand before you start building workflows in it. Skipping this section and going straight to automation is the Cowork equivalent of not reading the setup guide before connecting something to your network.
What you’ll learn
What Cowork is and how it differs from Chat. Cowork is the desktop app’s agentic mode. The key additions over Chat: file system access, the ability to run on a schedule, Dispatch (remote triggering from mobile), and computer use. The Claude model is the same; the surface is more powerful.
The three-tab desktop app: Chat, Cowork, and Code. How the desktop app is organized and what each tab provides. Understanding the surface prevents confusion about which mode you’re operating in.
File-system access and the permission dialogs you grant on setup. Cowork can read and write files in folders you authorize. You grant this access through permission dialogs. What you authorize, when, and how to manage those authorizations is covered here.
Global instructions vs. per-folder instructions. Cowork supports two levels of standing instructions: instructions that apply across all Cowork work, and instructions specific to a folder or workspace. Knowing which to use for which type of guidance prevents conflicts.
Connectors and plugins inside Cowork. The same connectors you configured in Act 1 work in Cowork. Plugins extend both Chat and Cowork capabilities. The configuration is largely shared.
Cowork instructions vs. Project instructions. Projects (from Section 5) and Cowork workspaces are related but different. Understanding the relationship prevents double-configuration and inconsistency.
Review mode vs. action mode. Cowork has settings for how autonomously Claude operates. Review mode keeps you in the loop; action mode lets Claude proceed without explicit confirmation. The right setting depends on the workflow and your confidence in it.
The mini project
You’ll set up a functional Cowork workspace: authorize folder access, write global and folder-level instructions, and connect the tools you’ll use in the sections ahead. The deliverable is a configured workspace, not just knowledge of the concepts.
How to approach this section
Cowork setup is done in the desktop app, not in a browser. If you haven’t installed it, that’s the first step. The setup dialogs walk you through folder authorization and connector configuration with permission prompts. Read them carefully; they describe exactly what access you’re granting.
By the end of this section, you’ll have a working Cowork environment and the conceptual foundation for everything in sections 10 through 14.