WEBVTT

NOTE Sentence-level transcript of https://www.youtube.com/watch?v=il1c1a2FufU

NOTE One cue per sentence. Cue ids are the line anchors on /transcripts/il1c1a2FufU.html. A cue ends where the next begins, or 2 s after its last word.

s1
00:00:01.309 --> 00:00:03.309
[music]

s2
00:00:13.280 --> 00:00:15.200
All right, let's just uh kick things off.

s3
00:00:15.200 --> 00:00:19.680
How many people here already saw the keynote that I gave?

s4
00:00:19.680 --> 00:00:21.119
Okay, not everyone.

s5
00:00:21.119 --> 00:00:21.920
That's good.

s6
00:00:21.920 --> 00:00:28.320
This talk is effectively going to be a stretched version of what I had given in the main stage except two things.

s7
00:00:28.320 --> 00:00:33.040
One, I want to give you some time to try to set things up yourself, you know, Wi-Fi gods permitting.

s8
00:00:33.040 --> 00:00:35.360
And then also two, be a little more interactive.

s9
00:00:35.360 --> 00:00:42.480
I I had to be very high level when I was talking about what I use Codex for, but here if you have any questions, we have like 70 minutes.

s10
00:00:42.480 --> 00:00:48.800
If you have any questions, just raise your hand and we can start answering some of these things, especially because not a lot of the workflows have been really well documented.

s11
00:00:48.800 --> 00:00:55.039
And so if you if you're very curious on how things work, I'm really happy to uh answer any questions we have here.

s12
00:00:55.039 --> 00:00:57.440
Um, yep.

s13
00:00:57.440 --> 00:00:57.920
I'm Jason.

s14
00:00:57.920 --> 00:00:58.800
I work at OpenAI.

s15
00:00:58.800 --> 00:01:00.399
I don't really know what my job is anymore.

s16
00:01:00.399 --> 00:01:01.920
We do a lot of things.

s17
00:01:01.920 --> 00:01:05.680
Um, clearly the slides are already in the wrong order as well.

s18
00:01:05.680 --> 00:01:16.080
But generally, you know, I've done things like doing a lot of prototyping work and just writing lots of code and just having a goal run for two days to build a game or some kind of web application, right?

s19
00:01:16.080 --> 00:01:19.680
We've also looked at things like running evals and hill climbing things.

s20
00:01:19.680 --> 00:01:24.799
Uh I also use computer use to edit iMovies and make little videos.

s21
00:01:24.799 --> 00:01:36.479
I do partnerships and education and operations by taking my meeting notes, turning them into documents, working with other vendors, and also working with different foundations and programs to get funding.

s22
00:01:36.479 --> 00:01:40.079
And all of this work is done effectively in the Codeex app.

s23
00:01:40.079 --> 00:01:46.880
Uh I don't know if you can tell, but right now the slide is being served on local host in the inapp browser of the Codeex application.

s24
00:01:46.880 --> 00:01:53.920
And so anytime I find something I don't like, I might just hit the annotate tool, give a comment, and have codeex clean up these slides.

s25
00:01:53.920 --> 00:01:58.560
Um, I'm not the biggest token token maxer.

s26
00:01:58.560 --> 00:02:00.240
Uh, I I think I'm doing all right.

s27
00:02:00.240 --> 00:02:04.159
I see some folks doing like, you know, a couple couple billion every day.

s28
00:02:04.159 --> 00:02:16.319
Uh, the goal of this talk isn't just to like waste all your tokens, but really help you avoid wasting your tokens by telling you what has actually worked and in particular sort of the tricks I use to make these things productive.

s29
00:02:16.319 --> 00:02:23.440
Um, and again, the goal, like I said earlier today, was to catch you up on what's changed in the Codeex app, uh, give you some time to set things up.

s30
00:02:23.440 --> 00:02:27.200
So, if you have time right now and you haven't downloaded Codex, just go ahead and do that.

s31
00:02:27.200 --> 00:02:29.440
And then we can go a little bit deeper into setting things up.

s32
00:02:29.440 --> 00:02:39.200
And so, I've actually prepared a little monor repo that you can use to clone in, get all the skills that you need, get all the setup that you need, and go from there.

s33
00:02:39.200 --> 00:02:40.560
So, let's go a little bit deeper.

s34
00:02:40.560 --> 00:02:42.800
Um, if you're new, feel free to set things up.

s35
00:02:42.800 --> 00:02:53.840
If you're pretty experienced, just like chill out, try some of the things I'm talking about and then, you know, I think every 15 minutes we'll have some time for questions and we can go into the more like

s36
00:02:53.840 --> 00:03:00.879
what feels like AI psychosis but maybe actually works kind of uh domain of using these systems, right?

s37
00:03:00.879 --> 00:03:07.360
A lot of the work in knowledge work now because the coding is solved, because a lot of this operations work is solved is really just understanding what you can do.

s38
00:03:07.360 --> 00:03:07.760
Right?

s39
00:03:07.760 --> 00:03:11.360
In a world without AI, maybe I have 10 teammates.

s40
00:03:11.360 --> 00:03:13.440
Each teammate is working on one thing.

s41
00:03:13.440 --> 00:03:16.480
So, I need to have like 10 things I'm keeping track of.

s42
00:03:16.480 --> 00:03:20.080
Now, we live in a world where like everyone I'm working with has 10 projects.

s43
00:03:20.080 --> 00:03:24.000
I now have to keep track of like 200 things and I don't know what's important.

s44
00:03:24.000 --> 00:03:25.680
There's definitely a Slack message I've missed.

s45
00:03:25.680 --> 00:03:28.480
There's probably some email I've missed somewhere by some foundation.

s46
00:03:28.480 --> 00:03:31.440
And Codeex helped me organize all of this stuff.

s47
00:03:31.440 --> 00:03:37.760
And so, again, the things I really want you to take away from this workshop is the fact that compaction works really, really well.

s48
00:03:37.760 --> 00:03:48.239
Like I have threads now that are like five weeks old that have you know 400 sub aents in them and they generally just know what they need to do.

s49
00:03:48.239 --> 00:03:49.840
They know what their job is.

s50
00:03:49.840 --> 00:03:53.040
I also want you to become really comfortable with talking your computer.

s51
00:03:53.040 --> 00:03:58.480
Uh earlier today I said that Tony Stark is not texting Jarvis, right?

s52
00:03:58.480 --> 00:04:04.000
And there's really no future when text input is the thing that matters.

s53
00:04:04.000 --> 00:04:05.360
I basically use a foot pedal.

s54
00:04:05.360 --> 00:04:08.879
So I like I have a button that is transcribe and a button that says enter.

s55
00:04:08.879 --> 00:04:17.199
And so I'll just come by my desk with my hands behind my back and I just go like you know fix this make this change also like message this guy on Slack

s56
00:04:17.199 --> 00:04:26.800
and then I just go back to you know talking to my co-workers and trying to figure out what is like the human side of actually working at OpenAI rather than just like monitoring Slack all day.

s57
00:04:26.800 --> 00:04:29.680
Uh appshots is my favorite feature of all time.

s58
00:04:29.680 --> 00:04:31.600
It's like very satisfying.

s59
00:04:31.600 --> 00:04:36.400
If any of you just like are on Codex right now, just press the command button side by side.

s60
00:04:36.400 --> 00:04:42.320
You're gonna get this real nice animation or you're gonna get a modal to tell you to install computer use, just do that.

s61
00:04:42.320 --> 00:04:43.919
It's amazing.

s62
00:04:43.919 --> 00:04:47.600
Uh, invest in your personal memory, right?

s63
00:04:47.600 --> 00:04:51.520
I at this point when someone asks me what I'm doing, I don't even have any idea.

s64
00:04:51.520 --> 00:04:57.120
I kind of have to like look at my threads and look at the conversations to figure out how much I've delegated away and how much has been automated.

s65
00:04:57.120 --> 00:05:07.120
And if you can then invest not only in skills for yourself but also plugins for your entire team, you can become the superhero that actually sort of augments the rest of your company.

s66
00:05:07.120 --> 00:05:11.840
It's one thing to say, "Oh man, like I can use all these tokens and look how many tokens I'm using."

s67
00:05:11.840 --> 00:05:19.120
But actually, if you're rewarded by how often the plugins you've built are being used by your teammates, that's a huge win, right?

s68
00:05:19.120 --> 00:05:20.880
How are we doing like implementation?

s69
00:05:20.880 --> 00:05:25.680
Like one of the most popular skills is just the like finalize the codeex app skill.

s70
00:05:25.680 --> 00:05:36.560
and anyone who makes a pull request basically triggers the skill before review and basically everyone at the company uses it and it's always been able to find things that I've done wrong or is against the style guide.

s71
00:05:36.560 --> 00:05:46.320
Um, one of the skills I have is just like reviewing docs and it's basically just copying the poll requests of uh the PR reviews of our friend Charlie over here.

s72
00:05:46.320 --> 00:05:52.000
And so I just have like a review my code like Charlie based off the past year of like feedback he's given on poll requests.

s73
00:05:52.000 --> 00:05:53.600
Review my code like Dominic.

s74
00:05:53.600 --> 00:05:56.560
And these things are incredibly valuable.

s75
00:05:56.560 --> 00:06:08.240
And then lastly, once you get more comfortable with all those first four things, your pinned threads with automations, these things that wake up these threads over time, they're going to feel like teammates.

s76
00:06:08.240 --> 00:06:18.800
And more interestingly, now that threads can talk to each other, so every thread has the ability to list other pin threads, has the ability to rename threads, and it has the ability to send messages to each other.

s77
00:06:18.800 --> 00:06:25.280
Not only can you have teammates, but you can have teammates that work together and you can effectively start having managers, right?

s78
00:06:25.280 --> 00:06:31.919
And so you you went from an IC enabled by an IDE, then you have pin threads that feel like a team where you're the manager.

s79
00:06:31.919 --> 00:06:37.039
And very quickly in the future, as models get better, this is where the the puck is going to skate to.

s80
00:06:37.039 --> 00:06:40.800
You're going to start having your like manager threads and then your IC threads.

s81
00:06:40.800 --> 00:06:46.000
And I'm sure in the future there's going to be some other crazy orchestration, right?

s82
00:06:46.000 --> 00:06:50.800
And all of this really is due to the fact that compaction works.

s83
00:06:50.800 --> 00:06:59.919
Even six months ago, I don't know like how many people here have been told this, but you were always told if a conversation goes very long, start a new thread,

s84
00:06:59.919 --> 00:07:00.319
right?

s85
00:07:00.319 --> 00:07:03.039
After 20 messages, it's it's not going to be that good.

s86
00:07:03.039 --> 00:07:07.680
Um, every feature should be its own its own uh conversation.

s87
00:07:07.680 --> 00:07:09.919
If you do a code review, start a new session.

s88
00:07:09.919 --> 00:07:11.520
Those things basically aren't true anymore.

s89
00:07:11.520 --> 00:07:13.919
And a lot of it has to do with compaction.

s90
00:07:13.919 --> 00:07:25.840
just pin the thread, rename it to the project ID, and that project thread should be able to delegate to sub agents, create new threads, and have conversations, and then write to your memory vault, which will allow you to

s91
00:07:25.840 --> 00:07:27.919
just log what's happening.

s92
00:07:27.919 --> 00:07:31.520
And then with automations, you can just wake them up.

s93
00:07:32.639 --> 00:07:35.280
And so there's really three acts of working with AI, right?

s94
00:07:35.280 --> 00:07:36.160
Working in codecs.

s95
00:07:36.160 --> 00:07:40.560
You bring the context in, and I'll talk about how you do that and what are the ways you can bring context in.

s96
00:07:40.560 --> 00:07:42.080
Then you work on it, right?

s97
00:07:42.080 --> 00:07:47.675
For example, the slide deck is just in the Codex app and then you take actions out in the real world.

s98
00:07:47.675 --> 00:07:49.280
[snorts]

s99
00:07:49.280 --> 00:07:58.800
So I asked this during the keynote, but I'm also curious what the audience here is doing, but how many people use dictation when they interact with an AI?

s100
00:07:59.120 --> 00:08:00.080
Nice.

s101
00:08:00.080 --> 00:08:03.840
How many use dictation even at work?

s102
00:08:04.160 --> 00:08:10.479
Yeah, I think we I think we should all be a little bit more shameless, you know, uh in doing these kinds of things.

s103
00:08:10.479 --> 00:08:24.479
uh you generally talk about three times faster than you type and it's just incredibly productive to be able to give the messy version of what you're thinking about to the AI and take that extra time and just try to be even more thoughtful to

s104
00:08:24.479 --> 00:08:26.160
the people you work with, right?

s105
00:08:26.160 --> 00:08:37.440
It's like now like I don't want to send my coworker like a 15-minute voice memo, but I should be I should feel very comfortable sending an AI a 15minute voice memo because you're going to include some random tangents.

