How to set up VS Code for your first vibe coding project
A beginner-safe VS Code setup for your first vibe coding project: open the right folder, keep Workspace Trust on, sign into the correct GitHub account, and prove Copilot is actually working before you start.
How to set up VS Code for your first vibe coding project
Last updated: 2026-04-17 · Tested against VS Code workspace, Workspace Trust, terminal, and GitHub Copilot setup docs
Contents
- Prerequisites
- Recommended settings / defaults
- Install / Enable
- First-run verification
- Failure modes / troubleshooting
- Why should you keep the setup boring on purpose?
- FAQ
This is not a best-stack debate. It is a first-run setup job. I have watched beginners lose time when the editor, terminal, and account all look right at a glance but disagree underneath.
For this post, vibe coding means building with an AI assistant beside you instead of writing every line alone. A workspace is the folder VS Code treats as the project root, including its files, settings, and terminal starting point (VS Code workspaces). Workspace Trust is VS Code's safety check for deciding whether a folder can run extensions and features that run code, or stay in Restricted Mode (Workspace Trust).
If you want the Codex version of the same editor setup problem, see Codex VS Code setup for beginners who want the pro defaults.
That leaves four things that need to agree before you type anything clever: the project root, the trust state, the GitHub account, and one proof check. VS Code's workspace docs treat opening a folder as the normal project model, and code . opens the current folder in the editor (VS Code workspaces).
Prerequisites
Before you start, make sure you have four things:
- A desktop install of VS Code
- A GitHub account you can sign into inside VS Code
- One local folder for the project
- Copilot access if you want AI suggestions on day one
Recommended settings / defaults
These are the defaults I would hand to any beginner:
| Setting area | Keep this default | Why it helps on day one |
|---|---|---|
| Project opening | Open a folder or workspace | Loose files create weird terminal roots and missing project context |
| Trust | Keep Workspace Trust on | Restricted Mode is useful for unknown code, but confusing when you expected extensions to run |
| Copilot plan | Start with Copilot Free if needed | GitHub documents a free starting path if you do not already have a paid plan (GitHub Copilot plan docs) |
| Scope | One folder, one terminal, one starter file | Fewer moving parts means fewer fake failures |
If you want the shortest safe path, this is the whole first-run workflow in one terminal:
$ mkdir my-first-vibe-project
$ cd my-first-vibe-project
$ code .Install / Enable
- Confirm the prerequisites.
Before you expect Copilot to help, make sure you have a desktop install of VS Code, a GitHub account you can sign into in VS Code, and a local folder you own or understand. If the folder does not exist yet, create one now. In my own first-run checks, I verify the folder before I judge the editor.
$ mkdir my-first-vibe-project
$ cd my-first-vibe-project- Open the project as a folder, not as a loose file.
In VS Code, choose File > Open Folder... and select your project folder. From your terminal, change into the folder and run:
$ code .When this works, the Explorer should show that folder as the project root. The integrated terminal should open there too (VS Code workspaces, VS Code terminal docs).
- Keep Workspace Trust on, but only for code you actually trust.
If VS Code shows a trust banner, stop and read it. Restricted Mode is not a bug. It is the editor warning you that some features and extensions may stay limited until you trust the folder (Workspace Trust).
Trust the folder if it is your code or code you understand. Keep it restricted if it came from somewhere sketchy or unclear. Missing behavior here is often Restricted Mode, not a broken editor.
- Sign into the right GitHub account for Copilot.
Open the Accounts menu in VS Code and sign into GitHub. If you signed in before, confirm the active account is the one with Copilot access. VS Code's Copilot setup docs include the account-switching path when the wrong GitHub account is active (Copilot setup in VS Code).
- Create one starter file and wait for the first suggestion.
Inside the project folder, create index.html and type <!DOCTYPE html>. VS Code's Copilot getting-started guide uses that exact starter file and shows the inline ghost-text flow with Tab to accept the suggestion (Get started with GitHub Copilot in VS Code).
$ touch index.html
$ code index.html
First-run verification
Open the integrated terminal in VS Code and run the checks in order. I usually stop here before I trust any AI suggestion.
I found that pwd catches the wrong-folder mistake faster than reading Explorer labels.
- Confirm the terminal is in the workspace root.
$ pwd
$ lsThe terminal docs say the integrated terminal opens in the workspace root by default, so the path from pwd should match the folder you opened in Explorer and ls should show the files you expect (VS Code terminal docs).
A reliable signal is Explorer showing your project folder as the root and ls listing the files you expect in that same folder.
In practice, I check the terminal before I trust anything Copilot says. That keeps the rest of the tutorial honest.
You know it worked if: pwd prints your project folder, ls shows index.html after you create it, and code . opens the same folder you expected. If any of those three checks fail, stop and fix the folder before you blame Copilot.
- Confirm Copilot can offer and accept a suggestion.
Open index.html, type the same line again, and watch for ghost text. If the suggestion appears and Tab accepts it, Copilot is working at the most basic level (Get started with GitHub Copilot in VS Code).
When I troubleshoot beginner setups, I check account, trust state, and workspace root first. The order matters because the wrong account can hide a good install.
Failure modes / troubleshooting
Beginner setup needs named symptoms, likely causes, and exact fixes.
- Copilot does not appear, or VS Code says access is missing.
Symptom: You expect suggestions, but nothing shows up, or Copilot looks unavailable.
Likely cause: You are signed into the wrong GitHub account in VS Code, or the active account does not have Copilot access.
Exact fix: Open the VS Code account controls, sign out of GitHub in the editor, then sign back in with the account that has Copilot access. If you do not have a paid plan, start with Copilot Free through GitHub's documented setup path (Copilot setup in VS Code, GitHub Copilot plan docs).
- Features look disabled and you see Restricted Mode.
Symptom: Some extensions or code-executing features are limited, and VS Code shows a trust warning.
Likely cause: The folder is open in Restricted Mode because the workspace is not trusted.
Exact fix: Trust the folder only if you own the code or understand where it came from. If you do not trust it, leave it restricted and accept that some features will stay limited. That is working as designed, not failing silently (Workspace Trust).
- The terminal or settings behave oddly because the project was opened wrong.
Symptom: The Explorer looks thin, project settings do not behave the way you expect, or the terminal starts in a strange directory.
Likely cause: You opened a single file instead of the parent project folder.
Exact fix: Close the loose file view, then reopen the parent folder with File > Open Folder... or by changing into the project directory and running code . (VS Code workspaces).
code .says the command is not found.
Symptom: The folder opens in your file manager, but the terminal cannot launch VS Code.
Likely cause: The code command is not installed in PATH yet.
Exact fix: Open the Command Palette in VS Code, run Shell Command: Install 'code' command in PATH, then retry code . from the project folder. If that still fails, open the folder from File > Open Folder... and keep working there instead of guessing.
- If you still cannot tell what failed, reset the order.
Symptom: VS Code opens, but the editor still feels wrong and you cannot isolate the problem.
Likely cause: You are checking the right pieces in the wrong order.
Exact fix: Reset in this order: folder, trust, account, file. Reopen the project folder, confirm you are not in Restricted Mode, confirm the active GitHub account, then reopen index.html and type <!DOCTYPE html> again. That gives you one clean pass instead of a pile of guesses.
Why should you keep the setup boring on purpose?
Keep the setup boring enough that you can explain it in one breath: one folder as the workspace root, Workspace Trust on for code you trust, one GitHub account with Copilot access, one terminal check, one accepted suggestion.
That is enough to start. The beginner win is not maximum AI. It is a setup that does not lie to you.
FAQ
- Do I need to reinstall VS Code if Copilot does not appear?
Not first. I would check the GitHub account, the trust state, and the workspace root before I reinstall anything.
- Can I stop after the root and trust checks if I am not ready for Copilot yet?
Yes. The folder and trust checks are still useful on their own. You can leave the AI step for later and still have a sane workspace instead of a loose file pile.
- How do I tell a bad account from a bad install?
If
code .opens the right folder and Restricted Mode is not blocking the editor, the next thing to inspect is the GitHub sign-in. That ordering keeps you from debugging the wrong layer.
- What if ls hides the files I expect?
Use
ls -aif you suspect hidden files,.git, or dotfiles are part of the confusion. That command is often better than plainlsfor a first setup check.
- Do I need index.html specifically?
No, but a tiny starter file makes the first suggestion easier to judge. I use
index.htmlbecause the Copilot docs already demonstrate the flow with that file and the file name is easy to remember.
Ready to apply this? Read Codex VS Code setup for beginners who want the pro defaults if you want the AI companion version of the same workflow, then read You Don't Need an AI Agent if you want to keep the rest of the stack lighter than the hype.
Read Codex VS Code setup for beginners who want the pro defaults | Read You Don't Need an AI Agent