Install Claude Code, Gemini CLI & Codex CLI
The complete setup for AI coding tools — built for dealership teams starting from zero. Install the dependencies first, in order, then the AI tools last. Copy-paste commands for Windows, Mac, and Linux.
Step 1 — Install the dependencies (in this order)
Install these top to bottom. After each one, open a new terminal and run the verify command to confirm it worked.Short on time? Node.js is non-negotiable (the AI tools won't install without it). Python and Git round out the essentials; Google Cloud CLI, VS Code, and Docker can wait until you need them.
Node.js (LTS)
EssentialThe runtime + npm package manager. Every AI CLI below installs through npm, so this MUST come first.
Python 3.12
EssentialThe language most AI tooling and MCP servers are built in. Needed for the broader AI toolchain.
Git
EssentialVersion control — your undo button when AI changes code. The CLIs use it to track every edit.
Google Cloud CLI (gcloud)
For cloud / deploy workDeploy apps and use Google Cloud services. Needed once you push things to the cloud — skip it if you're only trying the tools locally.
VS Code
OptionalThe editor that plays nicely with every AI tool, with a built-in terminal you'll launch the CLIs from.
Check everything at once
Once the dependencies are in, open a new terminal and run this one line. Every item should print a version number. Anything that says "not recognized" / "command not found" still needs installing — or just a fresh terminal window.
node --version; python --version; git --version; gcloud --versionStep 2 — Install the AI tools (last)
Now that Node.js is in place, each AI CLI is a single npm command. Install whichever you want — they happily coexist. After installing, open a terminal in your project folder and type the launch command.
Claude Code
Anthropicnpm install -g @anthropic-ai/claude-codeclaudeGemini CLI
Googlenpm install -g @google/gemini-cligeminiCodex CLI
OpenAInpm install -g @openai/codexcodexDon't use sudo with these npm commands — it causes permission headaches. If you hit a permissions error on Mac/Linux, see Troubleshooting below.
Your first session (60 seconds)
You're set up — here's the fastest way to a first win. (Examples use claude; swap in gemini or codex if you prefer.)
- 1
Open a terminal in a folder — or make a fresh one:
mkdir my-first-project; cd my-first-project - 2
Start the assistant:
claude - 3
Sign in when your browser opens, then come back to the terminal.
- 4
Ask it something in plain English. Try typing:
"Make a simple web page that says 'Welcome to [your dealership]' with our phone number."
You stay in control. The assistant shows you each change and asks before editing or running anything — nothing happens without your OK.
Launch from anywhere (Windows)
After install, the claude, gemini, and codex commands already work in any folder. To make them faster, add short cc / gg / cx shortcuts to your shell profile.
First, a one-time step: Windows blocks scripts by default, so the shortcuts won't load until you allow them. Run this once in PowerShell:
Set-ExecutionPolicy -Scope CurrentUser RemoteSignedThen paste this block to add the shortcuts, and restart your terminal:
if (!(Test-Path $PROFILE)) { New-Item -ItemType File -Path $PROFILE -Force }
Add-Content $PROFILE 'function cc { claude $args }'
Add-Content $PROFILE 'function gg { gemini $args }'
Add-Content $PROFILE 'function cx { codex $args }'
. $PROFILE
Write-Host "Done. Type cc, gg, or cx in any folder."If a command isn't recognized right after installing, close and reopen your terminal — the PATH only refreshes in new windows.
Troubleshooting — the usual snags
"command not found" or "is not recognized" right after installing
Close the terminal and open a brand-new one — the PATH only refreshes in new windows, so a just-installed command won't be found in a terminal that was already open.
Windows: the cc / gg / cx shortcuts or an install one-liner won't run
Windows blocks scripts by default. Open PowerShell and run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned (answer "Y"), then try again. This is safe and only affects your user account.
"python" is not recognized (Windows)
Re-run the Python installer and tick "Add python.exe to PATH" on the very first screen, then reopen your terminal.
npm permission error (EACCES) on macOS / Linux
Don't reach for sudo — it causes more problems. Point npm at a user-owned folder instead: npm config set prefix ~/.npm-global then add ~/.npm-global/bin to your PATH and reinstall.
It installed but won't sign in
Confirm you have the right account/plan for that tool (see each one above), then run it again — it reopens the browser sign-in page.
Other AI tools worth knowing
Beyond the coding CLIs, these are worth a look. The same dependencies (Node.js especially) cover the ones you install yourself.
OpenClaw
Open sourceA self-hosted personal AI assistant you can message from WhatsApp, Telegram, Slack, and more. Installs via npm like the coding CLIs above (needs Node.js).
npm install -g openclaw@latestHermes (Nous Research)
Open sourceNeutrally-aligned, open-source AI models — plus the Hermes Agent, an open agent with persistent memory you can run yourself.
Quick reference: what each piece does
| Tool | In plain English |
|---|---|
| Node.js | Runs the AI CLIs and add-ons. Bundles npm, which installs all three tools. Install first. |
| Python | The language behind most AI tooling and MCP servers. |
| Google Cloud CLI | Deploy apps and use Google Cloud services from the terminal. |
| Git | Tracks every change so you can undo anything the AI does. |
| VS Code / Docker | Editor with a built-in terminal / container packaging. Both optional. |
| Claude Code · Gemini CLI · Codex CLI | The AI assistants that read and edit your files from the terminal. Install last. |
Want AI working for your dealership — not just on your laptop?
We help dealers put AI to work on real problems: inventory, leads, compliance, and marketing. Get a free audit and we'll show you where it pays off first.