First terminal. Agent running.

A Mac set up from nothing: the terminal opened for the first time, an agent installed on it, and her own website checked out onto her own machine.

What came out of it. She started the evening having never opened a terminal and finished with an agent running natively on her Mac, Homebrew installed, a GitHub account, and the code of her own website cloned onto her own machine. A second agent spent the last half hour generating twenty versions of a cut-out portrait locally, on freeware, costing nothing. The one thing that could not be finished was the one thing she did not control: the site is on her brother's Cloudflare account, and he has to add her to it. That is where the next session starts.

The session

The full session · 1h 31m · Watch on YouTube

No prompt log for this session.

Bernadett Doka

The hero of this one

Bernadett Doka

Psychologist · Grief Method Specialist · couple and family therapist in training

The first guest on the show, and the one who kept coming back. Four sessions, from never having opened a terminal to running her own CRM.

Bernadett’s wishes and sessions →

Worth stealing

The difference that matters is where the code runs

In a browser it cannot touch your computer, so you fetch and paste everything by hand. In the terminal it reads and writes your own disk, which is why the setup is worth the hour. Same model either way.

Watch it happen · 24:58

No error message is the success message

She thought it had failed because nothing happened. A terminal that prints nothing has done what you asked; it is the wall of red text that means stop and read.

Watch it happen · 43:30

Twenty versions costs nothing when it runs on your machine

The cut-out ran on freeware it downloaded itself, so twenty attempts spent no quota at all. Asking for one when you could have twenty is the habit worth breaking early.

Watch it happen · 1:19:36

The terminal hides your password on purpose

Nothing appears as you type it, which reads as a broken keyboard the first time. Type it anyway and press enter.

Watch it happen · 14:13

What happened, when

Every line opens the session at that moment.

  1. 0:00 Getting the stream up, and closing every tab
  2. 6:11 Not the desktop app: why this runs in the terminal
  3. 9:34 Opening the terminal for the first time
  4. 10:40 Homebrew, and pasting the screen back at it
  5. 14:13 A password you cannot see yourself typing
  6. 17:15 What is actually downloading
  7. 20:10 Her question: could it fix a website somebody attacked?
  8. 24:58 Where the code runs, and why that is the whole difference
  9. 27:12 A portrait, and the hard part is the background
  10. 33:17 The native install, and one line to paste
  11. 40:22 The wish: stop having to ask her brother
  12. 43:30 Nothing happened, which is what working looks like
  13. 48:28 The second helper prompt
  14. 55:51 A second agent in a second tab
  15. 1:10:54 Her site is on Cloudflare, in her brother's account
  16. 1:14:26 Cloning the repo, public for a minute and private again
  17. 1:19:36 Twenty versions, generated on her own machine
  18. 1:20:54 Taking the password off the site
  19. 1:27:34 The one thing she cannot do tonight
  20. 1:29:24 Next week, and who is on Friday
Show notes

The first show. Her Mac had never had a terminal window open on it, and the evening was spent getting from that to an agent running on her own machine, with the setup prompts copied off this site a paragraph at a time.

She already had a website. Her brother built it, he owns the account it sits on, and every change to it has had to go through him. That is the thing she wanted to stop, and saying it out loud is what the second session was booked to fix.

It streamed live to Twitch and to his Facebook profile, and the recording went up on the channel afterwards.

Last updated 15 September 2026. Published as-is: read what a prompt does before you run it. The disclaimer has the rest.

Esc