Do I need to install anything in a terminal?

No. You download one app, open it like any other program, and sign in. The whole point of Claude Code Desktop is that there's no terminal and no setup ritual — you talk to it in plain English in a normal window.

What can Claude on Desktop actually see?

Only the folder you open. Claude can read and work with the files in that folder — and nothing outside it — so you stay in control of what it has access to. Open a folder with a copy of your work in it and you've drawn the boundary.

What if Claude changes or deletes something I needed?

Desktop's "Ask permissions" mode pauses and asks before anything consequential, and it keeps checkpoints you can roll back to. For your first week, work on copies of important files and a mistake costs you nothing.

Is this available on my computer?

Claude Code Desktop runs on macOS and Windows. If you're on Linux, you'll use the terminal version (the CLI) instead — it's the same Claude, just driven from the command line.

Getting started with Claude on Desktop (no terminal)

The thing that kept most people away from “AI that can actually do your work” was never the AI. It was being told to open a terminal — a blinking black window full of commands — before you could even start. Claude Code Desktop removes that step entirely. It’s a normal app: you install it, sign in, open a folder, and ask for what you want in plain English. No command line, no setup ritual, nothing to memorise.

Here’s how to go from nothing to a real, finished task — and you won’t see a terminal once.

Download Claude Code Desktop (it runs on macOS and Windows) and open it the way you’d open any program. Sign in. That’s the whole setup.

What you’ll see is a familiar-looking window: a chat pane where you type, a sidebar, and room for a file pane that shows the files you’re working with. It looks like software you already use — because that’s the point. If you’ve ever used a chat app, you already know how to drive this.

On Linux? Claude Code Desktop is macOS and Windows only. You’ll use the terminal version instead — same Claude, different door. Our Desktop vs CLI guide explains that path.

Step 2 — Open a folder (this is how you stay in control)

This is the one concept worth understanding up front, and it takes ten seconds: Claude can only see the folder you open. Open a folder, and Claude can read and work with the files inside it — and nothing outside it. That’s your boundary, and you draw it.

So for your very first task, make it easy on yourself:

Create a new folder somewhere — call it claude-test.
Drop in a copy of something real but low-stakes: a spreadsheet, a long document, a messy export.
Open that folder in Claude Code Desktop.

Now Claude is looking at exactly what you chose, and nothing else. Working on copies for your first week means any mistake costs you nothing.

Step 3 — Just ask, in plain English

There is no special language. You don’t learn commands. You type a sentence the way you’d ask a sharp, fast colleague:

Read budget.csv and tell me the three biggest line items and anything that looks unusual.

Claude reads the actual file and answers. This is the moment the mental model clicks for most people — Claude isn’t guessing from thin air, it read your file and is telling you what’s in it.

Then push one step further and ask it to do something, not just tell you:

Make a cleaned-up version with consistent date formats and save it as budget-clean.csv.

You just did data work without writing a single formula.

Step 4 — Watch the visual diff, then accept or reject

Here’s where Desktop earns its name. When Claude is about to change a file, it doesn’t just do it silently — it shows you a visual diff: the old version and the new version side by side, with the changes highlighted. You look it over and click accept or reject.

Nothing changes until you say so. You’re never guessing what happened or hunting through cryptic output — you see the edit, you approve the edit, the edit happens. This is the single feature that makes Desktop feel safe to a newcomer, and it’s why reviewing Claude’s work is a glance rather than a chore.

Step 5 — Let “Ask permissions” be your seatbelt

The first few times Claude wants to do something consequential, it will pause and ask. That’s the “Ask permissions” mode, and the docs recommend it for new users for exactly this reason: the safe path is the default path.

Spend five minutes on purpose here. Approve a couple of actions. Decline one. Watch what each does. Within a few clicks the permission prompts stop feeling like a hurdle and start feeling like a seatbelt — there so you can move fast without worrying.

A rule worth adopting from day one: anything involving personal data, money, or messages that go to other people should be drafted by Claude and checked by you. Claude is excellent at the first 90%; the last 10% is your job.

Step 6 — Teach it how you like things

Notice the instructions you keep repeating — “use UK date formats,” “keep summaries under 100 words,” “our company is Northwind, never abbreviate it.” Instead of saying them every time, ask Claude to write them down once:

Create a CLAUDE.md file with these standing instructions: [your rules].

From then on, Claude reads that file at the start of every session and works your way by default. It’s the closest thing to training the tool, and it takes two minutes. You’ve stopped re-explaining yourself forever.

What to remember after your first session

Plain English is the entire interface. You never memorise commands. If you’re unsure how to ask, ask Claude how to ask.
The folder is your boundary. Claude sees what you open and nothing more. Open deliberately.
The diff is your safety net. Read it, then accept or reject. Nothing happens without your click.
Specific beats vague. “Summarise this in five bullets for a non-technical manager” beats “summarise this.” Tell it the audience and the shape.

The reason this felt like it was “for developers” is that developers got the tools first. But a capable assistant that can read your real files and act on them — sitting in a normal app window, one folder away — is for anyone with repetitive work and a willingness to ask. After one session, that’s you.

When you’re ready to bring it to colleagues, our Desktop team rollout guide covers how to do it without the awkward “everyone figure it out yourselves” phase.