CHAPTERS
- 0:01 – 0:32
What Claude Cowork is: delegating end-to-end tasks where you already work
The video opens by defining Claude Cowork as a way to hand off complete tasks to Claude across your computer, cloud apps, and the browser. It emphasizes that you can observe progress, steer at key moments, or return later to finished results.
- •Delegates complete tasks rather than step-by-step prompting
- •Works across local computer files, cloud services, and web browsing
- •Claude can find and edit work artifacts directly
- •You can watch, intervene when needed, or step away and return to results
- 0:32 – 1:02
Availability and where to start in Claude Desktop
This chapter explains who can access Cowork and where it lives inside the Claude Desktop app. It contrasts regular chat workflows with Cowork’s task handoff model.
- •Available in Claude Desktop on macOS and Windows
- •Access for Pro, Max, Team, and Enterprise users
- •Start by opening Claude Desktop and selecting the Cowork tab
- •Difference: regular chat is collaborative step-by-step; Cowork is delegation and execution
- 1:02 – 1:17
Granting local folder access for direct file operations
Cowork begins with connecting Claude to a specific folder (or folders) on your computer. The video highlights permissions and the scope of what Claude can do once connected.
- •Select a folder/project directory for Claude to operate in
- •Claude asks permission before making file system changes
- •Once authorized, Claude can read, create, and edit files in that folder
- •Favorite frequently used folders for faster setup
- 1:17 – 1:32
Connecting cloud tools and multiple data sources
Next, the video introduces connectors that link Cowork to the services where work context lives. It also notes you can connect multiple folders to bring together separate sources of information.
- •Use connectors to integrate services like Google Drive, Notion, and Slack
- •Connectors let Claude pull relevant context from existing tools
- •You can connect multiple folders to combine disparate local sources
- •Tool connections expand Cowork beyond just local file management
- 1:32 – 1:49
Using Cowork with Chrome for browser-based tasks
This chapter explains how Cowork leverages Claude in Chrome to work on web pages and multi-tab workflows. It frames browser access as a way to read, extract, and navigate online information.
- •Cowork can use Claude in Chrome if set up
- •Reads web pages and extracts data from sites
- •Can navigate across browser tabs as part of a task
- •Enables end-to-end workflows that include the web
- 1:49 – 2:06
Global instructions and operational constraints (local storage, app must stay open)
The video shows where to set global instructions that apply to every Cowork session and calls out key practical constraints. It notes that sessions are stored locally and the desktop app needs to remain open during execution.
- •Set global instructions under Settings → Cowork tab
- •Examples: role context; specify output formats (e.g., Word docs vs Markdown)
- •Cowork sessions are stored locally on your device
- •Claude Desktop must stay open while a task is running
- 2:06 – 2:36
Demo setup: organizing a cluttered Downloads folder
The demonstration begins with a common problem: a messy Downloads folder full of mixed file types and duplicates. The user connects the folder and assigns Claude a bounded task with a clear requirement to propose a plan before acting.
- •Real-world use case: months of accumulated Downloads clutter
- •Task prompt includes scanning contents and proposing categories
- •Defines sorting rules, naming conventions, and items to flag
- •Requires Claude to show the plan before making changes
- 2:36 – 3:06
Claude proposes an organization plan (categories, naming, duplicates)
Claude returns a structured plan that includes folders by file type, a duplicates strategy, and naming conventions. It also flags suspicious duplicates for human review before any destructive action.
- •Proposed folders: Documents, Spreadsheets, Presentations, Images, Duplicates
- •Suggests date-based naming conventions
- •Flags specific files that appear to be duplicates
- •Keeps a review step to avoid accidental loss
- 3:06 – 3:21
Human-in-the-loop adjustment: refining what to keep vs review
The user inspects flagged duplicates and identifies cases that shouldn’t be deleted. Cowork supports quick course correction by updating instructions before proceeding with execution.
- •User reviews flagged duplicates and finds two are distinct versions
- •Instruction update: move them to a review folder instead of deleting
- •Claude adapts the plan and continues
- •Shows how user judgment guides final decisions
- 3:21 – 3:36
Monitoring execution and verifying real file changes
As Claude executes, the UI provides task progress and drill-down detail. The video underscores that Cowork performs real operations on your machine and produces tangible outcomes.
- •Progress is visible in the top-right corner
- •You can click tasks to see details or ask questions
- •Files are actually moved/renamed on the local machine
- •End state: Downloads folder organized, cleaned up, and renamed
- 3:36 – 4:16
The core Cowork loop: propose → approve → execute (delegate work, keep judgment)
The closing chapter summarizes the Cowork workflow as a structured loop with approval before action. It advises starting with bounded tasks and emphasizes that while Claude executes, the user remains responsible for judgment and review.
- •Cowork differs from chat: it performs the work, not just describes it
- •Claude proposes a plan and waits for approval before taking action
- •You can adjust, redirect, or skip steps before execution
- •Best practice: start with clear-bounded tasks and review outputs—delegate work, not judgment