s106
00:08:37.440 --> 00:08:51.120
You might just say, "I'm pretty sure I had a meeting with Charlie sometime last week about the agents SDK and it will go and read like 35 meeting messages to figure out which one it was and make it relevant."

s107
00:08:51.120 --> 00:08:57.519
And now all of a sudden like whatever memo you're going to write or some project tracker that you're trying to do uh is going to work, right?

s108
00:08:57.519 --> 00:09:02.000
But I would never do that with with um AI.

s109
00:09:02.399 --> 00:09:11.200
So as you guys are doing and uh just listening to this talk like try to just sort of set up codecs the way that I've been describing these things right.

s110
00:09:11.760 --> 00:09:20.000
So once you have your ability to just have you input into the machine a lot more effectively you can start thinking about using things like skills and plugins.

s111
00:09:20.000 --> 00:09:22.160
Um skills is a very simple construct.

s112
00:09:22.160 --> 00:09:24.160
It's just a couple of files and some scripts.

s113
00:09:24.160 --> 00:09:26.720
A plug-in is a library of these things.

s114
00:09:26.720 --> 00:09:31.920
And as you are just doing things many many times, you can start thinking about creating your own skills.

s115
00:09:31.920 --> 00:09:37.200
And as you package a bunch of skills, you might start thinking about building out a plugin.

s116
00:09:37.279 --> 00:09:40.240
If you want to install the plugins, we have a pretty good ecosystem now.

s117
00:09:40.240 --> 00:09:41.600
Something I'm really proud of.

s118
00:09:41.600 --> 00:09:44.080
If you just go in the sidebar, click plugins.

s119
00:09:44.080 --> 00:09:46.080
You can just search whatever plugins make sense for you.

s120
00:09:46.080 --> 00:09:47.920
So if you use Slack, you can install Slack.

s121
00:09:47.920 --> 00:09:52.000
If you use Gmail, Teams, most of these things are pretty built out.

s122
00:09:52.000 --> 00:10:02.800
If there's something that you feel like you are missing, just at me on Twitter and I'm sure one of my Twitter monitors will pick it up and send a message to someone in the connectors team.

s123
00:10:03.360 --> 00:10:11.120
If you're already actually looking at the plugins panel, I also really recommend just starting the process of setting up the Chrome extension as well as computer use.

s124
00:10:11.120 --> 00:10:21.279
We'll talk about this a little bit later, but like computer use was the first time in a long time I really sort of felt the AGI of being at work, right?

s125
00:10:21.279 --> 00:10:21.519
Right.

s126
00:10:21.519 --> 00:10:22.959
I was in iMovie for the first time.

s127
00:10:22.959 --> 00:10:27.519
I didn't know how to use it and it was just teaching me how to like export the movie.

s128
00:10:27.519 --> 00:10:31.839
It was able to like figure out where the sound effects were and it placed it in the right timestamps.

s129
00:10:31.839 --> 00:10:35.120
Really small things like this that really make using a computer very fun again, right?

s130
00:10:35.120 --> 00:10:37.360
Like I don't really have the time to like learn new software.

s131
00:10:37.360 --> 00:10:41.440
But if code if Codex can just show me what's going on, it's it's it's pretty awesome.

s132
00:10:41.440 --> 00:10:46.720
And as you can see the cursor move oftent times we're like cheering for it to to do the right action.

s133
00:10:46.720 --> 00:10:50.000
If you don't have a link for the Chrome extension, you can just click this button here.

s134
00:10:50.000 --> 00:10:56.160
The difference between computer use is computer use can work behind the scenes to control any application, right?

s135
00:10:56.160 --> 00:11:03.120
So whether it's Slack or some, you know, trading software, god forbid, uh it can control all of those things.

s136
00:11:03.120 --> 00:11:08.079
With the Chrome extension, it just controls everything in the Chrome app.

s137
00:11:08.079 --> 00:11:12.240
But the cool thing here too is again it doesn't take over your screen, right?

s138
00:11:12.240 --> 00:11:14.399
Sometimes I'll just be working on my computer.

s139
00:11:14.399 --> 00:11:25.839
I'll go to the Chrome browser and I'll realize that like Codex has just opened up three tabs to just look at my Twitter DMs and then just closes them back up as I'm just, you know, responding to some other email.

s140
00:11:25.839 --> 00:11:29.200
It's really cool to watch these things work in the background.

s141
00:11:29.200 --> 00:11:30.640
You can connect a bunch of other plugins.

s142
00:11:30.640 --> 00:11:32.240
I use things like Notion Linear.

s143
00:11:32.240 --> 00:11:33.519
I also use Obsidian.

s144
00:11:33.519 --> 00:11:36.160
It's just a good time.

s145
00:11:36.640 --> 00:11:47.920
Once you do this, what you're going to find is just by asking really vague questions about your day and just tagging the right plugins, you're going to realize the AI can learn a lot about you, right?

s146
00:11:47.920 --> 00:11:53.040
The AI does not a system now where it does like one search request and try to come up with an answer, right?

s147
00:11:53.040 --> 00:11:55.120
It might check your emails and find a loose thread.

s148
00:11:55.120 --> 00:11:58.399
It might check Slack or some meetings and figure out what's actually going on.

s149
00:11:58.399 --> 00:12:00.079
Who are these people?

s150
00:12:00.079 --> 00:12:09.680
I had I had one of my loops basically realize I was meeting with somebody look at their LinkedIn and realize that uh we went to the same university at the same time

s151
00:12:09.680 --> 00:12:16.079
and so the moment I jumped on my call I was like hey you were also from water you know do you remember this this and this person and immediately

s152
00:12:16.079 --> 00:12:26.240
we had a we had a connection right and obviously I didn't tell him it was AI but that's kind of some of the small things that you can do by just improving your automation you know it can make you closer to people

s153
00:12:26.240 --> 00:12:36.480
um as you build out your memory system right as as you build up the codeex memory system and your your ability to trigger plugins, maybe day one, you have to tag everything,

s154
00:12:36.480 --> 00:12:39.600
but I've become like a worse and worse manager over time.

s155
00:12:39.600 --> 00:12:46.720
Right now, I'll just open up the composer and just say like what has changed about the launch and it'll be able to do a good job, right?

s156
00:12:46.720 --> 00:12:53.600
And it it's that's possible because you have this long history, you have all these pin threads, you have these memories, right?

s157
00:12:53.600 --> 00:12:55.040
It's the same thing with an employee.

s158
00:12:55.040 --> 00:13:05.440
day one you have to show them every standard operating procedure you know but at some point you have an employee that has been here for seven years and you can just say hey I think you should make the company more money

s159
00:13:05.440 --> 00:13:14.560
and they can figure it out but it's only because they have this context um one thing you can just do for example if you want to try it out is you can just say hey check out the schedule

s160
00:13:14.560 --> 00:13:25.440
find all the sessions organize them in a markdown file put them in a spread spreadsheet and you'll just realize that we can do these things and maybe it'll do it with web search maybe you can do it with Chrome home.

s161
00:13:25.440 --> 00:13:29.680
Um, lots of fun things here.

s162
00:13:29.680 --> 00:13:35.360
If you want to get inspired by just looking at what kind of skills exist, we have two really great sources.

s163
00:13:35.360 --> 00:13:41.200
One is if you just run the skill installer skill, it will actually list out all of the OpenAI curated skills.

s164
00:13:41.200 --> 00:13:49.200
These include ones for things like GitHub, uh, best practices when writing playright code, you know, reotion for example.

s165
00:13:49.200 --> 00:13:58.399
But you can also check out websites like skill set.sh SH or use uh I think this is like Versel's skills uh tool and then you just find other skills, right?

s166
00:13:58.399 --> 00:14:07.279
So if I'm thinking about doing some more motion design or web design or I know that like someone told me I shouldn't do like use memo in React but I don't really know what that means.

s167
00:14:07.279 --> 00:14:11.360
I can now go install the React best practices skill, right?

s168
00:14:11.360 --> 00:14:22.320
But again, internally, one of the highest impact things I think I think you can do as like the AI champion in your company is to figure out what the team needs and build out those skills,

s169
00:14:22.320 --> 00:14:22.720
right?

s170
00:14:22.720 --> 00:14:26.560
I have a lot of skills on doing things like triage and how how do you do comms, right?

s171
00:14:26.560 --> 00:14:29.920
If there's an outage on Twitter, how do you like convert that?

s172
00:14:29.920 --> 00:14:35.600
Figure out who who needs to hear this, how do you like start the SEV, what stat sig gates do you need to check?

s173
00:14:35.600 --> 00:14:38.720
All these things are now just automated.

s174
00:14:39.839 --> 00:14:42.079
And that's exactly what I just said in this slide.

s175
00:14:42.079 --> 00:14:45.519
Um, we also have a really good plug-in creator and a skills creator skill.

s176
00:14:45.519 --> 00:14:50.639
So if you just ask Codex to trigger it, it will try to interview you to figure out what's going on.

s177
00:14:50.639 --> 00:14:59.199
And even in a more useful way, you can also just do it yourself once, document everything, and just tell Codex to make a skill from what you've learned, right?

s178
00:14:59.199 --> 00:15:03.839
And as long as you tell it, hey, by the way, every time you run this skill, you're allowed to edit yourself.

s179
00:15:03.839 --> 00:15:06.880
If you learn something new, you can edit the skill file.

s180
00:15:06.880 --> 00:15:09.199
These things will also improve over time.

s181
00:15:09.199 --> 00:15:17.600
And a big theme that's happening over this talk really is just you kind of have to just get really comfortable with asking.

s182
00:15:17.600 --> 00:15:23.360
Like we'll obviously try to make more of these things like more slash commands, but more and more like I'm just not touching a computer.

s183
00:15:23.360 --> 00:15:26.160
So it doesn't even make sense for me to like run a slash command.

s184
00:15:26.160 --> 00:15:34.000
I just want to say what's launching this week, check Twitter, you know, look at what I'm seeing in the browser.

s185
00:15:34.560 --> 00:15:39.440
Um the example I've been developing internally has just been this like developer experience triage skills, right?

s186
00:15:39.440 --> 00:15:46.720
So again this skill just documents like every Slack channel that should be uh you should be aware of.

s187
00:15:46.720 --> 00:15:49.360
It knows which engineers have worked on what projects.

s188
00:15:49.360 --> 00:15:52.160
It knows what Slack channels are taking in feedback.

s189
00:15:52.160 --> 00:15:58.880
I know that if you DM me on Slack and you tell me that some regression has happened, I need to ask for a feedback ID.

s190
00:15:58.880 --> 00:16:06.079
Right now, the agent does this automatically and it does it automatically with appshots.

s191
00:16:06.079 --> 00:16:10.639
So again, I don't know how many times I'm going to say this, but appshots is one of my favorite features.

s192
00:16:10.639 --> 00:16:17.040
How many people here have just like sent a screenshot to Slack to Codeex, right?

s193
00:16:17.040 --> 00:16:18.639
Like almost everybody.

s194
00:16:18.639 --> 00:16:22.000
But the issue is the screenshot does not have that much information, right?

s195
00:16:22.000 --> 00:16:23.920
The model has to then do OCR.

s196
00:16:23.920 --> 00:16:36.160
And if you send a screenshot of like a Slack thread, the model has to like read the Slack thread and then do a list Slack channels function and then realize like there's a guy named Charlie and then do like a list persons.

s197
00:16:36.160 --> 00:16:38.320
It takes a lot of hops.

s198
00:16:38.320 --> 00:16:44.240
But with appshots, it takes not only the image but the entire accessibility tree of the app.

s199
00:16:44.240 --> 00:16:48.399
And so when I give it an appshot of a Slack channel, it knows the channel ID.

s200
00:16:48.399 --> 00:16:51.279
So it knows exactly what function to call to post there.

s201
00:16:51.279 --> 00:16:54.720
It has the user ids of every single person in that channel.

s202
00:16:54.720 --> 00:16:59.440
So if I take an appshot and say do some research and reply, it's only one function call.

s203
00:16:59.440 --> 00:17:12.959
It knows to send the send a message to channel like U12725 and then because you know it knows that Charlie is like U425, it can do that in a very fast hop.

s204
00:17:12.959 --> 00:17:22.000
So, not only is it a very quick way of getting context into your system, it just gives so much more context that these subsequent tool calls do a really good job.

s205
00:17:22.000 --> 00:17:28.559
I have not like filled out a form in like two weeks because I just now tell Codeex to fill out this form, right?

s206
00:17:28.559 --> 00:17:30.080
It it knows all the fields.

s207
00:17:30.080 --> 00:17:33.840
It then figures out that it's in Chrome and so it'll use the browser extension.

s208
00:17:33.840 --> 00:17:36.320
If it's in Safari, it'll use computer use.

s209
00:17:36.320 --> 00:17:39.440
The model has become really really intelligent.

s210
00:17:39.440 --> 00:17:47.679
And so just like you might have a manager that gets an email and they forward the email to me with like three question marks and is your job to figure out what's going on.

