# INSTALL GUIDE -- one row per step. Paste into Google Sheets: Data > Split text to columns > Tab. # Filter on the mini/standard/full columns to see one format's chapters only. # Built 2026-10-14. Free to copy, use and republish. chapter_no chapter chapter_id mini standard full minutes step_no platform step extra 01 Back up your computer first backup yes yes yes 45 1 windows Get an external drive bigger than the used space on your laptop. A 1 TB USB disk costs less than the AI Workshop and you will reuse it for years. Why we start here: Everything later in this guide is about giving an AI assistant access to files. A verified backup turns every mistake after that into an inconvenience. | It also means you can say yes to the interesting experiments instead of hesitating over them, which is most of the value. | This is the least the AI Workshop can do for you: make you finally do the thing you have been postponing. // If you would rather not install anything: Windows has its own: Control Panel → Backup and Restore (Windows 7) → Create a system image. Older and clumsier, and it works. | File History copies your documents but not the system. Better than nothing, worse than an image. | Whatever you use, test that you can see the files in the backup before you trust it. // Download: Hasleo Backup Suite Free — Windows, full disk images // Download: Time Machine — built into macOS, nothing to install 01 Back up your computer first backup yes yes yes 45 2 windows Install Hasleo Backup Suite Free from the link above. It is free for personal use, it makes full disk images, and it can restore to a machine that will not boot — which is the only test of a backup that matters. 01 Back up your computer first backup yes yes yes 45 2 macos macOS needs nothing installed: System Settings → General → Time Machine → Add Backup Disk. 01 Back up your computer first backup yes yes yes 45 3 windows Run a FULL system backup, not a file backup. In Hasleo: System Backup, pick the external drive, start it. It takes an hour or two; start it in the evening and go away. 01 Back up your computer first backup yes yes yes 45 3 macos Time Machine's first run takes about as long. Leave it plugged in and let it finish. 01 Back up your computer first backup yes yes yes 45 4 windows Make the recovery media while you are there: Hasleo → Tools → Create Emergency Disk, onto a USB stick. A backup you cannot boot to restore is a backup you do not have. 01 Back up your computer first backup yes yes yes 45 4 macos macOS recovery is built in — hold Command-R at startup. Nothing to prepare. 01 Back up your computer first backup yes yes yes 45 5 windows Write down where the drive is and when you made it. Then disconnect it. A backup drive left plugged in is a drive that gets encrypted along with everything else. 01 Back up your computer first backup yes yes yes 45 6 windows Check it worked — browse inside the backup you just made: Hasleo → Tools → Explore Image, open the image on the external drive, and look for your own documents in it. A backup you have not opened is a guess. 01 Back up your computer first backup yes yes yes 45 6 macos Time Machine → Browse Time Machine Backups, step back to last night, and open any folder of your own. 02 A separate Windows account, for your own safety clean-account yes yes yes 15 1 windows You do NOT need a Microsoft account for this. Make a plain local account: Settings → Accounts → Other users → Add account → “I don't have this person's sign-in information” → “Add a user without a Microsoft account”. Admin for a day, not for good: Administrator during the AI Workshop is a deliberate trade: the separate account is what limits the damage, and the rights are what stop an install stalling in the middle of a session. | The separation is doing the work here, not the privilege level. A fresh account has nothing of yours in it either way. | Demote it to Standard or delete it when the day is done. That is step 6, and it is the one people forget. | No Microsoft account anywhere in this — a local account is enough and it keeps the machine out of somebody else's cloud. // Recommended — maximum protection: A separate local account, used for the AI Workshop and nothing else. Claude Code only ever sees that account's files, so the worst a wrong answer to a permission prompt can reach is a folder of practice material. | Administrator during the day so installs do not stall; Standard or deleted afterwards. Five minutes to set up. | This is the recommended route and the rest of the guide assumes it. // If you accept the risk: Working in your everyday account is faster and it is what most people will do. It also means an afternoon of experiments is happening next to your documents, your photos and your accounts. | If you do it anyway: make sure a backup exists that you have actually restored from once, keep all practice work inside one new folder, and read every permission prompt instead of clicking through it. | Your call. Not ours to repair — see the note at the top of this page. 02 A separate Windows account, for your own safety clean-account yes yes yes 15 1 macos System Settings → Users & Groups → Add Account. A local account, not an Apple ID. 02 A separate Windows account, for your own safety clean-account yes yes yes 15 2 windows Name it something you will recognise — ai-workshop will do. Give it a password you will remember for one day. 02 A separate Windows account, for your own safety clean-account yes yes yes 15 3 windows Make it an ADMINISTRATOR for the AI Workshop. Windows: on the same screen, Change account type → Administrator. Installing Node, Git and the Claude app all need it, and a session that stalls on a password prompt we cannot answer costs the whole room ten minutes. 02 A separate Windows account, for your own safety clean-account yes yes yes 15 3 macos macOS: tick “Allow this user to administer this computer”. 02 A separate Windows account, for your own safety clean-account yes yes yes 15 4 windows Sign in to the new account once, so Windows finishes setting it up before the AI Workshop rather than during it. 02 A separate Windows account, for your own safety clean-account yes yes yes 15 5 windows Do every remaining step in this guide while signed in to that account. 02 A separate Windows account, for your own safety clean-account yes yes yes 15 6 windows AFTER THE AI WORKSHOP, take the rights away again: Change account type → Standard, or delete the account altogether. Administrator was for the installing, not for keeping. Deleting the account deletes its files with it, so move anything you want to keep first — and if you pushed your work to GitHub as chapter 06 says, it is already safe. 02 A separate Windows account, for your own safety clean-account yes yes yes 15 7 windows Check it worked — sign out, sign in as the new account, and try to open your own Documents folder. You should be refused. If you can read your own files from the workshop account, it is not separate and the chapter has not done its job. 02 A separate Windows account, for your own safety clean-account yes yes yes 15 7 macos Log out and back in as the new user, then open Finder → Go → Home. You should see an empty home folder, not yours. 03 A Google account you are willing to connect google-account yes yes yes 15 1 windows Open accounts.google.com/signup in the new Windows account. Create the address — something like yourname.ai@gmail.com. Sharing beats connecting: Drive's Share button is the whole trick: the AI works on a file you deliberately handed it, not on everything you own. | Un-sharing takes one click and takes the access away immediately. | You can do the entire AI Workshop on the demo pack — sample invoices, a bank statement and photographs, all invented. Ask in the pre-flight e-mail and nothing of yours leaves your laptop. // Recommended — maximum protection: Make a new Google account, used for nothing else. Then the connectors reach exactly the folder of practice files you chose and nothing more — not your contracts, not six years of mail. | Need to work on something real? SHARE it into the AI Workshop account from your main one, one file or one folder at a time, from Drive's own Share button. You keep the original, you can un-share it in one click, and the AI only ever sees the copy you pointed at. | This is the recommended route and it costs five minutes. // If you accept the risk: Connecting your everyday Google account works, and it is faster. It also means an afternoon of experiments is happening inside your real mail and your real Drive. | If you do it anyway: check that Drive has a backup you trust, keep the practice work in one new folder, and disconnect the connectors when the day ends. | Your call. Not ours to repair — see the note at the top of this page. 03 A Google account you are willing to connect google-account yes yes yes 15 2 windows Turn on two-step verification straight away: myaccount.google.com → Security → 2-Step Verification. You will be connecting this account to software; protect it now, not later. 03 A Google account you are willing to connect google-account yes yes yes 15 3 windows Put the practice material in: send two or three real invoice PDFs from your main address, or share them in from your main Drive, or use our demo pack and send nothing at all. 03 A Google account you are willing to connect google-account yes yes yes 15 4 windows Put 10–20 photos in Drive, in one folder, for the video block. Family photos are fine; see the note on faces in the safety chapter. 03 A Google account you are willing to connect google-account yes yes yes 15 5 windows Keep the account afterwards or delete it. If you keep it, it stays a useful sandbox: anything you want to try on real data gets shared in, tried, and un-shared. 03 A Google account you are willing to connect google-account yes yes yes 15 6 windows Check it worked — open gmail.com in a private browser window and sign in with the new account. An empty inbox and no access to your real mail is the correct result. 04 A Claude account, and a paid plan claude-account yes yes yes 10 1 windows Go to claude.ai and sign up with the Google account from the previous chapter. Why Pro is not optional: We are not teaching you to chat with an AI. You can do that for free and most people already have. | We are teaching you to put it to work: a folder on your own machine, your mail and your Drive connected, a real spreadsheet built, a year of invoices filed, an app on your phone. Every one of those needs Claude Code or Claude Design, and both start at Pro. | On the free plan you would spend the afternoon watching somebody else build. That is a worse use of your day than the price of one month. | Cancel after the AI Workshop and you get the unused part back. Keep it if the first week pays for itself — which is the actual test, and it is yours to run. // What a plan buys: Pro: Claude Code, Claude Design, bigger context, the connectors we use. Enough for everything in STANDARD. | Max: more usage per hour. Worth it only if you keep going hard after the AI Workshop. | Free: the chat window, and none of the tools. 04 A Claude account, and a paid plan claude-account yes yes yes 10 2 windows Upgrade to Pro: your initials, bottom left → Settings → Plans. Max only matters if you intend to work hard after the AI Workshop; Pro is enough for the day. 04 A Claude account, and a paid plan claude-account yes yes yes 10 3 windows Add the card now, in your own time. Doing it in the room costs everybody ten minutes. 04 A Claude account, and a paid plan claude-account yes yes yes 10 4 windows Sign in once in a browser and send one message, so you know the account works. 04 A Claude account, and a paid plan claude-account yes yes yes 10 5 windows Check it worked — claude.ai → your initials, bottom left → Settings. The plan line says Pro or Max. If it still says Free, the payment did not go through and the workshop will hit the limit in twenty minutes. 05 The Claude desktop app desktop-app yes yes yes 10 1 windows Download from claude.ai/download. Take the Windows installer. Both, not either: Keep the browser open as well. Some things — Claude Design, billing, the skills page — live on the web only. | The app and the web share one account and one history. // Download: Claude for Windows — installer // Download: Claude for macOS — .dmg 05 The Claude desktop app desktop-app yes yes yes 10 1 macos Take the macOS build; it is a normal .dmg, drag it to Applications. 05 The Claude desktop app desktop-app yes yes yes 10 2 windows Install and sign in with the same account. 05 The Claude desktop app desktop-app yes yes yes 10 3 windows Check Settings → Connectors exists and is empty for now. That is the shelf we fill in a later chapter. 05 The Claude desktop app desktop-app yes yes yes 10 4 windows Check it worked — the app opens from the Start menu, not from a browser tab, and shows your own name. If it asks you to sign in again every time you open it, you installed it as one Windows account and are running it as another. 05 The Claude desktop app desktop-app yes yes yes 10 4 macos The app is in Applications and opens from Spotlight. Same test: it knows who you are the second time. 06 Claude Code in PowerShell claude-code yes yes yes 25 1 windows ONE LINE, AND IT IS DONE. Open PowerShell (not the old Command Prompt) and paste: ¶ winget install Anthropic.ClaudeCode ¶ That is the installer route: winget is built into Windows 11 and fetches a signed package. Nothing else in this chapter is needed if it works — skip to step 4. Two words that save confusion: Claude.ai — the chat window, in a browser or the app. | Claude Code — the terminal one, that works in a folder. | Same account, same model, different hands. We use both, for different jobs. | PowerShell, not cmd. Windows ships both; cmd is the older one and some commands behave differently in it. 06 Claude Code in PowerShell claude-code yes yes yes 25 1 macos macOS: `brew install --cask claude-code`, or the script in step 2. 06 Claude Code in PowerShell claude-code yes yes yes 25 2 windows No winget, or it failed? The official one-liner installs the same thing: ¶ irm https://claude.ai/install.ps1 | iex ¶ It downloads a script from claude.ai and runs it — `irm` fetches, `iex` executes. It shows no progress while it works, so leave the window open. You are trusting Anthropic's domain with that line, which is the same trust the app itself needs; if that is not a trade you want, use step 3 instead. 06 Claude Code in PowerShell claude-code yes yes yes 25 2 macos macOS and Linux: ¶ curl -fsSL https://claude.ai/install.sh | bash 06 Claude Code in PowerShell claude-code yes yes yes 25 3 windows The long way, via npm — only if the two above did not work, and the ONLY one that needs Node.js. Install Node.js LTS from nodejs.org/en/download (the Windows Installer .msi, 64-bit, default options), reopen PowerShell, then: ¶ node --version ¶ npm --version ¶ npm install -g @anthropic-ai/claude-code 06 Claude Code in PowerShell claude-code yes yes yes 25 3 macos Same three commands. If npm complains about permissions, fix the npm prefix rather than reaching for sudo. 06 Claude Code in PowerShell claude-code yes yes yes 25 4 windows Check it: ¶ claude --version ¶ If PowerShell says the command is not recognised, close every PowerShell window and open a new one — the PATH is read at start. 06 Claude Code in PowerShell claude-code yes yes yes 25 5 windows Make a folder to work in and start it there: ¶ mkdir ai-workshop ¶ cd ai-workshop ¶ claude ¶ First run asks you to log in; it opens a browser and comes back. 06 Claude Code in PowerShell claude-code yes yes yes 25 6 windows Say hello, then ask it what files are in the folder. When it asks permission, read the question before answering yes. That habit is most of the safety. 06 Claude Code in PowerShell claude-code yes yes yes 25 7 windows Check it worked — type claude --version in PowerShell. A version number means it is installed. “not recognized” means the terminal has not read the new PATH yet: close it, open a new one, try again. 06 Claude Code in PowerShell claude-code yes yes yes 25 7 macos Same command in Terminal, same answer. 07 Git, GitHub, and somewhere for the work to survive git-github yes yes yes 20 1 windows Install Git for Windows from git-scm.com. Default options are right. This also gives you the credential helper that stops GitHub asking for a password every time. Why a folder is not enough: A folder forgets. A repository remembers every version and who changed what. | It also means you can open the same work from another machine, or from claude.ai on the web, without copying files around. | Keep the repository private until you decide otherwise. Invoices are nobody else's business. // Download: Git for Windows — 64-bit installer // Download: GitHub Desktop — optional, if you prefer buttons 07 Git, GitHub, and somewhere for the work to survive git-github yes yes yes 20 1 macos macOS: run `git --version` once and accept the Xcode command line tools prompt, or `brew install git`. 07 Git, GitHub, and somewhere for the work to survive git-github yes yes yes 20 2 windows Create a free account at github.com with the workshop Google address. 07 Git, GitHub, and somewhere for the work to survive git-github yes yes yes 20 3 windows Turn on two-factor authentication. GitHub requires it for contributors and you will hit the wall later if you skip it. 07 Git, GitHub, and somewhere for the work to survive git-github yes yes yes 20 4 windows Tell Git who you are, in PowerShell: ¶ git config --global user.name "Your Name" ¶ git config --global user.email "you@example.com" 07 Git, GitHub, and somewhere for the work to survive git-github yes yes yes 20 5 windows In the workshop folder, ask Claude Code to create a repository and push it. It will walk you through the browser login the first time. After that, “save this to GitHub” is one sentence. 07 Git, GitHub, and somewhere for the work to survive git-github yes yes yes 20 6 windows Check it worked — git --version answers with a number, and your repository page on github.com shows at least one commit with today's date on it. A repository with no commits is a folder with extra steps. 08 Connectors: Gmail, Drive and Sheets mcp yes yes yes 20 1 windows In the Claude desktop app: Settings → Connectors → Browse connectors. Add Gmail, Google Drive and Google Sheets. Connector or skill: A connector gives Claude access to somewhere. | A skill teaches Claude how to do something. | You need both, and they are configured in different places — which is exactly why people mix them up. | The context is a desk, not a library: install what today needs, not everything you can find. 08 Connectors: Gmail, Drive and Sheets mcp yes yes yes 20 2 windows Each one opens a Google consent screen. Read it. Grant it to the WORKSHOP Google account, never your business one. 08 Connectors: Gmail, Drive and Sheets mcp yes yes yes 20 3 windows Ask Claude to find invoice attachments from the last three months. If it lists them, the connector works. 08 Connectors: Gmail, Drive and Sheets mcp yes yes yes 20 4 windows Disconnect anything you are not using when the day is over: same screen, Disconnect. A connector you forgot about is a door you left open. 08 Connectors: Gmail, Drive and Sheets mcp yes yes yes 20 5 windows Check it worked — ask Claude: list the subjects of my last three e-mails. Real subjects mean the connector works. An offer to help you set up e-mail means it does not, and the consent went to a different Google account. 09 The caveman plugin, and why you would want it caveman yes yes yes 10 1 windows In Claude Code, run: ¶ /plugin ¶ and install the caveman plugin from the marketplace listing. Other things worth installing: The document skills, for reading and writing .docx, .xlsx and .pdf. We use these for the workbooks. | Your own skill, written in the room: czech-invoices, which knows what a Czech or Slovak invoice looks like. 09 The caveman plugin, and why you would want it caveman yes yes yes 10 2 windows Turn it on with `/caveman full`, off with `/caveman off`. Try one question each way and compare the length. 09 The caveman plugin, and why you would want it caveman yes yes yes 10 3 windows Decide which you prefer. Some people find it abrupt; the point is that you choose, not that you must. 09 The caveman plugin, and why you would want it caveman yes yes yes 10 4 windows Check it worked — type /caveman full in Claude Code and ask anything. The answer comes back short. /caveman off puts it back to normal. 10 When it will not install troubleshoot yes yes yes 10 1 windows “unable to get local issuer certificate”, from pip, npm or git. Your antivirus is opening every secure connection to inspect it, and the tool does not know the certificate it signs them with. Avast, AVG, Kaspersky and ESET all do it. Either turn HTTPS scanning off while you install — Avast: Menu → Settings → Protection → Core Shields → Web Shield → uncheck Enable HTTPS scanning — or export the antivirus root certificate and point the tool at it. How to report an error so somebody can fix it: Copy the text, do not describe it. “It says something about a certificate” cannot be searched; the exact line can. | Say what you typed immediately before it, and which chapter of this manual you were in. | Say what you already tried. Two people trying the same wrong fix twice is the slowest way to spend an evening. // The one you are most likely to meet: The certificate error is the common one here, because most machines in Czech Republic and Slovakia run an antivirus that inspects secure traffic. | It is not a virus, it is not a broken install, and reinstalling does not clear it. It is the antivirus standing in the middle of the connection, exactly as it was asked to. | Turn the HTTPS scanning back on when you are done installing. It is there for a reason the rest of the year. 10 When it will not install troubleshoot yes yes yes 10 1 macos Same message, usually a company device-management profile instead of an antivirus. System Settings → General → VPN & Device Management shows whether one is installed. 10 When it will not install troubleshoot yes yes yes 10 2 windows “running scripts is disabled on this system”, when you start anything in PowerShell. Windows blocks scripts for a new account. Run: Set-ExecutionPolicy -Scope CurrentUser RemoteSigned, answer Y, and start the command again. 10 When it will not install troubleshoot yes yes yes 10 2 macos macOS has no equivalent block. If a command will not run, it is a missing execute bit: chmod +x the file. 10 When it will not install troubleshoot yes yes yes 10 3 windows “claude is not recognized”, or command not found, right after the install succeeded. The terminal reads its PATH once when it opens. Close it, open a new one, and check node -v and npm -v answer with version numbers before you try again. 10 When it will not install troubleshoot yes yes yes 10 3 macos Same cause and same fix. If a new Terminal still cannot find it, open ~/.zshrc and check the PATH line the installer added. 10 When it will not install troubleshoot yes yes yes 10 4 windows Claude Code starts but says it cannot see your files. You are in the wrong folder. Run pwd, compare it with where the work actually is, and cd into the project folder before you start Claude Code. It reads the folder you started it in, and nothing above it. 10 When it will not install troubleshoot yes yes yes 10 5 windows The connector says connected and Claude still cannot read your mail. The browser is signed in to more than one Google account, and the consent went to the wrong one. Sign out of all of them, sign in only with the account from chapter 3, and connect again. 10 When it will not install troubleshoot yes yes yes 10 6 windows An installer asks for an administrator password you do not have. The workshop account is a standard user. Go back to the account chapter, make it an administrator for the day, install, and take the right off again afterwards. 10 When it will not install troubleshoot yes yes yes 10 6 macos System Settings → Users & Groups → the account → Allow this user to administer this computer. 10 When it will not install troubleshoot yes yes yes 10 7 windows Everything is slow, the fan is loud, the browser stops answering. It is memory, not the AI. Close every Chrome window except the one you need, close Teams and Outlook, and read “Will it run on your machine?” again. Eight gigabytes works; eight gigabytes with forty tabs does not. 10 When it will not install troubleshoot yes yes yes 10 8 windows Nothing above helps and the workshop is tomorrow. Write to info@wikilook.com with the last twenty lines of the terminal, what you typed, and which chapter you were on. We answer the same day, and you come to the room either way — a machine that will not install is a thing we can fix in person in ten minutes. 11 Closing the door when the workshop is over teardown yes yes yes 20 1 windows Disconnect the connectors first, because they are the ones with reach: claude.ai → Settings → Connectors, then Disconnect on Gmail, Drive and Calendar. Then check the other side at myaccount.google.com → Security → Your connections to third-party apps, and remove anything you do not recognise. What we would keep, and why: The separate machine account. It cost one evening and it is the reason you can say yes to experiments. | The repository, private. It is the only record of what you built, and it is free. | The paid plan only if you open it in the first week. If it is still unopened after a month, cancel it and come back when you have a reason. // What never comes back by itself: A connector stays connected until somebody disconnects it. Nothing expires because the workshop ended. | An API key works until it is revoked, including from a copy of the file you deleted. | A public repository is indexed and cached within hours. Making it private later does not unpublish what was already taken. 11 Closing the door when the workshop is over teardown yes yes yes 20 2 windows If you made a Google account only for the day and will not use it again, delete it: myaccount.google.com → Data & privacy → Delete your Google Account. If you would rather keep it, keep it — it costs nothing and it is a clean place to try things next time. 11 Closing the door when the workshop is over teardown yes yes yes 20 3 windows Take the administrator right back off the workshop account: Settings → Accounts → Other users → the account → Change account type → Standard user. Keep the account itself. That is where the practice files live, and a standard account can still run everything you built. 11 Closing the door when the workshop is over teardown yes yes yes 20 3 macos System Settings → Users & Groups → the account, and turn off Allow this user to administer this computer. 11 Closing the door when the workshop is over teardown yes yes yes 20 4 windows Delete any API key you created. A key in a file on your disk is a key that works for whoever reads that file, and it keeps working until you revoke it at the console that issued it. If you are not sure whether you made one, search your project folder for the word KEY. 11 Closing the door when the workshop is over teardown yes yes yes 20 5 windows Look at the repository, not just at the folder. If anything real ended up in it — a client name, an invoice, a password — make the repository private or delete it, and check the history rather than the current files: a commit remembers what you removed afterwards. 11 Closing the door when the workshop is over teardown yes yes yes 20 6 windows Decide about the Claude plan on purpose. If you will use it weekly, keep it; if you took it for one afternoon, cancel before the renewal date. Your chats stay readable on the free tier, so cancelling loses the capacity, not the work. 11 Closing the door when the workshop is over teardown yes yes yes 20 7 windows Write down what you kept, in one line, somewhere you will find it: which account, which repository, which plan renews when. Six months from now this is the difference between a system you own and a subscription you forgot about.