How to Open VSCode from Terminal Commands

Clicking through menus to launch your code editor wastes time you could spend writing code.

Learning how to open VSCode from terminal cuts seconds from every project switch. Those seconds add up fast.

The code command transforms your workflow. Open files, folders, or entire workspaces without leaving the command line interface.

This guide walks you through PATH configuration on Windows, macOS, and Linux. You’ll learn launch options, troubleshooting fixes, and shortcuts that experienced developers use daily.

Five minutes of setup. Faster project access forever.

How to Open VSCode from Terminal

Opening Visual Studio Code from the terminal is the process of launching the code editor using command line commands instead of clicking the application icon.

Developers need this when working with project directories, automating workflows, or switching between shell tasks and code editing quickly.

This guide covers 5 steps requiring 2-5 minutes and basic familiarity with your operating system’s command line interface.

Prerequisites

Before you start, make sure you have these ready:

• Visual Studio Code version 1.90 or later installed on your system
• Operating system: Windows 10/11, macOS 10.15+, or Ubuntu 20.04+
• Terminal or Command Prompt access
• Administrator permissions (Windows only, for PATH modification)

Time required: 2-5 minutes.

Skill level: Beginner.

If you haven’t installed the editor yet, check out our guide on what is VSCode to get started.

Step One: How Do You Verify VSCode Installation on Your System?

Check that Visual Studio Code exists on your machine before configuring terminal access.

The verification process confirms the executable path is accessible and the application launches correctly.

On Windows

Open the Start menu and type “Visual Studio Code”.

If the application appears in search results, your installation is valid.

On macOS

Open Finder and navigate to Applications folder.

Look for “Visual Studio Code.app” in the list.

On Linux

Run which code in your terminal.

If installed via Snap or APT, the output shows the binary location.

Ubuntu users can follow our how to install VSCode on Ubuntu guide if the editor is missing.

Step Two: How Do You Access the Terminal on Your Operating System?

Each operating system has different methods to open the terminal emulator or shell.

Accessing the correct terminal ensures your commands execute in the right environment.

Windows Terminal Access

Action:

• Press Win + R, type cmd, press Enter for Command Prompt
• Press Win + X, select “Windows Terminal” for PowerShell
• Search “Git Bash” in Start menu if installed

macOS Terminal Access

Action:

• Press Cmd + Space to open Spotlight
• Type “Terminal” and press Enter
• Alternative: Applications > Utilities > Terminal

iTerm2 users can use the same method or configure hotkey access.

Linux Terminal Access

Action:

• Press Ctrl + Alt + T (works on most distributions)
• Search “Terminal” in your application menu
• Right-click desktop and select “Open Terminal” (if enabled)

Once you have terminal access, learn how to open terminal in VSCode for integrated shell access.

Step Three: How Do You Add the Code Command to Your System PATH?

The code command needs to exist in your system’s PATH environment variable before terminal launching works.

This step creates the connection between typing “code” and executing Visual Studio Code.

Windows PATH Configuration

The VSCode installer typically adds the code command automatically.

Action:

1. Open Command Prompt
2. Type code --version and press Enter
3. If recognized, skip to Step Four

If the command fails, reinstall VSCode and check “Add to PATH” during setup.

macOS Shell Integration

macOS requires manual PATH configuration through the Command Palette.

Action:

1. Open Visual Studio Code manually
2. Press Cmd + Shift + P to open Command Palette
3. Type “Shell Command: Install ‘code’ command in PATH”
4. Press Enter and wait for success notification

This creates a symbolic link in /usr/local/bin/code.

Restart your terminal for changes to take effect.

Linux PATH Setup

Linux installations via Snap or APT usually configure PATH automatically.

Action:

1. Open terminal and run code --version
2. If command not found, check your installation method
3. For manual installs, add VSCode’s bin folder to your shell profile

Add this line to ~/.bashrc or ~/.zshrc for Bash or Zsh shells:

export PATH="$PATH:/usr/share/code/bin"

Run source ~/.bashrc to reload your shell configuration.