s211
00:17:47.679 --> 00:17:51.919
You can kind of start doing that with your AI as you start investing in these skills.

s212
00:17:51.919 --> 00:17:56.400
And most of this is because of the fact that you've built out your memory system.

s213
00:17:56.400 --> 00:18:08.000
So if if you guys are are taking a look at these these slides, JXML/personal monorreo template that is actually the template I use on my personal computer.

s214
00:18:08.000 --> 00:18:14.720
It's basically just a directory tree and a bunch of skills that I use to sort of grow out my memory.

s215
00:18:14.799 --> 00:18:26.240
I'll also make one call out which is uh if you open this in your browser just press appshots and tell Codus to set this up for you and then you can pay attention to the rest of the talk.

s216
00:18:30.000 --> 00:18:30.240
Yeah.

s217
00:18:30.240 --> 00:18:30.480
Yeah.

s218
00:18:30.480 --> 00:18:32.480
Yeah.

s219
00:18:33.840 --> 00:18:38.160
You can just tell Codeex, Jason has written a personal monorreo template on GitHub.

s220
00:18:38.160 --> 00:18:41.440
Please find it and install it.

s221
00:18:43.120 --> 00:18:44.640
All right.

s222
00:18:44.640 --> 00:18:46.640
Yep.

s223
00:18:51.200 --> 00:18:51.600
Yeah.

s224
00:18:51.600 --> 00:18:54.160
So, this is this is a really good point.

s225
00:18:54.160 --> 00:19:05.919
So like for example on the DX team I make a lot of demos and so I have like 16 repos like you know real time demo one like real time demo two like funny right you have all these demos

s226
00:19:05.919 --> 00:19:20.799
I don't create new projects for them right the only project that exists on my sidebar is the like personal monor repo sidebar but codeex is able to still manage files outside of that project directory

s227
00:19:20.799 --> 00:19:26.559
and so in my agents MD file I just say, don't save any of the code in the monor repo.

s228
00:19:26.559 --> 00:19:28.880
Save it in like slashdev.

s229
00:19:28.880 --> 00:19:33.200
And just by that one line, if I tell it to clone a new project, it saves it in /dev.

s230
00:19:33.200 --> 00:19:38.240
If I tell it that I want to work in my slides, it knows that there's like a slashdev slides directory.

s231
00:19:38.240 --> 00:19:40.320
But it's just an easier way of managing everything, right?

s232
00:19:40.320 --> 00:19:48.240
Like I want to start all my projects from my personal vault and then it can touch the file system in any way that it wants to.

s233
00:19:48.240 --> 00:19:58.559
um one column it kind of breaks uh like git review sometimes in the sidebar but generally it's been a pretty good experience for me because I just re I just review my code in in GitHub.

s234
00:19:59.360 --> 00:20:01.200
Sweet.

s235
00:20:01.200 --> 00:20:04.640
Um these are some of the skills I have just installed there.

s236
00:20:04.640 --> 00:20:08.640
Uh there's no need to take a photo just ask codeex afterwards.

s237
00:20:08.640 --> 00:20:14.240
But um the assistant plugin basically has the ability to uh onboard you.

s238
00:20:14.240 --> 00:20:15.200
It will interview you.

s239
00:20:15.200 --> 00:20:20.720
It will figure out what plugins you need to install and then it will actually go create the threads it thinks it needs.

s240
00:20:20.720 --> 00:20:21.760
It'll create the automations.

s241
00:20:21.760 --> 00:20:22.960
It's a pretty fun one.

s242
00:20:22.960 --> 00:20:27.360
I have a bunch of skills on like auditing AI code and AI writing.

s243
00:20:27.360 --> 00:20:33.120
Um, I don't include this, but one of the my favorite skills of all time is called write like me.

s244
00:20:33.120 --> 00:20:47.520
And if you want to make one like that, all you had to tell Codeex is, "Hey, Codex, I want you to read all the emails I've written in the past six months, all the Slack messages I've written the past six months, and write a style guide for how to message just like me."

s245
00:20:47.520 --> 00:20:48.240
And then that's it.

s246
00:20:48.240 --> 00:20:53.520
And then anytime I tell it to send a Slack message or write an email, it'll go, "Okay, this is an email.

s247
00:20:53.520 --> 00:20:58.000
Clearly, this is just like a customer support form, so I will be much more stern in my messaging.

s248
00:20:58.000 --> 00:20:59.919
Let me go draft this email."

s249
00:20:59.919 --> 00:21:01.919
Hasn't failed me yet.

s250
00:21:01.919 --> 00:21:10.880
Um, one thing I've also added that I think are are really valuable to call out is I've made my own loop skill just because I I do like having a slash command every once in a while.

s251
00:21:10.880 --> 00:21:13.120
I'll talk about this in in part two.

s252
00:21:13.120 --> 00:21:18.799
And I also have a skill called simple HTML artifact that just designs artifacts the way I like them.

s253
00:21:18.799 --> 00:21:20.559
I want my backgrounds to be white.

s254
00:21:20.559 --> 00:21:23.200
I want some uh certain style guides.

s255
00:21:23.200 --> 00:21:28.320
And an Ultra Goal, which is like a super version of Goal that we'll also talk a little bit more about.

s256
00:21:28.320 --> 00:21:31.919
Um, and then if anyone's curious, like new person, new project.

s257
00:21:31.919 --> 00:21:35.039
That's just a way of like writing a script to bootstrap a new person.

s258
00:21:35.039 --> 00:21:37.600
I kind of have like a palunt here for my personal life now.

s259
00:21:37.600 --> 00:21:39.200
It's just like a CRM.

s260
00:21:39.200 --> 00:21:47.520
And basically, anytime my AI agent like finds a new person that's emailed me or messages me on Slack or on iMessage, I just keep track of these things.

s261
00:21:47.520 --> 00:21:50.799
And the new project is the same way.

s262
00:21:51.919 --> 00:21:52.720
Let me just double check.

s263
00:21:52.720 --> 00:21:53.520
Yeah, cool.

s264
00:21:53.520 --> 00:22:00.640
Um, and so I'll give you maybe like 10 minutes to try to try to set this up and we can go in a little bit of a Q&A.

s265
00:22:00.640 --> 00:22:11.760
I'm happy to answer any questions about like how we bring context into our systems, how I've organized my personal memory vault and uh, you know, some other crazy uses of app shots if anyone has any questions.

s266
00:22:11.760 --> 00:22:12.000
Yeah.

s267
00:22:12.000 --> 00:22:12.559
What's your question?

s268
00:22:12.559 --> 00:22:16.159
Does this get rid of the need for like an

s269
00:22:16.215 --> 00:22:18.215
[snorts]

s270
00:22:20.240 --> 00:22:20.720
Yeah.

s271
00:22:20.720 --> 00:22:24.400
Um, so the question was, do I still basically use Obsidian Brain?

s272
00:22:24.400 --> 00:22:28.960
The answer is yes, because I still want to sort of like keep track of everything.

s273
00:22:28.960 --> 00:22:35.760
Um, one thing I actually really like doing is I make my monor repo vault like a git repo.

s274
00:22:35.760 --> 00:22:41.840
And so maybe it'll work on it for like a couple of days and I'll come back and I'll just run git diff.

s275
00:22:41.840 --> 00:22:46.880
And by running git diff, I can just see like what the model has updated and what the model has not updated.

s276
00:22:46.880 --> 00:22:54.000
And I can just confidently review that over time and just realize that, oh yeah, like I guess Charlie did respond to this person and close the loop.

s277
00:22:54.000 --> 00:22:56.880
And I didn't realize that, but now I know, right?

s278
00:22:56.880 --> 00:23:00.400
And and oftentimes that's relevant in another conversation.

s279
00:23:00.400 --> 00:23:05.520
More than that, it's also very helpful for when other people are asking me questions, right?

s280
00:23:05.520 --> 00:23:12.960
Codeexes will feel very good about reading my memory vault, drafting a response, and then ask me for permission to send that message off.

s281
00:23:12.960 --> 00:23:19.200
And so if someone messaged me on Slack a question that the AI could have answered, the AI will just try to answer it.

s282
00:23:19.200 --> 00:23:24.000
Um, and it might be simple things like, oh, like who should I talk to about this project, right?

s283
00:23:24.000 --> 00:23:27.039
And the model knows because it's it's in the memory vault.

s284
00:23:27.039 --> 00:23:37.760
Um, one thing I also call is if you want to use more tokens, you can also have like custom automations where the job is to maintain and manage and garden your memory vault.

s285
00:23:37.760 --> 00:23:42.480
Um, but generally that has not been a big issue for me.

s286
00:23:42.720 --> 00:23:45.440
One question over there.

s287
00:23:55.200 --> 00:23:57.200
Yeah,

s288
00:23:59.679 --> 00:24:04.720
honestly I generally go down the path of like yolo one shot only because

s289
00:24:04.720 --> 00:24:08.640
Oh, that's scared the hell out of me.

s290
00:24:08.799 --> 00:24:16.960
Um, only because I know that like the way I build my skills is that they they self-improve all the time, right?

s291
00:24:16.960 --> 00:24:25.200
Like I think the difference would be if I make a skill that I share with my team, I think about that a little bit more, right?

s292
00:24:25.200 --> 00:24:30.640
Because it's like okay, do do does the does the triage plugin know that like who is working on what feature?

s293
00:24:30.640 --> 00:24:32.159
Can it route correctly?

s294
00:24:32.159 --> 00:24:40.880
For my personal work, I generally just build a skill as quickly as possible and every time it makes a mistake, I just correct it and I tell it to to move on.

s295
00:24:40.880 --> 00:24:48.799
And then generally what happens is if I've used a skill for two months, I just generally feel pretty good about sharing with my team because I I've just experienced it working.

s296
00:24:48.799 --> 00:25:00.480
Um yeah, most of my skills connect to so many other plugins and connectors that uh I just don't know how to eval because I can't like snapshot my Slack

s297
00:25:00.480 --> 00:25:02.559
at any given time.

s298
00:25:02.559 --> 00:25:05.200
There's a question over there.

s299
00:25:09.520 --> 00:25:27.919
Sometimes I'll use the codec cli every once in a while if I want to like like be a little bit faster, but generally the desktop app has pretty good has a pretty good experience primarily because everything I do is an appshot.

s300
00:25:28.480 --> 00:25:33.120
Like if I'm watching a video, I'll just like appshot like summarize this and I'll continue to watch the video.

s301
00:25:33.120 --> 00:25:36.720
I'll just watch a video with like the LLM like summary, right?

s302
00:25:36.720 --> 00:25:43.760
Or it's like if I see some kind of form or someone asked me to sign something, I go like appshot use docuign like sign this and save it to my desktop.

s303
00:25:43.760 --> 00:25:50.080
Uh like last week it like docu signed something then like found a faxing service and like fax my medical records.

s304
00:25:50.080 --> 00:25:53.360
Like that's awesome, but the CLI can't really do that.

s305
00:25:53.360 --> 00:25:59.200
Um yeah, any other questions?

s306
00:26:00.000 --> 00:26:02.000
Yep.

s307
00:26:02.080 --> 00:26:04.080
Why?

s308
00:26:04.720 --> 00:26:06.159
Like I'm like learning to juggle.

s309
00:26:06.159 --> 00:26:08.400
I'm like I'm like learning to play the drums.

s310
00:26:08.400 --> 00:26:10.960
Um well, I think it's like two things.

s311
00:26:10.960 --> 00:26:15.440
Like in the office, what I'm trying to do is I'm trying to like talk to more people, right?

s312
00:26:15.440 --> 00:26:20.240
It's like it's like I'm just the AI's assistant to get more context that the AI can't get.

s313
00:26:20.240 --> 00:26:25.600
Uh no, I think my job when I'm at work really is just when the AI is running, I should be talking to somebody.

s314
00:26:25.600 --> 00:26:33.200
I should be like learning about what they're working on, try to make connections and then figure out what are the, you know, points of connection, right?

s315
00:26:33.200 --> 00:26:38.640
It's like I should be talking to more people in real life as AI works.

s316
00:26:38.640 --> 00:26:40.000
Like someone had a question over there.

s317
00:26:40.000 --> 00:26:42.000
Oh,

s318
00:26:51.318 --> 00:26:53.039
[snorts]

s319
00:26:53.039 --> 00:26:54.400
yeah.

s320
00:26:54.400 --> 00:27:12.960
So the question is like when do I think 55 is overkill versus 53 spark I think this is colored by two things like because I have unlimited tokens I I don't really make those decisions and then secondly because I'm not watching my AI work like most of these things are automations that run in the background the latency

s321
00:27:12.960 --> 00:27:27.440
has not really affected me the times where I use Spark is primarily when there's a very simple uh there's a really simple computer use task Like I just wanted to like click all the buttons and fill out this form

s322
00:27:27.440 --> 00:27:33.200
like uh I think I think I have a thing that just checks me into flights and that is like a spark agent.

