Command Code Desktop App

The Command Code Desktop App includes chat, agent activity, files, Git changes, a terminal, local browser previews, and plans in one workspace. The agent runtime is built in, so you do not need to install the Command Code CLI.

Alpha

Command Code Desktop is currently in alpha, so you may run into bugs or unexpected behavior. We recommend reviewing its actions, backing up your work, and monitoring model usage and costs.

Report any issues on GitHub.

macOSDownload for macOS LinuxDownload for Linux WindowsDownload for Windows

Install

Choose your operating system and follow the installation steps.

Download for macOS

Open the downloaded DMG.
Drag Command Code to the Applications folder.
Open Command Code from Applications.

Download for Linux

Open a terminal in your Downloads folder, then run:

sudo apt install ./CommandCode-*.deb

Open Command Code from your application menu.

Getting started

Open the app and sign in with your Command Code account.

Open a project

Select Open project, then choose a repository or folder.

Start a chat

Select the project, start a chat, and describe what you want changed.

Review and ship

Review Changes, run final checks in Terminal, then commit or push.

Navigate Desktop

The workspace is split into three main areas:

Area	What it contains	How to use it
Sidebar	Search, projects, chats, history, and account controls	Open a project or return to a chat
Chat	Messages, agent activity, approvals, questions, plans, and the composer	Describe work, add context, choose a model, and set permissions
Workbench	Terminal, Changes, Files, Plan, and Browser	Review and verify changes

Use Search to find commands and files in the active project.
Use Add project to add an existing folder or repository.
Select a project to make it active.
Select a chat to reopen it and continue working.
Use the project action next to a project to start a new chat.
Open the account menu for account details, Settings, and sign out.
Collapse the sidebar when you need more space.

The active project determines which files, terminal sessions, Git changes, and browser previews Command Code can access. Check the project shown below the composer before starting a task.

Chat and composer

Use the composer to describe a task, add context, choose a model, set permissions, and start or stop a run.

Type @ to attach a project file.
Paste text or add images when you need extra context.
Send a follow-up while the agent is working to queue it in the current chat.
Check tool rows to see what is running, complete, failed, or waiting for approval.
Answer agent questions directly in the composer.
Check the active project, model, and permission mode before sending sensitive work.

Workbench

Open the workbench from the right side of the app. Select Open a view to open terminal, changes, files, plan, or browser. Each view opens in its own tab.

Changes

Changes shows the Git working tree for the active project:

Added, modified, deleted, and untracked files.
Total additions and deletions.
File diffs.
Open files in Files.
Discard individual file changes with confirmation.
Switch the current branch.
Commit, commit and push, or push from the Ship menu.

A commit includes all current project changes, not only changes made by the agent. Review every file in Changes before committing or pushing.

Files

Files includes a searchable project tree, source and text previews, text editing, image previews, and links to lines referenced in chat, tools, terminal, or changes. Use the save action to save edits.

If a file changes on disk while you have unsaved edits open, review the conflict before overwriting the newer version.

Terminal

Terminal opens your shell in the active project. Use it to run the app, run tests, inspect logs, and verify changes. Local development URLs shown in terminal can be opened in the browser.

Plan

Plan shows the current chat's implementation plan. Review it, make changes, accept it, or ask the agent to start the work.

Browser and design mode

Browser opens a local development URL inside Command Code.

Open Terminal and start your local app.
Open the detected development URL in Browser, or enter the local address yourself.
Use back, reload, and the address field to navigate the preview.
Turn on Design mode when the local page is ready.

Design mode lets you:

Select an element in the local preview.
Send the selected element and page context to the active chat.
Ask the agent to review or change the design.
Preview supported style changes in the page.
Apply supported changes to source files.
Undo design edits while Design mode is active.

Use Design mode only with local development pages you trust. It is a product-building surface, not a general-purpose browser for sensitive accounts.

Permission modes

Mode	Behavior
Ask for approval	Asks before edits and commands. Good for unfamiliar projects or release work.
Auto-accept edits	Applies edits and safe commands automatically, but still asks before riskier actions.
Plan	Investigates the task and prepares a plan without changing files.
Auto-accept	Runs normal edits and commands without asking each time after you confirm the mode.

Use Shift+Tab in the composer to cycle the modes shown there. Review the active mode before every task that can modify or ship code.

Slash commands

Type / in the composer to browse commands. See the full Slash Commands reference.

/design       Your design partner. Audit, build, compose, and ship UI
/goal         Give the agent a standing objective
/plan         Investigate a task and prepare a plan
/mode         View or change the permission mode
/mcp          Inspect configured MCP connections
/taste        Work with learned project preferences
/compact      Reduce a long chat's context
/fork         Copy the current conversation into a new chat

Read the /design docs and /goal docs for their complete workflows.

Settings, account, and MCP

Open the account menu at the bottom of the sidebar, then select Settings.

General: Set default model behavior, permissions, workbench behavior, and terminal options.
Appearance: Set the theme, interface font, code font, and zoom level.
Agent: Manage Taste learning and connected project context.
Taste: Review or forget learned project and user preferences.
MCP: Add an HTTP or local command server, test the connection, and view its available tools.
Account: View your profile, plan, billing, credits, and usage. You can also refresh account data or sign out.

MCP settings use the active project for project-specific configuration. Open the correct project before testing a project-specific server.

Updates

Command Code checks for updates in the background. When an update is available, the app shows a notice and installs it after restart. You can also install the latest version from GitHub Releases.

Windows preview updates may need to be installed manually while the installer is unsigned.

Troubleshooting

Why does Windows show an installer warning?

The Windows preview may be unsigned. Confirm that you downloaded it from the official Command Code Desktop App Releases page, then follow the options shown by Windows. Do not disable system security globally.

Why are Terminal or Git tools unavailable?

Check that your shell and Git work in the system terminal. Restart Command Code after changing your shell environment or installing Git.

Why is a project or file missing?

Check that the correct project is selected in the sidebar. Files, search, Terminal, Git status, and browser previews all use the active project folder.

Why does Browser not load my local preview?

Start the local app in Terminal and confirm the address works locally. Then enter that address in Browser. Reload Browser after restarting the server.

Why can't the agent edit a file?

Check that the correct project is active, the file is not locked or read-only, and Command Code can access the project folder. Review any pending approval in chat.

How do I report a problem?

Open a GitHub issue and include:

Command Code Desktop App version.
Operating system and architecture.
What you did before the problem.
What you expected and what happened.
A screenshot and exact error message, when available.

Next steps

Install the Command Code Desktop App.
Read Common Workflows for focused task examples.
Learn how permissions work across Command Code.
Report a Desktop App issue on GitHub.