anfloy.AcademyBook a call

Foundation · 01 · Setup from scratchLesson 2 of 4

Install: terminal, VS Code & first run

45 min working time · Week 1

By the end of this lesson you can
  • Install Claude Code and authenticate
  • Set up VS Code (or your editor) with the extension
  • Run your first session and understand the interface

Install the native way

Three things get done in the next 45 minutes: Claude Code installed, logged in, and your first session run in both the terminal and VS Code. Use the native installer - it auto-updates, which matters because Claude Code ships improvements weekly and stale versions miss features this course depends on.

macOS / Linux / WSL - paste into your terminal
curl -fsSL https://claude.ai/install.sh | bash
Windows - paste into PowerShell
irm https://claude.ai/install.ps1 | iex

Other paths exist if you need them: Homebrew (brew install --cask claude-code - stable channel, runs about a week behind), WinGet (winget install Anthropic.ClaudeCode), and npm (npm install -g @anthropic-ai/claude-code - which now installs the same native binary; you only need Node to install it, not to run it).

Verify the install worked
claude --version
claude doctor

claude doctor is your health check - it inspects the install and flags anything wrong. Run it whenever something feels off. To update later: claude update (the native installer mostly does this for you).

Log in

The binary is installed; now it needs to know who you are. First run triggers a browser login, and the whole flow takes under a minute when the seat is right.

  1. Open a terminal and type: claude
  2. On first run it opens your browser to log in. Use the account with your Claude Code seat - your work account, not a personal one.
  3. Approve the login in the browser, then come back to the terminal. You are in a session.
  4. Type /status and press Enter. It shows which account and plan you are authenticated with. Confirm it says your org, not a personal Pro account.
  5. If you ever need to switch accounts: /logout, then /login.

VS Code: the editor setup

The terminal works everywhere, but most operators are happier in VS Code: you see file changes as visual diffs, you can @-mention files, and you can review plans before Claude acts. The extension also installs in Cursor if that is your editor.

  1. Install VS Code if you do not have it (free, code.visualstudio.com).
  2. Open the Extensions panel, search for Claude Code, and install the official Anthropic extension.
  3. Open any folder (File > Open Folder) - Claude Code always works inside a folder, which becomes its workspace.
  4. Open the Claude Code panel and confirm it picks up the login you did in the terminal.

One engine, six surfaces

Claude Code now runs in seven places, all the same engine underneath: the terminal CLI, the VS Code extension, a JetBrains plugin, the Desktop app (visual diff review, parallel sessions, a built-in browser, scheduled tasks; macOS and Windows, Linux in beta), the Web at claude.ai/code (cloud sessions, also on the iOS app), Claude in Chrome (generally available since July 2026 on direct Anthropic plans: Claude drives your browser for web tasks), and Claude Tag in Slack (beta, Team and Enterprise: tag @Claude in a channel and it works as a shared teammate; launched June 2026 and is replacing the earlier Claude in Slack app on those plans).

There are also bridges between them: Remote Control (out of research preview since August 2026) lets you continue a local session from your phone, and claude --teleport pulls a web session into your terminal. You do not need any of this in week one - just know the terminal is not the only door.

Related but distinct: the Desktop app also carries the zero-setup document-and-spreadsheet workflow that launched as Cowork. Anthropic's product page now reads 'Claude Cowork is now just Claude', so the tab label may not match older screenshots. The positioning holds: that surface for files-and-documents people, Claude Code for anyone who needs repos, connections, skills, and automation - which is what this course builds. Same Claude underneath.

Your first session: a guided tour

  1. In the terminal, cd into any folder with some files in it, then run: claude
  2. Ask something about the folder: "What's in this folder? Give me a one-paragraph summary." Watch it read files and answer.
  3. Reference a specific file with @ - type @ and start typing a filename, then ask a question about it.
  4. Press Esc while Claude is working. It stops. This is your interrupt key - you are always in control.
  5. Type /clear to wipe the conversation and start fresh. You will use this constantly.
  6. Type /status one more time to see your account, model, and settings at a glance.

Two more things to know exist, both covered properly in week two's 'Models, effort and cost' lesson: /model switches models (Opus 5.5 is the default on every plan; Sonnet 5 is the fast, cheaper option; Fable 5.1 is the top model for the hardest long autonomous work; Haiku 4.5 is for cheap bulk work), and /effort sets how hard the model thinks, from low to max. Both save your choice as the new default (press s to make it session-only), so if sessions suddenly feel different, check what you left them on.

Do this now

Sources and further reading

We set it up with you

Want us to set it up with you, end to end?

Three one-on-one sessions. We train you on your real stack and build your first agents together, until you can run it yourself. You keep everything.