Workbranch › Guides

How to use Claude Code if you're not a developer

Claude Code is sold as a coding tool, but what it really does is read, write and reorganize files in a folder you give it. That makes it useful for reports, research notes and messy folders too. Here is the simplest way in, without a terminal, and how to keep your files safe.

Updated 30 October 2026

What Claude Code does with your files

Anthropic calls Claude Code an agentic tool: it reads the files in a folder, edits them, creates new ones and runs commands to get a job done. Code is the main use, but nothing stops the folder from holding meeting notes, drafts, CSV exports or a pile of PDFs. Compared with uploading files to a chat, the difference is that Claude works on the actual files on your computer and saves its results there.

Anthropic also makes Cowork, which it describes as the same agent brought to knowledge work. If your goal is mainly finished documents, decks and spreadsheets, see our guide to using Claude Cowork. Claude Code is the better fit when you want to see and approve every change in a folder.

The simplest setup: the desktop app

You don't need a terminal, Node.js or any extra install. The Claude desktop app contains Claude Code.

1. Check your plan. Claude Code needs Pro, Max, Team or Enterprise.
2. Download the Claude desktop app for macOS or Windows (Linux is in beta) and sign in.
3. Click Code at the top of the sidebar.
4. Under the prompt box, open the first control (the environment selector) and choose the top entry under Local.
5. Click the folder control beside it, choose Open folder… and select your folder.
6. Open the mode selector in the same row and pick Manual or Plan while you're learning.
7. Type your request and press Enter.

Our guide to Claude Code in the desktop app covers the rest of the interface. If you'd rather use a terminal, Anthropic has a beginner's terminal guide and our Claude Code setup guide walks through installing it.

First tasks worth trying

Pick work that is tedious, repetitive and easy to check. Some examples:

• Reports: "Read every meeting note in this folder from October and write a one-page summary called october-summary.md, with decisions and open questions."
• Research: "Go through these articles and make a table comparing what each says about pricing, with the file name as the source."
• Organizing: "Propose a folder structure for these files by client and year. Don't move anything until I approve."
• Data: "This CSV has duplicate rows and inconsistent date formats. Make a cleaned copy and tell me what you changed."
• Standing instructions: "Create a CLAUDE.md that explains what this folder is for and how I like reports written." Claude Code reads that file at the start of every session in the folder.

Ask for a new file instead of overwriting the original whenever you can. To point Claude at one file, type @ and the file name.

Staying safe with your files

• Work on a copy. Make a separate folder with copies of the files for your first sessions.
• Choose the mode deliberately. Manual asks before every edit and command. Plan only proposes what it would do. Accept edits and Auto let Claude act with fewer questions; Anthropic says Bypass permissions belongs only in sandboxed environments, so leave it alone.
• Review before accepting. After edits, click the +12 -1 style counter to see exactly what changed in each file.
• Read the command before approving it. If Claude wants to run something you don't understand, ask it to explain first or decline.
• Stop it any time with the stop button or Esc.
• Be careful with untrusted content. Documents and web pages can carry hidden instructions. Anthropic warns about this for Cowork, and the same caution makes sense here: don't point Claude at sensitive files and untrusted downloads in the same session.

Good to know

• Plans: most ways of using Claude Code need a paid Claude subscription or an Anthropic Console account. The desktop Code tab needs Pro, Max, Team or Enterprise.
• Usage: long, multi-file jobs use more of your plan's limit than a single chat question.
• Other surfaces: the same Claude Code runs in the terminal, in VS Code and JetBrains, and on the web at claude.ai/code. A folder's CLAUDE.md works in all of them.
• Connectors: Claude Code can connect to tools such as Google Drive through MCP, but start with local files until you're comfortable.

If it doesn't work

• Clicking Code asks you to upgrade: your account is on Free.
• Claude can't find a file: make sure it's inside the folder you opened, not elsewhere on your computer.
• It keeps asking for permission: that's Manual mode doing its job. Once you trust a task, switch to Accept edits so file changes go through.
• The result missed the point: stop it, then describe the audience, format and length you want, or ask for a plan first in Plan mode.

Keep the decisions, not just the files

A session that writes a report also produces decisions and follow-ups that tend to get lost. The Workbranch Claude Code plugin lets you say "save this to Workbranch" to file them into a project by topic, and shows what's still open next time you start a session in that folder. See Workbranch for Claude.

Sources

• Claude Code overview (Claude Code Docs, checked 2026-10-30)
• Get started with the desktop app (Claude Code Docs, checked 2026-10-30)
• Use Claude Code Desktop (Claude Code Docs, checked 2026-10-30)
• Get started with Claude Cowork (Claude Help Center, checked 2026-10-30)
• Use Claude Cowork safely (Claude Help Center, checked 2026-10-30)

Frequently asked questions