Welcome to the VS Code Terminal Bible

The VS Code integrated terminal is just a command line inside your project. It lets you install tools, start local servers, run tests, use Git, and talk to coding agents without switching apps.

SOP: where to click

Terminal words in plain English

First five commands

pwd
ls
git status
node --version
npm --version

The safest first question when you open a folder you did not create — a cloned repo, a downloaded sample, or a project an AI generated for you — is simple: should I let this code run on my computer? VS Code answers it with a built-in feature called Workspace Trust.

What Restricted Mode does

When you open an unfamiliar folder, VS Code can open it in Restricted Mode and show a banner across the top. You can read, browse, and edit every file safely — but VS Code will not automatically run the project's tasks, start its debugger, or apply settings the project itself defined. Those are exactly the things that could run code without you asking. When you trust the folder, they turn back on.

When to trust, when to wait

How to trust a folder

• Click Manage or Trust in the banner at the top of the window, or open the Command Palette (Cmd/Ctrl + Shift + P) and search Workspace Trust.
• Trusted folders are remembered, so you usually only do this once per project.
• Want VS Code to pop up a prompt every time instead of just showing a banner? Set security.workspace.trust.startupPrompt to once in Settings.

Ask Your AI This

This project is open in VS Code in Restricted Mode and I did not write it.

Before I trust this folder:
1. Tell me what this project is and what it does.
2. List any files that run code automatically (tasks, scripts, build steps).
3. Flag anything that downloads, installs, deletes, or sends data anywhere.
4. Tell me plainly whether it looks safe to trust.

Do not change any files.

These are the commands non-technical builders use constantly. You do not need to memorize everything. Learn what each category does and copy the command when needed.

Command cheat sheet

Version checks

git --version
node --version
npm --version
python3 --version
code --version

Power terminal shortcuts

Most modern projects have the same loop: install dependencies, start a local server, open the browser, then stop the server when done.

Detect the project type

Most common web app commands

npm install
npm run dev
npm run build
npm test
npm run lint

Ask AI before installing

I opened this project in VS Code.

Please inspect the files and tell me:
1. What kind of project this is.
2. Which terminal command installs dependencies.
3. Which command starts it locally.
4. Which command tests or builds it.
5. Whether any command is risky or requires secrets.

Do not edit files yet.

When the server starts

• Look for a local URL like http://localhost:3000 or http://localhost:5173.
• Hold Command/Ctrl and click the URL, or copy it into your browser.
• Leave that terminal running while you test the app.
• Press Control + C when you want to stop the server.

Git is your undo system. GitHub is your cloud backup and collaboration hub. Use the terminal for the exact status, then use VS Code Source Control for visual review.

Safe Git loop

Everyday Git commands

git status
git diff
git branch --show-current
git add README.md public/index.html
git commit -m "Describe what changed"
git push

GitHub CLI power commands

gh auth status
gh repo view --web
gh pr status
gh pr create --draft --fill
gh pr view --web

Prompt: safe commit review

Before I commit, inspect the working tree.

Tell me:
1. Current branch.
2. Changed and untracked files.
3. Files that should not be committed.
4. A safe git add command using explicit file names.
5. A clear commit message.

Do not run git add, commit, push, reset, or checkout until I approve.

The terminal tells you what is really happening. Error messages are not failure; they are instructions for what to fix next.

What to run by project type

Error-message workflow

1. Copy the first error, not the whole noisy terminal if it is huge.
2. Include the command you ran.
3. Include the folder you were in.
4. Ask the AI to identify the root cause before changing code.
5. Rerun the same command after the fix.

Prompt: debug terminal error

I ran this command in the VS Code terminal:
[paste command]

I was in this folder:
[paste pwd result]

Here is the error:
[paste error]

Please explain in plain English:
1. What failed.
2. The likely cause.
3. The safest fix.
4. The exact command to verify the fix.

VS Code Tasks turn repeated terminal commands into menu items. This is useful when you always run the same dev server, build, test, or deploy command.

When to create a task

Beginner tasks.json example

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "Run dev server",
      "type": "shell",
      "command": "npm run dev",
      "problemMatcher": []
    },
    {
      "label": "Build project",
      "type": "shell",
      "command": "npm run build",
      "problemMatcher": []
    }
  ]
}

How to run a task

• Open Command Palette: Command/Ctrl + Shift + P.
• Search Tasks: Run Task.
• Select the task label.
• Watch the terminal output.

Extensions should make the terminal and project safer, not heavier. Install a small set first, then add more only when you feel a real need.

Beginner-friendly extension stack

Install extensions from terminal

code --install-extension GitHub.vscode-pull-request-github
code --install-extension eamodio.gitlens
code --install-extension dbaeumer.vscode-eslint
code --install-extension esbenp.prettier-vscode
code --install-extension ritwickdey.LiveServer
code --install-extension usernamehw.errorlens
code --install-extension ms-vscode-remote.remote-containers
code --install-extension ms-azuretools.vscode-docker
code --install-extension humao.rest-client

Good terminal habits make AI-assisted building much safer. The goal is not to become a command-line expert. The goal is to stop being surprised by commands.

Rules that prevent pain

Folder naming rules

Prompt: explain a command first

Explain this terminal command before I run it:
[paste command]

Tell me:
1. What it does.
2. Which folder I should be in.
3. Whether it changes files, installs packages, deletes anything, commits, pushes, or deploys.
4. A safer alternative if there is risk.
5. The verification command after it runs.

Most terminal problems are boring: wrong folder, missing install, wrong shell, server already running, or a stale terminal session.

Common problems

Reset your terminal calmly

1. Press Control + C if something is running.
2. Click the trash icon on the terminal panel to close the session.
3. Open Terminal -> New Terminal.
4. Run pwd and git status.
5. Try the command again, or paste the error into your AI assistant.

Prompt: terminal doctor

Act as my VS Code terminal doctor.

Ask me for:
1. The command I ran.
2. The full error.
3. The result of pwd.
4. The result of git status.
5. The operating system and shell if needed.

Then give me the smallest safe fix and one verification command.

This guide is written for non-technical AI Con Todo learners. It combines official VS Code concepts with practical project workflows.