Understanding source control integration becomes easier once terminal access is configured.

Step Four: How Do You Open VSCode from Terminal Using the Code Command?

The code command launches Visual Studio Code directly from your shell.

Basic syntax accepts files, folders, or no arguments at all.

Basic Launch Commands

Action:

• code opens a new VSCode window
• code . opens the current project directory
• code filename.js opens a specific file
• code ~/projects/myapp opens a folder by path

The editor launches within 1-2 seconds on most systems.

Opening Multiple Files

Pass multiple file paths separated by spaces.

code index.html style.css app.js

All files open as tabs in the same workspace folder.

Opening in Existing Window

Use the -r flag to reuse the last active window.

code -r newfile.py

Useful when you don’t want multiple VSCode instances running.

Step Five: What Are the Common Code Command Options You Can Use?

The VSCode CLI includes flags that modify launch behavior and enable specific features.

These options speed up your software development workflow significantly.

Window Management Options

• code -n forces a new window regardless of settings
• code -r reuses the most recently focused window
• code --new-window same as -n, explicit syntax

File Comparison

Compare two files side by side using the diff flag.

code -d file1.js file2.js

Opens the built-in diff viewer showing changes between files, perfect for code refactoring reviews.

Learn more about how to compare two files in VSCode for advanced diff options.

Line Navigation

Jump directly to a specific line number on file open.

code -g filename.py:42

Opens the file with cursor positioned at line 42.

Add column number for precise positioning: code -g file.js:10:5

Wait Mode

The -w flag blocks the terminal until you close the file.

code -w config.json

Essential for Git commit messages and other CLI tools that need editor integration.

Verification

Confirm your setup works correctly before relying on it daily.

Testing the Installation

Run this command to verify everything:

code --version

Expected output: three lines showing version number, commit hash, and architecture (x64/arm64).

Functional Test

Create a test scenario:

1. Open terminal in any directory
2. Run code .
3. Confirm VSCode opens showing that folder’s contents

If the file explorer displays your directory structure, the configuration succeeded.

Troubleshooting

Common issues and their fixes when the code command fails.

Issue: “code” Command Not Recognized

Cause: PATH environment variable doesn’t include VSCode’s binary location.

Solution:

• Windows: Reinstall VSCode, check “Add to PATH” option
• macOS: Open VSCode, run Shell Command from Command Palette (Cmd + Shift + P)
• Linux: Verify installation with which code or reinstall via APT/Snap

Restart your terminal after any PATH changes.

Issue: VSCode Opens But Shows Empty Window

Cause: Invalid path or permissions problem.

Solution:

• Check the path exists: ls /path/to/folder
• Verify read permissions on the target directory
• Use absolute paths instead of relative ones

Issue: Permission Denied Error

Cause: Insufficient privileges for the target location or VSCode installation.

Solution for macOS/Linux:

• Check folder permissions: ls -la /path/to/folder
• For shell command install: sudo code --install-extension if needed
• Never run VSCode itself with sudo

Issue: Multiple VSCode Installations Conflict

Cause: Both stable and VS Code Insiders versions installed, or duplicate PATH entries.

Solution:

• Run which -a code (macOS/Linux) to find all code binaries
• Remove duplicate entries from your shell profile
• Use code-insiders command specifically for Insiders build

Issue: Terminal Hangs After Running Code Command

Cause: You’re using wait mode unintentionally or VSCode is starting slowly.

Solution:

• Press Ctrl + C if terminal seems stuck
• Remove -w flag if you don’t need wait behavior
• Check system resources if VSCode consistently launches slowly

Related Processes

Once terminal launching works, explore these connected workflows.

Version Control Integration

Combine terminal navigation with Git operations.

cd my-repo && code .

Opens your repository ready for commits, and you can connect VSCode to GitHub for seamless push/pull.

Python Development Workflow

Launch projects with the correct interpreter active.

After opening via terminal, learn how to run Python in VSCode and how to change Python interpreter in VSCode.

Code Formatting Automation