s323
00:27:33.200 --> 00:27:44.000
And so now like anytime there's an email that's that's like a flight check in my agent will check me in, download the boarding pass and then send the boarding pass to myself on iMessage,

s324
00:27:44.000 --> 00:27:44.880
right?

s325
00:27:44.880 --> 00:27:48.000
And like I just never do that kind of stuff anymore.

s326
00:27:48.000 --> 00:27:59.520
Uh again, it is really weird when you're just like working all of a sudden you check your you check your Chrome desktop and it's just like you know JetBlue is just like the first page but again it's it speaks to the fact that like

s327
00:27:59.520 --> 00:28:08.320
having access to your computer is uniquely powerful because it has your O and your credentials and and your your um your file system.

s328
00:28:08.320 --> 00:28:09.919
Yeah.

s329
00:28:09.919 --> 00:28:12.240
Over there.

s330
00:28:16.640 --> 00:28:18.640
Yeah.

s331
00:28:20.640 --> 00:28:21.760
Sorry, you're you're really quiet.

s332
00:28:21.760 --> 00:28:24.559
Do you mind just speaking up?

s333
00:28:41.360 --> 00:28:41.679
Yeah.

s334
00:28:41.679 --> 00:28:53.600
So I have we'll talk about this basically in the next section but um with remote control I can control both my local computer and like a remote computer.

s335
00:28:53.600 --> 00:28:57.679
I think the difference is computer use is tricky because it has to be on your computer.

s336
00:28:57.679 --> 00:28:58.640
That's one thing.

s337
00:28:58.640 --> 00:29:06.080
The second thing too is if you go into settings computer use there's a flag called locked use.

s338
00:29:06.080 --> 00:29:15.120
And if you enable that, as long as your laptop is plugged in, even if the monitor is closed, you can still trigger computer use commands through your phone.

s339
00:29:15.120 --> 00:29:20.880
Um, that also gets really weird because like go on.

s340
00:29:22.880 --> 00:29:24.880
Yeah,

s341
00:29:31.919 --> 00:29:32.880
you're you're really quiet.

s342
00:29:32.880 --> 00:29:34.320
I can't hear you.

s343
00:29:34.320 --> 00:29:34.559
Okay.

s344
00:29:34.559 --> 00:29:35.600
Okay, cool.

s345
00:29:35.600 --> 00:29:42.559
Um, yeah, like if you have multiple computers, you can still connect both your your your iPhone to both those devices, right?

s346
00:29:42.559 --> 00:29:44.559
Like some people just have a Mac mini.

s347
00:29:44.559 --> 00:29:51.120
Uh, I think the difference is do you want to control your codecs or specifically computer use because that that requires like an operating system with a guey.

s348
00:29:51.120 --> 00:29:54.240
Um, but we can talk about this in in a little bit.

s349
00:29:54.240 --> 00:29:56.240
Cool.

s350
00:29:58.159 --> 00:30:00.720
Like I said before, were there any more questions?

s351
00:30:00.720 --> 00:30:02.559
I don't know if someone just raised their hand.

s352
00:30:02.559 --> 00:30:04.720
Go ahead.

s353
00:30:05.039 --> 00:30:08.159
risk and how do you control that?

s354
00:30:08.159 --> 00:30:20.799
Yeah, I mean there's always some kind of risk like like I think earlier versions might like edit a document a little too eagerly, right?

s355
00:30:20.799 --> 00:30:37.840
Um, but realistically I think we've done I I think these models have done a really good job of being very precautious and more often than not it's me going like no please just just do it like just just like just sign the document like this is like please just like send this message.

s356
00:30:37.840 --> 00:30:43.919
Um I found that uh the 55 models are pretty reluctant to take these like destructive actions.

s357
00:30:43.919 --> 00:30:44.880
That's one thing.

s358
00:30:44.880 --> 00:30:55.279
The second thing is if you look at the sidebar here you have the ability to change your permissions.

s359
00:30:55.279 --> 00:31:02.720
And so as a show of hands, like how many people use like uh ask me for every permission?

s360
00:31:02.720 --> 00:31:03.760
Yeah.

s361
00:31:03.760 --> 00:31:04.399
Yeah.

s362
00:31:04.399 --> 00:31:04.960
Exactly.

s363
00:31:04.960 --> 00:31:05.440
Okay.

s364
00:31:05.440 --> 00:31:11.600
How many people use like full auto full permissions yolo mode?

s365
00:31:11.600 --> 00:31:12.080
Okay.

s366
00:31:12.080 --> 00:31:13.200
I don't like that.

s367
00:31:13.200 --> 00:31:17.520
Um and then how many people have used auto review?

s368
00:31:17.520 --> 00:31:18.320
Yeah.

s369
00:31:18.320 --> 00:31:21.440
So, I think auto review is actually has been really really great.

s370
00:31:21.440 --> 00:31:26.399
And again, I'm usually annoyed by the fact that my models won't do more than I want them to do.

s371
00:31:26.399 --> 00:31:30.720
Um, and so generally has not been as big of an issue.

s372
00:31:30.720 --> 00:31:41.600
The only times the only examples where I'm really annoyed is it will like edit documents it shouldn't be editing, but I just like add something with the HSMD and it's never really

s373
00:31:41.600 --> 00:31:43.440
messed with me too much.

s374
00:31:43.440 --> 00:31:51.760
Yeah, I know that's not a real answer, but I think with a combination of auto review and agents MD file, I have generally felt pretty safe.

s375
00:31:51.760 --> 00:31:52.559
Yeah.

s376
00:31:52.559 --> 00:31:56.559
And then if you're also at an organization, there's different admin settings that you can have.

s377
00:31:56.559 --> 00:32:06.640
So, for example, at OpenAI, uh you can't use an MCP server to send an email if any of the people in that email is a non OpenAI email, right?

s378
00:32:06.640 --> 00:32:11.279
Or like you can't uh send a Slack message to external Slack channels.

s379
00:32:11.279 --> 00:32:14.960
Um, that's when things get dangerous, right?

s380
00:32:14.960 --> 00:32:18.080
But these are some things that you can control.

s381
00:32:19.039 --> 00:32:20.799
One question over there.

s382
00:32:20.799 --> 00:32:22.799
Yeah.

s383
00:32:29.679 --> 00:32:35.360
Do you have any concerns regarding either security and or privacy?

s384
00:32:36.559 --> 00:32:38.720
That's not because I work here.

s385
00:32:38.720 --> 00:32:48.720
Um, I think that I think that's hard to answer because I don't really know what are like data retention policies for like individual versus enterprise.

s386
00:32:48.720 --> 00:32:51.519
But Charlie, do you have any thoughts there?

s387
00:32:51.519 --> 00:32:56.159
I'm just gonna throw over to you.

s388
00:32:59.279 --> 00:33:00.799
Privacy.

s389
00:33:00.799 --> 00:33:07.919
Let's say you get a I don't know email offering you a job at a competitor company.

s390
00:33:07.947 --> 00:33:09.760
[snorts]

s391
00:33:09.760 --> 00:33:15.200
Uh I mean I I think a lot of it goes back to we do want to make like the models are fallible, right?

s392
00:33:15.200 --> 00:33:20.399
I don't think anybody in this room would be shocked to understand that like you can still jailbreak a model for example.

s393
00:33:20.399 --> 00:33:31.360
Uh but both the the models themselves are getting smarter and better at not you know doing silly things and at the same time we're figuring out like Jason mentioned what are those bigger

s394
00:33:31.360 --> 00:33:33.519
you know limitations around the sandbox.

s395
00:33:33.519 --> 00:33:38.480
We we started with very simple sandboxes where it was like you can just run this command and nothing else.

s396
00:33:38.480 --> 00:33:51.039
And slowly the sandbox has grown to the entire computer and I think we're figuring out what are the like computer level or organization level you know edges to that sandbox that we need to build.

s397
00:33:52.720 --> 00:33:56.320
This is me using the delegate skill.

s398
00:33:57.600 --> 00:33:58.720
Great answer.

s399
00:33:58.720 --> 00:34:02.559
Any more questions before we jump into act two?

s400
00:34:02.559 --> 00:34:03.200
Sweet.

s401
00:34:03.200 --> 00:34:03.919
Awesome.

s402
00:34:03.919 --> 00:34:07.840
So, we just talked about a bunch of different ways of bringing context into the system, right?

s403
00:34:07.840 --> 00:34:18.000
You can use your voice, you have plugins, you can use appshots, and then you can also design different skills and plugins to figure out how to do more system systematic work.

s404
00:34:18.000 --> 00:34:21.200
So, now we can talk a little bit more about the work itself.

s405
00:34:21.200 --> 00:34:26.159
So, like I said before, like every pinned thread effectively is a teammate in my mind.

s406
00:34:26.159 --> 00:34:28.159
I have my chief of staff thread.

s407
00:34:28.159 --> 00:34:31.839
I have uh you know, Swix prefers to call it like, you know, the god thread.

s408
00:34:31.839 --> 00:34:37.119
uh I I have a thread to manage the agency SDK whether that's implementation and documentation.

s409
00:34:37.119 --> 00:34:46.720
It has two sub agents that it delegates to uh the CLI, the open source program and uh Twitter.

s410
00:34:49.520 --> 00:34:58.320
But if you want to make it wake up, right, all you have to say is keep an eye on this until sometime, you know, keep an eye on this every 30 minutes.

s411
00:34:58.320 --> 00:35:03.599
If you remember those like secret words, you can effectively automate like about everything in your life at this point.

s412
00:35:03.599 --> 00:35:09.359
Um, and what this does, it will trigger a heartbeat automation, a thread automation.

s413
00:35:09.359 --> 00:35:14.800
You should think of it as a way of scheduling a message back into the thread.

s414
00:35:14.800 --> 00:35:15.119
Right?

s415
00:35:15.119 --> 00:35:21.440
In the beginning when we set up automations, it was very much the case that a automation would create a new thread every time.

s416
00:35:21.440 --> 00:35:25.599
So it might be give me a morning brief and it would create a new thread and then it would do this kind of work.

s417
00:35:25.599 --> 00:35:31.839
But as these models got better, I think the right design is scheduling these messages into the same thread.

s418
00:35:31.839 --> 00:35:36.320
So for example, because if you if you download the monor repo, we have a loop skill.

s419
00:35:36.320 --> 00:35:40.000
If you just do loop, right, this is the equivalent of just saying keep an eye on this.

s420
00:35:40.000 --> 00:35:45.040
Uh keep an eye on this pull request anytime there's feedback fix it.

s421
00:35:45.040 --> 00:35:46.720
Make sure it's always mergeable.

s422
00:35:46.720 --> 00:35:48.400
Make sure it's always rebased on master.

s423
00:35:48.400 --> 00:35:50.960
Make sure that CI is always passing.

s424
00:35:50.960 --> 00:35:52.400
And it'll just do that.

s425
00:35:52.400 --> 00:35:56.320
And then maybe you make a pull request in in on a Monday, you get really busy.

s426
00:35:56.320 --> 00:36:00.079
Thursday afternoon, all the feedback has been integrated.

s427
00:36:00.079 --> 00:36:08.640
You know, CI is passing and uh you know, you're not like 4,000 commits behind uh the main thread.

s428
00:36:08.730 --> 00:36:08.800
[snorts]

s429
00:36:08.800 --> 00:36:10.800
I also do this with support, right?

s430
00:36:10.800 --> 00:36:16.880
Again, if if someone is like dealing with some issues on on Twitter, on Slack, Appshot, right?

s431
00:36:16.880 --> 00:36:30.480
you know like at like at developer experience skill figure this out and it'll say okay this was an issue on the browser side like James is the one that works in a browser the channel is called like browser feedback

s432
00:36:30.480 --> 00:36:45.520
I'm going to post in that channel DM James and then I'll use computer use to open up Twitter to let them know that I've like escalated this internally and then I will check every hour to figure out if James on that channel has responded

s433
00:36:45.520 --> 00:36:56.480
and then let the user No. And then sometime later in the future, you're like checking your computer and all of a sudden like Twitter opens up and it's just like hey so and so this has been resolved

s434
00:36:56.480 --> 00:37:02.960
and then you just you you just hit enter and then you check your thread it's like oh yeah pull request has been made it will get merged by next Thursday

s435
00:37:02.960 --> 00:37:14.079
and like this is a crazy experience to witness right this is this actually allows us to do way more support without making it like the worst part of my job.

s436
00:37:16.240 --> 00:37:22.160
And then with a chief of staff thread, oh this is this is I remember this is where my slides get really messed up thanks to a codeex.

s437
00:37:22.160 --> 00:37:23.920
So I can't do everything just yet.

s438
00:37:23.920 --> 00:37:32.800
Um you can also just do a loop that says check all my connectors and give me an update as to what is the most important thing I should be thinking about.

s439
00:37:32.800 --> 00:37:34.880
You know give it give it to me in a nice format.

s440
00:37:34.880 --> 00:37:38.000
You know make sure you have links to every email that you read.

