liveBook · Manning

Chapter 3: Using Claude Desktop and Cowork

What you will learn in chapter 3 of Claude at Work

The chapter introduction explains why moving from Claude on the web to a permissioned local workspace reduces file transfers and supports Git-backed work.

After this chapter you will be able to

What it builds on

Section by section

Introduction

The chapter introduction explains why moving from Claude on the web to a permissioned local workspace reduces file transfers and supports Git-backed work.

Key terms: web interface, network boundary, upload-download round trips, Claude Desktop, Cowork, working sandbox, permissioned access, Git repository, version control, project files

3.1 Why you need the desktop app

This section explains why Cowork is useful for work involving local files, how it combines cloud-based reasoning with a local sandbox, and how its tasks differ from regular chats.

Key terms: attachments, canonical source document, versioning problem, Claude Desktop, Cowork, sandbox, server-side, chat interface, task interface, Cowork task

3.2 Installing Claude Desktop and trying Cowork

This section gets readers started with Claude Desktop and Cowork, then uses a local-file task to explain permissions and how Cowork runs commands on the reader’s machine.

Key terms: Claude Desktop, Cowork, summary.md, folder access, approved folder list, sandbox, task, model, command tool, local sandbox

3.3 Working with local files and folders

This section uses an OWID research task to show how Cowork works with a local folder, analyzes data without filling Claude’s context, and saves the resulting files.

Key terms: Cowork task, owid folder, ZIP files, sandbox, pandas, CSV files, context, summaries, training data, additional data sources

3.4 Projects: Organizing chats, tasks, and data

This section contrasts chat projects with Cowork Projects and explains how local folders and Git make Cowork work easier to organize, review, and reverse.

Key terms: projects, chat projects, Cowork Projects, tasks, project-level instructions, chat context, sandbox, data courier, Cowork Project, folders

3.5 Accessing external systems with connectors

This section explains how connectors let Claude work with external systems through MCP, and uses an email task to show the execution flow and permission controls.

Key terms: Model Context Protocol (MCP), MCP server, connectors, discoverable actions, OAuth token, action-by-action control, approve once, approve for this task, tool request, Cowork

3.6 Live artifacts and connectors

This section explains how Cowork live artifacts use connectors to refresh mini-apps with current data, using an email dashboard as an example.

Key terms: live artifacts, claude.ai, Cowork, MCP, live artifact, HTML, JavaScript, webview, connectors, Artifacts

3.7 Computer use: Letting Claude drive your desktop

This section explains how Claude Desktop can operate other apps through computer use, demonstrates it with Calculator, and warns about the permissions and risks involved.

Key terms: Computer use, context, legacy apps, Desktop settings, OS permissions, calculator app, approval, stop button, backup

3.8 Your turn: Set up your application project

This section has the reader prepare a shared Claude Code and Cowork workspace with version-controlled design documents ready for implementation.

Key terms: Cowork Project, Claude Desktop tools, codebase, Git repo, design documents, docs/design, initial commit, commit history

3.9 Summary

Where this is used later

Concepts explained in this chapter

← Chapter 2: Your side of the conversation Chapter 4: Maximizing productivity with skills and schedules →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.