CHAPTERS
What Claude Cowork is and where it works (desktop, cloud, browser)
Claude Cowork is positioned as a way to delegate complete tasks to Claude directly in the environments where work already lives. It can operate on local computer files, connect to cloud services, and handle browser-based work via Chrome integration.
- •Delegates end-to-end tasks rather than step-by-step prompting
- •Works with local files on your computer (find/edit/create)
- •Connects to cloud tools like Google Drive, Notion, and Slack
- •Can operate in the browser through Claude + Chrome
- •You can monitor, intervene, or step away and return to results
Availability and how Cowork differs from regular chat
Cowork is available inside the Claude Desktop app for eligible paid tiers on macOS and Windows. The workflow shifts from collaborative, incremental chatting to handing off a task that Claude runs independently while you focus elsewhere.
- •Available in Claude Desktop on macOS and Windows
- •Accessed via the Cowork tab
- •Available for Pro, Max, Team, and Enterprise users
- •Regular chat: work step-by-step; Cowork: hand off tasks for execution
- •Designed to run tasks while you do other work
Granting local folder access (scoped permissions and favorites)
To enable file operations, you grant Claude access to a specific folder or project directory. Permissions are scoped to what you connect, and Cowork asks before making file-system changes.
- •Choose the folder/project Claude should operate in
- •Claude requests permission before making changes
- •Can read, create, and edit files within the connected folder
- •Favorite frequently used folders for quick access
- •Connect multiple folders to combine separate data sources
Connecting tools and enabling browser automation
Cowork can be linked to external services via connectors to pull relevant context from existing workflows. With Claude set up in Chrome, Cowork can also perform web tasks like reading pages, extracting data, and navigating tabs.
- •Connectors integrate Claude with services where work already lives
- •Pulls context from linked tools/services
- •Chrome setup enables browser-based task execution
- •Can read web pages and extract site data
- •Can navigate across tabs to complete multi-step web workflows
Global instructions, local session storage, and runtime requirements
You can define persistent “global instructions” that apply to every Cowork session to standardize outputs and context. Operationally, sessions are stored locally, and the desktop app must remain open while tasks run.
- •Set global instructions in Settings → Cowork
- •Examples: role context; output format preferences (Word vs Markdown)
- •Cowork session data is stored locally on your device
- •Claude Desktop must stay open during task execution
- •Establishes consistent defaults across sessions
Demo setup: tackling an overgrown Downloads folder
The walkthrough begins with a common, bounded problem: a messy 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.
- •Realistic scenario: months of accumulated Downloads clutter
- •Folder contains PDFs, spreadsheets, screenshots, duplicates, etc.
- •User delegates: scan contents and propose a sorting plan
- •Plan includes categories, sorting rules, naming conventions
- •User requests flagged items for review/deletion before execution
Claude’s proposed structure and duplicate detection
Claude returns a concrete plan with sensible category folders and a dedicated duplicates area. It also recommends a date-based naming convention and flags suspected duplicate files for human review.
- •Proposes top-level folders (Documents, Spreadsheets, Presentations, Images)
- •Creates a Duplicates folder for redundant copies
- •Suggests date-based naming conventions
- •Flags specific files likely to be duplicates
- •Waits for review before taking action
Human-in-the-loop corrections before executing changes
The user inspects the flagged duplicates and corrects Claude’s assumptions—two are actually distinct versions to keep. Claude updates the plan by moving them to a review folder and proceeds with the remaining approved actions.
- •User validates flagged duplicates rather than auto-deleting
- •Two files identified as separate versions worth keeping
- •User requests a review folder placement instead of deletion
- •Claude adapts the plan based on feedback
- •Execution proceeds only after the adjustment is approved
Monitoring task execution and verifying results
As Claude works, progress is visible in the interface, and each task can be opened for details or questions. The changes occur directly on the machine, culminating in an organized, renamed, and cleaned Downloads folder.
- •Progress indicator shown in the top-right during execution
- •Each sub-task can be inspected for details
- •User can ask questions mid-process
- •Files are actually moved/renamed on the local device
- •End state: organized, cleaned, and deduplicated Downloads
The core Cowork loop: propose → approve → execute (with boundaries)
The closing section contrasts Cowork with standard chat: it doesn’t just advise—it performs the work after approval. It recommends starting with clearly bounded tasks, reviewing outputs carefully, and keeping human judgment in the loop.
- •Regular chat explains; Cowork executes
- •Claude proposes a plan and waits for approval before action
- •User can adjust, redirect, or skip steps
- •Best practice: start with clear, bounded tasks
- •Principle: delegate execution, not judgment
