Start: CLI and VS Code

Start in 3 steps

1Install the CLIor VS Code extension2Sign in3Open a project folder,start talking

Getting started: CLI and VS Code

Command line (CLI)

Follow the official page for installation (overview). After installing, open a terminal in your project folder and type claude to start a conversation. Common ways to use it:

cd your-project-folder
claude                 # start an interactive conversation
claude -p "question"   # ask once, print the answer and exit (common in scripts)
claude --continue      # continue the previous conversation

VS Code

Install the Claude Code extension in VS Code, or just run claude in VS Code's built-in terminal. Both read the same configuration (CLAUDE.md, Skills, permissions, ...); only the interface differs. Official page: VS Code integration.

My habit: open the project folder in VS Code, look at the files on the left, and run Claude Code on the right or at the bottom. The files it should change and the diff after it changed them are right there in the editor.

Common commands and status

Typing / in the input box lists all available commands. The most used ones (full list on the official commands page):

CommandPurpose
/helpHelp and the command list
/statusShow the current state (version, model, account, connections, ...)
/clearClear the conversation and start over (use it when the context is messy or the topic changed)
/compactCompress a long conversation into a summary to free context
/memoryOpen and edit the CLAUDE.md memory files
/mcpView and manage MCP external tools
/permissionsView and change permission rules
/modelSwitch model
/initLet it read your project and draft a CLAUDE.md

There is also a status line (statusline) that can permanently show model, directory, cost and more under the input box; it is configured in settings.json.

The status words shown while waiting

While Claude Code is thinking or working it shows words in turn on screen: garnishing, thinking, working, planning, analyzing, exploring, building, crafting, processing, researching and so on.

They are only "still running" indicators. They do not mean a particular mode, and they do not mean it really did "planning" before "building". If the word keeps changing, it is not stuck. To use words you like, set spinnerVerbs in settings.json (the official description is "add or replace the verbs shown while a turn runs", see the settings reference).

To judge whether it is really stuck: see whether output keeps coming and whether the time is far beyond normal; if needed press Esc to interrupt and ask "what are you doing right now?".