Three things,
from memory.
Three words from Part 1 that Part 2 stands on. Answer out loud before you tap.
By the end of this chapter you have Claude Code open in front of you, Munim’s invitation accepted, and a way to tell whether the guided session is on this Mac or not.
To open Claude Code: press the preset, your saved button at the top of Superset, the app that lists your projects. Claude Code opens in your project folder.
He sends you an invitation to the playbook, his folder of building methods. Accept it from your email. The guided session copies that folder onto your Mac, and it cannot do that until you have accepted.
How to tell the first paste line worked. In chapter 03 you paste /workshop 2 into Claude Code. It worked if Claude Code answers by naming Part 2 and asking you a question before it does anything.
It has not worked if Claude Code replies as though you had typed an ordinary sentence, or says it does not know that name. Nothing is broken, and nothing you did caused it.
The guided session is one small file that has to be put on this Mac once, and nobody has put it there yet. Paste the line below, and Claude Code puts it there itself.
This one is written for Claude Code rather than for you, and it names folders you will never open. You are not expected to read it. Press copy, paste the whole line into Claude Code, and read what comes back.
Much of this will not
work first time.
That is the shape of this work, not a sign that you are doing it wrong. Every step is an experiment: try it, look at what came back, adjust. The people who do this for a living work the same way.
So when something does what you did not expect, nothing is broken and nothing is your fault. You have found something. Stop, and tell Claude Code what is on your screen.
This chapter gives you the one thing to do with what you find: write it down as it happens, in a file you keep.
By the end of it you know what goes in that file and what does not. You make the file itself in chapter 09.
You keep a site diary.
A site diary is one file in your project where the awkward moments get written down as they happen.
When something confuses you, blocks you, or does what you did not expect, you type two words to Claude Code: diary that. It writes the entry for you, with the date and what you were doing.
What goes in it: the moment you got stuck, the word nobody explained, the thing you wished worked differently. Every entry is about the instructions, never about you.
You make your own diary file in chapter 09, and it gets its first entry the same day. Part 5 turns those entries into changes to the method itself.
Do none of this on a work Mac. Part 2 installs software, changes settings and signs into accounts, and a work machine belongs to your employer, with their rules running on it.
If the only Mac you have is the work one, tell Munim before you start rather than working around it.
Two-factor is the lock.
The codes are the
spare key.
This chapter locks the account that will hold every version of your work. It is the one step in Part 2 that can shut you out for good, so it comes with a spare key.
By the end of this chapter your GitHub account no longer opens on your password alone, and the list of codes that gets you back in is on paper in front of you.
GitHub is the website that stores projects online. Two-factor authentication adds a second proof on top of your password: a six digit number that changes every thirty seconds.
The number comes from the Passwords app already on your Mac. Choose Authenticator app, not text message: GitHub marks that one Less secure. GitHub makes this compulsory on your account from 23 September 2026.
Recovery codes are a short list GitHub gives you while two-factor turns on. Each code opens your account once, without the six digit number, and then stops working.
Put them on paper, where your passport lives.
Clicked past that screen? Go to github.com/settings/security, signed in, and press View beside Recovery codes.
Lose the device that makes the six digit number, with no codes on paper, and nobody at GitHub can let you back in. That is the whole reason for the codes.
What it is like if the codes are gone too
Your work is not lost. Every file is still on your Mac, and the shared copy online is still there. What you lose is the way in to the account that holds it.
You cannot prove you are you. The six digit number is the proof, the codes are the spare proof, and there is no third one.
Nobody there can wave you through, and that is the lock working rather than failing. A door that opens for you without the proof opens for anybody else the same way.
- Put the codes on paper today, while the screen is still in front of you.
- Keep them where your passport lives, not in a folder on the Mac that makes the number.
- If you have already clicked past that screen, the panel above says how to get back to it.
Ask for the walk, and the stop.
Claude Code,
in Chrome.
Until now, when a page did not match what you were told, you described it. Now Claude Code can look at it with you.
By the end of this chapter Claude Code can see the page in front of you, on the sites you have allowed and on no others, and the list of allowed sites starts empty.
You add an extension, a small piece of software that adds a feature to Chrome. Then you sign in inside Chrome with the same account you signed into Claude Code with in Part 1. Until you do, the extension does nothing.
It can read the pages open in your browser and act on them: clicking, typing, moving from page to page.
Chrome asks you site by site, and you can take a site back whenever you like. Decide now, while you are reading this, rather than in the moment a box appears asking you.
On a site you are signed into, it sees what you see. Not the public version of the page: your version, with your account open on it. That is the whole reason Chrome asks you one site at a time instead of asking once.
A page will half work one day and you will not know why. This is the one thing in Part 2 most likely to find you weeks from now, with nobody sitting beside you, so it is here rather than left to be discovered.
NextDNS, the lookup service you set up in chapter 06, can refuse a name that a page quietly needs. Nothing shows you an error. A button spins and never finishes, or part of the page stays blank, and everything else looks normal.
You do not have to work out which name. After this chapter Claude Code can see the page with you, so you describe what has stopped and it goes looking.
Describe it, do not hunt for it.
You do not have to guess which one. Claude Code can read all three of them on this Mac, so let it look rather than deciding in advance.
Or do it yourself. Sign in at my.nextdns.io and open the Logs tab. It lists every name your Mac has asked for, newest first, with the refused ones marked.
Reload the page that broke, then look at the very top of that list. The refused name you want is the one that appears at the moment you reloaded, which saves you reading any of the rest.
Beside that name there is an option to allow it from now on. If what you see is worded differently, read it out to Claude Code rather than guessing.
The install, and the stop.
Your repository.
Your work needs a home that is not only this Mac, and Munim needs to see it without asking you. You make that here.
A repository is your project folder, plus a full record of every version and a twin on GitHub. Sending work to the twin is a push: you ask Claude Code once, and the twin catches up.
By the end of this chapter your project exists on GitHub as a private repository, Munim has an invitation into it, and five skills are sitting in your project folder.
One ask.
It stays your repository. You can take that access back at any time.
He can see how far you have got without asking you.
If what comes back has no Private badge on it, say so before you carry on. That is the one thing on this page worth stopping to put right.
This is the page before anyone is invited. Find two things: the Private repository line at the top, and Collaborators highlighted on the left. Once Claude Code sends the invitation, Munim’s name appears in the empty panel.
The playbook is a folder of its own, and your access to it is read-only: open every page, change none.
Five skills land in your project. You have met /secure-machine and /guardian. The other three are introduced in Part 4.
Is my work on the internet now?
It is on GitHub’s computers, and it is shut. Private means it opens for you and for anybody you invite, and for nobody else. There is no link that lets a stranger in.
Munim can open it once he accepts the invitation you send here. That is one person, by name, and you can take it back at any time.
What it is not is a published website. Nothing you put in it appears in a search.
Your work has a home now. One file is still missing from it, and it is the one you write yourself: the diary chapter 02 told you about.
The diary,
made.
Chapter 02 said what it is for. Here it becomes a real file: SITE_DIARY.md in your project folder, visible in Finder. Claude Code adds an entry when you ask, and never edits one already there.
By the end of this chapter that file exists with its first entry in it, and you have said the two words that add the next one.
How an entry happens.
The nearest thing you already run.
An RFI register. The methodology is the site, you are the inspector, and every entry is raised against the playbook, never against you.
Where that comparison breaks.
An RFI blocks work until someone answers it. A diary entry blocks nothing. You raise it and carry on.
Claude Code puts one of three tags on each entry, so Part 5 can sort them into three piles: [stuck], [confusing], [wish]. You never type them yourself.
Eight to fifteen entries across the five parts is normal. Fewer than that usually means they were not written down, not that nothing happened.
WORDS.md sits beside it: one line for every name these five parts use, so a word never sends you back to a page.
Say it out loud,
instead of typing it.
Part 3 opens by asking you to describe the app you want, at length and in your own words. That is a great deal of writing, and typing is where people quietly shorten what they meant.
So you set this up today, while there is nothing else to think about. You press a key, you speak, and the words arrive as text where you were about to type.
By the end of this chapter VoiceInk is on your Mac, unlocked with the key Munim sent you, set to the two models below, and started once with a key you picked yourself.
Munim has already sent you a key that unlocks VoiceInk for good. It is not printed on this page and it is not in the guided session, because a key on a page is a key anybody can use.
Find that message before you start. If you cannot, ask him for it again on WhatsApp.
Two asks, in that order.
Chapter 05 said to ask the guard before anything new lands on your Mac. This is the next thing that lands on it.
Everything after this is in one window with a list down the left side of it. Two items on that list are all you need today.
AI Models holds the first setting. Modes holds the rest. Dashboard, Transcribe, History, Dictionary and Audio can wait for another day.
Two models do two different jobs, one after the other. That is the part worth having straight before you press anything, because you set them in two different places.
Both are chosen on one sheet further down this page. The first one has to be on your Mac before it can be chosen, though, and that is what AI Models is for.
Open it, open the Model Catalog, and stay on the Local tab.
Three rows begin with the word Parakeet and only one of them is yours. Parakeet V2 and Parakeet V3 are not it, and they sit directly above the one that is.
Parakeet Unified, the row carrying the Experimental badge, English, 1.2 GB. Press Download and leave it to finish. When it has, the button on the right reads Downloaded, as it does here.
Four blocks: Triggers, Transcription, AI Enhancement, Advanced. A handful of rows in them have to say the right thing, and Save Changes at the foot is what keeps them.
Then Modes, then Dictation. That opens one long sheet. Here it is top to bottom, so you know how far it runs before you start.
Six things to set, in the order they appear on that sheet. Tick them off as you go.
Set it to Parakeet Unified, the one you downloaded. Not V2 and not V3.
Switched on.
Switched on. This is the tidying step from the drawing above, and it does nothing until you turn it on.
Set it to Anthropic.
Set it to claude-haiku-4-5. Read it letter by letter and pick the row that matches exactly.
Output set to Paste, and Set as default switched on. Then press Save Changes.
If a row on your sheet is not in that list, leave it exactly as you found it.
Last, the key that starts a dictation. You choose that one, so this page does not name one.
Press Record, then press the key you want to use. Pick one you never press by accident. Munim uses one of the function keys along the top of his keyboard, and yours does not have to be his.
Nobody on this workshop has a picture of that row with a key already in it, so there is no picture here of what it looks like afterwards. What appears there is whatever you pressed.
Press your key and this bar appears. The line in the middle moves while it can hear you, which is how you know it is working. The red button at the left stops it.
The sheet you set is on Paste, so the finished words should arrive where you were about to type, on their own.
If they do not, Munim holds Control and Command and presses V to bring them in. He told us that. There is no picture of it here, so treat it as the first thing to try rather than the only way.
The screens a brand new install shows you the first time you open it. Every picture above is of an app that has been running for months, so your first few minutes will not look like them.
Read what is actually on your screen rather than hunting for these exact words. If a row is not where these pictures put it, read it out to Claude Code and ask what it is before you press it.
It does not ask you
about everything.
Claude Code stops and asks your permission for some of what it does and not for the rest. Which is which is decided by one setting, and yours is already on the right one. This chapter is about recognising it, not about changing it.
By the end of this chapter you can find that setting at the bottom of your own window, you know the one thing it does not protect you from, and you know two words to walk away from.
The words auto mode on, in yellow. Auto mode is Claude Code getting on with the ordinary steps by itself, instead of stopping to ask you about each one.
There is nothing here for you to switch on: from 14 August 2026 this is what every new session starts in. If you can see those words, you are where you should be.
The greyed words after it are a reminder that there are other settings to cycle through. You want none of them, so leave that line alone.
If the bottom of your window says something else, read the line out to Claude Code and ask it to put you into auto mode. Do not go hunting through the settings yourself, and the rest of this page is why.
What if I press those two keys to see what happens?
Nothing happens on your Mac. That press changes what Claude Code asks you about next, and nothing else. No work is lost, and nothing runs.
The bottom line will read something other than auto mode on. That is the whole of what has changed, and it is written there for you to see.
Do not press it again to find your way back. The setting at the foot of this page is on that same cycle.
Read the bottom line out to Claude Code and ask it to put you back into auto mode. That works from wherever you have landed.
Auto mode is not yes to everything. A second, separate model reads each action before it happens and stops the ones that reach further than what you asked for.
Downloading something off the internet and running it straight away is one of the things it stops. So is sending private information out of your Mac, and so is wiping work you did before today.
The dot is the same one in both lanes. It reads the label, and never the contents.
That is the whole reason chapter 05 asked you to wait a week before taking anything new. Auto mode reads what is being done, sees an ordinary thing, and lets it through. It does not open the parcel and look inside.
The week is what stands there instead, and your project already applies it by itself. That is the connection chapter 05 promised you, and it is the whole of it.
It does still stop and ask about some things, and this is what that looks like when it happens.
A question, two answers, and a line of other keys underneath. On the real screen there is a box above this question saying exactly what it wants to do.
That box is cut out of this picture because it named a private folder. Read it before you answer.
This is the shape chapter 05 called a gate: nothing moves until you say yes or no. The dot in the drawing above is the other shape, something reading as it goes past.
One thing worth knowing before it happens to you: if it stops three actions in a row, it stops trusting the run and starts asking you about everything again. That is the system working, not your Mac breaking.
There is one more setting past the one you are on, and it is called bypass permissions. That one really does mean yes to everything: no reading, no stopping, no question.
Its makers say to use it only on a machine holding nothing you would mind losing. Yours holds your project and your accounts.
If you ever see those two words on your screen, you have gone one setting too far. Go back.
You will not do this
in one sitting.
Nobody does. Your work lives in the folder on your Mac, not in the chat, so closing the chat loses none of it.
By the end of this chapter you know the two lines that get you moving again on any later day, and where each of them goes.
The first picks Part 2 back up wherever you stopped. The second starts a project of your own, from nothing.
Both are on this page below, in full, each with a copy button. Neither is worth memorising: if you cannot find them again, ask Claude Code in plain words for the line that picks the workshop back up, and it will know what you mean.
Coming back is two moves. Press the preset on your project, then paste the line below. A new chat does not remember the last one, so it reads your project and tells you where you stopped.
Where was I?
The playbook on your Mac is a folder of methods. You never open it yourself. You point Claude Code at it, and it does the setting up by asking you questions.
End of Part 2.
Five things are true, and you watched the evidence for four of them.
01 Your machine’s protections were read, control by control, and you saw every verdict.
02 Your GitHub account has a second lock, and you have said the spare key is on paper.
03 Your Mac refuses scam and malware pages, and interrupts anything trying to install itself. If you took the paid one, everything leaving your Mac is recorded too.
04 Your repository exists, it is private, and it holds five skills that can read the playbook.
05 Your site diary has its first entry.
That is the ground. Part 3 builds an app on it in a single ask, and each of those five is something you would otherwise have stopped to fix later.
None of this makes you unhackable, and nothing here claims it does. It makes the likely attacks expensive.
Your one next action
Type diary that to Claude Code, for the one thing on these pages you had to read twice.
Next
Part 3: The Quick Build
You build the whole app by asking once, after writing down what good looks like.
Open Part 3 →