Nathan Labenz: belief

Transcript context

…rmation. And so I've set up a message bus where the, and it's hosted on the Mac mini. So any agent, whether it's me or the, the autonomous agents on the Mac mini, they can write to the message server. The laptop is constantly pinging it. And it also like sends me a, there's another interface. It sends me a push notification to the phone when there's a new question for me. And we can like give information, but hopefully not too much information, right? So, and hopefully we would no, wait a second, like, why are you asking for that? You know, if somebody's kind of adversarially jail broken or whatever, My, my agents. Then there's also the question of just like, OK, we're all on this tail scale network together. How do we make sure that the laptop or you know the the Mac mini agents can't just like root the laptop? So what I've tried to set up there is kind of one way hierarchical control where and I've structured this in a couple different ways. 1 is like the Mac mini cannot SSH into the laptop, but the laptop can SSH into the Mac mini and my phone can also SSH into both. And then on a repository level as well, I have kind of a hierarchy that's like the main top level agent that knows everything is the like second brain repo. And I call that, you know, Nathan's personal AI infrastructure, you know, with your inspiration. And then different repositories kind of sit under that and have like partial information and some of those get mirrored across the different computers and the, the other agents also have access to them, including write X. They also have their own GitHub by the way. So they can write, you know, come and make commits to GitHub and push stuff to GitHub, but only in certain repository. So there's like the the second brain one just lives on the computer is not shared with the agents. The podcast production repo that does all the things that is shared and both can use it. The shared wiki is of course shared and both can use it. The, you know, there's more and more of these things, you know happening over time, right? Like now using Mercury credit cards also to create often individual merchant limited credit cards that I can then give over to the agents and say, OK, you can buy groceries on shipped, but that's literally all you can do with this card, right? So I'm kind of limiting my willing to take a little risk that they buy the wrong peanut butter or whatever. But I'm as long as it's like, you know, a transaction under $500 a week on shipped, like I can live with whatever, you know, could go, could go wrong there. And so this hierarchy of kind of information flow and like who sits on top and and who can see what beneath them has been interesting. And then there's also like shared tools that sometimes a kind of a cross repo, right? Like a, you know, the brave search API, for example, like I need that from my main second brain, but I also need that from the podcast repo. And then the agents, you know, themselves also kind of need it. So there's kind of this, the lowest level thing is just like shared utilities. I think last comment and then I'll just ask you for feedback is a big unlock. you know, themselves also kind of need it. So there's kind of this, the lowest level thing is just like shared utilities. I think last comment and then I'll just ask you for feedback is a big unlock. I think has been realizing that my top level second brain called Code Agent can change all these repos underneath it without needing to be it. So I think an early version of me was like, I've got these autonomous agents over here. I'll go prompt them to enhance themselves, they'll make commits and then that'll go up to the cloud. And now I've realized it's probably best for me to just have this single agent at the top of the hierarchy change itself and also make the edits to whatever other repositories need to be edited. And then the command to the agents is like, you've got changes coming from the, you know, you're, you're sort of highest level AI supervisor update yourself. Of course, that could even be that command could also be issued, you know, via SSH from the top level agent. But it's, it's less of a like, update yourself as you see fit and more of A at us as a, as a system. We've made some upgrades like get yours and you know now you'll be using that in the future. I'm sure I've left out some details there that might be relevant. So if there, if you see gaps in terms of how this works, ask me and then otherwise, you know, tell me what do you think? What am I doing right or or wrong? I mean, I think that's that's overall correct. It sounded I heard a lot of different repos in there. I think I'm trying to be more unified or simplified. So I have a unsupervised learning unified GitHub, which is essentially what are we doing work it's So the reason I'm using GitHub for this is because it has so many primitives already built in. So you can use issues, you can actually comment on things. And what's cool about it is those replies and everything can actually be targeted by emails. So you can actually interact with the file structure or the system structure of GitHub kind of for free, like as a project management system with e-mail or with GitHub command line individually. So what I have is I have separate agents. They're in Mac minis, they're on a DMZ inside of my firewall. So they are essentially Internet boxes that I treat them like cloud boxes, like like an actual separate employee. They have their own personalities. They have a first name and last name. They have an image. I didn't give them a writing style because I didn't really need to, but other than just like B, terse and concise and stuff like that. But they have their own Mac, their own Mac account, their own UL account, which is Google and their own AI account. And the way I handle the access to skills and tools and stuff is just a GitHub repo. So and all this is automated so that it's regularly doing checks. Now what's cool about the universal UL system is Kai has access to that that one also. But all my I have 3 Devi, Soren and Mira are their names and they're kind of broken up by different roles. But Kai can see all of them and the GitHub repo, they each can see the GitHub repo. But what's cool is I can say, hey, I have a project blah blah blah that gets automatically marked up as pending or future or whatever. Plus it's a project. So tags within GitHub is also really powerful feature here. And what's cool is the agents can then go and look every 5 minutes at the repo to see if there's something new to be done. Like I just gave a resource task to Chi, which means I've given it to my overall system, I've given it to the company, and now whoever gets there first or whoever's best suited for the job, I haven't really sorted that out. Right now, it's just who gets there first. Literally sees an open GitHub issue. It's unresolved, so it marks it as I'm currently working on it, and then just goes and works and brings back the results. And now all of my AI, most importantly, Chi and my overall π automation could just know the state of the company by looking at the state of GitHub. So for separation, it's separate everything on those individual boxes, including the AI account, and I'm using all of that through just π. So the other thing that gets you is the fact that each instance has their own skills, and the shared skills are on GitHub.…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.