Set up format-on-save after terminal launch.

Check how to format code in VSCode and how to use Prettier in VSCode for automatic styling.

Configuration File Access

Quickly edit VSCode settings from terminal.

code ~/.config/Code/User/settings.json

Or follow the guide on how to open settings.json in VSCode through the UI.

Testing Integration

Developers using test-driven development can open test files directly.

code -g tests/test_main.py:15

Jumps to failing test line for quick debugging.

FAQ on How To Open VSCode From Terminal

What is the command to open VSCode from terminal?

The command is code followed by an optional file or folder path.

Type code . to open the current directory, code filename for a specific file, or just code for an empty window.

Why is the “code” command not working in my terminal?

The code command fails when VSCode’s binary isn’t in your system PATH.

On macOS, open VSCode and run “Shell Command: Install ‘code’ command in PATH” from the Command Palette. Windows users should reinstall with the PATH option checked.

How do I add VSCode to PATH on Windows?

Reinstall Visual Studio Code and check “Add to PATH” during setup.

Alternatively, manually add C:UsersYourNameAppDataLocalProgramsMicrosoft VS Codebin to your system environment variables, then restart Command Prompt or PowerShell.

Can I open a specific file at a certain line number?

Yes. Use the -g flag with the format code -g filename:line:column.

Running code -g app.js:25 opens app.js with your cursor at line 25. Useful when debugging issues in your codebase.

How do I open VSCode from terminal on macOS?

First, launch VSCode manually. Press Cmd + Shift + P to open the Command Palette.

Type “Shell Command: Install ‘code’ command in PATH” and press Enter. Restart your terminal. The code command now works in Bash or Zsh.

What is the difference between “code .” and “code -r .”?

The code . command opens a new window with the current folder.

Adding -r reuses the most recent VSCode window instead of creating another instance. Keeps your taskbar clean when switching between projects.

How do I compare two files using the code command?

Use the diff flag: code -d file1.txt file2.txt.

VSCode opens both files in a side-by-side diff view highlighting changes. Great for reviewing modifications before commits or checking configuration differences.

Can I open VSCode from Git Bash on Windows?

Yes. Git Bash uses the same PATH as Windows Command Prompt.

If code works in CMD, it works in Git Bash. If not, close Git Bash, add VSCode to PATH, then reopen the terminal.

How do I make terminal wait until I close VSCode?

Add the -w or --wait flag to your command.

Running code -w config.yml blocks the terminal until you close that file. Required for Git commit messages and other CLI tools expecting editor input.

Does the code command work with VS Code Insiders?

VS Code Insiders uses code-insiders as its command instead of code.

Both versions can coexist. Use whichever command matches the build you want to launch. The web development IDE features remain identical across builds.

Conclusion

Knowing how to open VSCode from terminal removes friction from your daily coding routine.

A single command replaces multiple clicks. Your developer workflow gets faster.

The setup takes minutes. Configure your PATH environment variable once, and the code command works everywhere: Bash, Zsh, PowerShell, or Command Prompt.

You’ve learned the essential terminal commands for launching files, folders, and diff comparisons. The troubleshooting section covers common PATH issues across Windows, macOS, and Linux.

Start using these shortcuts today. Open your next project directory with code .` instead of navigating through menus.

Small efficiency gains compound over time. Your shell integration with Visual Studio Code is now complete.

• Author
• Recent Posts

Bogdan Sandu

Bogdan Sandu specializes in web design, focusing on creating user-friendly websites, and innovative UI kits.

Many of his resources are available on various design marketplaces and for free on Codepen.

Over the years, he's worked with a range of clients and contributed to design publications like Design Your Way, Designmodo, WebDesignerDepot, WPDean, Speckyboy, and Slider Revolution among others.

Latest posts by Bogdan Sandu (see all)

• Tailwind CSS Cheat Sheet - June 9, 2026
• The Stuff Nobody Tells You About Hiring Web Design Services - June 9, 2026
• How to Create a Pull Request in GitHub Easily - June 8, 2026