A visual walkthrough of your setup.
1. Set up Claude Desktop.
2. Run the installer.
3. Finish with your own workbench, on your machine and on GitHub.
Twelve short sections. Most of it is the app doing the work.
- 1Get Claude and sign in.
- 2Install Git, the one prerequisite.
- 3Open your home folder in the app.
- 4Paste one prompt.
- 5It checks your computer and tells you the plan.
- 6Your computer asks you to approve a few things.
- 7Two sign-ins in your browser.
- 8The secrets guard, so a key can never leak.
- 9Your private workbench is created.
- 10Open the workbench in the app.
- 11Done looks like this.
- 12On to lesson 3.
Three things ready before page one.
A free GitHub account, signed in
github.com/signup takes two minutes. Be signed in at github.com in your browser; when the app sends you there, you click one button. No invitation, no membership, nothing to accept.
A paid plan for Claude
A Claude account on a paid plan. Pro is enough to start. You do not need the strongest model to install things.
An hour nobody will interrupt
Most of it is watching things happen. A computer you are allowed to install things on; a work laptop may say no, so ask your IT person first.
If anything on screen makes no sense, you have a superpower.
Screenshot it and ask
Keep a second chat open in your browser, with any AI. Paste a screenshot of the window you do not understand and ask three things: what is this, is it safe to click, what do I click? That one habit gets people through their first install.
Nothing happens silently
The installer reads and writes inside your home folder, installs a few tools, and signs you in to two services. Every step is explained before it happens, and you can stop at any point. A popup you did not expect, a folder that already exists, something that does not sit right: ask before you click.
Get Claude and sign in.
A download from a website, like any other app. Pick one app and stay in it for the whole course.
Download the app.
- 1Open claude.ai/download in your browser.
- 2Download the Windows version and install it like any other app.
- 3Open it and sign in with the account you pay for. Sign-in happens in your browser, then you come back to the app.
You land on the welcome screen.
- 1The app greets you by name. That is the signed-in state.
Click the Code tab.
- 1The switch at the top of the sidebar has two icons: a speech bubble for Chat, a code mark for Code.
- 2Click Code. The installer runs here, in a folder you can see.
12Install Git first. It is the one prerequisite.
Git is the program that keeps a history of your files. The app cannot open a folder on your computer without it, and this is the red error every past cohort hit. Three minutes now saves the afternoon.
If the app says Git is required, this section is for you.
- 1This is the message the app shows when it opens before Git exists.
- 2Do the next two pages, then quit the app fully and open it again. It only sees Git after a restart.
Download Git for Windows and click Next until it is done.
- 1Open git-scm.com/install/windows and download the 64-bit installer.
- 2Run it. Click Next on every screen; the choices it offers are already right. Click Finish.
- 3If Claude was already open, close it and open it again. It only sees Git after a restart.
Check it: Windows key, type PowerShell, Enter.
- 1Press the Windows key. Start opens.
- 2Type PowerShell. The best match is Windows PowerShell. Press Enter.
- 3A plain window with a blinking cursor opens. You type one line; your computer types one line back. That is all PowerShell is.
12Type git --version and press Enter.
- 1Type
git --versionexactly like that (two dashes) and press Enter. - 2A version number comes back: Git is on. Close PowerShell and go to section 03.
- 3If it says git is not recognized, close PowerShell and open it again; it was opened before the installer finished. Still nothing? Run the installer again.
PS C:\Users\you> git --version
git version 2.51.1.windows.1
12Open your home folder in the app.
Your root folder: the one with your name on it (mine is wademurley; on Windows it may be Owner). Not Desktop, not Documents, and nothing inside OneDrive, iCloud, Dropbox or Google Drive.
New session. Local. The folder badge.
- 1Click + New in the sidebar.
- 2At the bottom, make sure Local is selected, not Cloud.
- 3Click the folder badge beside it (it reads No folder) and choose Open folder... in its menu. Your Finder opens.
123Click through to the folder with your name.
- 1Your home folder is the one named after your Windows username (mine is Owner).
- 2The next three pages show each click.
From This PC, click Local Disk (C:).
- 1Start at This PC in the left column.
- 2Double-click Local Disk (C:).
- 3The address bar at the top always shows where you are.
123From Local Disk (C:), click Users.
- 1The address bar reads This PC, then Local Disk (C:).
- 2Double-click Users. Every account on the computer has a folder here.
- 3Not Select Folder yet.
123Click your folder, then Select Folder.
- 1Click the folder with your username once. Skip Public.
- 2Its name appears in the Folder field at the bottom.
- 3Click Select Folder.
123Click Trust Workspace.
- 1The app asks whether you trust this folder. It is your own folder.
- 2Click Trust Workspace. It lets the app read and edit files in your home folder during setup, with your permission, and nothing else on your computer.
Your home folder is connected.
- 1The row above the box where you type reads Local, then your username.
- 2The word at the bottom left is Auto. Leave it. In Auto the app decides which steps are safe and asks you about the rest. Lesson 3 explains the choice.
Paste one prompt, and follow along.
The app fetches the setup procedure and runs it, step by step, telling you what it is doing and why.
The prompt lives on GitHub, and in your lesson card.
- 1It is in START-HERE.md in the aibl-installer repository, under step 3. This is what that page looks like; nothing here is scary, it is a text file with a copy button.
- 2Use the Copy button in your lesson 3 card; that short request is the one we use. The GitHub page carries a longer form of the same request (its copy icon is at the top right of the code block); it works too, but the short one is kinder to the app's reviewer. Do not copy either out of a PDF of this deck: long links get mangled.
- 3Paste it into the box where you type. Next page.
It looks like this before you send.
- 1The whole prompt sits in the box.
- 2Press Enter (or the send arrow). The app greets you, checks your operating system, and starts.
12It checks first, then tells you the plan.
Nobody should install a tool they cannot name. Before anything lands on your computer, here is what is coming and why.
What happens, in order.
- 1It checks your operating system and which of the tools you already have. Installed, hidden, or missing.
- 2It shows you the plan, one reason per item, and asks once: Sound good? You reply yes. It does not ask again per tool.
- 3It installs only what is missing. Your computer will ask you to approve a few things along the way; section 06 shows each one.
- 4Two sign-ins in your browser: GitHub, then the command-line twin of your app. Section 07.
- 5It installs the secrets guard and proves it works. Section 08.
- 6It creates your private workbench, on your machine and on GitHub, and tells you how to open it. Sections 09 and 10.
Six things, in plain words.
Git
Keeps a history of your files, like a save point in a game. You choose when to save and you write a one-line note. Your workbench is a Git folder, which is why it comes first.
GitHub CLI (gh)
GitHub is the website that keeps a private copy of your folder online. This small tool lets the app talk to GitHub for you: one sign-in, and it creates your private repository. You will rarely visit the site yourself.
Node.js
An engine that some tools run on, including the secrets guard. Nothing for you to learn or open; it just has to be there.
Python
Another engine. The workbench's own helper scripts run on it. Same story: it just has to be there.
Claude Code CLI
The same brain as the app, in a terminal window. Setup uses it for the sign-in and the guard check; later, so will you, without knowing it.
The secrets guard
A check that runs before every command and stops a password or key from being printed, read or uploaded. Section 08 explains why it matters.
Read the plan. Then say yes.
- 1Each tool is marked installed, installed but hidden, or missing.
- 2Each thing it will do has one reason beside it.
- 3It ends with 'Sound good?'. Reply yes. From here on you mostly watch.
Your computer is going to ask you things.
Installing a program is a change to your computer, and the operating system wants a human to approve it. That is your computer doing its job, and it is the same prompt you get installing anything.
If the app asks before doing something, this is what it looks like.
- 1A question under the step it wants to take: what it wants to write or run, and where.
- 2Allow once is the safe answer during setup; it only touches your home folder. In Auto most of these are handled for you, so you may never see one.
- 3Deny if something looks wrong, and ask what it was.
123'Allow this app to make changes to your device?' Click Yes.
- 1Windows shows this two or three times, once per install.
- 2Click Yes each time. No password.
- 3Nothing installs without your say-so. That is the point of the prompt.
Two sign-ins, both in your browser.
GitHub first, then the command-line twin of your app. No password and no code is ever typed into the chat.
The app will ask you to run one command: gh auth login. Here is why.
It lets the app act on GitHub for you
Once GitHub knows your app, the app can create your private repository, save your work online and bring it back, all from the chat. You tell it what you want; it does the GitHub part.
You will rarely visit github.com
Our team almost never opens the website. The apps and their tools do it for us. Signing in once is how that starts. The sign-in itself happens on github.com in your browser, the normal way.
Copy the one-time code the app shows you.
- 1The app runs the GitHub sign-in. The chat shows 'First copy your one-time code: XXXX-XXXX'.
- 2Copy it. Your browser opens to github.com/login/device.
Paste the code into the eight boxes. Click Continue.
- 1Sign in to GitHub if it asks.
- 2Type or paste the code. No hyphen needed.
- 3Click Continue.
Review what GitHub CLI asks for. Click Authorize github.
- 1It lists gists, organizations, repositories and workflows.
- 2The banner confirms you started this from your own device. If it looks unfamiliar, click Cancel.
- 3Click the green Authorize github. Close the tab. The app continues on its own.
If the twin is not signed in, type claude in PowerShell.
- 1The app checks first. If the command-line twin already shares your sign-in, skip this page.
- 2Otherwise: Windows key, type PowerShell, Enter. Type
claude, press Enter. It asks for a text style (press Enter) and then how you sign in. - 3Choose 1, Claude account with subscription. Your browser opens: click Authorize, close the tab, and back in PowerShell you see Authentication complete. Type /exit and go back to the app.
The secrets guard. Why we built it.
A seatbelt that goes on before you need it.
Keys are passwords. The guard makes sure one never leaks by accident.
What a key is
As you use these tools you will collect API keys: long codes that let a program use a service on your behalf. Treat each one like a password. If one leaks, nothing explodes, but someone could run up usage on your account, and you spend an afternoon rotating keys and cleaning up.
Why an automatic check
An AI reading your files can print a key back to the screen by accident, and you might not notice. The guard runs before every command, whether the AI remembers or not, and blocks it. It errs on the side of caution, so expect a false alarm now and then. Better overprotective once than one leak.
The app installs it, then proves it works.
- 1It installs the guard into the app's own settings on your computer, so it protects every folder you ever open, not just this one.
- 2Then it proves it: it asks the app to read a fake secret file. The only right answer is a refusal that names the secrets guard. You will see that refusal in the chat.
- 3If the guard did not fire, the app notices and tries again. You do nothing.
Your workbench is created.
A private repository called my-workbench on your GitHub account, and a copy of it at C:\Users\your-name\GitHub\my-workbench. It is yours.
One tested script, so every workbench is made the same way.
It creates the private repository
github.com/your-name/my-workbench, private, so only you can see it, made from the AI Build Lab template (aibuild-lab/my-workbench-template, public): the day-one files, notes for the app to read, a context folder for what it learns about you, a library for things you hand it, a work folder, and three skills: aibl-personalize, aibl-checkpoint, aibl-enroll.
It puts a copy on your machine
~/GitHub/my-workbench, linked to that repository, so a save on your machine can be backed up online with one command. Programs join later from inside the workbench with one command; nothing to accept up front.
It writes a .gitignore
A list of files Git must never upload: passwords, keys, local-only stuff. It is fine if you have no idea what that is yet; Git and your app both know, and they handle it for you.
It exists. Private, with your name on it.
- 1On your machine: open File Explorer, then This PC, Local Disk (C:), Users, your name, GitHub, then my-workbench. These are the day-one files: AGENTS.md, CLAUDE.md, LICENSE, README.md, blueprints, context, library, work.
- 2On GitHub: open github.com/your-name/my-workbench in your browser. The Private label sits beside the name; only you can see it.
- 3Same files in both places. That is the whole idea: a folder on your machine with a private copy online.
12Point the app at your workbench.
A new session, in the new folder. This is where every lesson after this one happens.
New session, then the folder badge, then Open folder.
- 1+ New, top left, same as before.
- 2Click the folder badge at the bottom.
- 3Click Open folder... at the bottom of its menu. Your Finder opens.
23Same path as before, two folders deeper.
- 1This time you go INTO your username folder instead of selecting it.
From Users, open your folder this time.
- 1The address bar reads Users.
- 2Double-click the folder with your username. You are going into it, not selecting it.
12Inside your folder, click GitHub.
- 1The address bar reads Users, then your name.
- 2The installer created GitHub. Double-click it.
- 3Not Select Folder yet; one more folder to go.
123Click my-workbench, then Select Folder.
- 1The address bar reads GitHub.
- 2Click my-workbench once.
- 3Its name appears in the Folder field.
- 4Click Select Folder.
1234Trust the folder. It is yours.
- 1The same trust question as section 03, for the new folder.
- 2Click Trust Workspace.
my-workbench is the active folder.
- 1The badge above the box where you type reads my-workbench, with the branch, main, beside it. That is the whole check.
- 2Nothing to do on this page. The next page tells you what to type.
That is the whole install.
What you type first, and everything after it, is in lesson 3. Leave the app open on my-workbench and go there.
Three things true at once.
✓All true
The app is open with my-workbench as the active folder.
github.com/your-name/my-workbench shows Private beside the name.
The app's summary says the secrets guard was proven, not just installed.
If not
Something on this list is not true? Screenshot the exact spot, paste it into a second AI chat and ask what it means; or bring it to your program's channel. Do not delete anything and do not switch a safeguard off to get past it.
Congratulations! You did it!
Everything from here happens inside my-workbench. And it is your folder: rename it whatever you like, whenever you like.