Nathan Labenz: uncertainty

Transcript context

…Yeah. So I have that in my so Π now has this pulse system. So the Pulse system is basically local host 31337 old security joke for Elite, but that is my unified system for like all life management. So under work, it also has all my listed Cron jobs. And another way to think about it is like Cron is like the old Unix word for it, but it's just scheduled tasks. And if you abstract one layer more, the thing we're trying to do is make our AI proactive that that's the only reason I'm doing this. So I want pings. I want heartbeats if if my A is job is to monitor to make sure I'm eating enough or not too much, it has to be checking all the time. So technically that's a 5 minute Cron job. But really the goal that to be given to the AI is again, current state, ideal state. How often are you going to check that? So pretty much anything that we're building in including like the maintenance of our skills, the maintenance of our memory files. They need consistent refreshes. They need constant refreshes. Cloudflare workers have built in right into workers a scheduled task. So it's easy to turn on. It's easy to turn on with cloud code. You're like, hey, run this and within Mac, Mac OS you have the ability to do use launch D and do regulars. It uses actual Cron for the Mac, so Kai's pulse management of tasks is managing both local Mac OS stuff and all the different schedule tasks in Cloudflare. So that's all the business stuff, all the AI automation happening in in the cloud. Cool. That's an interesting one as well. I guess I'm starting to do that a little bit with my kind of hierarchy of having the the top most agent modify the others as opposed to having them modify themselves. Do you think there's anything lost? I mean, one thing people sort of seem to find surprise and delight in at least, you know, as reported on Twitter often is when, you know, agents do something cool that wasn't expected or they're sort of, you know, some emergent property. I don't know, I guess I don't, I'm not too worried about it. But do you think there is something that I or maybe we both are sort of missing by not allowing our like, you know, employee agents to be a little bit more fully autonomous, You know, like truly self modifying? Like, yeah, have you experimented with things like, surprise me with something cool? Not really, no. The one I'm really working on is trying to get this customer interaction thing to work perfectly, which they'll be able to talk to surge and basically manage the whole customer relationship. I, I just really don't want any surprises when it comes to that. It's just like you, you really can lose a customer if it's like calls them by the wrong name and then sends the wrong data to them and then make some assertion about something that happened. It's like, that's not me. And then signed Daniel. Really, first of all, it wasn't me. That's my wrong data. You gave the wrong name for you and for me, like now, how do I feel about the person who put this AI in place? You know what I mean? So I just I, I'm very cautious about that with Kai. Absolutely. I the one thing I do with Kai regularly. And this goes to this concept, you know about the the bitter, bitter lesson engineering.…

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