Quickstart

In this quickstart guide, we'll walk you through the steps to get started with Command Code. By the end, you'll have a working setup, your taste learning active, and be ready to start building!

1

Install Command Code

Command Code requires Node.js 22 or newer (the current LTS), it will refuse to start on Node 20 and below. Check yours with node -v, and if it's older, read the upgrade guide for every option.

Install Command Code globally with npm:

Install Command Code

npm i -g command-code@latest

Verify the install:

Verify install

cmd --version

Command Code is available globally as command-code or the shorter alias cmd.

Windows

On native Windows the short alias is cmdc. In WSL it is cmd.

Where you run itAlias
macOS, Linux, WSLcmd
Native Windows (PowerShell, Windows Terminal, Git Bash)cmdc

cmd is already the built-in Windows command shell, so Command Code cannot claim that name there — but WSL is Linux, so cmd is free and every example in these docs works verbatim. On native Windows, read cmd as cmdc throughout: cmdc login, cmdc --version, cmdc -r, cmdc update. The full name command-code works everywhere. Set the shell code blocks to Windows and they rewrite themselves to cmdc, so you can copy them as-is.

2

Log in

Run the following command to log in to the CLI.

Login to Command Code

cmd login

This opens a browser to authenticate. Click the Authorize button to sign in and return to the terminal after the login successful message appears. You can create an API key and paste it in your terminal to log in.

Login successful

✔ Logged in as yourname API key stored in ~/.commandcode/auth.json Run cmd to get started.
Tip

Chrome may ask to allow access to your local network. Command Code runs a temporary local server to complete the OAuth callback. This is safe and expected. Click the Allow button to proceed.

3

Start coding with Command Code

Navigate to a project directory and run:

Run the Command Code CLI

cmd

The first time you run cmd in a project, Command Code asks whether to trust the files in that folder. Select Yes, proceed to continue. Command Code asks this once per project directory.

Tip

Skip this prompt with cmd --trust.

Next, Command Code checks for existing coding sessions. If none are found, it offers a taste learning demo. Select Yes, show me a demo to see how Command Code learns your preferences.

Importing your setup

If you've used Claude Code, Codex, Cursor, or another agent before, bring your setup over with /import/import claude, /import codex, /import cursor, /import pi, /import opencode, or /import gemini. To build your taste profile from those existing sessions, use /learn-taste in a session or run cmd learn-taste.

4

Run your first prompt

Let's run a small prompt. Paste the following prompt in the input box.

Prompt

Build a date.js CLI that tells ISO format of date. Use commander.js and pnpm.

Taste learnings land inline in the transcript as they happen — a green TASTE row with what was learned, its confidence, and a link to the file it went to. Open .commandcode/taste/taste.md to see the whole profile:

.commandcode/taste/taste.md

# CLI - Use pnpm as package manager. Confidence: 0.50 - Use commander.js for CLI argument parsing. Confidence: 0.50

As you work, Command Code builds a taste profile in .commandcode/taste/. It continuously learns which package manager you use, which libraries you prefer, and how you structure code. These preferences carry into future sessions - and only relevant taste context loads per session.

Useful shortcuts

Run /hotkeys to see every keyboard shortcut. See the keybinding reference for the full list and how to remap them.

You've installed Command Code, logged in, and run your first prompt with taste learning active. From here, every session only gets smarter as Command Code adapts to your libraries, patterns, and learns your taste as you build.

Keep Command Code up to date for the latest features and fixes:

Update Command Code

cmd update

Questions or feedback? Join the Discord community.