🤯Mishaps and Brain Twists: What ACTUALLY Happens When a No-Code Builder Installs Claude Code on Windows

Let me paint you a picture. 🎨

First, a little context about me.

I am a low code/no code builder through and through.

Lovable? That's my comfort zone.

Claude Code? Open Claw? No, really — These terminal-based tools are about as far from my natural habitat as you can get.

However.

I've just finished binge-watching four Claude Code videos from Nate Herk in AIS+ and I am 🔥FIRED UP! These videos a great, and I am excited to get started.

My interpretation of Claude Code is it's basically like having a senior developer living inside your terminal, building apps for you while you sip coffee.

And the skills, the loops, all the good stuff I picked up from those videos — I am READY to put it all to work.

I want that life.

I deserve that life.

So I go to install it.

What I thought would happen:

Type one command.

Done. Sip coffee.

What actually happened:

A 2-hour odyssey involving Git Bash,

hidden folders, PATH variables,

and at least three existential crises. 🤷 😂

🛠️ The Setup:

Windows Is Not macOS

Here's the thing EVERYBODY tells you upfront —

Claude Code loves Mac and Linux.

Windows? Windows gets the "bless your heart" treatment.

The official docs mention something called Git Bash, which is basically a way to trick Windows into pretending it's Linux.

Fine.

I install Git for Windows.

Straightforward enough.

Then I try to paste a command into Git Bash.

Ctrl+V doesn't work.

Right-click. Paste. Nothing. 🫠

Turns out you have to use Shift+Insert to paste in Git Bash.

A fun little secret the universe decided not to tell me.

The PATH Problem (A Love Story)

After installing Claude Code, I type claude into Git Bash and get:

bash: claude: command not found🤦

It installed.

I can see the file sitting there on my computer.

But my terminal doesn't know it exists.

This is the computer equivalent of your friend standing right next to you while you call their name and they don't respond.

The fix? You have to tell Windows where to find Claude by editing something called your PATH — essentially a list of places Windows looks when you type a command.

To do that you go to: System Properties → Advanced → Environment Variables → User Variables → Path → Edit → New → paste the folder path → OK → OK → OK

Yes, three OKs. Windows loves OKs.

💰The Commitment Tax

At some point during all this, I realized my main laptop was a mess of old software, conflicting settings, and general chaos. Not exactly the clean environment you want when you're trying to get a finicky terminal tool working.

So I did what any completely reasonable person would do. LOL!

I wiped an old laptop and dedicated it entirely to Claude Code.

Full factory reset.

Fresh Windows install.

Nothing on it except Git, VS Code, and Claude Code.

My own little AI development machine.

Overkill? Maybe.

Satisfying? Absolutely.

Oh, and I also had to sign up for the Claude Pro plan ($20/month) through the Anthropic Console to actually use Claude Code. The free plan doesn't include it.

I will say, before anyone loses heart about Claude Code — within about 20 minutes of it actually working, I was already convinced it was worth it.

🚀The Moment It All Worked

After closing and reopening the terminal (another thing you learn along the way as a low coder — changes don't apply until you restart), I typed claude...

And got a beautiful ASCII art Claude logo staring back at me. 🎉🎈🎊

Then it asked me to pick a color theme.

Then it asked me to log in.

And then — finally — the cursor blinked at me, waiting for instructions.

I typed my first prompt. Holy Smokes!

Claude Code started building files automatically,

narrating what it was doing like a very confident intern.

It was glorious. ☀️

What I'm Building With It

Now that it's running, I'm using Claude Code to build a custom customer support app — a knowledge base, a theme tracker, and a direct message template library.

Basically everything I use to do to ensure this community runs smoothly.

💙The Honest TL;DR

Getting Claude Code running on Windows is genuinely worth it, but it's not plug-and-play if you are not a developer — and I say that from very fresh, very personal experience. 😅

However, here's the move that saved me:

I set up a second monitor, and

literally cut and pasted everything on my screen

directly into Claude, step by step, error by error.

Every confusing message, every cryptic terminal output — I just copied it and asked Claude what it meant. Game changer. You don't need to understand any of it, you just need to show Claude what you're seeing.

Total time if everything goes smoothly: ~15 minutes.

Total time if you're me: 2-3 hours and one very patient AI assistant.

Worth it? Absolutely!

Next: 👇

Now that Claude Code is installed, back to

@Nate Herk

videos. And asking my buddy

@Matthew Sutherland

a ton of questions.

Thought you would enjoy this:

@Nick Mohler

@Usman Mohammed