s441
00:37:38.000 --> 00:37:41.280
Make sure you have a Slack link so you can deep link into the application.

s442
00:37:41.280 --> 00:37:44.880
And now just it's been really really helpful to track these random things.

s443
00:37:44.880 --> 00:37:56.720
And again I think in my chief of staff thread I had that line that says check into all my flights if you can like send me the book the uh the boarding pass on iMessage

s444
00:37:56.720 --> 00:37:58.079
and it just works.

s445
00:37:58.079 --> 00:38:08.000
And again it's really weird when you start seeing your computer doing doing stuff while you're while you're working because again most of these tasks run in the background and because I've had my permissions on

s446
00:38:08.000 --> 00:38:10.640
it's not like it needs to tell me that it's using Safari.

s447
00:38:10.640 --> 00:38:17.839
I just like find out that it's using Safari that might be scared to some people, but you know, it's pretty great.

s448
00:38:17.839 --> 00:38:26.640
And then lastly, this is something that happens really a lot at at OpenAI, which is I don't even know what's what what's launching, right?

s449
00:38:26.640 --> 00:38:28.000
Is something delayed?

s450
00:38:28.000 --> 00:38:29.119
Has something landed?

s451
00:38:29.119 --> 00:38:31.119
Is it, you know, going to happen at 11:00 a.m.?

s452
00:38:31.119 --> 00:38:33.359
Is it happen at 4 p.m.?

s453
00:38:33.359 --> 00:38:35.440
I have no idea.

s454
00:38:35.440 --> 00:38:43.119
We've actually made a ton of progress on this and I'm pretty sure this is also just automation and AI, but I actually used to have codeex make me a PowerPoint

s455
00:38:43.119 --> 00:38:48.000
every Wednesday night of what's shipping for the rest of the week, right?

s456
00:38:48.000 --> 00:38:48.800
And that's useful.

s457
00:38:48.800 --> 00:38:50.640
And then you just say, "Great, it's useful for me.

s458
00:38:50.640 --> 00:38:54.000
Now, let me make sure I can just post this on the channel as a Slack message."

s459
00:38:54.000 --> 00:38:59.280
And now you're again using your skills not only to benefit yourself, but benefit your entire team.

s460
00:38:59.280 --> 00:39:02.720
That's kind of like the plug-in hero mindset.

s461
00:39:03.680 --> 00:39:04.960
And this one's pretty funny too.

s462
00:39:04.960 --> 00:39:05.920
Uh I have an example.

s463
00:39:05.920 --> 00:39:07.280
Let me just double check the slide.

s464
00:39:07.280 --> 00:39:16.400
Yeah, I have another example which has also been pretty crazy which is the one I gave during the keynote which is I had been editing like a short film

s465
00:39:16.400 --> 00:39:21.760
in iMovie and on my bike ride someone gave me feedback about the video.

s466
00:39:21.760 --> 00:39:25.599
So I just went on my phone and I just like sent told the like, "Okay, there's a file somewhere.

s467
00:39:25.599 --> 00:39:27.119
Can you just like find it in iMovie?

s468
00:39:27.119 --> 00:39:28.800
There's only one iMovie project.

s469
00:39:28.800 --> 00:39:29.839
Read the Slack message.

s470
00:39:29.839 --> 00:39:31.440
Export the video.

s471
00:39:31.440 --> 00:39:43.920
If you can't, if the Slack MCP server does not allow file upload, use computer use to upload the file and then watch that thread every hour and if they have any feedback, reexport the video and reshare it

s472
00:39:43.920 --> 00:39:45.680
and then like bite home.

s473
00:39:45.680 --> 00:39:50.000
And by the time I got home, it was like, oh, by the way, it was actually way easier to use a Google Drive connector.

s474
00:39:50.000 --> 00:39:53.040
So, I've just been uploading the same file on Google Drive instead.

s475
00:39:53.040 --> 00:39:56.079
So, they only have like one URL to manage.

s476
00:39:56.079 --> 00:40:03.520
And uh yeah, we like fixed a bunch of stuff in the typography and then we shipped it again like kind of mind-blowing stuff.

s477
00:40:03.520 --> 00:40:06.160
It's very simple but mind-blowing, right?

s478
00:40:06.160 --> 00:40:07.599
But that's what a heartbeat is, right?

s479
00:40:07.599 --> 00:40:11.599
A heartbeat is just a way of waking up your thread over time to take some actions.

s480
00:40:11.599 --> 00:40:14.320
The other thing you can do is set goals.

s481
00:40:14.320 --> 00:40:16.800
So slash goal is pretty amazing.

s482
00:40:16.800 --> 00:40:25.280
It basically defines a verification step and says, "Okay, as long as this is running, check this verification step.

s483
00:40:25.280 --> 00:40:28.240
if if it's not done, keep going, right?

s484
00:40:28.240 --> 00:40:29.839
Very simple idea.

s485
00:40:29.839 --> 00:40:35.680
Um, and as long as there's a verifier, it does really really well.

s486
00:40:35.680 --> 00:40:41.520
For example, I've just been uh migrating a bunch of software into Rust, right?

s487
00:40:41.520 --> 00:40:52.240
It's like if this is a Python project that is amendable to be rewritten in Rustgo, migrate the back end to Rust, make sure all the unit tests pass.

s488
00:40:52.240 --> 00:41:03.440
And I was able to not only rewrite the rich terminal library in Rust, I also rewrote UV and TypeScript um just to see if I could and uh we're like 100%

s489
00:41:03.440 --> 00:41:04.079
test coverage.

s490
00:41:04.079 --> 00:41:05.520
It's it's pretty amazing.

s491
00:41:05.520 --> 00:41:13.760
Obviously, you should not be doing this in your work, but it's it's very helpful to just understand that as these systems have better verification, you can make a lot of progress.

s492
00:41:14.400 --> 00:41:19.440
In the in the monor repo, I've also included a skill called ultra goal.

s493
00:41:19.440 --> 00:41:25.359
And all it does is instead of setting the goal in the app, we set it in a file, right?

s494
00:41:25.359 --> 00:41:27.599
So we have a goal MD file.

s495
00:41:27.599 --> 00:41:30.640
And what that means is you can edit the goal while it's being run.

s496
00:41:30.640 --> 00:41:35.520
So you can add more scope uh just like many many real projects do.

s497
00:41:35.520 --> 00:41:38.480
We also define a plan again that we can reference.

s498
00:41:38.480 --> 00:41:46.960
But the benefit of this is as you're learning more about the projects and you're changing the plan and the goal as these as these models are just like looping

s499
00:41:46.960 --> 00:42:01.599
uh it can update it understanding of the system and then sometimes I have like a state MD file or a work log just to track these like longer running tasks like if if things are running for like a day or two I want to know what's going on and I'm never going to read this like 4 gigabyte

s500
00:42:01.599 --> 00:42:10.640
like you know session JSON object but I can look at the work log have it have another model summarize it using like a side chat and go from there.

s501
00:42:11.280 --> 00:42:18.480
This meant to say remote control, but again, if folks are just like on their computers, I also recommend trying that out.

s502
00:42:18.480 --> 00:42:22.640
In the sidebar, there should be a button that says remote control, especially if you have the iOS app.

s503
00:42:22.640 --> 00:42:26.480
This is the thing where we talked about being able to control your phone.

s504
00:42:26.480 --> 00:42:28.960
So, control your computer through your phone, right?

s505
00:42:28.960 --> 00:42:38.880
So if you go on the iOS app, you enter codecs, you can you can do this like flow where you can scan a QR code and all of a sudden your your your uh touchp

s506
00:42:38.880 --> 00:42:45.359
can message and cue any thread in the in the application including I think remote threads.

s507
00:42:45.359 --> 00:42:54.800
Uh this is super powerful because again oftent times you know every time I try to leave the house someone's like asking me for something and now I can just ask codecs.

s508
00:42:54.800 --> 00:42:58.079
Uh really I should just be having something that monitors Slack and just does it.

s509
00:42:58.079 --> 00:43:01.359
But like I you know I'm not there yet.

s510
00:43:01.359 --> 00:43:08.560
But again this is one of those big uh you know feel the AGI moments, right?

s511
00:43:09.760 --> 00:43:10.400
Yeah.

s512
00:43:10.400 --> 00:43:17.839
And again like I said the chief of staff threat effectively is like the single source of truth for basically what's going on in in in my life on my personal computer.

s513
00:43:17.839 --> 00:43:19.119
I have a different one.

s514
00:43:19.119 --> 00:43:22.800
Uh lots of good stuff.

s515
00:43:22.880 --> 00:43:24.960
This is all I wrote for mine.

s516
00:43:24.960 --> 00:43:28.720
Create a create and pin a cha staff thread every day at 8 am.

s517
00:43:28.720 --> 00:43:34.720
Check all these connectors, figure out what's going on, and then uh you know, do a good job.

s518
00:43:34.720 --> 00:43:37.280
And again, you'll just start you'll start editing it over time, right?

s519
00:43:37.280 --> 00:43:40.480
Maybe you don't like the formatting or you wish you included links.

s520
00:43:40.480 --> 00:43:51.440
Uh for a while, what I made it do was if it found all the emails, not only to ask it to draft the responses, but I would make it open a Chrome tab for every email I need to reply to in Chrome.

s521
00:43:51.440 --> 00:44:02.079
And so I'll open my computer, I'll take a meeting, I come back and on my computer is just like seven Chrome tabs and I can just review the drafts and send each one like small things like this just to prepare your computer

s522
00:44:02.079 --> 00:44:03.920
while your meetings are happening.

s523
00:44:03.920 --> 00:44:05.520
Uh really productive.

s524
00:44:05.520 --> 00:44:08.800
So now we talked a little bit more about like just like doing the work itself, right?

s525
00:44:08.800 --> 00:44:15.680
We haven't really gone into things like artifacts just yet, but I'm also curious if anyone has any questions on how I've been doing things so far

s526
00:44:15.680 --> 00:44:16.240
over here.

s527
00:44:16.240 --> 00:44:19.200
So I notic so I do a lot of

s528
00:44:19.200 --> 00:44:20.880
Yeah.

s529
00:44:20.880 --> 00:44:23.040
I notic.

s530
00:44:27.920 --> 00:44:30.240
I get a lot of stuff.

s531
00:44:30.240 --> 00:44:32.240
So, what's your advice?

s532
00:44:32.240 --> 00:44:39.599
I generally always prefer to have the model write the goal or write the write the prompt itself.

s533
00:44:39.599 --> 00:44:43.520
Like more and more of these models are just getting better at doing that.

s534
00:44:43.520 --> 00:44:46.560
And it's like more in distribution to what they want.

s535
00:44:46.560 --> 00:44:50.640
Um, in reality, I just I will send like a 10-minute voice memo, right?

s536
00:44:50.640 --> 00:44:54.560
I'm just like like, you know, this is some issue that's happening.

s537
00:44:54.560 --> 00:44:57.440
I think there's a project about some thread.

s538
00:44:57.440 --> 00:44:58.880
Uh, I don't know if they got back to me.

s539
00:44:58.880 --> 00:45:00.960
I think their name is Dylan.

s540
00:45:00.960 --> 00:45:03.359
Uh, please look in Gmail.

s541
00:45:03.359 --> 00:45:07.359
Like, take it's like a really really messy.

s542
00:45:07.359 --> 00:45:09.839
And then it's like, okay, well, do I want to make a set of gold?

s543
00:45:09.839 --> 00:45:11.119
Do I want it to create a new thread?

s544
00:45:11.119 --> 00:45:13.359
Do I want to make a new skill?

s545
00:45:13.359 --> 00:45:16.240
Like that's really sort of where my taste lies now.

s546
00:45:16.240 --> 00:45:20.640
It's like, okay, how do I want to organize what the work product is, you know?

s547
00:45:20.640 --> 00:45:25.680
Do I tell it to then do all this work and put it into a index HTML to share it?

s548
00:45:25.680 --> 00:45:28.240
Do I want to make a word doc?

s549
00:45:28.240 --> 00:45:29.119
That's basically it.

s550
00:45:29.119 --> 00:45:32.000
But I generally just send very long messages.

s551
00:45:32.000 --> 00:45:37.839
Yeah, like for example here, like this is not the prompt for the chief of staff thread.

s552
00:45:37.839 --> 00:45:42.400
This is the prompt so the model can make the cha staff thread, right?

s553
00:45:42.400 --> 00:45:51.760
And that model will be much that output will be much better at determining how verbose the the automation is or how often it should check or what connectors.

s554
00:45:51.760 --> 00:46:03.119
Um and then because I have this monor repo, one of the things I do is every project file has a link to every slack channel this project is relevant for.

s555
00:46:03.119 --> 00:46:06.240
And the model will just see that and you go read those slack channels, right?

s556
00:46:06.240 --> 00:46:15.599
every like person file has their email address, their Slack connector, multiple work addresses, and they'll read all those things.

s557
00:46:15.599 --> 00:46:17.440
I would never prompt that myself.

