Do I need to use a terminal, or can I just use the app?

You can just use the app. Claude Code Desktop and the command-line version are the same engine behind two different interfaces. Desktop is an ordinary window you point and click. The terminal is for automation, scripting, and the Linux distributions Desktop's beta doesn't cover.

Which Linux distributions are supported?

Ubuntu 22.04 or later and Debian 12 or later, on x86_64 or arm64. Other Debian-based distributions meeting those requirements may work but aren't officially tested. Fedora and RHEL aren't supported yet — on those, the CLI is still the route, and it supports a much wider range of distributions.

Do I still need the terminal?

Once, to install it. The app installs through Anthropic's apt repository, which means a handful of commands the first time and then updates arriving with your normal system updates. After that you use a normal application window — no command line involved in the actual work.

Is anything missing compared to macOS and Windows?

A few things. Computer Use (app and screen control) isn't available on Linux, voice dictation isn't in the app, and the Quick Entry global hotkey works on X11 but needs your desktop environment's GlobalShortcuts portal on native Wayland. Chat, Cowork, and Code are all present.

Can I sign in with an API key?

Not on Desktop. The Linux app signs in the same way as macOS and Windows — with a claude.ai subscription or through your organisation's SSO. If you need API-key authentication, use the CLI, which runs the same engine.

Is Claude Code Desktop less powerful than the CLI?

No. It's the same Claude model and the same agent doing the work — Desktop just gives it a visual interface with click-to-accept diffs and an "Ask permissions" mode. The CLI adds scripting and automation on top, which matters for power users, but for everyday work the two are equally capable.

Do I need to know how to code to use either one?

No. You drive both by typing plain English. Desktop simply removes the one barrier that scares non-technical people away — the blank terminal — by giving you a normal app window with buttons, panes, and visual approvals instead.

Which should a non-technical professional choose?

Claude Code Desktop. It needs no terminal, leads new users into an "Ask permissions" mode the docs recommend for beginners, and shows changes as visual diffs you accept or reject with a click. Reach for the CLI later only if you want to automate, or if you're on a Linux distribution the Desktop beta doesn't cover yet.

Is Claude Code Desktop available on my computer?

Desktop runs on macOS, Windows, and — in beta — Ubuntu 22.04+ and Debian 12+. Linux support is newer and a few features aren't in the beta yet, so on an unsupported distribution the CLI is still the route. Same Claude either way.

The app vs the command line — Claude for Humans

This question stops more people than it should, so here is the short version: the terminal is optional. It is a second door into the same building, not a stage you have to pass through before you’re allowed the good one. Everything the command line can do to your files, the app does too — the difference is whether you type an instruction or click one.

It helps to have the three words below straight, because they get used loosely. A GUI is any software you drive by looking and clicking, which is nearly everything you already use. A terminal is the plain-text window where you type instructions instead. A CLI is a program built to be driven that way. Claude Code has both a GUI and a CLI; Desktop is the GUI.

There are two honest reasons to open a terminal anyway. The first is an unsupported Linux — Desktop reached Ubuntu 22.04+ and Debian 12+ in beta in June 2026, but on Fedora, RHEL and the rest there is still no app, so those readers have no choice and none of the terminal material here is optional for them. The second is automation: once you want Claude to run inside a scheduled script or a pipeline rather than a conversation, you need something a script can call, and that is what claude -p is for. That path continues in automation.

The rest of the commands below are terminal comfort rather than terminal necessity — teaching your shell a newline shortcut, vim-style editing, running a shell command without leaving the chat. Useful if you live there, ignorable if you don’t. Nothing on this page is a prerequisite for getting started with Claude Code; come back to it the day you actually need it.

Where to actually learn it

If you’ve decided you want the terminal — because you’re on Linux, or because automation is where you’re headed — there’s a short hands-on track for it: the Power Track. Shell basics you practise in a sandbox in the browser (nothing on your machine to break), then worktrees, hooks and headless mode. It’s deliberately kept out of the main path, because a non-technical reader should never be routed through cd and rm on the way to their first useful hour with Claude.

The words

GUI graphical interface · graphical user interface: A GUI (Graphical User Interface) is the kind of software you drive by looking and clicking — windows, buttons, menus, panels — instead of typing commands. Your everyday apps are GUIs. It's the opposite of the CLI, where you type instructions into a terminal. Claude Code Desktop is the GUI way to use Claude Code.
CLI command-line interface: A Command-Line Interface — running a program by typing commands instead of clicking buttons. The terminal is where you do it. It looks bare, but it's precise, fast, and easy to automate.
Terminal shell: The window where you type commands and read their output — a plain-text way to talk to your computer. Same machine as your usual desktop, just a different door in. ("Shell" is the program inside it that actually reads your commands.)

Commonly confused with

Two things people mix up here, and the difference that actually matters.

Claude Code Desktop vs the terminal (CLI): which should you use? Desktop and the command line are two doors into the exact same engine. One asks you to learn a terminal first; the other doesn't. For most professionals that decides it.

Claude Desktop on Linux: the terminal is no longer mandatory For years, "I'm on Linux" meant "you're using the command line, then." That stopped being true, which changes who on a Linux team can actually use this. 8 min

How to do it

claude -p Run one prompt without the chat UI and print the answer — a Power-Track tool for scripts and pipes.
/terminal-setup Teach your terminal the shortcut for a newline (Shift+Enter) — a Power-Track setup step.
/vim Toggle vim-style editing in the input prompt — a Power-Track comfort for terminal users.
! <command> Run a shell command from inside the chat and see the output land directly in the conversation.

Where to actually learn it

The words

Commonly confused with

Read more

How to do it