How to Use Claude Code: Real Usage After Install (Commands, VS Code)

How to actually use Claude Code after installing — run claude, reference files with @, approve diffs, key commands/shortcuts, interactive vs one-shot, and the VS Code extension.

🌐 This article was machine-translated and may contain inaccuracies. Refer to the Korean original if in doubt.

Once you've installed Claude Code, here's how to use it. The core is simple — run claude in your project folder and tell it what to do in plain language; it reads and edits files directly. Before changing anything, it always shows a diff and asks for approval.

Claude Code basic flow 1. Run claude in folder 2. Ask request with @file 3. Review diff approve / reject 4. Iterate /rewind to undo Changes are always shown as a diff for approval first. Undo with /rewind if needed.

Getting started

  1. Open a terminal in your project folder and run claude. On first run you'll log in via the browser (OAuth) once.
  2. After the welcome screen you get an interactive prompt. Type your request in natural language.
# after cd into your project folder
claude

Claude can see the folder you launch in and its subfolders, so be mindful of where you run it.

Asking + referencing files

Just ask in plain language. To point at a specific file, type @ then the path (autocomplete supported); that file's content is injected into the conversation.

@src/pages/Home.tsx change the header text to 'Welcome'

Claude shows the change as a diff (preview) and asks for approval — you can accept, reject, or ask for revisions.

Handy commands & shortcuts

  • / — list available slash commands
  • @path — add a specific file to context
  • ! — run a terminal command and feed the output to Claude
  • ? — show shortcuts / Tab autocomplete / history
  • Esc — stop the current action
  • /rewind or Esc twice — roll back to a previous checkpoint (a snapshot is saved on every edit)
  • /login switch accounts · /mcp manage MCP servers

Two modes

  • Interactive (default): open a session with claude and go back and forth. Good for complex implementation.
  • One-shot: claude -p "list every TODO left in src/api" runs once and returns a result. Good for scripts, CI, and quick lookups.

Using it in VS Code

Two ways:

  • Official extension ("Claude Code for VS Code"): adds a sidebar panel and a diff view where you approve changes with a click. (Works in Cursor too, since it's a VS Code extension.)
  • Built-in terminal: run claude directly; file changes show up in your editor tabs immediately. MCP setup, the ! command, and some slash commands are CLI-only.

Safety

By default Claude Code requires approval before writing files or running commands (Ask mode). You can configure permissions to block dangerous commands (force pushes, deletes). Every edit is saved as a checkpoint you can undo with /rewind.

Getting more out of it

Writing your project's structure, rules, and common commands into a CLAUDE.md makes every session faster and reduces mistakes. See the CLAUDE.md guide. To connect external tools, see the MCP connection guide.

Disclaimer: Claude Code is included with Claude Pro/Max/Team/Enterprise subscriptions or usable via pay-as-you-go API (inclusions/pricing vary). Commands, shortcuts, and extension behavior can change by version — check the official docs (code.claude.com/docs) for the latest. This site is not affiliated with Anthropic.

Keep reading

Have a question or want to share how you use Claude?

Join the community to share tips with other users, or explore more guides.