Command Code Desktop App

The Command Code Desktop App brings project-aware chat, live agent activity, files, Git changes, a terminal, local browser previews, and plans into one workspace. The agent runtime is included, so you do not need to install the Command Code CLI.

Install

Choose your operating system and follow the steps.

sudo apt install ./CommandCode-*.deb

Getting started

Navigate Desktop

The workspace has three persistent areas:

Sidebar

• 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 the active workspace.
• Select a chat to restore its transcript and continue the session.
• Use the project action beside a project to start a new chat.
• Open the account menu at the bottom for account details, Settings, and sign out.
• Collapse or reopen the sidebar whenever you need more room for chat and the workbench.

The active project is the boundary for agent file operations, terminal sessions, Git changes, and browser preview discovery. Check the project shown below the composer before starting a task.

Chat and composer

Use the composer to describe a task, add context, select a model, choose a permission mode, and send or stop a run.

• Type @ to attach a project file.
• Add pasted text or images when the task needs visual or written context.
• Send a follow-up while the agent is working to queue it for the current chat.
• Read tool rows to see what is running, completed, failed, or waiting for approval.
• Answer an agent question from the answer surface that appears in the composer.
• Check the selected project, model, and permission mode before sending sensitive work.

Workbench

Open the workbench from the right side of the workspace. Use Open a view to add Terminal, Changes, Files, Plan, or Browser. Each view opens as a tab, and you can close tabs independently.

Changes

Changes shows the complete Git working tree for the active project:

• Added, modified, deleted, and untracked files.
• Total additions and deletions.
• Expandable file diffs.
• Open-in-Files actions.
• Per-file discard with confirmation.
• Current branch selection.
• Commit, commit and push, or push from the Ship menu.

Committing includes all current changes in the project, not only edits made by the agent. Review every file in Changes before shipping.

Files

Files gives you a searchable project tree, source and text previews, direct text editing, image preview, and navigation to lines referenced by chat, tools, Terminal, or Changes. Save an edited file with the save action shown by the app.

If a file changes on disk while you have an unsaved edit open, review the conflict before replacing the newer version.

Terminal

Terminal starts your shell in the active project. Use it to run the app, execute tests, inspect logs, and perform additional verification. Development URLs printed in Terminal can be opened in Browser.

Plan

Plan shows the current chat's proposed implementation plan. Review the scope and order, then refine the plan, accept it, or ask the agent to build it.

Browser and design mode

Browser opens a local development URL inside Command Code.

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

Design mode lets you:

• Hover over and select an element in the local preview.
• Send the selected element and page context directly to the active chat.
• Ask the agent for a design fix, review, responsive pass, or implementation change.
• Preview supported style adjustments directly in the page.
• Apply supported changes to source files.
• Undo direct 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

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.

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

Settings, account, and MCP

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

• General: Choose default model behavior, permissions, workbench behavior, and terminal options.
• Appearance: Select a 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 inspect its available tools.
• Account: View your profile, plan, billing, credit, and usage information, refresh account data, or sign out.

MCP settings use the active project when resolving project-scoped configuration. Open the intended project before testing a project-specific server.

Updates

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

Windows preview updates may remain manual while the installer is unsigned.

Troubleshooting

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.