Getting Started with the Claude Desktop App

The Claude desktop app puts Claude chat, Cowork, and Claude Code in one desktop window. Code supports macOS and Windows, with Linux available as a beta for Ubuntu and Debian. The Code tab is the no-terminal entry point for letting Claude read a project, edit files, run checks, and show you a visual diff.

You still need to choose the right folder and read every proposed edit. File changes remain real work, even when the interface looks like chat.

I use Claude Code Desktop's Browser pane for visible app testing, and I keep the diff beside that preview because the rendered page and changed files answer different review questions.

What Is Claude Code Desktop?

Claude Code Desktop is the Code workspace in the Claude desktop app. It connects a conversation to a project folder so Claude can inspect files, propose changes, run development tools, and show the resulting diff.

You do not need to install the separate Claude Code CLI to start. The app includes its own coding runtime; your project may still need Git, language runtimes, or other development tools.

A terminal is a text window for running commands. Desktop can show command output while letting you direct the task and review changes through the visual interface.

Choose Chat, Cowork, or Code

Claude Desktop has three work areas, and they do different jobs. Chat is for questions and writing that do not need access to a project folder. Cowork can take a broader task and work through it in its own environment. Code opens Claude Code through a visual interface and ties the session to a folder or repository you choose.

Use Code for a bug fix, a small feature, or a test run where the agent must inspect the project. A local Code session works with files and developer tools on your machine. A remote session runs in an Anthropic-hosted environment and can keep working after you close the app.

The desktop reference also documents SSH sessions for projects that live on another computer.

Computer use belongs to a separate desktop feature. It lets Claude control approved desktop apps when a connector or shell command cannot do the job. Anthropic calls it a research preview, makes you turn it on in Settings, and asks before it accesses an app.

Leave it off for your first coding session. The Code tab already has the file, terminal, diff, and preview tools needed for normal project work.

Create Your Account

1. Open claude.ai in any web browser to get started.
2. Choose Sign up, and register with your email address or a Google account.
3. Confirm your email if it asks you to, and you are in.

That free account already lets you chat with Claude, in the browser and in the desktop app, which is a fine way to try it before you pay for anything.

Pick a Plan

The app itself is free to download and use for chat on any account. The Code tab and Cowork require a paid plan. Prices were checked on October 16, 2026, so check the official pricing page before you commit.

Plan	Price	Good for
Free	$0	Chat only
Pro	$200/year / $20 monthly	Code and Cowork
Max 5x	$100/mo	Five-times Pro usage
Max 20x	$200/mo	Twenty-times Pro usage

Free covers ordinary Claude chat. Pro is the least expensive individual plan that includes both Code and Cowork. Max raises the usage allowance to five or twenty times the Pro level and adds priority access during busy periods. Begin with Pro unless you already know that long, daily coding sessions will exhaust its limits.

Plan limits are shared across Claude products, and Anthropic can revise prices or access. Treat the table as a dated buying snapshot. The model menu can also differ by account, so choose from what the app shows instead of following an old model list.

Install the App

1. On claude.ai, look for the Download option (in the menu or your account settings) and grab the app for your computer. The Code workspace supports macOS, Windows, and a Linux beta for Ubuntu and Debian.
2. Open the file you downloaded and follow the normal install prompts, the same as any other app.
3. Launch it and sign in with the account you just made.

The coding runtime is included. Install any development tools your chosen project requires; Windows local sessions also require Git.

Start Your First Code Session

Open the Code tab, select Local, and choose a small project folder. Pick a project that is already in Git and has no uncommitted work. The official desktop quickstart recommends a project you know well because you can judge its plan and edits.

Start with a read-only inspection tied to the project:

Find the page that renders the contact form. Explain which file controls its labels and how I can preview it. Do not change files yet.

After checking the answer, give Claude one bounded edit:

Change the contact form's submit label to "Send message." Keep its behavior unchanged, run the relevant build, and show the diff and browser preview.

Set the permission mode to Plan if you want Claude to inspect the folder before it edits. Ask it to name the files it expects to touch and the check it will run when done.

