The session
The full session · 3h 40m · Watch on YouTube
No prompt log for this session.
One machine. Never sleeps.
A machine of its own for the agents she already uses, so the work carries on when she shuts the laptop.
What came out of it. She turned up with the machine already bought and assembled, memory fitted by her own hands because it was cheaper that way, chosen by asking her agent rather than by asking him. The evening put an operating system on it and moved her work onto it. One prompt described the whole server, Ubuntu with a terminal that keeps its tabs, an auto install script, a fixed address on her network, and the agent wrote the script; the first flasher would not take a four terabyte disk, so the image went on with a second one. She carried the box downstairs, plugged it into the router and the battery, and it came up first time. Then the move: a terminal on the laptop that can actually hold the server's tabs open, Claude Code installed and signed in on the server itself, GitHub logged in, and twenty three projects with their credentials and their memory files moved across. The three automations that had been running on her laptop were turned off there and re-planned on the server, where they reach the storage services over the internet instead of watching a folder. A shared folder and a small local web page server went on so files and results can get in and out. What did not get finished is reaching it from outside the house: the router had a password nobody remembered, it was reset off stream, and the rest was left for a quieter evening. Her phone already reaches it. The laptop keeps its old setup for another two weeks, and then it gets it back.
The hero of this one
Adrienn Volcz
Accountant and registered Tax Agent
She came on to work on Xero and document filing. A month later, she was back with a reconciliation tool she had built herself.
Worth stealing
Describe the machine, not the steps
One prompt carried the whole thing: the operating system, a terminal that keeps its tabs, an install script rather than an installer, a fixed address on the network, and a login password in case. Nothing was downloaded by hand until the agent said which file to write where.
One agent per job, each in its own folder
Five at once by the end: the install, the router, the terminal question, and two migrations. Separate folders, because memory is per folder, and because a stuck one then costs you one job instead of the evening.
When the prompt is fine and the tool is not, change the tool
Her terminal has no way to keep a session's tabs open, and no amount of asking was going to give it one. The answer was a different terminal, installed by the agent in a few minutes. Knowing which half is broken is most of it.
Auto mode does the same job as the three letters
He has been starting sessions with a shorthand that turns the safety rails off. Auto mode gets the same work done and keeps more of them on, so that is what went on the new machine.
Move the memory with the projects
The notes files and everything the agent had been told go across too. Skip them and the agent on the new machine is a stranger who has to be re-explained a month of decisions.
A moved automation is not the same automation
On the laptop it watched a folder that a desktop app kept up to date. On a server in the hallway there is no such folder, so the same job has to go out to the storage service over the internet with a key. Same outcome, different plumbing, and it has to be re-planned rather than copied.
The new machine is not a backup
A second computer holding the only copy of something is a second place to lose it. The external drive that carried the installer became the nightly backup in the same breath, before anybody left the call.
What happened, when
Every line opens the session at that moment.
- 0:00 Back for the third time, and the machine is already bought
- 0:48 Two apps she built on her own since the last session
- 1:39 A money laundering check she walks a client through
- 2:56 Who she asked about which computer to buy
- 3:44 A hard drive and a battery, because it has to stay on
- 6:16 Naming a project so you can still find it in a year
- 11:06 One prompt: Ubuntu, the tabs, an install script, a fixed address
- 18:43 A second agent, sent to look at the router
- 22:36 Reaching the agent from her phone
- 51:22 Locked out of her own router
- 59:57 The first flasher, and a disk too big for it
- 1:09:36 A second flasher, and the image is written
- 1:20:59 Back into the router
- 1:26:55 "It is turned off"
- 1:29:33 Installing Ubuntu on somebody else's machine, remotely
- 1:30:34 It boots, and she logs in with the key
- 1:32:00 The computer arrived a week ago. She started a month ago.
- 1:39:36 Her terminal cannot hold the tabs open
- 1:41:12 A different terminal, and the word is multiplexer
- 1:42:59 Start moving the projects across
- 2:06:55 She closes the window, and the tabs come back
- 2:10:03 Claude Code, installed on the server itself
- 2:22:28 Auto mode instead of the three letters
- 2:28:13 Logging the server into GitHub
- 2:32:23 Twenty three projects and their credentials, moved
- 2:48:49 Seven tabs open, and she is not a developer
- 2:50:12 Turning the laptop's scheduled agents off
- 2:52:28 She works out the tab completion herself
- 3:00:52 The signing agent stops watching a folder and goes to the internet
- 3:14:52 One command that runs a plan to the end
- 3:17:59 A shared folder, so files can reach the box
- 3:32:53 A web page instead of an artifact
- 3:37:12 Two weeks, then the laptop gets itself back
- 3:38:43 A backup to the drive, every night
Show notes
Her third time in the chair, and the first one where the thing being built was not software. She had bought the computer, put the memory in herself because it was cheaper that way, and picked the parts by asking her agent rather than by asking him. Somewhere in the fortnight since the last session she had also built two more apps on her own, one for onboarding a client and one for walking through a money laundering check, and mentioned both in the first minute the way you mention what you did at the weekend.
So the evening was an install and a move. One prompt described the whole server and the agent wrote the script for it. The first flasher refused the four terabyte disk, a second one took it, and she carried the box downstairs, plugged it into the router and the battery, and came back up. It answered on the first try. By the end her laptop’s terminal was holding tabs that live on the server, twenty three projects had moved across with their keys and their memory, and the automations that used to run while the lid was open had been turned off on the laptop and re-planned on the machine that never closes.
The part that did not get finished is on the tape too. Reaching the server from outside the house needs the router opened up, and the router had a password nobody remembered. It was reset off stream, and the rest was left for a quieter evening rather than done at speed in front of an audience. Her phone reaches it already. The laptop keeps its old setup for another fortnight, and then it gets itself back.
Last updated 20 September 2026. Published as-is: read what a prompt does before you run it. The disclaimer has the rest.
