How to Use Claude Code in the Terminal (CLI Setup, Step by Step)

In short: install with one command, run claude in your project folder, sign in, run /init to create CLAUDE.md, and keep permission prompts on.

Why use the CLI

The terminal works everywhere: Neovim, Vim, Emacs, IntelliJ's terminal, a remote Linux box. You are not tied to one editor. You can also script it with claude -p for one-shot jobs.

What you need

• A supported system: macOS 13+, Windows 10 1809+, Ubuntu 20.04+, Debian 10+ or Alpine 3.19+. 4 GB+ RAM.
• An Anthropic account: a paid Claude plan (Pro, Max, Team, Enterprise) or a Claude Console account (pay per use).
• A terminal: Bash, Zsh, PowerShell or CMD. Internet is required.

How it flows

Install steps

1. macOS, Linux or WSL: run curl -fsSL https://claude.ai/install.sh | bash.
2. Windows PowerShell: run irm https://claude.ai/install.ps1 | iex.
3. The installer shows no progress bar. Wait, then open a new terminal.
4. Check: claude --version prints a version number.
5. Go to your project: cd my-project, then run claude.
6. Sign in when asked (or later with /login). Check with claude auth status --text.
7. Native installs update themselves. To update by hand: claude update.

curl -fsSL https://claude.ai/install.sh | bash
claude --version
cd my-project
claude

Daily commands

Settings inside a session

1. /init: Claude reads the project and writes a starter CLAUDE.md. Edit it to be short and true.
2. Permission modes: press Shift+Tab to cycle modes (for example normal, auto-accept edits, plan). Beginners: stay in normal or plan.
3. /model: switch model. /compact: shrink a long chat. /usage: see what is using your plan.
4. Esc: stop Claude mid-step. /ide: connect to VS Code or JetBrains for diffs, when you run it in an external terminal.

Configuration files

1. CLAUDE.md (project root): rules, test command, files to avoid.
2. ~/.claude/settings.json (you) or .claude/settings.json (shared in the repo): permissions, environment variables, MCP servers.
3. Deny secret files so Claude never reads them:

{
  "permissions": {
    "deny": ["Read(./.env)", "Read(./secrets/**)", "Bash(rm -rf:*)"]
  }
}

First task (5 minutes)

1. In a small repo run claude, then type: “Explain this project in 5 lines.”
2. Then: “Add a test for the add function in utils.py and run pytest.”
3. Read each proposed edit and command. Approve with care.
4. Check with git diff yourself. Commit only what you understand.

Quick quiz

Save tokens and money

Start Claude in the right subfolder, not your whole home folder. Use claude -p with piped input for small jobs. Run /compact or start a fresh session for each new task. Keep CLAUDE.md short.

Save these cards