Desktop application - Claude Code Docs
Documentation Index Fetch the complete documentation index at: /docs/llms.txt Use this file to discover all available pages before exploring further. Skip to main content Assistant Responses are generated using AI and may contain mistakes. In the Claude Desktop app, Claude Code is the Code tab. The app also has chat and Cowork , which handles Dispatch and longer agentic work. This page is the reference for the Code tab.
Download for macOS Universal build for Intel and Apple Silicon Download for Windows For x64 processors Get Claude for Linux (beta) apt or .deb for Ubuntu and Debian For Windows ARM64, download the ARM64 installer . On Linux, install with apt; see Claude Desktop on Linux . After installing, launch Claude, sign in, and click the Code tab. For a walkthrough of your first session, see the Get started guide . In the Code tab, each conversation is a session : it has its own chat history and project folder, independent of any other session.
The sidebar lists your sessions and lets you run several in parallel. Within a session you can: Review and comment on diffs , then watch the resulting PR through CI Preview your running app in the Browser pane while Claude verifies its own changes, and open external sites alongside it Watch Claude run and test your iOS app in the iOS Simulator pane Arrange panes for the chat, diff, browser, terminal, and file editor side by side Ask a side question that uses the session’s context without derailing it Let Claude check on, message, or archive your other sessions Connect external tools like GitHub, Slack, and Linear Let Claude open apps and control your screen Run on your machine, in the cloud , or over SSH For scheduled recurring work , keyboard shortcuts , or sending tasks from your phone , see the linked pages and sections.
If you already use the terminal-based CLI, see the CLI comparison for what carries over. Start a session Before you send your first message, choose the environment, project folder, permission mode, and model in the row under the prompt box: Environment : use the environment selector, the first control in the row, to choose where Claude runs. See environment configuration . If a new session shows no environment under the prompt box, follow the earlier layout’s steps .
Project folder : click the project folder control, next to the environment selector, to choose the folder Claude works in. Cloud session : select repositories instead of a folder Saved local or SSH environment : the environment already holds its folders, so the row shows no project folder control. To change the folders, edit the environment . Permission mode : use the mode selector to choose how much autonomy Claude has.
You can change the permission mode during the session. Model : pick a model from the model picker toward the right end of the row. You can change the model during the session. Type your task and press Enter to start. Each session tracks its own context and changes independently. Work with code Give Claude the right context, control how much it does on its own, and review what it changed. Use the prompt box Type what you want Claude to do and press Enter to send.
Claude reads your project files, makes changes, and runs commands based on your permission mode . You can redirect Claude at any point: click the stop button to interrupt immediately, or type a correction and press Enter to send it without stopping the running action. Claude reads the correction as soon as the current action completes and adjusts before its next step. Click the + button next to the prompt box for file attachments, skills , connectors , and plugins .
Accept a suggested prompt After Claude replies, the Code tab can show a suggested next prompt as gray text in the empty prompt box. Claude Code generates each suggestion from your conversation with a short background request that counts toward your plan’s usage limits or your API costs. Use the suggestion : press Tab or Right arrow to place it in the prompt box, edit it if you want, then press Enter to send it. Pressing Enter before you accept the suggestion doesn’t send it.
Write your own prompt : start typing. The suggestion shows only while the prompt box is empty and has no attached files. Turn off Prompt suggestions in Settings > Code or Settings > Claude Code to stop suggestions. Each session stops showing them the next time it starts or resumes. Add files and context to prompts To give Claude a file, @mention it or attach it in the prompt box: @mention files : type @ followed by a filename to add a file to the conversation context.
In a cloud session : @ can list files only after you send your first message. If @ lists none, send your first message without the file, then @mention the file in your next message. Attach files : attach images, PDFs, and other files to your prompt from the + button next to the prompt box, or drag and drop files directly into the prompt. This is useful for sharing screenshots of bugs, design mockups, or reference documents.
In a WSL session : if the + menu shows Add image instead of Add files or photos , you can attach only images. To give Claude any other file from the session’s folder, @mention it. Choose a permission mode Permission modes control how much autonomy Claude has during a session: whether it asks before editing files, running commands, or both. You can switch permission modes at any time using the mode selector in the row under the prompt box.
To approve each change yourself, switch to Manual. To set a default permission mode for new local sessions, add permissions.defaultMode to your settings file . A mode you pick in a local session is remembered per folder and outranks a defaultMode in the project’s .claude/ settings. A new local session can still start in a defaultMode from ~/.claude/settings.json or managed settings, so check the selector before your first message.
If you pick Plan, it applies to this session only. Mode Settings key Behavior Manual default Claude asks before editing files or running commands. You see a diff and can accept or reject each change. Accept edits acceptEdits Claude auto-accepts file edits and common filesystem commands like mkdir , touch , and mv , but still asks before running other terminal commands. Use this when you trust file changes and want faster iteration.
Plan plan Claude reads files and runs commands to explore, then proposes a plan without editing your source code. Good for complex tasks where you want to review the approach first. Auto auto Claude runs without routine prompts; before actions such as shell commands and network requests run, a background classifier checks that they align with your request. Appears when auto mode is available ; there is no separate Settings toggle for it.
Bypass permissions bypassPermissions Claude runs without permission prompts, except for the actions no mode auto-approves , safety classifiers when Claude acts on external sites , or desktop actions such as deleting a session, though not archiving one . Equivalent to --dangerously-skip-permissions in the CLI. On Pro, Max, and Ultra plans, enable “Allow bypass permissions mode” in Settings > Code or Settings > Claude Code .
On Team and Enterprise plans there is no Settings toggle, and organization policy controls it instead. Only use this in sandboxed containers or VMs. Earlier versions of the Code tab labeled these modes Ask permissions, Auto accept edits, and Plan mode. The dontAsk permission mode is available only in the CLI . Start complex tasks in Plan so Claude maps out an approach before making changes. Once you approve the plan, switch to Accept edits or Manual to execute it.
See plan mode for more on this workflow. Cloud sessions support Accept edits, Plan, and Auto. Accept edits corresponds to default mode: cloud sessions pre-approve file edits, so the selector shows Accept edits instead of Manual. Bypass permissions isn’t available in cloud sessions, including sessions in a self-ho
The rest of this page is on the live site.