Chapter 20 · DESKTOP
Claude Code in Desktop
Code in Desktop works on a workspace with visual diff review. It differs from Cowork and from a cloud Code session. Where the session runs determines which files and tools it can reach.
Video
Steps
- Open Code and choose a sample project folder. Check whether it is a local workspace or a cloud task. Do not use production for your first exercise.
- Ask Claude to read the project and propose a plan before editing. Specify tests and boundaries for files, commands and network access.
- After edits, inspect every changed file in the diff. Run tests and open the app itself. One passing test does not verify every flow.
- Inspect handoff, parallel tasks and scheduling offered by your interface. CLI sessions can move to Desktop through supported flows; not every history, permission or plan transfers across surfaces.
Common pitfall: Written code is not necessarily tested or deployed. Keep those states separate.
Hands-on exercise: Have Claude fix a text issue in a sample project. Inspect the diff and tests without committing or deploying.
Filmed demo · Video is added in the media phase
Recap
Comprehension check
How does writing code differ from deployment?
Recap
- Identify local versus cloud execution
- Review plan, diff and tests
- Separate writing, testing and deployment