CHAPTERS
- 0:04 – 0:14
Installation options overview across platforms and surfaces
The video opens by outlining where Claude Code can be used: terminal, web, or inside an IDE. It frames installation as straightforward and previews the different OS-specific methods.
- •Claude Code can run in the terminal, on the web, or via IDE integrations
- •Installation approach varies by OS (macOS/Linux/WSL vs Windows)
- •Different package managers and commands are available depending on preference
- 0:14 – 0:24
macOS/Linux/WSL install: curl one-liner vs Homebrew (auto-update tradeoff)
For Unix-like environments, the recommended approach is a curl one-liner for quick setup. Homebrew is also supported, but comes with the important limitation that it won’t auto-update.
- •Use a curl command to install in one step on macOS/Linux/WSL
- •Homebrew installation is available via brew install
- •Homebrew installs do not include auto-update capabilities
- •Choosing install method affects how updates are received
- 0:24 – 0:34
Windows install methods: PowerShell, CMD curl, and winget (update caveat)
Windows users can install via PowerShell or CMD using provided commands, with winget as another option. Similar to Homebrew, winget installs won’t auto-update.
- •PowerShell installation uses Invoke-RestMethod
- •CMD users can install with a curl command
- •winget is available as an alternative installer
- •winget installs do not auto-update
- 0:34 – 1:04
First run in a project directory: setup flow and authentication choices
After installation, you run Claude from your project directory and complete initial setup steps. The video highlights sign-in options and notes how directory scope determines what files Claude can access.
- •Run Claude from the project directory to begin
- •Initial prompts include theme selection and sign-in
- •Sign in with Pro, Max, or Enterprise account—or use an API key
- •Enterprise users should select the Claude Enterprise option
- •Claude can access the chosen directory and all subfolders
- 1:04 – 1:19
VS Code extension install: verified extension, restart, and opening Claude Code
The VS Code setup involves installing the official Anthropic extension and potentially restarting the editor. You can then launch Claude Code via the command palette or the Claude icon in the UI.
- •Install “Claude Code” from the Extensions panel
- •Ensure it’s the official Anthropic extension (blue check)
- •Restart VS Code if required after installation
- •Open via Command Palette: Claude Code → Open in New Tab
- •Launch via Claude logo when a file is open
- 1:19 – 1:34
VS Code configuration: opting out of UI for terminal-only workflow
If you prefer a more minimal experience, you can disable the UI integration and use the terminal flow instead. This is controlled through VS Code settings.
- •UI integration is optional in VS Code
- •Users can choose a terminal-only experience
- •Change behavior via the VS Code settings file
- 1:34 – 1:50
JetBrains IDE plugin: marketplace install and in-IDE pane experience
For JetBrains products, installation is done through the JetBrains Marketplace followed by an IDE restart. Claude Code appears as a logo that opens a pane mirroring the terminal experience while you work.
- •Install Claude Code plugin from JetBrains Marketplace
- •Restart the IDE after installing the plugin
- •Claude logo appears on reopen
- •Opens a pane with the terminal-like Claude Code experience
- •Designed to work alongside your normal development flow
- 1:50 – 2:05
Claude Desktop: enabling Code mode, folder permissions, and cloud work
Claude Code is also accessible within Claude Desktop after signing in. Toggling into Code mode provides a chat-like UI tailored for working within a specific folder and managing permissions, including cloud environments.
- •Install Claude Desktop and sign in first
- •Enable Claude Code via the “Code” toggle at the top
- •UI resembles Claude Chat but is project/folder-oriented
- •Supports selecting a folder and managing permissions
- •Can work in a cloud environment
- 2:05 – 2:35
Web version at claude.ai/code: GitHub-repo-only constraint
On the web, Claude Code is available at a dedicated URL and behaves similarly to the desktop app. A key limitation is that it only works with GitHub repositories.
- •Access via claude.ai/code
- •Experience is similar to the desktop app
- •Restricted to GitHub repositories only
- 2:35 – 3:01
Choosing the best surface: updates, integration depth, background use, and remote workflows
The video closes by comparing the strengths of each way to use Claude Code. Terminal gets features fastest, IDE integrations feel more native in editors, Desktop supports background operation, and Web is ideal for remote GitHub-based sessions.
- •Terminal is best for staying up to date; features ship there first
- •IDE integrations provide a tightly integrated editor experience
- •Desktop is useful for running in the background while multitasking
- •Web is good for remote work via GitHub and parallel sessions
- •Pick the approach that best matches your workflow
