CHAPTERS
What Claude Cowork is: delegating complete tasks where your work lives
Claude Cowork is positioned as a task-delegation mode where Claude can act directly across your computer, cloud tools, and the web. Instead of guiding Claude step by step, you describe an outcome and Claude carries out the work with optional supervision.
Where Cowork runs and who gets access
Cowork is generally available through the Claude Desktop app on macOS and Windows. The feature is available to paid and organizational tiers, and you start it from a dedicated Cowork tab.
Cowork vs. regular Claude chat: handoff vs. step-by-step
The transcript contrasts regular chat—where you collaborate interactively—with Cowork—where you hand off a task and Claude executes it. Cowork emphasizes autonomous execution within agreed boundaries.
Granting local folder access: choosing Claude’s workspace
To enable local actions, you connect Claude to a specific folder or project directory. Claude requests permission before making changes, and once connected it can read, create, and edit files within that scoped area.
Managing multiple folders and frequent locations
Cowork supports favoriting commonly used folders and connecting more than one folder at a time. This enables workflows that pull from separate local sources without moving data first.
Connecting cloud tools: bringing context from Google Drive, Notion, Slack, and more
Cowork can link to external services through connectors so Claude can reference and act on work stored in common productivity tools. The goal is to reduce manual context gathering by pulling it from where it already lives.
Using Claude in Chrome for browser-based work
If Claude is set up in Chrome, Cowork can perform browser tasks such as reading web pages, extracting information, and moving across tabs. This extends Cowork from local/cloud files into web workflows.
Global Cowork settings: persistent instructions for every session
You can define global instructions in Settings that apply to all Cowork sessions. These can include role context and output preferences (e.g., create Word docs instead of Markdown).
Operational notes: local session storage and keeping the desktop app open
Cowork sessions are stored locally on the device, and the Claude Desktop app must remain open while tasks run. These constraints shape how you monitor work and manage longer-running automations.
Demo setup: tackling a messy Downloads folder
The walkthrough uses a common pain point—an overgrown Downloads folder filled with mixed file types and duplicates. The user connects the folder and asks Claude to propose an organization plan before making any changes.
Plan-first workflow: proposed categories, naming conventions, and duplicate review
Claude responds with a structured plan including top-level folders, a dedicated duplicates area, and date-based naming. It also flags suspected duplicates for human review before any deletion or irreversible action.
Human-in-the-loop adjustments: correcting assumptions and approving execution
When the user notices that some “duplicates” are actually different versions, they redirect Claude to move them to a review folder rather than delete them. After approval, Claude proceeds with the updated plan and executes changes on the machine.
Monitoring progress and inspecting task details during execution
Cowork provides progress visibility, including a top-right status indicator and task-level drill-down. The user can click into tasks to see details or ask questions as work proceeds.
The core Cowork loop and best practices: delegate work, keep judgment
The concluding guidance frames Cowork as a loop: Claude proposes a plan, waits for approval, then takes action. Users are advised to start with bounded tasks, review outputs carefully, and treat Cowork as delegated execution—not delegated judgment.
Get more out of YouTube videos.
High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.
Add to Chrome