s558
00:46:17.440 --> 00:46:19.440
Yeah.

s559
00:46:20.240 --> 00:46:20.880
Yeah.

s560
00:46:20.880 --> 00:46:21.119
Yeah.

s561
00:46:21.119 --> 00:46:27.680
So, I think in that example, what I realized was when I mentioned the Slack channels that are relevant for a project, the results were better.

s562
00:46:27.680 --> 00:46:30.800
So, I just added that in the front matter of like the markdown file.

s563
00:46:30.800 --> 00:46:34.240
But these are the things that you grow over time.

s564
00:46:46.400 --> 00:46:48.560
the only

s565
00:46:51.359 --> 00:46:54.160
I mean I have not tried like the deepest.

s566
00:46:54.160 --> 00:46:58.560
So the question is like what is the difference between this and like an open claw and a Hermes agent?

s567
00:46:58.560 --> 00:47:07.599
Think I think I'm sure there's differences I'm not aware of right now, but I can imagine a world where it's going to get much like very very similar very quickly,

s568
00:47:07.599 --> 00:47:07.839
right?

s569
00:47:07.839 --> 00:47:12.880
Like most of my work and I'll talk about this later on is like my threads manage themselves, right?

s570
00:47:12.880 --> 00:47:14.880
It could be the same thing as a sub agent.

s571
00:47:14.880 --> 00:47:22.000
Um I don't know how many people use Hermes agents and open claw for like very wide work, right?

s572
00:47:22.000 --> 00:47:27.520
Like I think I like I think I tried openclaw to do some like house automation stuff.

s573
00:47:29.760 --> 00:47:31.760
Yeah.

s574
00:47:36.480 --> 00:47:36.880
Yeah.

s575
00:47:36.880 --> 00:47:40.480
So the qu the comments like yeah with with these models there's only one thread.

s576
00:47:40.480 --> 00:47:48.720
I think that's very reasonable just in in reality there's just there's just like so many things that we work on that like I need the organization right it's like

s577
00:47:48.720 --> 00:47:56.319
you know it's like is there a world where like my banker and my therapist and my personal trainer and my girlfriend is the same person like maybe but like

s578
00:47:56.319 --> 00:48:10.800
my like you know tiny brain can't figure that out and like it's easy for me to understand what the work is by making folders right it's like the computer doesn't know the folders is but the folders are for me in some ways if that makes sense

s579
00:48:10.800 --> 00:48:13.920
Yeah, cool.

s580
00:48:13.920 --> 00:48:15.200
Great.

s581
00:48:15.200 --> 00:48:15.680
No more.

s582
00:48:15.680 --> 00:48:19.520
Yeah, one question that one.

s583
00:48:30.160 --> 00:48:32.160
Yeah.

s584
00:48:38.880 --> 00:48:39.680
Yeah.

s585
00:48:39.680 --> 00:48:45.200
skills, but like I didn't know that it just automatically.

s586
00:48:46.720 --> 00:48:47.839
Um I think it depends.

s587
00:48:47.839 --> 00:48:53.280
I think it depends on how proactive you are in like telling the AI to remember these things.

s588
00:48:53.280 --> 00:49:00.480
So for example, like once I realized I should include Slack channel IDs in like project documents, the model's like, "Oh, there's a Slack channel.

s589
00:49:00.480 --> 00:49:01.920
I should read the Slack channel."

s590
00:49:01.920 --> 00:49:03.680
And that became really obvious.

s591
00:49:03.680 --> 00:49:06.079
Now I I basically never tag things.

s592
00:49:06.079 --> 00:49:08.079
I don't really know when that happened.

s593
00:49:08.079 --> 00:49:18.720
Um but yeah, again a a lot of it is just getting the habit of remember this for next time, update the skill for next time, update the agent dot for next time.

s594
00:49:18.720 --> 00:49:21.280
And that is the

s595
00:49:21.280 --> 00:49:23.520
uh sometimes

s596
00:49:25.359 --> 00:49:27.839
I mean I think it would be hard for me to like prove it.

s597
00:49:27.839 --> 00:49:31.520
Like there's also a memory system that's like outside of the docs.

s598
00:49:31.520 --> 00:49:33.040
Generally, I'm like pretty happy with the memory.

s599
00:49:33.040 --> 00:49:38.559
I I don't know if if I can like give you like a time estimate, but I think I'll just try it out, right?

s600
00:49:38.559 --> 00:49:42.880
Like use it for a couple weeks, have make sure memory is turned on, by the way.

s601
00:49:42.880 --> 00:49:44.000
Like it's also in your settings.

s602
00:49:44.000 --> 00:49:58.240
I know our settings panel is like pretty crazy right now, but um yeah, I think I would just turn memories on and just see whether or not these changes happen over time because like I basically never I don't remember a single time I've like you like at mentioned something.

s603
00:49:58.240 --> 00:50:00.880
Um yeah,

s604
00:50:00.880 --> 00:50:02.800
and the last part is pretty pretty fast, right?

s605
00:50:02.800 --> 00:50:06.079
So we talked about reading context, we talked about working with the context.

s606
00:50:06.079 --> 00:50:09.440
Now that the last thing to do is just like write context.

s607
00:50:09.440 --> 00:50:13.760
Um most of this has been pretty pretty uh simple, right?

s608
00:50:13.760 --> 00:50:15.839
You can draft emails, you can draft Slack updates.

s609
00:50:15.839 --> 00:50:19.359
If you feel very brave, you can send them, but like be please be respectful.

s610
00:50:19.359 --> 00:50:26.240
Like um I'm sure Charlie has gotten hundreds of sent from chatbt uh Slack messages from me over time.

s611
00:50:26.240 --> 00:50:29.680
Uh but I hope they're they sound like me more now.

s612
00:50:29.680 --> 00:50:32.480
Uh building one pages is also pretty good.

s613
00:50:32.480 --> 00:50:44.079
Like this slide deck was made with uh codecs and soon we'll be able to do things like serve applications and now I think you know at least internally so much of the work that we do has just been sharing like

s614
00:50:44.079 --> 00:50:47.599
apps rather than like full documents.

s615
00:50:49.119 --> 00:50:52.720
I don't know how many people know about this but we also have a really good like artifacts ecosystem.

s616
00:50:52.720 --> 00:50:56.640
like more and more uh codeex has become a tool for all of the work that I do.

s617
00:50:56.640 --> 00:51:07.200
It can open and render like Excel spreadsheets, word documents, uh PDFs, slides and with the annotation tool uh editing things is like pretty fun.

s618
00:51:07.200 --> 00:51:12.160
So even with these slides, this is this is actually served on the inapp browser of the Codex app.

s619
00:51:12.160 --> 00:51:16.000
And what I'll do is I'll just give my talk and I'll press next and press next.

s620
00:51:16.000 --> 00:51:17.839
And then when I don't like something, I just select it.

s621
00:51:17.839 --> 00:51:18.880
It's like, hey, like fix this.

s622
00:51:18.880 --> 00:51:19.920
I don't like the white space.

s623
00:51:19.920 --> 00:51:21.920
Like these two slides need to be broken up two more slides.

s624
00:51:21.920 --> 00:51:23.280
I hit enter.

s625
00:51:23.280 --> 00:51:27.280
As Codex is working to clean this up, I'm just going down to get down the slides.

s626
00:51:27.280 --> 00:51:30.559
And it's it's generally been a pretty natural way of working.

s627
00:51:30.559 --> 00:51:39.200
Like this this deck really came from me reading my own blog post out loud and then generating the material as we go along.

s628
00:51:39.200 --> 00:51:44.400
But, you know, it's still it's still like two or three skills to make the slides look this way.

s629
00:51:45.280 --> 00:51:47.280
Yeah.

s630
00:51:47.920 --> 00:51:49.040
Um Yeah.

s631
00:51:49.040 --> 00:51:51.359
And then once you do that, you can do again again.

s632
00:51:51.359 --> 00:51:53.119
It's the same concept over and over again, right?

s633
00:51:53.119 --> 00:51:56.000
You can you can build out these loops that just touch other parts of the system.

s634
00:51:56.000 --> 00:51:59.520
Like most of our project tractors are just Google Sheets updated with loops.

s635
00:51:59.520 --> 00:52:02.559
Uh the slides are loops and the annotations.

s636
00:52:02.559 --> 00:52:03.760
Yeah, I just said everything.

s637
00:52:03.760 --> 00:52:05.040
My bad.

s638
00:52:05.040 --> 00:52:12.240
Um and then one thing that's also very helpful is like as the company gets more like context dense, right?

s639
00:52:12.240 --> 00:52:19.359
Maybe it's all OA agents, just the ability to like summarize things like over Slack has been incredibly useful.

s640
00:52:21.440 --> 00:52:26.880
That was clearly like a slop slide that uh Chad GBT edited in.

s641
00:52:28.240 --> 00:52:35.280
So once you can take actions on these D artifacts, I think the the biggest thing and the thing I really want people to try out is just computer use.

s642
00:52:35.280 --> 00:52:40.480
Um again, it's like it's like the first time I had that like feel the AGI moment, right?

s643
00:52:40.480 --> 00:52:43.200
Like a cursor is like trying to do some action.

s644
00:52:43.200 --> 00:52:50.319
you can see like move across the screen and like when it does it really well like you really gain a lot of faith in the system.

s645
00:52:50.319 --> 00:52:52.400
So we we obviously have like plugins, right?

s646
00:52:52.400 --> 00:52:58.319
And this is for sending stack messages, but then the inapp browser is going to get even more powerful soon, right?

s647
00:52:58.319 --> 00:53:03.040
We're going to be able to basically treat this like the browser that you use.

s648
00:53:03.040 --> 00:53:05.920
Like I now try to use the in browser as much as possible.

s649
00:53:05.920 --> 00:53:08.880
And then for everything else, use computer use.

s650
00:53:08.880 --> 00:53:11.839
Um how many people have used computer use by the way?

s651
00:53:11.839 --> 00:53:12.960
Very.

s652
00:53:12.960 --> 00:53:14.960
Oh, it's like 10% of you.

s653
00:53:14.960 --> 00:53:16.720
What's a crazy thing that you've done?

s654
00:53:16.720 --> 00:53:19.520
What's like the craziest thing anyone's done?

s655
00:53:19.520 --> 00:53:21.760
Any any volunteers?

s656
00:53:21.760 --> 00:53:23.359
Managing my home.

s657
00:53:23.359 --> 00:53:24.079
Home lab.

s658
00:53:24.079 --> 00:53:24.319
Yes.

s659
00:53:24.319 --> 00:53:26.960
What's a home lab?

s660
00:53:33.119 --> 00:53:35.119
Nice.

s661
00:53:46.800 --> 00:53:47.520
Wow.

s662
00:53:47.520 --> 00:53:52.559
Any other like crazy computer use stories?

s663
00:53:53.040 --> 00:53:57.359
Got to get AGI pill and try out computer use.

s664
00:53:57.359 --> 00:54:05.200
Um yeah, one thing I'll say is like because computers are so powerful like you get like you mentioned before there is some like safety component.

s665
00:54:05.200 --> 00:54:10.800
I am now remembering this example where like again because the slack connector was not able to upload files.

s666
00:54:10.800 --> 00:54:13.200
If this model is really determined, right?

s667
00:54:13.200 --> 00:54:15.040
Uh it could be like the one wish willow.

s668
00:54:15.040 --> 00:54:16.000
it just says, "Okay, great.

s669
00:54:16.000 --> 00:54:22.720
Well, if I can't add a Slack uh file, let me like go on computer use and press file upload and do that, right?"

s670
00:54:22.720 --> 00:54:32.480
There will be some times where the model based on how you prompted becomes really determined and say, "Oh, like I I it seems like I can't email someone using the Gmail connector.

s671
00:54:32.480 --> 00:54:35.280
Let me open up Chrome and hit the send button."

s672
00:54:35.280 --> 00:54:38.240
So, those are the kind of things that you should be really wary about, right?

s673
00:54:38.240 --> 00:54:39.839
These are like real security issues.

s674
00:54:39.839 --> 00:54:51.200
And again, um, more than not, like having things in the agent MD file has been really, really helpful, especially if you do things like, uh, guardian mode or auto mode, excuse me.

s675
00:54:51.200 --> 00:54:55.359
Um, and it has also really changed the way I think about uh doing work.

s676
00:54:55.359 --> 00:55:04.000
I feel like now when I'm doing things like building an application, if it's a native application, most of my testing is just done by codeex using computer use.

s677
00:55:04.000 --> 00:55:08.319
If it's a website, again, it's just using the inapp browser.

s678
00:55:08.319 --> 00:55:18.480
Um, I think we talked a lot about this already, like handle service work, like it's kind of awesome just like being on a checkout page, app shot, you know, find me a coupon.

s679
00:55:18.480 --> 00:55:22.480
Like, it's made me more money than than I I would have uh expected earlier.

