Base Usage & IDE Integration
Core commands
Once inside the Claude Code REPL (run claude in your project directory):
| Command | What it does |
|---|---|
| Just type | Send a prompt to Claude |
/help |
Show all available commands |
/status |
Show session info, model, token usage |
/clear |
Clear conversation history (start fresh) |
/config |
Open interactive config editor |
/exit |
Exit Claude Code |
!command |
Run a shell command directly |
Ctrl+C |
Cancel the current operation |
Sending your first real task
> Build me a REST endpoint in routes/api.php that returns a paginated list of posts
Claude Code will:
- Read the relevant files in your project
- Show you what it plans to change (diff)
- Ask for confirmation before writing
- Execute the change
IDE Integration — VS Code
Install the Claude Code extension from the VS Code marketplace:
ext install anthropics.claude-code
This gives you:
- In-editor chat panel
- One-click "Ask Claude about this file"
- Diff viewer integrated into the editor
- Keyboard shortcut:
Cmd+Shift+C(macOS) /Ctrl+Shift+C(Windows/Linux)
IDE Integration — Cursor
Cursor has native Claude integration. You can also run claude in Cursor's terminal. For the best experience, keep Cursor's AI features for autocomplete and use Claude Code's REPL for autonomous multi-file changes.
IDE Integration — JetBrains
Run Claude Code in the built-in terminal. JetBrains' own AI Assistant doesn't conflict — they serve different scopes.
Workflow tip: "explain before changing"
Develop the habit of asking Claude to explain its plan before applying changes to unfamiliar code:
> Explain what you would change in the authentication service to add OAuth2 support,
but don't make any changes yet.
Review the explanation, ask follow-up questions, then give approval to proceed.