For a web project, that check might be one test command, a build, or an app preview. A task without a pass-or-fail check leaves you to decide from a confident-sounding message.

Review Changes Before Keeping Them

The desktop interface earns its keep after Claude starts editing. Open the diff pane and read each changed file. Green lines are additions and red lines are removals. If a file has no clear link to your request, ask why it changed before you accept the work.

Use the preview pane for a web app. Claude can start a development server, open the page, inspect the page structure, click controls, and take screenshots.

A passing build proves that the code compiles. Layout and form behavior need a preview check as well, so ask for both results when the task affects a user interface.

Claude Code checkpoints track changes made through its direct file-editing tools. They do not track file changes made through Bash commands, or undo database writes, deployments, or payments. The CLI's Escape-twice and /rewind controls are documented in the checkpoint guide. Git remains the stronger boundary: begin clean, inspect git diff, and commit only after you understand the result.

Troubleshoot Common Desktop Problems

• The Code tab asks you to upgrade: confirm the account has a paid Pro, Max, Team, or Enterprise plan.
• You see a 403 error: sign out, sign in again, restart the app, and confirm the paid plan is active.
• A command is missing: open the Local environment settings and check the PATH seen by the app.
• The preview loses your login: turn on Persist sessions in the preview menu so cookies and local storage survive server restarts.
• Windows cannot start a local session: install Git, then restart Claude Desktop.

Update the app before chasing a stale bug. On macOS use Claude → Check for Updates; on Windows use Help → Check for Updates. The desktop reference keeps a versioned changelog and lists platform limits, including the Linux beta and the absence of inline autocomplete.

A Peek at the Terminal

The desktop app is the gentle on-ramp, and most people are happy here for a good while. The next step up, when you want it, is the terminal: that plain text window where you type commands instead of clicking.

Anthropic's Claude Code runs there, with access to your whole project at once, which is what makes it good for bigger, more automated jobs.

You do not need any of that yet. Get comfortable inside the app first, with no rush to move on. When the app starts to feel like the limit rather than the helper, that is the signal to read the Claude Code guide and try the terminal version.

When Desktop Is the Right Starting Point

Claude Desktop is a sound first step when you want Claude Code's project access and visual review without living in a terminal. Start with one clean test project, stay in Plan mode until the proposed scope makes sense, and keep the diff and preview panes open.

Move to the CLI when scripting and terminal speed become more useful than the desktop workspace.

FAQ

Does Claude Code Desktop need the command line?

Claude Code Desktop does not require command-line knowledge. Its Code tab includes the coding agent, a file view, a visual diff, an app preview, and an integrated terminal, but you can begin without typing terminal commands. The separate Claude Code CLI is only needed if you want to run Claude from your own terminal or use scripting flags.

Can I use Claude Code Desktop for free?

Claude Code in the desktop app requires a paid plan; the Free plan supports ordinary Claude chat. The Code tab and Cowork require a paid Pro, Max, Team, or Enterprise plan. Pro costs $20 month to month or $200 billed annually, advertised as about $17 per month.

What folder should I open first?

Beginners using Claude Code Desktop should open a small project they know and can restore from Git. Avoid your home folder, a directory full of private files, or a production checkout. A familiar test project makes it easier to judge the plan, read the diff, and spot a file Claude should not have touched.

Is computer use the same as the Code tab?

Claude computer use and the Code tab are different features. The Code tab works through coding tools tied to the project folder you select. Computer use can click and type in approved desktop apps when no connector or command-line tool fits. Anthropic labels computer use a research preview, keeps it off by default, and asks for app access.

Where to Go Next

• Claude Code guide: the terminal version, for more control and automation once you are ready.
• Beginners guide to AI coding tools: how these tools actually work under the hood, in plain English.
• Best AI coding tools: see how Claude stacks up against Cursor, Codex, and the rest, so you can pick what fits.

Desktop setup, platform support, and pricing checked against official documentation on October 16, 2026.