s680
00:55:22.480 --> 00:55:25.119
Uh, filling out forms, testing applications.

s681
00:55:25.119 --> 00:55:31.200
Um, I haven't really had a good use of this just yet, but it can also control the iPhone through screen screen mirroring.

s682
00:55:31.200 --> 00:55:35.440
So, uh, do with that what you will.

s683
00:55:35.680 --> 00:55:38.720
And this is kind of sort of the escalation of the talk, right?

s684
00:55:38.720 --> 00:55:42.000
Then the question is like what can the computer not do and like why can't it do it?

s685
00:55:42.000 --> 00:55:45.680
And one of the things that like you can't do is control codecs.

s686
00:55:45.680 --> 00:55:51.920
But you don't really need to because these codeex threads can already talk to each other.

s687
00:55:51.920 --> 00:55:57.200
Uh you it can already control itself in very powerful ways, right?

s688
00:55:57.200 --> 00:56:01.760
If you think of the example, this is not the slide I want.

s689
00:56:02.480 --> 00:56:02.880
Damn.

s690
00:56:02.880 --> 00:56:03.200
Okay.

s691
00:56:03.200 --> 00:56:06.559
I think I think I messed up some slides.

s692
00:56:06.559 --> 00:56:16.319
Earlier in the talk, I talked about this idea that if there was some kind of support issue, I could take an appshot and it'll call this like DX triage skill and I will it will rename the skill.

s693
00:56:16.319 --> 00:56:23.359
It'll do the loop and it communicates like Slack and Twitter and it's very nice, but I still need to be the person that triggers these things, right?

s694
00:56:23.359 --> 00:56:29.119
That's the same thing as me seeing an issue and making a polar request in the future.

s695
00:56:29.119 --> 00:56:31.920
Well, I I mean the future for you it's happening already now here.

s696
00:56:31.920 --> 00:56:45.200
But now what I just have is I just have a single like monitor thread and anytime it identifies any of these issues, it will go off and create a new thread and the thread's job is to do all this triage.

s697
00:56:45.200 --> 00:56:50.079
And what might happen is maybe this triage is waiting on someone on Slack to acknowledge this issue.

s698
00:56:50.079 --> 00:56:53.200
Maybe a pull request has been created but it has not merged.

s699
00:56:53.200 --> 00:56:57.520
If someone else complains again in the future, the monitor thread just goes, "Oh, yeah.

s700
00:56:57.520 --> 00:56:59.520
I think this is the same issue."

s701
00:56:59.520 --> 00:57:06.000
Not only is the same issue, let me send a message to that, you know, downstream thread so that it's aware that this issue is recurring.

s702
00:57:06.000 --> 00:57:13.760
Maybe that thread will send a Slack message, but in the main thread, I'll still see a message that says, "Hey, it's been like the third day this issue has been live

s703
00:57:13.760 --> 00:57:16.400
uh based on Twitter feedback.

s704
00:57:16.400 --> 00:57:18.319
Should we do something?"

s705
00:57:18.319 --> 00:57:25.280
And like those are the things I'm I'm it's very hard for me to keep track of these things because I'm just like on Twitter all the time.

s706
00:57:25.280 --> 00:57:32.559
But by the agent being able to just manage and consume all this information, it makes these things much more tractable.

s707
00:57:32.559 --> 00:57:37.440
Um I definitely messed up the slides over here, so I'm going to skip a couple slides.

s708
00:57:39.119 --> 00:57:42.160
Yeah, this is this is the example.

s709
00:57:42.160 --> 00:57:47.599
Um and and I really want you I really really want you to play around with this idea.

s710
00:57:47.599 --> 00:57:51.359
I don't think it's been fully baked yet, right?

s711
00:57:51.359 --> 00:57:54.960
Most of my work is about just having monitors create subthreads.

s712
00:57:54.960 --> 00:57:57.760
These threads are then managed and pinned onto the sidebar.

s713
00:57:57.760 --> 00:57:59.359
Like that's also one of the best things, right?

s714
00:57:59.359 --> 00:58:06.640
Like with a sub agent, the thread just has these like shapeless entities floating in the background.

s715
00:58:06.640 --> 00:58:12.000
Uh like you know the JSON thread or like the Galileo thread or whatever.

s716
00:58:12.000 --> 00:58:17.680
The difference with sub aents versus these threads is because they show up in the sidebar, you can kind of just notice that something has changed.

s717
00:58:17.680 --> 00:58:19.760
You know, there's a new issue that's come up, right?

s718
00:58:19.760 --> 00:58:28.319
And a lot of it too is like just using the sidebar as effectively like the hub of understanding like what are the ongoing like work streams.

s719
00:58:28.319 --> 00:58:30.720
And this has been like super powerful for me.

s720
00:58:30.720 --> 00:58:39.280
But it all just starts from pinning a thread, taking actions, having this monor repo to sort of manage all of your context and then having different ways of waking systems up.

s721
00:58:39.280 --> 00:58:44.559
And earlier these systems wake up because you messaged it or you set up a heartbeat.

s722
00:58:44.559 --> 00:58:49.040
And now these things can be woken up by another thread running somewhere else.

s723
00:58:49.040 --> 00:58:58.720
And so more often than not like most of my automations just happen on the monitor level of threads and they trigger and create new threads and then manage themselves.

s724
00:58:59.839 --> 00:59:00.960
Yeah.

s725
00:59:00.960 --> 00:59:02.400
So I think we talked about a bunch of things, right?

s726
00:59:02.400 --> 00:59:11.040
tal about computer use structured plugins and uh yeah, I think that's basically it.

s727
00:59:11.040 --> 00:59:12.480
Try out some computer use stuff.

s728
00:59:12.480 --> 00:59:16.000
I I know I can't really I'm like really worried about the Wi-Fi here.

s729
00:59:16.000 --> 00:59:25.040
I'm going to try something too bad, but um yeah, try out app shots, try out computer use, and really play around with what uh these models are capable of.

s730
00:59:25.040 --> 00:59:25.920
There's a question over there.

s731
00:59:25.920 --> 00:59:28.640
I'll do that one next.

s732
00:59:35.680 --> 00:59:37.520
I don't think I can show you on this computer.

s733
00:59:37.520 --> 00:59:40.799
They're going to like take me away.

s734
00:59:40.799 --> 00:59:43.200
Um I mean I I can talk about a little bit.

s735
00:59:43.200 --> 00:59:49.200
So So basically my monor repo is set up so that it looks very much like the one over there.

s736
00:59:49.200 --> 00:59:55.040
I have a projects directory and in that projects directory is a named directory for every workstream I'm working on.

s737
00:59:55.040 --> 01:00:07.839
So maybe it is the you know voice launch video or it is the um like the the agents SDK right or it is uh the codeex open source grant program.

s738
01:00:07.839 --> 01:00:10.240
So those are sort of some of the projects.

s739
01:00:10.240 --> 01:00:16.799
Then I have a people directory which is just like every single person that's ever DM me, right?

s740
01:00:16.799 --> 01:00:18.079
I know what they're working on.

s741
01:00:18.079 --> 01:00:19.839
I know what kind of problems they're thinking about.

s742
01:00:19.839 --> 01:00:24.240
I know what other like uh like Slack channels they're part of.

s743
01:00:24.240 --> 01:00:28.240
And then I have a bunch of different like loose notes, agent summaries.

s744
01:00:28.240 --> 01:00:29.839
I have like daily summaries of what I've done.

s745
01:00:29.839 --> 01:00:31.760
This is mostly just to test the limits of AI.

s746
01:00:31.760 --> 01:00:34.240
I don't think it's very useful for that kind of stuff.

s747
01:00:34.240 --> 01:00:39.359
Mostly it's just the projects and the people, right?

s748
01:00:39.359 --> 01:00:42.079
Um, and then I have a to-do list that an agent just maintains.

s749
01:00:42.079 --> 01:00:44.640
So I have a single thread just like checks that to-do list.

s750
01:00:44.640 --> 01:00:46.079
Oh, this says it was undone.

s751
01:00:46.079 --> 01:00:50.400
Let me have a sub agent verify that like no one has done this task.

s752
01:00:50.400 --> 01:00:52.799
Those things are pretty token token expensive.

s753
01:00:52.799 --> 01:00:59.440
I don't really know if it would be worth people do setting this up for themselves unless they just like don't use that many credits.

s754
01:00:59.440 --> 01:01:04.000
Um, but I think the biggest ones is just like the Shiva staff thread.

s755
01:01:04.000 --> 01:01:05.839
9:00 a.m. tell me what's happening today.

s756
01:01:05.839 --> 01:01:07.200
Tell me what's happening this week.

s757
01:01:07.200 --> 01:01:12.960
And I think if you just do that, you're going to get a lot of uh a lot of juice out of that.

s758
01:01:19.680 --> 01:01:24.480
It's like honestly I just I've never experienced it.

s759
01:01:24.480 --> 01:01:30.240
I think like I think I think the compaction is just like really really good.

s760
01:01:30.240 --> 01:01:43.359
Um I know this not a very satisfactory answer, but like if I could improve parts of the model, I would rather improve like its writing tone rather than like its ability to search the context.

s761
01:01:43.359 --> 01:01:52.400
Um, generally it's been it's been a pretty good I think it might have to do with like the way the codeex memories have been set up, but I have not dug in too much into those details.

s762
01:01:52.400 --> 01:01:55.520
I think you had a question over here.

s763
01:01:56.720 --> 01:01:58.720
Yeah.

s764
01:02:16.160 --> 01:02:18.160
Yeah.

s765
01:02:22.319 --> 01:02:22.559
Yeah.

s766
01:02:22.559 --> 01:02:29.680
So I think the question was just like how do you deal with memories like bleeding across different projects?

s767
01:02:29.680 --> 01:02:36.960
I don't think I have a good answer to that primarily because it's unclear to me what the downstream side effect would be.

s768
01:02:36.960 --> 01:02:42.160
Maybe like one project uses like npm, another project uses like yarn or something.

s769
01:02:42.160 --> 01:02:47.520
But I mean generally I just clean those up in the agent MD files for those specific projects, right?

s770
01:02:47.520 --> 01:02:53.200
So another thing to mention is like every project directory has its own readme and its own agent MD files.

s771
01:02:53.200 --> 01:02:59.599
And so yeah, like I think sometimes like one project I was working on was like npm and one was like PMP.

s772
01:02:59.599 --> 01:03:01.040
I just clean that up in the agents MD.

s773
01:03:01.040 --> 01:03:05.839
And I was I would be curious like how much of that can be cleaned up just by using those simple tools.

s774
01:03:05.839 --> 01:03:06.720
But talk to me afterwards.

s775
01:03:06.720 --> 01:03:12.319
I'm really curious like what's so bad about the the bleeding.

s776
01:03:12.640 --> 01:03:18.559
Yeah, maybe that that would be a good example of like having project level scoping versus a single thread.

s777
01:03:18.559 --> 01:03:25.680
But um yeah, I might have to look into more details about how the memory part is actually running.

s778
01:03:25.680 --> 01:03:28.880
Any other questions over here?

s779
01:03:36.000 --> 01:03:42.319
No. So I think um honestly at this point it just kind of knows.

s780
01:03:42.319 --> 01:03:48.160
It's like such a it's such a bad answer but it's almost like an AGI like I feel like to me it feels like a very AGI pil.

s781
01:03:48.160 --> 01:03:57.920
But I think generally in the beginning when I was working with it I would have a skill called like check notes and it's like hey if you feel like you need to check your notes like check the notes.

s782
01:03:57.920 --> 01:03:58.240
All right.

s783
01:03:58.240 --> 01:04:06.000
And so if I if I had a hunch or some intuition that the model might not be able to do this, I would just mention like, hey, check the notes.

s784
01:04:06.000 --> 01:04:19.359
Um, but even like if you look at my like uh open profile, I think like my like check notes skill has been used like a 150,000 times, but I've like never mentioned it

s785
01:04:19.359 --> 01:04:20.480
in the past like two three months.

s786
01:04:20.480 --> 01:04:24.400
It's because again, I think this the memory system has been uh doing a lot of the heavy lifting.

s787
01:04:24.400 --> 01:04:30.559
But again it's it's like onboarding an employee in the in the first you know two three months of onboarding an employee.

s788
01:04:30.559 --> 01:04:32.079
You have to give a lot of instruction.

s789
01:04:32.079 --> 01:04:42.160
You have to give a lot of you have to give them a lot of context and you have to let them fail and when they fail you have to give them an opportunity like write down what they've learned and like clean up itself.

s790
01:04:42.160 --> 01:04:47.839
Um I would be very surprised if you got good results in the first like day of setting this up.

s791
01:04:47.839 --> 01:04:53.520
But I mean just yet maybe not to your surprise but now it's like I don't it kind of just works right.

s792
01:04:53.520 --> 01:04:55.039
And that that's a great feeling to have, right?

s793
01:04:55.039 --> 01:04:59.520
Because it it it lets me go back in the flow of just like doing my job.

