Fleet repo for all your machines
Workflow
Keep one repo (a project folder) that documents every computer you use: how to connect, what it's for, what is installed. Agents work from it to do machine chores and set up new machines from a single prompt.
Theo's current stance
Theo no longer logs into machines himself. He tells an agent in the fleet repo to set up a new box 'the way I like' and just approves the Tailscale request.
Try it
- Have your agent create a repo listing each machine, how to connect to it, its purpose and installed software.
- Start new threads in that repo for chores like moving files or installing a build.
- Give instructions ahead of time, e.g. 'when the download is done, copy it over.'
First seen
13:50
…is how I manage all of the different computers that I currently have set up for real work, vibe coding, whatever else. It has documented all of the computers, how to connect to them via SSH, what I use them for, what's installed on them, all of those things.
Every mention
23:59
So, when I get a new machine, step one, I set up as a SSH. Step two, I go to this repo. I open up Claude or Codex or in my case usually T3 code and I say, ‘Look, here's a new box. Here's the SSH key. Go set it up the way I like.’
13:50
…is how I manage all of the different computers that I currently have set up for real work, vibe coding, whatever else. It has documented all of the computers, how to connect to them via SSH, what I use them for, what's installed on them, all of those things.
15:42
I literally just told it will be in this directory. I want you to copy it to the other machine in the same directory and then left. I stopped looking. I stopped caring and then I got a little ping when it was done.
Theo Daily is unofficial and not affiliated with Theo or t3.gg. Written by Claude Opus 5.5 from each video's transcript.