The Veil

When you open a terminal in VS Code, is it PowerShell blue? That default shell was chosen for you, not by you. The AI that’s helping you code assumes Bash. If your terminal doesn’t match, you’re not building. You’re translating.

The Dross

The AI speaks Bash. Every path it gives you, every command it suggests, every script it writes – Bash. When your terminal is PowerShell, every / becomes a \ you have to fix by hand. You’re spending mental energy on translation instead of on the problem.

The Strike

Set Bash as your default terminal in VS Code.

1. Open the Terminal in VS Code.
2. Click the dropdown next to the + icon.
3. Select “Select Default Profile”.
4. Choose Bash (or WSL/Ubuntu).

Verify it worked:

echo $SHELL

You should see /bin/bash. If you do, the switch is done.

The Truth

Consistency is infrastructure. When your terminal matches what the AI expects, its suggestions run the first time. You stop second-guessing whether a command failed because of the code or because of the shell. That’s one less variable between you and knowing.

Next up: your terminal is set up. Now let’s open a project in VS Code without touching the mouse.

Every time you move your hand to the mouse to find a terminal, you’re losing the race against your own AI. I was clicking through the View menu for months before I found this. VS Code has a terminal built in, and you can summon it without touching the mouse.

The Dross

Vibe-coding is high-frequency work. You’re jumping between the code the AI gave you and the terminal where you need to run it. If that jump takes three clicks, you’ll stop doing it. You’ll start “guessing” if the code works instead of “knowing.”

The Strike

Summon the integrated terminal with one keystroke. Same shortcut on every platform.

Ctrl + `

This works in VS Code on all platforms. Mac users: Ctrl, not Cmd.

Try it now. Open and close the terminal five times in five seconds. Feel the friction disappear. You’re no longer visiting the terminal. You’re living in it.

The Truth

Every hallucination your AI generates has a name, a path, or a dependency you can check. The terminal is the forge where you test what the AI shaped. One keystroke closes the gap between “the AI said so” and “I know it works.” That gap is where bad code ships.

Next up: we will discuss how not all terminal windows are created equal.

I was introduced to computing on a Commodore and then moved to a DOS-based PC. Both used a terminal window as the primary interface, and I figured out the basics of both. I was comfortable typing commands before I ever used a mouse. Then college introduced me to UNIX, and I hit a wall. I avoided it for years and lived safely in the comfort of the Windows GUI.

Eventually, I came back. I was an aspiring developer, and by the late nineties, I switched my home computer’s operating system to Linux. I had to start learning bash and the terminal. It took time to get comfortable with it.

Those skills sat in the background for years. Now AI has shown up, and they are more valuable than ever.

The Dross

AI is fast. It generates code, writes config files, and scaffolds entire projects. It also lies. Confidently. It will tell you to import a library that does not exist, reference a file it never created, and call a method that was deprecated two versions ago. It presents all of this the same way it presents correct code: cleanly, with explanation, and zero hesitation.

If you only work inside the chat window, it all seems like reality.

The terminal is where you find out. Run the code. Read the error. Check if the file actually exists. That is how you burn away what is false and keep what is real.

The Strike

This series is one command at a time. Each post is short. Each post has something you can run.

Start here:

ls

That is it. List what is in your current directory. The AI told you it created three files. Did it? ls will tell you the truth.

This is the whole series in one command. The terminal does not guess. It does not hallucinate. It reports what is actually there.

The Truth

The terminal took me years to get comfortable with. I am not going to tell you it is easy or that you will love it immediately. What I will tell you is that it is the one part of your workflow that will not deceive you.

Coding with AI moves fast. The terminal is how you keep up without getting lost.

This series will build that up one command at a time. Next up: getting the terminal open and in front of you.