s794
01:04:59.520 --> 01:05:00.240
You a question?

s795
01:05:00.240 --> 01:05:00.799
Yeah.

s796
01:05:00.799 --> 01:05:08.400
Thanks so much for asking CSS and

s797
01:05:09.200 --> 01:05:12.799
given that it's rapidly changing

s798
01:05:15.599 --> 01:05:18.559
develop like just so not productivity but just like coding in general.

s799
01:05:18.559 --> 01:05:20.559
Yeah.

s800
01:05:22.640 --> 01:05:24.640
Yeah,

s801
01:05:28.799 --> 01:05:29.680
I'm so old.

s802
01:05:29.680 --> 01:05:31.039
That's so long ago.

s803
01:05:31.039 --> 01:05:43.280
Um, like I have a line that's like if you want to have good taste, you kind of have to eat, right?

s804
01:05:43.280 --> 01:05:51.359
Like I think your job is to like consume a little bit more like try out different applications like you know like do you know what a good onboarding flow looks like?

s805
01:05:51.359 --> 01:05:52.400
Do you know what that feels like?

s806
01:05:52.400 --> 01:05:55.200
Have you built an app that makes you frustrated?

s807
01:05:55.200 --> 01:06:02.720
And just like your ability just like consume more things and develop your vocabulary on like how to complain about things that are bad.

s808
01:06:02.720 --> 01:06:05.039
How do you like complain about like the slop?

s809
01:06:05.039 --> 01:06:08.000
Those are the things those are the skills I think will be very valuable.

s810
01:06:08.000 --> 01:06:10.400
And specifically around vocabulary, right?

s811
01:06:10.400 --> 01:06:13.839
like you can't really describe things that you don't really understand.

s812
01:06:13.839 --> 01:06:18.960
Um, and this happens in like both like things like cooking, right?

s813
01:06:18.960 --> 01:06:24.559
Like if you just don't know what the ingredients are, you can't describe that something is too salty or it could be it's like it lacks some acid.

s814
01:06:24.559 --> 01:06:31.839
Like you just need to like consume a little bit more and then think critically about why you like something and why you don't like something.

s815
01:06:31.839 --> 01:06:41.359
Um because I think I think taste is the is a big issue but I think a lot of it is because we are not consuming the right like stuff

s816
01:06:41.359 --> 01:06:46.720
right like try out all the different apps if you're thinking about apps for example.

s817
01:06:46.720 --> 01:06:48.720
Yeah.

s818
01:06:49.839 --> 01:06:52.400
Any other questions?

s819
01:06:55.200 --> 01:06:57.161
Yep.

s820
01:06:57.161 --> 01:06:59.161
[snorts]

s821
01:06:59.359 --> 01:07:01.359
Yeah.

s822
01:07:13.520 --> 01:07:14.720
Uh which part?

s823
01:07:14.720 --> 01:07:27.760
So, so I understand aast

s824
01:07:40.559 --> 01:07:40.880
Yeah.

s825
01:07:40.880 --> 01:07:45.119
I mean like unironically that slide just says like threads can talk to each other just ask.

s826
01:07:45.119 --> 01:07:51.760
Basically there is a list thread tool and a send message to thread tool that Codex has available.

s827
01:07:51.760 --> 01:08:02.000
And so typing that is kind of awkward but really I just say like sometime last week I was working on slides.

s828
01:08:02.000 --> 01:08:06.160
Can you go find that thread, rename it and pin it for next time?

s829
01:08:06.160 --> 01:08:06.720
Right?

s830
01:08:06.720 --> 01:08:10.160
Like I would never type that but again voice input makes it really easy.

s831
01:08:10.160 --> 01:08:14.720
Um, sometimes I'll say for for example, this talk I I I think I messed up some slides.

s832
01:08:14.720 --> 01:08:17.520
Basically, I had a main slide writing system.

s833
01:08:17.520 --> 01:08:21.679
Uh, and I said, "Okay, like this slide could be split up in three acts.

s834
01:08:21.679 --> 01:08:23.440
Make up a thread for each act.

s835
01:08:23.440 --> 01:08:28.480
Pin it, rename it act one, two, and three, and uh, review each section.

s836
01:08:28.480 --> 01:08:30.880
And then once it's done, review the whole slide."

s837
01:08:30.880 --> 01:08:35.199
Um, and yeah, I generally like to just ask it.

s838
01:08:35.199 --> 01:08:46.400
I mean, I think I'm going to try to add more like commands to be a little bit more explicit around thread control, but I think that will just come as the models get better and and as the model is like more aware of what codecs can do.

s839
01:08:46.400 --> 01:09:01.040
Um, but yeah, it really is just like like I think one thing you should try to do is just have a thread and just say read all the other threads that are pinned and like rename them and like use an emoji to color code its like readiness.

s840
01:09:01.040 --> 01:09:06.640
And just seeing it do that will be like a first step um to to just like understand how this thread control works.

s841
01:09:06.640 --> 01:09:11.920
This feature is like very new, but it already has been pretty wild to just sort of have a single thread.

s842
01:09:11.920 --> 01:09:15.199
You're just talking to it for like the entire afternoon.

s843
01:09:15.199 --> 01:09:17.199
Yeah.

s844
01:09:17.279 --> 01:09:17.920
Sweet.

s845
01:09:17.920 --> 01:09:19.040
If there's no more questions.

s846
01:09:19.040 --> 01:09:21.520
Yeah, one more.

s847
01:09:28.719 --> 01:09:30.080
Don't say that name to me.

s848
01:09:30.080 --> 01:09:34.640
No. No. Uh so the question was like do other coding systems um have these kind of tools?

s849
01:09:34.640 --> 01:09:35.120
Not yet.

s850
01:09:35.120 --> 01:09:40.080
I think I'm sure you know I'm sure they will soon.

s851
01:09:40.080 --> 01:09:51.520
Uh but as far as I know, this goes back to the eating thing like I just have not tried like the latest versions of other tools like I don't know if like conductor has these skills but definitely

s852
01:09:51.520 --> 01:09:58.560
um I'm sure again like very competitive space the these features will probably propagate very quickly.

s853
01:09:59.600 --> 01:10:01.120
threads run on old models.

s854
01:10:01.120 --> 01:10:05.280
Will you have the new threads go back and pull that in as context?

s855
01:10:05.280 --> 01:10:05.920
It depends.

s856
01:10:05.920 --> 01:10:11.199
Sometimes just say find the old thread and like update the model and it'll just update the model.

s857
01:10:11.199 --> 01:10:22.480
Like for for example, I I I like so when when uh 45 54 came out and then we moved to 55, I realized all my old automations were just on

s858
01:10:22.480 --> 01:10:33.440
54 and it really bugged me and I was like, "Hey guys, like can we add a feature that like has like GPT latest so we can avoid this issue and someone was just like

s859
01:10:33.440 --> 01:10:42.480
tell a thread to update the other threads and I was like yeah like so much of it is just ask you just have to like develop the language anguage to figure out what you want to do.

s860
01:10:42.480 --> 01:10:45.520
But I think that's again like the most important most important thing.

s861
01:10:45.520 --> 01:10:45.679
Yeah.

s862
01:10:45.679 --> 01:10:49.600
So just ask it and then it'll automatically do it rather than you having to go through it.

s863
01:10:49.600 --> 01:10:49.840
Yeah.

s864
01:10:49.840 --> 01:10:54.640
Like I think I have an automation that just like cleans up old threads and like by like model ids.

s865
01:10:54.640 --> 01:10:59.040
Um but uh yeah.

s866
01:10:59.040 --> 01:11:01.199
What's up?

s867
01:11:01.840 --> 01:11:04.239
Uh not yet.

s868
01:11:04.239 --> 01:11:08.960
I'm not happy with the slides enough that I I'll publish them, but I have a blog post.

s869
01:11:08.960 --> 01:11:19.600
just search if you just Google codeex maxing it's all there uh you know three x's I think uh but I I'll I'll share some more stuff on on Twitter go on

s870
01:11:19.600 --> 01:11:21.840
yeah so you said that you work

s871
01:11:21.840 --> 01:11:22.439
yeah

s872
01:11:22.439 --> 01:11:24.159
[snorts]

s873
01:11:24.159 --> 01:11:30.299
so do you have any loops you

s874
01:11:30.299 --> 01:11:30.400
[snorts]

s875
01:11:30.400 --> 01:11:47.760
get a lot into the limit advice share how we can limit.

s876
01:11:47.760 --> 01:11:54.480
Yeah, I think the biggest misconception here is that like X high will give me the best results.

s877
01:11:54.480 --> 01:11:57.440
And so there's like there's a lot of like X high maximalists here.

s878
01:11:57.440 --> 01:11:59.120
I want everything on X high, right?

s879
01:11:59.120 --> 01:12:05.199
Like uh like I was demoing the like getting a coupon thing and my friend like does an app shot and like hits enter.

s880
01:12:05.199 --> 01:12:07.520
I'm like why did you turn it on X high?

s881
01:12:07.520 --> 01:12:07.760
right?

s882
01:12:07.760 --> 01:12:12.800
It ran for like two minutes like searching like every website available for like coupons.

s883
01:12:12.800 --> 01:12:24.320
Um, obviously I I can't give that much advice because it's something like on my personal computer I don't really run into limits but really get comfortable with like low and medium thinking.

s884
01:12:24.320 --> 01:12:26.800
Like these models are still very very smart, right?

s885
01:12:26.800 --> 01:12:33.040
Like low thinking on five like five five is like still so much better than prior models.

s886
01:12:33.040 --> 01:12:37.679
And for a lot of this work that's not just like you know make me a video game from scratch.

s887
01:12:37.679 --> 01:12:39.040
You just don't need that kind of work.

s888
01:12:39.040 --> 01:12:43.040
Like my my chief of staff I think is like default medium.

s889
01:12:43.040 --> 01:12:44.000
That's very helpful advice.

s890
01:12:44.000 --> 01:12:44.400
I agree.

s891
01:12:44.400 --> 01:12:52.960
Just as a follow I guess in a few words how do I tell the thread to shut up same thing and

s892
01:12:52.960 --> 01:13:04.000
oh uh I mean the answer is really bad but I just like I just say like if there's no updates just reply with like one word no updates.

s893
01:13:04.000 --> 01:13:09.920
Uh that's one thing and the second thing too is um I would also play around with like how often these heartbeats are happening.

s894
01:13:09.920 --> 01:13:12.239
You know are you running this thing every 30 minutes?

s895
01:13:12.239 --> 01:13:14.159
are you running this every 9:00 am?

s896
01:13:14.159 --> 01:13:14.800
That's one thing.

s897
01:13:14.800 --> 01:13:18.480
And the second thing, too, it's like, do you have some kind of stopping criteria?

s898
01:13:18.480 --> 01:13:18.719
Right?

s899
01:13:18.719 --> 01:13:23.760
So, for example, like I was I had some argument with like Amazon and I'm just like great.

s900
01:13:23.760 --> 01:13:26.880
Like they put me in a 75m minute wait list.

s901
01:13:26.880 --> 01:13:31.679
Like check every five minutes if the queue is like better.

s902
01:13:31.679 --> 01:13:37.199
And once you get to five minute wait time, check every one minute and keep replying until you get my money back.

s903
01:13:37.199 --> 01:13:42.239
And I took a shower and when I came back, I had like $400 in my credit card.

s904
01:13:46.960 --> 01:13:51.199
I've not tried too much there, but it's all possible, right?

s905
01:13:51.199 --> 01:13:53.760
Because to create a heartbeat is just edit a text file.

s906
01:13:53.760 --> 01:13:59.520
And so you should definitely be able to create your own heartbeat and then change how frequent or infrequent.

s907
01:13:59.520 --> 01:14:01.280
Um, I might try to do that actually.

s908
01:14:01.280 --> 01:14:13.120
I might just say like, "Hey, like during the weekdays like change your heartbeat to be more active and during weekends or in the afternoons change them to um be less active."

s909
01:14:13.120 --> 01:14:13.840
Yeah.

s910
01:14:13.840 --> 01:14:20.560
Like I've tried versions of the chief of staff thread where I just set a goal that says like never stop and you're only allowed to like set sleep.

s911
01:14:20.560 --> 01:14:22.000
And that has also worked pretty well.

s912
01:14:22.000 --> 01:14:26.480
It'll be like, "Hey, it's like 900 p.m. Jason like I haven't seen Jason post a Slack message in like two hours.

s913
01:14:26.480 --> 01:14:28.719
I'm going to sleep for like five hours."

s914
01:14:28.719 --> 01:14:32.080
Uh and that also kind of works.

s915
01:14:32.080 --> 01:14:32.800
Yeah.

s916
01:14:32.800 --> 01:14:39.199
But um I I think the biggest one honestly is just like people should not be afraid of low reasoning.

s917
01:14:39.199 --> 01:14:41.679
Like X high is not like X high results.

s918
01:14:41.679 --> 01:14:45.520
It's just like think more