WEBVTT 1 00:00:00.000 --> 00:00:05.000 Okay, welcome back to our team training. 2 00:00:05.000 --> 00:00:09.720 This is where we spend each week just talking about all of our workflows for AI and how 3 00:00:09.720 --> 00:00:15.280 we're working using ShapeUp, how, as an agency, we're quickly adapting to all this new tech 4 00:00:15.280 --> 00:00:16.540 that's coming out. 5 00:00:16.540 --> 00:00:21.720 So rather than trying to make videos and playbooks and stuff for our team, we're just kind of 6 00:00:21.720 --> 00:00:26.300 live training every single week on these live calls, and we thought, why not just stream 7 00:00:26.300 --> 00:00:28.840 them to anyone else who's wanting to learn? 8 00:00:28.840 --> 00:00:34.900 And if you guys are interested, we actually have put out a course for you guys and a little 9 00:00:34.900 --> 00:00:35.900 community. 10 00:00:35.900 --> 00:00:38.140 It's just a free thing you can check out. 11 00:00:38.140 --> 00:00:45.600 And if you go over to the, like in the description here, you can see there is a link, you get 12 00:00:45.600 --> 00:00:50.700 over to our courses, and we have a ton of content in here just going through our process, 13 00:00:50.700 --> 00:00:53.880 how we do framing, how we work with clients. 14 00:00:53.880 --> 00:00:54.880 So all this is just free. 15 00:00:54.880 --> 00:00:58.520 This is what we use internally as a team, a lot of videos from me, we have some videos 16 00:00:59.200 --> 00:01:01.000 from other resources here. 17 00:01:01.000 --> 00:01:05.800 And then in addition to that, we even have all of our sessions that we spent with Ryan. 18 00:01:05.800 --> 00:01:09.200 If you really want to dive deep, we're happy to share this with you guys. 19 00:01:09.200 --> 00:01:15.600 We spent some two and three hour calls with Ryan as a team, and you can welcome that this 20 00:01:15.600 --> 00:01:17.200 is a three hour call. 21 00:01:17.200 --> 00:01:21.640 If you want to dive deep and learn from the man himself, Ryan Singer, it's in there as 22 00:01:21.640 --> 00:01:22.640 well. 23 00:01:22.640 --> 00:01:27.000 So this is just available, jump in there on the link, and that way you're just kind of 24 00:01:27.480 --> 00:01:29.200 included in all the updates we're making. 25 00:01:29.200 --> 00:01:34.280 So we're basically just taking our team, internal team resources, and just sharing them publicly 26 00:01:34.280 --> 00:01:39.360 and kind of just letting you guys see behind the curtain here a little bit. 27 00:01:39.360 --> 00:01:42.040 So I've been messing around this week. 28 00:01:42.040 --> 00:01:48.000 My new tool of the week is what it's like, I'm trying stuff all the time. 29 00:01:48.000 --> 00:01:49.740 Last week, we talked about MCPs. 30 00:01:49.740 --> 00:01:54.480 We talked about how to, how we set up a Novo dashboard MCP. 31 00:01:54.480 --> 00:02:01.720 We're slowly building out kind of this diagram here, I'll show you, where we have sort of 32 00:02:01.720 --> 00:02:05.040 a central hub here that's using Superbase. 33 00:02:05.040 --> 00:02:10.000 And then we have some UI layers here where there's an owner dashboard, where clients 34 00:02:10.000 --> 00:02:16.160 can view data, and then there's a team dashboard our team can use to see tasks and billing 35 00:02:16.160 --> 00:02:18.240 and all kinds of things. 36 00:02:18.240 --> 00:02:23.680 We've built it all into the Superbase central hub. 37 00:02:23.680 --> 00:02:27.640 And then with that, we can pull motion tasks in and out. 38 00:02:27.640 --> 00:02:32.240 We can pull, we're going to be adding some meeting notes so we can have transcripts of 39 00:02:32.240 --> 00:02:33.240 meetings coming in. 40 00:02:33.240 --> 00:02:35.200 So there's just this one central point. 41 00:02:35.200 --> 00:02:41.520 And then anyone can use either the MCP or CLI to basically pull content in and out of 42 00:02:41.520 --> 00:02:42.880 this central repository. 43 00:02:42.880 --> 00:02:45.840 So this is what we've all come up with. 44 00:02:45.840 --> 00:02:50.160 We spent many of these calls, you can go back and watch some of the earlier live streams 45 00:02:50.160 --> 00:02:52.880 where we sat as a team and whiteboarded this. 46 00:02:52.880 --> 00:02:58.120 There's a massive diagram of stuff we've been working our way through all together. 47 00:02:58.120 --> 00:03:03.280 Started out as some ideas here on some sticky notes. 48 00:03:03.280 --> 00:03:08.840 And there's things like task grid and it's funny to see kind of these stickies now. 49 00:03:08.840 --> 00:03:12.000 And we took all those, put those ideas in there and we've kind of turned them into this. 50 00:03:12.000 --> 00:03:21.080 So it's become probably the biggest tool that we've been leveraging for the company by far. 51 00:03:21.080 --> 00:03:25.040 So a lot of time has gone into it, but I feel like we've got a massive ROI for it. 52 00:03:25.040 --> 00:03:31.280 So last time, if you're going to check out the MCP, I was just showing a demo here where 53 00:03:31.280 --> 00:03:34.960 we just finished up a new feature for Tribe. 54 00:03:34.960 --> 00:03:38.760 And so I asked it here to go write a short blog post. 55 00:03:38.760 --> 00:03:43.000 And so it looked at all the code as context, but it also looked at the projects in the 56 00:03:43.000 --> 00:03:44.400 dashboard as context. 57 00:03:44.400 --> 00:03:50.140 Basically just wrote a super short post here and I can, I'll grab it real quick here and 58 00:03:50.140 --> 00:03:53.500 just show it to you in a prettier version. 59 00:03:53.500 --> 00:03:54.500 Let's see here. 60 00:03:54.500 --> 00:03:55.500 Yeah. 61 00:03:55.500 --> 00:03:59.620 So you just wrote this little post. 62 00:03:59.620 --> 00:04:04.140 Now we'd probably go there and edit it, but this took two minutes and the context here 63 00:04:04.140 --> 00:04:05.140 is extremely well. 64 00:04:05.140 --> 00:04:10.460 It's as if I had asked Lucian who built this feature to go and like write this beautiful 65 00:04:10.460 --> 00:04:14.180 blog post because he was the one who was actually part of it. 66 00:04:14.180 --> 00:04:19.620 Now we can kind of just reference all the code here and reference all the framing docs. 67 00:04:19.620 --> 00:04:23.060 We can reference any of the task grid, any of those notes that went in there. 68 00:04:23.060 --> 00:04:27.940 So there's not a lot that's left that isn't being surfaced here as context. 69 00:04:27.940 --> 00:04:32.260 The only thing maybe is maybe the meetings we had where we talked about it. 70 00:04:32.260 --> 00:04:36.420 But any notion, I think it's a notion, any notion comments were included. 71 00:04:36.420 --> 00:04:40.100 All that comes in as context and then we can create something like a quick blog post. 72 00:04:40.100 --> 00:04:45.180 So previously the thing is we wouldn't have not have even sent a blog post is reality. 73 00:04:45.180 --> 00:04:46.860 Like we just don't have time. 74 00:04:46.860 --> 00:04:47.860 We're a very small team. 75 00:04:48.100 --> 00:04:52.900 It's like seven of us and sure we could have dedicated some time, but like Lucian's already 76 00:04:52.900 --> 00:04:56.740 on to the next project doing a whole bunch of other stuff. 77 00:04:56.740 --> 00:04:59.220 So this is great that we can have this kind of come in behind. 78 00:05:00.000 --> 00:05:04.300 That leads me right into the tool I wanted to show you today, 79 00:05:04.300 --> 00:05:06.580 which is Paperclip. 80 00:05:06.580 --> 00:05:08.340 We've talked about OpenClaw, 81 00:05:08.340 --> 00:05:12.980 we've talked about so many different tools that are out there now. 82 00:05:12.980 --> 00:05:14.860 We've played with a bunch of them. 83 00:05:14.860 --> 00:05:18.420 I'm becoming a huge fan of Paperclip right now. 84 00:05:18.420 --> 00:05:19.980 I'll show you a quick little tour here. 85 00:05:19.980 --> 00:05:22.780 It's totally open source on GitHub. 86 00:05:22.780 --> 00:05:29.220 The idea here is that you can set up a company that runs here. 87 00:05:29.220 --> 00:05:32.200 You essentially create a CEO role, 88 00:05:32.200 --> 00:05:33.260 you give it a vision, 89 00:05:33.260 --> 00:05:35.540 and then tell it what things you want to do. 90 00:05:35.540 --> 00:05:41.620 I want to start promoting our business so that people know that we exist. 91 00:05:41.620 --> 00:05:44.980 Here's some examples of projects that we're doing. 92 00:05:44.980 --> 00:05:49.580 Things are going out on X and Facebook and whatever. 93 00:05:49.580 --> 00:05:53.020 These are things we just don't have time for normally. 94 00:05:53.020 --> 00:05:55.860 It's hard to keep it up even if as a founder, 95 00:05:55.860 --> 00:05:58.660 you can set reminders and build your calendar and schedule. 96 00:05:58.660 --> 00:06:02.340 To me, this is just not something like, it's not interesting. 97 00:06:02.340 --> 00:06:05.740 I'm not super passionate about sitting and making content. 98 00:06:05.740 --> 00:06:07.980 I'd rather just talk and show you guys raw, 99 00:06:07.980 --> 00:06:09.260 like live what's going on, 100 00:06:09.260 --> 00:06:11.740 and then you can figure out stuff from there. 101 00:06:11.740 --> 00:06:15.980 But the main thing I love about this is that you actually bring your own agent. 102 00:06:15.980 --> 00:06:20.700 I'm actually using my Cloud Mac subscription for this, 103 00:06:20.700 --> 00:06:25.660 instead of having to give it an API key and then just burn through tokens. 104 00:06:25.660 --> 00:06:28.220 Then it's got all the same features. 105 00:06:28.380 --> 00:06:29.740 You can have heartbeats, 106 00:06:29.740 --> 00:06:32.020 you can figure out cost control if you want. 107 00:06:32.020 --> 00:06:34.100 You act as the boards. 108 00:06:34.100 --> 00:06:36.140 This is an interesting, I've not seen this take on it, 109 00:06:36.140 --> 00:06:38.580 but the positioning is really creative. 110 00:06:38.580 --> 00:06:42.540 I just want to give a shout out to the creators of this because they 111 00:06:42.540 --> 00:06:45.500 really try to make it not technical, 112 00:06:45.500 --> 00:06:47.060 which I think makes it easy to understand. 113 00:06:47.060 --> 00:06:48.660 They essentially set you up as the board, 114 00:06:48.660 --> 00:06:50.460 and then you get to approve hires, 115 00:06:50.460 --> 00:06:51.620 and then you hire the CEO, 116 00:06:51.620 --> 00:06:54.940 and the CEO goes and runs your business for you. 117 00:06:55.940 --> 00:06:59.260 It's a fun little process here. 118 00:06:59.260 --> 00:07:04.500 Again, it works with OpenClaw, Codex, whatever you want to bring. 119 00:07:04.500 --> 00:07:08.340 Then it has a nice little UI that I'll show you how I've got it dialed in. 120 00:07:08.340 --> 00:07:10.300 I think that's pretty much all I wanted to show you. 121 00:07:10.300 --> 00:07:13.700 It's a beautiful page as well for just an open source project. 122 00:07:13.700 --> 00:07:18.660 This is a beautifully designed page. 123 00:07:18.660 --> 00:07:22.100 You can check it out on GitHub. 124 00:07:22.260 --> 00:07:25.020 I think they have, what are the stars they've got now? 125 00:07:25.020 --> 00:07:29.100 Yeah, about 33,000. 126 00:07:29.780 --> 00:07:32.780 Here's how I set it up. 127 00:07:32.780 --> 00:07:38.980 First off, I set up the entire thing from my phone. 128 00:07:38.980 --> 00:07:41.980 I was sitting around on Sunday. 129 00:07:41.980 --> 00:07:44.100 It's beautiful weather here. 130 00:07:44.100 --> 00:07:46.580 One of our kids was not feeling great, 131 00:07:46.580 --> 00:07:48.340 so we ended up staying home, didn't go to church. 132 00:07:48.340 --> 00:07:51.500 We just hung out and the weather was like 78 degrees. 133 00:07:51.580 --> 00:07:52.580 We just sat outside. 134 00:07:52.580 --> 00:07:54.580 We had a lot of time just sitting around. 135 00:07:54.580 --> 00:07:56.860 I looked at Paperclip and I was like, 136 00:07:56.860 --> 00:08:01.260 you know what, I'm just going to go see how far I can get this on my phone. 137 00:08:01.260 --> 00:08:04.380 I basically set the entire thing up from my phone. 138 00:08:04.380 --> 00:08:08.100 I have Terminus set up on my iPhone. 139 00:08:08.100 --> 00:08:10.540 I have a VPS in DigitalOcean. 140 00:08:10.540 --> 00:08:14.340 Then I was able to just SSH from my phone. 141 00:08:14.340 --> 00:08:18.180 I went in there, I have Cloud installed on the root of that server. 142 00:08:18.180 --> 00:08:20.060 I can just say, hey, I want to set this project up. 143 00:08:20.060 --> 00:08:21.340 Here's the GitHub link. 144 00:08:21.340 --> 00:08:22.620 Let me know what you need. 145 00:08:22.620 --> 00:08:26.900 It just ran off there for 20, 30 minutes, prompting, 146 00:08:26.900 --> 00:08:31.380 and basically came back with a URL that I was able to use. 147 00:08:31.380 --> 00:08:35.220 This is the future, is basically building this thing. 148 00:08:35.220 --> 00:08:39.740 Actually, I used it all Sunday, had it working on tasks, had it working on stuff. 149 00:08:39.740 --> 00:08:41.659 Then on, I think, Monday, I picked up my computer 150 00:08:41.659 --> 00:08:45.620 and I actually looked at it for the first time on a desktop. 151 00:08:45.620 --> 00:08:47.900 It is really, really nice. 152 00:08:47.900 --> 00:08:50.300 It's very mobile-friendly, so once you set this up. 153 00:08:50.300 --> 00:08:53.020 You can see it's running on my server here, 154 00:08:53.020 --> 00:08:57.060 and only I can get to it through my VPN. 155 00:08:57.060 --> 00:09:03.620 And then, okay, so the way we set it up, I just got the CEO. 156 00:09:03.620 --> 00:09:07.540 Everybody's Claude right now, and I'll just click into these. 157 00:09:07.540 --> 00:09:09.780 You can kind of see what their instructions are. 158 00:09:09.780 --> 00:09:11.660 Like, hey, you're the CEO. 159 00:09:11.660 --> 00:09:14.100 It kind of wrote all this, so I'm not coming in here 160 00:09:14.100 --> 00:09:19.140 and building these documents for this particular agent. 161 00:09:19.140 --> 00:09:21.500 It kind of figured itself out here. 162 00:09:21.500 --> 00:09:22.940 I'm like, hey, you own the P&L. 163 00:09:22.940 --> 00:09:23.780 This is your goals. 164 00:09:23.780 --> 00:09:26.660 You can try to maximize profit, whatever. 165 00:09:26.660 --> 00:09:31.060 I threw in one or two custom notes, like, hey, Bruce is a pilot and likes checklists, 166 00:09:31.060 --> 00:09:37.220 so let's incorporate that kind of thought process into things. 167 00:09:37.220 --> 00:09:39.060 So each one here kind of got created. 168 00:09:39.060 --> 00:09:43.300 And the way that it gets created is I tell the CEO, like, hey, 169 00:09:43.300 --> 00:09:47.660 it's time we start getting serious about content. 170 00:09:47.700 --> 00:09:49.620 I want to be really consistent. 171 00:09:49.620 --> 00:09:52.580 By the way, we do these live streams every Thursday. 172 00:09:52.580 --> 00:09:54.020 I'm already saying a bunch of stuff here. 173 00:09:54.020 --> 00:09:57.740 Like, surely an agent can go and, like, pull my transcript, 174 00:09:57.740 --> 00:10:00.020 create a bunch of posts for me, create a blog post. 175 00:10:00.000 --> 00:10:02.160 Let's create an email, like, why not? 176 00:10:02.160 --> 00:10:04.600 So it says, great, I think I need to hire a content manager. 177 00:10:04.600 --> 00:10:06.200 Are you okay if I hire a content manager? 178 00:10:06.200 --> 00:10:07.000 And I said, yes. 179 00:10:08.440 --> 00:10:14.760 And so that, that agent got hired and the job description here, or the skills that 180 00:10:14.760 --> 00:10:18.840 had got added came from the CEO and they kind of collaborated together or they 181 00:10:18.840 --> 00:10:20.880 kind of wrote up what they thought needs to happen. 182 00:10:21.160 --> 00:10:23.840 So you can see there's like a YouTube transcriber skill. 183 00:10:24.360 --> 00:10:25.800 It needs to be able to send emails. 184 00:10:25.840 --> 00:10:29.360 I also have it connect to active campaign to schedule the newsletter. 185 00:10:30.920 --> 00:10:33.720 And that's sort of the process it went through. 186 00:10:33.720 --> 00:10:41.360 So generally when I'm using this, I will come in here to this dashboard and then 187 00:10:41.360 --> 00:10:42.440 it's always an inbox. 188 00:10:42.440 --> 00:10:44.120 So it's very similar to Notion. 189 00:10:45.040 --> 00:10:49.880 There's kind of like a read, unread process and I can kind of see what's going on. 190 00:10:49.880 --> 00:10:56.160 So one of the tasks I said to it right before we hopped on here was just, hey, 191 00:10:56.160 --> 00:10:59.440 I'm demoing this, give me a little update of what all we did. 192 00:10:59.880 --> 00:11:03.760 And so we set up the CEO, we've got the content marketer. 193 00:11:03.760 --> 00:11:08.040 I ended up creating this little platform engineer role who just owns integrations. 194 00:11:08.040 --> 00:11:12.760 And so his job is like every morning at 5am, it goes and checks the YouTube API, 195 00:11:12.760 --> 00:11:16.680 checks Mailgun, checks active campaign so that it's all ready for the day for the 196 00:11:16.680 --> 00:11:19.920 rest of the bots to go and figure itself out. 197 00:11:20.360 --> 00:11:22.520 And then I have a project manager. 198 00:11:22.560 --> 00:11:26.960 So this is funny because I was like, basically I need someone to monitor the 199 00:11:26.960 --> 00:11:27.520 humans. 200 00:11:28.040 --> 00:11:29.800 We can't just be over here monitoring agents. 201 00:11:30.160 --> 00:11:35.960 And so we have, I said, hey, we have this NW-MCP and you can basically pull all 202 00:11:35.960 --> 00:11:36.720 that data in. 203 00:11:36.720 --> 00:11:43.200 So at 9am and then at 4pm, it basically runs out and grabs all the projects. 204 00:11:43.200 --> 00:11:44.320 I'll show you what this looks like. 205 00:11:45.080 --> 00:11:48.800 Gets a status of what's going on, who's, what things are and what status, where 206 00:11:48.880 --> 00:11:50.480 task grids are, where tasks are at. 207 00:11:50.880 --> 00:11:52.360 Did I get mentioned in any comments? 208 00:11:52.360 --> 00:11:56.560 And like distills it down to a little email and like briefs me on like, here's 209 00:11:56.600 --> 00:11:59.960 everything that's going on with like the team right now and where projects are at. 210 00:12:00.280 --> 00:12:04.200 And it's funny because immediately it just does things that we, like it kind of 211 00:12:04.200 --> 00:12:07.360 gives you a view into like the raw data of what's going on in Notion. 212 00:12:08.200 --> 00:12:11.080 And we maybe don't see everything because we have these views built and we don't 213 00:12:11.080 --> 00:12:12.400 really see things. 214 00:12:12.400 --> 00:12:15.000 Like I'm looking at a client, so I may not see certain things. 215 00:12:15.400 --> 00:12:17.920 And I realized like, man, there's some things that were disorganized. 216 00:12:17.920 --> 00:12:23.040 Like I had projects sitting in Inbox or in DevReady that are actually not DevReady. 217 00:12:23.040 --> 00:12:24.680 So I was able to go and like clean those up. 218 00:12:24.720 --> 00:12:27.840 So it's getting, making, but I never didn't even know that was there. 219 00:12:27.840 --> 00:12:33.160 So this is kind of surfacing things that like only like a computer could do because 220 00:12:33.160 --> 00:12:38.000 it's just doing it, spending so much time getting it and not making any mistakes. 221 00:12:38.280 --> 00:12:39.840 They set up this content pipeline. 222 00:12:40.160 --> 00:12:42.760 So what it's doing now is it grabs the YouTube transcript. 223 00:12:43.320 --> 00:12:45.680 We create a blog post, we've got three social posts. 224 00:12:47.080 --> 00:12:52.680 And then we created a content pipeline SOP to help get the tone of voice correct. 225 00:12:52.880 --> 00:12:55.360 Still dialing this in, but it's 80, 90 percent there. 226 00:12:56.800 --> 00:12:59.120 We did a bunch of iterations on the YouTube transcripts. 227 00:12:59.440 --> 00:13:04.920 We processed 10 videos from a backlog and then went ahead and like set up this 228 00:13:04.920 --> 00:13:08.680 recurring Thursday. So Thursdays we do our live stream, like right after we finish 229 00:13:08.680 --> 00:13:14.280 this, an hour after it, it'll go and like grab the, it'll grab the new transcript 230 00:13:14.280 --> 00:13:16.480 and create the content like that. 231 00:13:17.280 --> 00:13:19.960 And it also goes ahead and writes the post for me. 232 00:13:20.000 --> 00:13:23.520 We use Typefully for X posts and LinkedIn. 233 00:13:24.200 --> 00:13:27.800 And so it came in here and it schedules them all as drafts. 234 00:13:27.960 --> 00:13:29.640 And so I just click in here. 235 00:13:29.800 --> 00:13:32.200 This all came from the agent, from the transcript. 236 00:13:32.200 --> 00:13:33.280 And so I can read through this. 237 00:13:33.320 --> 00:13:35.200 Now this is probably good or bad. 238 00:13:35.240 --> 00:13:40.440 I just tweak it and then hit schedule and it jumps, puts it on a schedule and I kind 239 00:13:40.440 --> 00:13:41.240 of forget about it. 240 00:13:42.560 --> 00:13:48.040 So like, and I was kind of joking with Macy because we've talked about different 241 00:13:48.040 --> 00:13:52.800 processes like this, like I would have had to go in and look at this anyway, because 242 00:13:52.800 --> 00:13:56.000 if it's going out as me, I do want to kind of look at it and make sure it's my voice 243 00:13:56.000 --> 00:13:59.040 and stuff. So even if a human had gone through and done this, which would have been 244 00:13:59.040 --> 00:14:04.280 a very time consuming process to try to listen through all these, this content and 245 00:14:04.280 --> 00:14:07.920 then try to make sense of it all and then try to create content that's useful. 246 00:14:09.160 --> 00:14:13.080 Just having, you know, three to five and I had to put three or five out there per 247 00:14:13.240 --> 00:14:16.360 video. And if I use two or three of them, that's great. 248 00:14:16.360 --> 00:14:20.720 It definitely helps. And also it kind of forces me into the process of like, hey, 249 00:14:20.720 --> 00:14:24.160 there's content I need to go and approve and then it kind of bugs me when it's not 250 00:14:24.160 --> 00:14:27.280 done. So we hired the four agents. 251 00:14:27.280 --> 00:14:31.320 We've done 70 tasks so far and we've got all these integrations and then it's been 252 00:14:31.320 --> 00:14:32.680 sending these reports. 253 00:14:32.680 --> 00:14:38.520 So I'll see if I can, maybe I can pull up my email so you can kind of see what this 254 00:14:38.520 --> 00:14:45.240 looks like, because I took it a step further and I went ahead and set this up for 255 00:14:45.280 --> 00:14:46.280 Lindsay as well. 256 00:14:46.720 --> 00:14:51.560 So Lindsay could have her, all her content and stuff is starting to be monitored and 257 00:14:51.560 --> 00:14:53.760 ads and all that. So here I am. 258 00:14:54.760 --> 00:14:59.760 This is this morning. Even the agents don't know how time zones work. 259 00:15:00.000 --> 00:15:04.700 Because this is like here's your 7 a.m. Report and I now it knows I fixed this today 260 00:15:04.700 --> 00:15:09.000 But it just could not get the time zone of being in Nashville verse 261 00:15:10.140 --> 00:15:17.180 DC so there's a little debt like brief here of like, you know, here's the reactive projects, you know 262 00:15:17.180 --> 00:15:19.460 We have a bunch of stuff that's sitting in review, which is which is fine 263 00:15:19.460 --> 00:15:23.720 That's kind of our process for reactive, but it's just funny to see how it like pulled that 264 00:15:23.720 --> 00:15:26.260 It's kind of highlighted a critical bug that it saw 265 00:15:26.260 --> 00:15:31.500 You know, and then it noticed actually caught something here, which is interesting because I think 266 00:15:32.020 --> 00:15:33.820 This one didn't sink 267 00:15:33.820 --> 00:15:38.440 And in the state synced has been this is kind of like identified a little gap here 268 00:15:38.440 --> 00:15:43.340 I want to go look at because it didn't sink this particular task. I mean, I know there's been tasks in this 269 00:15:43.900 --> 00:15:46.940 Since then so it was kind of like flagging that 270 00:15:47.540 --> 00:15:49.540 Here's some things that are on track 271 00:15:49.700 --> 00:15:55.620 And you know based on its criteria of what it thinks is on what you know on track means 272 00:15:56.260 --> 00:16:03.220 And then it just gives me like team activity. This is what the the agents have been doing and then 273 00:16:03.980 --> 00:16:06.940 Yeah, it's kind of a little highlight of anything to like note 274 00:16:06.940 --> 00:16:11.860 So it just comes in I can look at it just kind of forces my attention there for a little bit 275 00:16:12.900 --> 00:16:19.700 So I think this is good. I'm I've been using it since since Sunday. I'm pretty pretty happy with it 276 00:16:20.380 --> 00:16:23.180 And it is very addicting to kind of just sit here 277 00:16:24.140 --> 00:16:26.260 Play with all the bots as Lindsay would say 278 00:16:27.340 --> 00:16:28.500 bots 279 00:16:28.500 --> 00:16:32.300 It's it's a it's kind of very nerdy, but it's it's a lot of fun 280 00:16:33.500 --> 00:16:39.100 So right now I'm also gonna have set up routines. So that's where these project status check-ins look 281 00:16:39.900 --> 00:16:40.980 and 282 00:16:40.980 --> 00:16:47.120 You can have them do certain things. I can set the you know timing of this what that what you know, when does it run? 283 00:16:47.940 --> 00:16:50.940 Here and then it just kind of goes on like a heartbeat 284 00:16:51.580 --> 00:16:57.020 As well so as far as like some of the costs it's kind of interesting if you look down here 285 00:16:58.220 --> 00:17:02.620 Each of the agents are you know, it's been about a bunch of tokens 286 00:17:03.140 --> 00:17:11.099 And a lot of these are cash tokens. So I have spent zero dollars on all this. I'm not 100% sure. This is like 287 00:17:11.980 --> 00:17:16.900 approved by the Claude terms and conditions, you know officially but 288 00:17:17.260 --> 00:17:20.260 It's working in fact because I thought I had to put my 289 00:17:20.900 --> 00:17:26.380 API key in but because this is running on my VPS where Claude is installed globally 290 00:17:26.460 --> 00:17:30.060 it just started using my subscription and because that's it's already like 291 00:17:30.900 --> 00:17:36.300 Authenticated with my beep whole VPS. It just started using Claude, you know directly there. So 292 00:17:36.980 --> 00:17:39.340 Use that hack if you want to do all this free 293 00:17:39.700 --> 00:17:44.660 But if you didn't want to get really specific about costing and token usage you could set these in here 294 00:17:45.180 --> 00:17:46.340 I 295 00:17:46.340 --> 00:17:51.860 Have some projects I've started to try to build out you can connect github. I haven't tried to have it do any coding 296 00:17:51.860 --> 00:17:56.340 I'm I specifically told it that like our product is writing really good 297 00:17:56.340 --> 00:18:02.460 Well thought-out code and our team is like managing that as its own thing with their own agents 298 00:18:02.460 --> 00:18:05.460 And we need essentially support everything else that's happening 299 00:18:05.980 --> 00:18:07.980 around this so 300 00:18:08.540 --> 00:18:12.860 There's anything else anything else you guys want to see not this is where I'm clicking around anything 301 00:18:12.860 --> 00:18:17.100 I know there's a there's a few things like this. It's similar to open Claude similar to other 302 00:18:17.700 --> 00:18:19.700 orchestration tools 303 00:18:20.740 --> 00:18:22.740 What do you guys any thoughts 304 00:18:23.020 --> 00:18:28.020 Questions, here's kind of the Kanban board of everything. It's done where it's blocked 305 00:18:28.780 --> 00:18:30.780 What's being reviewed? 306 00:18:31.060 --> 00:18:32.620 so 307 00:18:32.620 --> 00:18:39.780 There's no chat interface as well. So from a like a UX standpoint the way I would do something just go here and say like 308 00:18:40.780 --> 00:18:42.780 Grab like I don't know my 309 00:18:44.460 --> 00:18:49.100 Most but why am I gonna do this? Let's say like I'll give it some sort of task like 310 00:18:50.220 --> 00:18:54.080 Tell me what's happening in drive reactive 311 00:18:55.580 --> 00:18:59.860 So I could I could do that and I'm just gonna it would sort of figure itself out 312 00:18:59.860 --> 00:19:06.140 I just throw it a task in the to-do and you'll see that one of the bots here will start to like fire up 313 00:19:06.700 --> 00:19:08.700 once that task 314 00:19:09.260 --> 00:19:15.260 Comes in and you'll see they'll kind of go live a little blue dot and then it'll start working through in progress and so forth 315 00:19:15.260 --> 00:19:17.260 And then it comes back into my inbox 316 00:19:17.900 --> 00:19:19.820 when it's all done, so 317 00:19:19.820 --> 00:19:22.380 That's the general flow, but there's not a chat interface 318 00:19:22.940 --> 00:19:25.500 So you can come back and comment on tasks 319 00:19:25.500 --> 00:19:29.860 So if I come back like here's where it was like sending the time zoning correctly 320 00:19:29.860 --> 00:19:35.540 I just come in here kind of like you're leaving a comment, you know on a notion task or something 321 00:19:35.540 --> 00:19:39.620 You can just comment here and then it will sort of pick it up and go from there. So 322 00:19:40.340 --> 00:19:41.660 cool 323 00:19:41.660 --> 00:19:45.140 Anything else want to look at a paperclip? I read some other stuff, too 324 00:19:47.300 --> 00:19:53.020 I think maybe maybe one interesting thing to show is the company's dot a 325 00:19:54.260 --> 00:20:00.020 Sh that was launched. I think yesterday maybe but it's very cool because it's 326 00:20:00.000 --> 00:20:09.360 It's a kind of quick start, interesting quick start way to test Paperclip because now you have 327 00:20:09.360 --> 00:20:17.200 like this directory of Paperclip companies. Yeah, it's very, it's so nice, like I love it. 328 00:20:17.200 --> 00:20:22.080 And you have like... This is by the people who made Paperclip, right? 329 00:20:22.640 --> 00:20:28.560 Yeah, exactly. I think that's how they are going to monetize at some point. I think at some point 330 00:20:28.560 --> 00:20:35.040 they're going to turn this into a managed cloud infrastructure and they are going to sell the 331 00:20:35.040 --> 00:20:40.000 companies for you to run, which is funny. But I think that's where they are going because 332 00:20:40.000 --> 00:20:45.760 everything is free for now and it's bring your own keys and it's open source. So I'm thinking 333 00:20:45.760 --> 00:20:51.680 about like how they are going to monetize all the things they are building and maybe that's the way. 334 00:20:51.680 --> 00:21:01.040 But I was testing the G-Stack. It's very nice. I asked it to... Basically, I gave it a quick 335 00:21:01.040 --> 00:21:08.640 prompt to create a workout app that was voice-based and timeline-based because I wanted 336 00:21:08.640 --> 00:21:16.400 kind of just a nice timeline of feed of different trainings like strength and running and stuff 337 00:21:16.400 --> 00:21:23.120 like that all on the same page. And I wanted to track it by voice. And basically, I just 338 00:21:23.840 --> 00:21:30.320 installed G-Stack on top of Paperclip, like using Paperclip and used the G-Stack templates. 339 00:21:30.960 --> 00:21:40.000 And I did a small fig jam of what I wanted and I simply created that task for the CEO. 340 00:21:40.000 --> 00:21:47.840 Hey, analyze this fig jam and create a Flutter app following this and this standard and hire 341 00:21:47.840 --> 00:21:52.960 the team that you need to do it. And then it starts to do all this stuff. I think it ran for 342 00:21:52.960 --> 00:22:00.240 around like one hour or something. And by then, the app was fully built. There was one or two 343 00:22:00.240 --> 00:22:06.960 issues that were crashing, but the bulk of the work was there. And it was even following 344 00:22:06.960 --> 00:22:14.160 the standards I guided it to because of the call, the settings that I had. So, 345 00:22:14.800 --> 00:22:21.200 yeah, very, very powerful. And so when you did the code, I haven't tried the coding 346 00:22:21.200 --> 00:22:24.640 and I was trying to like basically solve everything else. We've spent so much time 347 00:22:24.640 --> 00:22:32.960 on the coding workflows. But when it builds it, does it build it locally on that either 348 00:22:32.960 --> 00:22:39.040 VPS or locally on a machine in a directory or did you give it a repo to build in or how did it? 349 00:22:39.920 --> 00:22:46.320 Yeah, I gave it a private repo. And to be honest, it actually figured it out 350 00:22:47.760 --> 00:22:56.240 because I didn't inform where I wanted it built. But since my local clouds connected to my GitHub 351 00:22:56.240 --> 00:23:03.280 account, my private GitHubs, it saw that I already had the GitHub click connected 352 00:23:03.280 --> 00:23:11.360 and it created its own repo and it's founded a different work tree for each agent. And they were 353 00:23:11.360 --> 00:23:17.680 in the CTO coordinated the merge between all the agents, which was very interesting, like 354 00:23:18.400 --> 00:23:28.240 they started to merge and it happened like a couple of conflicts, but the CTO was able to 355 00:23:28.240 --> 00:23:37.200 figure it out. That's amazing. I, yeah, it's fat. This is the, I hit one thing like that as well, 356 00:23:37.920 --> 00:23:43.760 where one of the agents got stuck on something and it's like, oh, it's erroring out because some API 357 00:23:43.760 --> 00:23:50.480 something or other, the CEO like jumps into the task, makes a comment. Hey, looks like we need to 358 00:23:50.480 --> 00:23:55.200 bring the platform engineer in, pulls the platform engineer, creates a new task for him to go fix the 359 00:23:55.200 --> 00:24:01.120 API to do the thing. And then like, and I didn't touch it. And I was just like, this is, it just, 360 00:24:01.120 --> 00:24:07.680 it was like, okay, we're the future is now like we are, we are living in it right now. But anyway, 361 00:24:07.680 --> 00:24:12.800 so it's, it's been fun. Like this is this little task I was going to show what it looks like when 362 00:24:12.800 --> 00:24:19.520 it's running in case you haven't seen it is it does kind of show you all the back and forth. You 363 00:24:19.520 --> 00:24:25.200 don't have to, you know, do anything with this. I haven't, I rarely touch any of this. Probably 364 00:24:25.200 --> 00:24:31.600 shouldn't share whatever that's on that screen. It's probably a lot of stuff, but it's all, 365 00:24:31.600 --> 00:24:39.200 it's all protected with the SSH key. So and then when it's done, I don't have to like do anything. 366 00:24:39.200 --> 00:24:44.800 It's going to basically pop a new item into my tasks here when it's, when it's all finished. So, 367 00:24:46.240 --> 00:24:52.080 and you can kind of see like all the agents that go, it's funny that they copied linear interface. 368 00:24:52.080 --> 00:24:59.840 It's like, it's very similar for sure. They must've used that as the, as the, like 369 00:25:00.000 --> 00:25:01.680 reference because it's very minimal. 370 00:25:01.680 --> 00:25:08.640 I think there is a linear open source GitHub that's basically this interface, but not with 371 00:25:08.640 --> 00:25:09.800 the agents connected. 372 00:25:09.800 --> 00:25:12.680 So I think they kind of use it as base. 373 00:25:12.680 --> 00:25:14.440 So this is great. 374 00:25:14.440 --> 00:25:18.120 So this is what it went and got. 375 00:25:18.120 --> 00:25:23.840 It looked at the task grid, I guess, of the slices here of what's so this one obviously 376 00:25:23.840 --> 00:25:28.960 doesn't have a task because it's reactive, but I love that, like the flags. 377 00:25:28.960 --> 00:25:29.960 Bruce Van Zael's overloaded. 378 00:25:29.960 --> 00:25:35.080 12 of the 18 tasks are his because I just basically have a ton of stuff I forgot to 379 00:25:35.080 --> 00:25:37.960 mark completed. 380 00:25:37.960 --> 00:25:40.320 Just pointing out that I made a mistake. 381 00:25:40.320 --> 00:25:45.760 But then it's funny because it shows that this is in review still, and it's funny because 382 00:25:45.760 --> 00:25:49.680 that got released on Monday. 383 00:25:49.680 --> 00:25:53.720 So it's trying to guess at some things, but it's trying to use some logic like, hey, it's 384 00:25:53.720 --> 00:25:55.720 just still sitting in review. 385 00:25:55.720 --> 00:25:56.720 So maybe it's blocked. 386 00:25:56.720 --> 00:25:57.920 It can't get reviewed. 387 00:25:57.920 --> 00:26:02.360 So it's just funny that obviously we could go fix that. 388 00:26:02.360 --> 00:26:05.320 One thing that it will do as well, it's like, hey, do you want me to clean those up? 389 00:26:05.320 --> 00:26:16.960 So I can say mark all Bruce's tasks in review as completed and the 5.2 release. 390 00:26:16.960 --> 00:26:20.880 So I can just give it one line like that and keep this conversation going, and then it 391 00:26:20.880 --> 00:26:24.240 will go back and use the MCP and close all those out for me. 392 00:26:24.240 --> 00:26:27.320 So it just kind of surfaces something, like what do you want to do with this? 393 00:26:27.720 --> 00:26:29.160 Oh, you can clean these things up. 394 00:26:29.160 --> 00:26:35.360 In other cases, it will actually give me some suggestions of tasks because I quickly ran 395 00:26:35.360 --> 00:26:36.480 out of stuff to do. 396 00:26:36.480 --> 00:26:39.920 I quickly ran out of ideas for how it could work. 397 00:26:39.920 --> 00:26:49.240 And so one thing I did is in the check-in, I asked it to suggest a task, one task for 398 00:26:49.240 --> 00:26:53.540 each team member, go ahead and write it and put it in the backlog. 399 00:26:53.540 --> 00:26:59.060 And then when it sends me my little daily email, looks at everything that all the agents 400 00:26:59.060 --> 00:27:00.060 are doing. 401 00:27:00.060 --> 00:27:05.300 And this was a suggestion where it said, hey, you've already got this whole content pipeline. 402 00:27:05.300 --> 00:27:06.700 I'm writing you a blog post. 403 00:27:06.700 --> 00:27:08.580 I'm writing you the email. 404 00:27:08.580 --> 00:27:14.740 Why don't we have the platform engineer connect to whatever newsletter tool you're using? 405 00:27:14.740 --> 00:27:16.420 And I'll just go ahead and preload it into that. 406 00:27:16.420 --> 00:27:17.780 I was like, oh, that's awesome. 407 00:27:17.780 --> 00:27:18.780 I didn't even think about that. 408 00:27:18.780 --> 00:27:22.740 It's like just, you know, I handed it, it's the API keys for ActiveCampaign and the notes 409 00:27:22.740 --> 00:27:25.500 it needed, and then it went and added that to the pipeline. 410 00:27:25.500 --> 00:27:27.380 But I didn't come up with that idea. 411 00:27:27.380 --> 00:27:30.500 It was able to, you know, keep up with it. 412 00:27:30.500 --> 00:27:31.380 So pretty cool. 413 00:27:35.420 --> 00:27:35.920 Awesome. 414 00:27:38.720 --> 00:27:39.220 Sweet. 415 00:27:39.220 --> 00:27:43.100 Well, we can...anything else you want to talk about on Paperclip or we can jump into some 416 00:27:43.100 --> 00:27:47.660 more like, I don't know, something else. 417 00:27:48.660 --> 00:27:49.780 What else do you guys want to talk about? 418 00:27:49.780 --> 00:27:55.260 I would love to hear from like how...I know Luch and you just did a project, and you've been 419 00:27:55.260 --> 00:27:57.340 working this week since we talked last week. 420 00:27:57.340 --> 00:27:59.980 Like, I don't know if you're using the MCP and what's working. 421 00:27:59.980 --> 00:28:04.620 I know you started assigning tasks to me of stuff that was not working. 422 00:28:04.620 --> 00:28:09.260 So, because one of the tasks, things I thought for this call would be helpful to hear, 423 00:28:09.260 --> 00:28:13.300 like, feedback on like what is working or not working. 424 00:28:13.300 --> 00:28:14.500 And I'll take that. 425 00:28:14.500 --> 00:28:16.980 Yeah, honestly, it just overall works like really great. 426 00:28:16.980 --> 00:28:18.700 It's just like little details. 427 00:28:18.700 --> 00:28:20.660 So, let's keep using it. 428 00:28:20.660 --> 00:28:21.300 It's great. 429 00:28:21.300 --> 00:28:25.420 I'm going to like definitely jump on the bandwagon with Paperclip. 430 00:28:25.420 --> 00:28:28.060 So much like potential. 431 00:28:28.060 --> 00:28:31.900 Yeah, that's really awesome. 432 00:28:31.900 --> 00:28:34.020 It's...you know, it's interesting. 433 00:28:34.020 --> 00:28:40.660 Like, we have, I'll show this as well, totally different use case for Paperclip. 434 00:28:40.660 --> 00:28:50.100 So, I set this up for Lindsey, and it's already gone and done like 46 tasks for her. 435 00:28:50.100 --> 00:28:56.860 And what I've got hers doing is essentially pulling...we're running ads right now. 436 00:28:56.860 --> 00:29:03.060 So, it went in and added...created an ad strategist, connected it to Meta. 437 00:29:03.060 --> 00:29:08.820 And so, now it's...I just set it up as read-only because I was a little nervous initially. 438 00:29:08.860 --> 00:29:20.460 And so, if I open up my email here, you'll see I now get like a daily email of everything 439 00:29:20.460 --> 00:29:24.140 going on with this like little campaign that we're running. 440 00:29:24.140 --> 00:29:27.500 And so, she gets...she gets copied on this as well. 441 00:29:27.500 --> 00:29:30.060 And so, I can see, hey, our total spend is this. 442 00:29:30.060 --> 00:29:34.260 Like we've gone...we've gotten, you know, 3,300 leads so far. 443 00:29:34.260 --> 00:29:35.460 This is what the cost is. 444 00:29:35.460 --> 00:29:36.860 Hey, this is what happened yesterday. 445 00:29:37.220 --> 00:29:38.660 You spent this much money. 446 00:29:38.660 --> 00:29:41.820 And then, same thing on this other boosted campaign. 447 00:29:41.820 --> 00:29:46.460 And then, it gives some suggestions of like what it thinks we could do to improve this. 448 00:29:46.460 --> 00:29:50.500 And I haven't got it quite yet to where like, okay, go make those changes. 449 00:29:50.500 --> 00:29:56.260 I'm not trusting it just quite that yet because this is all attached to like a credit card. 450 00:29:56.260 --> 00:30:00.100 And if you spend money on Facebook, like if money's gone, it's not like... 451 00:30:00.000 --> 00:30:01.800 Like there's no protection in there really. 452 00:30:02.480 --> 00:30:04.640 It'll just keep spending until the accounts are empty. 453 00:30:06.400 --> 00:30:10.640 But so that gives me like a little overview. 454 00:30:10.680 --> 00:30:14.440 And again, I kind of dialed this in a little bit to get like a very brief update 455 00:30:14.440 --> 00:30:17.240 here. And now it's just coming in every morning. 456 00:30:17.560 --> 00:30:20.440 I get this little email to see what's going on with that. 457 00:30:20.480 --> 00:30:25.640 So, you know, I think when you're when you're like when you're a founder, 458 00:30:25.680 --> 00:30:28.480 you're kind of jumping between so many different things. 459 00:30:28.480 --> 00:30:31.880 Like you're looking at, you know, so many different things have your attention. 460 00:30:31.880 --> 00:30:35.920 And I'll say not as a founder, but like as a human, like you're working. 461 00:30:36.520 --> 00:30:38.880 You can have all these things going, but at some point you start to feel 462 00:30:38.880 --> 00:30:41.520 overwhelmed because you're like, oh man, I haven't checked on the ads. 463 00:30:41.560 --> 00:30:44.000 Like maybe I'm spending money I shouldn't be spending. 464 00:30:44.480 --> 00:30:48.440 But now I get an email every morning that just like glance at for 30 seconds. 465 00:30:48.440 --> 00:30:51.080 I'm like, oh good. Like we're trending in the right direction. 466 00:30:51.120 --> 00:30:52.680 It's not getting more expensive. 467 00:30:53.800 --> 00:30:57.440 It's got some suggestions, but the suggestions aren't like stop everything. 468 00:30:57.440 --> 00:31:01.160 It's, you know, your cost has gone insanely up because that could happen on Facebook. 469 00:31:01.200 --> 00:31:05.480 You leave it for a few days, you know, something changes and now like the cost has 470 00:31:05.480 --> 00:31:08.640 spiked and you don't realize it for a few days and you start burning money. 471 00:31:09.880 --> 00:31:12.800 So it's interesting that I think it's going to make. 472 00:31:13.680 --> 00:31:20.000 I think this idea of having the like autonomous agents is make a huge difference 473 00:31:20.000 --> 00:31:25.320 to the to the flow here, because, yeah, it's it's you kind of I'm I don't want to 474 00:31:25.320 --> 00:31:30.840 think about building content like I'm going to do this one call where we just talk and 475 00:31:30.840 --> 00:31:33.560 then let it go, like figure out some content from that. 476 00:31:34.840 --> 00:31:36.720 So, you know, and I did spend a lot. 477 00:31:36.760 --> 00:31:41.800 So I think we are going to be spending a lot more time as like builders in the future 478 00:31:41.800 --> 00:31:47.280 building the systems and dialing in these or these workflows than just sitting and doing 479 00:31:47.280 --> 00:31:50.560 the work. Right. So, yeah. 480 00:31:51.560 --> 00:31:53.080 Totally, totally. 481 00:31:55.000 --> 00:31:58.480 Two things I wanted to complement with this. 482 00:31:59.000 --> 00:32:04.560 First, I sent in the private chat here the Gas City repo. 483 00:32:04.680 --> 00:32:08.600 Very interesting stuff from Steve Wynton. 484 00:32:08.640 --> 00:32:12.440 I'm not sure how to pronounce his second name, but it's Steve. 485 00:32:13.680 --> 00:32:18.920 He started with like this concept called Gas Town, which is very interesting. 486 00:32:19.480 --> 00:32:21.320 It's a orchestration tool. 487 00:32:23.320 --> 00:32:29.840 In some sense, it's similar to Paperclip, but it takes a technical, different approach, 488 00:32:29.880 --> 00:32:39.920 let's say, which I think is more it's more solid for our software factory. 489 00:32:40.240 --> 00:32:48.000 But the problem was that Gas Town was very opinionated and they created Gas City, which 490 00:32:48.000 --> 00:32:56.720 is more like an SDK that allows you to configure your agents to run in this city 491 00:32:56.720 --> 00:33:01.160 structure, which is basically how they call the orchestration layer. 492 00:33:02.240 --> 00:33:07.800 And it's funny because configuring it is just like you said, you start to realize that a 493 00:33:07.800 --> 00:33:13.120 lot of the work now is just about like how to set it up, how to set everything 494 00:33:13.120 --> 00:33:20.120 correctly and like how to have different setups for each agent. 495 00:33:20.520 --> 00:33:27.840 And the whole idea is that we could probably create a Gas City that would be like named 496 00:33:27.840 --> 00:33:34.640 like InnovoCity and then would be like managing like the different areas and then 497 00:33:34.640 --> 00:33:38.200 different projects that we have. 498 00:33:38.600 --> 00:33:45.080 But the interesting thing to me is that they are using the underlying, they are using 499 00:33:45.080 --> 00:33:54.000 like the bits, which is basically a very simple kind of Git-like structure, but to 500 00:33:54.000 --> 00:34:01.160 track like tasks or small, like very small pieces of work that was changed. 501 00:34:01.880 --> 00:34:07.440 And you can have this as its own backend, which is called the dot backend. 502 00:34:07.680 --> 00:34:15.600 So you have the agents working on your local machine, but they are all updating the 503 00:34:15.600 --> 00:34:17.360 dot backend. 504 00:34:17.600 --> 00:34:22.560 So Bruce can have agents running, I can have agents running, Lucien can have agents 505 00:34:22.560 --> 00:34:29.239 running, but they are all writing to the same minimal session slash state interface, 506 00:34:29.600 --> 00:34:35.520 meaning that we all be operating the same agents from the point of view that they are 507 00:34:35.600 --> 00:34:41.520 sharing the same prompts and tools, but they are running on our local machines and they 508 00:34:41.520 --> 00:34:49.560 leave the session debuggable for all of us, meaning I would be able to debug an agent 509 00:34:49.560 --> 00:34:51.760 session from Lucien and vice versa. 510 00:34:52.000 --> 00:34:55.560 So we can continue work from each other, which is very nice. 511 00:34:55.560 --> 00:34:57.520 So I can say like, hey, I just stopped here. 512 00:34:57.640 --> 00:34:59.960 You can continue from this session and you. 513 00:35:00.000 --> 00:35:05.200 be able to continue the work from where I stopped and the context would be shared. 514 00:35:06.240 --> 00:35:07.200 Yeah, that's awesome. 515 00:35:07.200 --> 00:35:13.200 So yeah, that's very early. I believe it was launched yesterday, like yesterday, but 516 00:35:14.640 --> 00:35:17.280 That's the reason you would know about it because it's like 517 00:35:19.360 --> 00:35:25.200 Yeah, but I was like, man, this solves like a lot of problems that we are trying to solve 518 00:35:25.840 --> 00:35:27.840 and the thing now is just like 519 00:35:30.080 --> 00:35:32.080 set it up correctly because it's very 520 00:35:34.540 --> 00:35:42.020 Flexible you can set it up like you can have agents for marketing but also for coding and all under the same structure 521 00:35:42.560 --> 00:35:44.320 and 522 00:35:44.320 --> 00:35:51.200 Let's say consume consuming the same database, uh, like we want the same knowledge database so we could have like 523 00:35:52.080 --> 00:35:55.920 city of agents set up that's consuming, uh, 524 00:35:56.000 --> 00:36:02.160 Or the or the data that we already have centered in our knowledge database, so it's very 525 00:36:03.200 --> 00:36:08.640 Yeah interesting stuff. Uh, i'm testing it right now. I'm actually like 526 00:36:09.360 --> 00:36:11.360 Creating a seat a seat 527 00:36:11.920 --> 00:36:18.000 For my obsidian vault so that obsidian vault that I showed last week that i'm, uh, 528 00:36:18.720 --> 00:36:20.900 Using to manage my para infrastructure 529 00:36:21.780 --> 00:36:26.580 Uh, I attached a a city on top of that. So now I have like 530 00:36:27.300 --> 00:36:32.900 Agents managing the vault like making sure I don't have nodes that are not connected to anything 531 00:36:33.300 --> 00:36:42.020 So and and making sure that everything is clean and no project stays on my pipeline for more than 14 days without an actionable item 532 00:36:42.340 --> 00:36:49.780 So I can make sure that everything on this infrastructure is running being monitored by this this this little city. So yeah, it's 533 00:36:50.580 --> 00:36:52.580 Very very interesting stuff 534 00:36:53.140 --> 00:36:56.900 Yeah, I think we gotta just keep experimenting with it. Um, 535 00:36:57.540 --> 00:37:01.460 This is great. I want to keep playing with it because like we kind of have this 536 00:37:02.260 --> 00:37:08.580 This flow like this paperclip to me, you know, it's just we're just sitting out over here somewhere, you know 537 00:37:09.140 --> 00:37:10.020 um 538 00:37:10.020 --> 00:37:11.620 And that's going to be like mine 539 00:37:11.620 --> 00:37:16.260 But like if lucian wants to have one to go get tasks and do stuff and like help him 540 00:37:17.060 --> 00:37:19.060 Do whatever organizes, you know 541 00:37:19.620 --> 00:37:21.460 What your week or whatever? 542 00:37:21.460 --> 00:37:25.620 Um, and you were we were talking about this last week. I don't think I showed it necessarily on the stream 543 00:37:25.700 --> 00:37:28.120 But yeah, you could technically use obsidian 544 00:37:29.060 --> 00:37:34.100 Um an open call or whatever tech stack you want down here and just keep feeding stuff in and out of the business 545 00:37:34.660 --> 00:37:35.860 because 546 00:37:35.860 --> 00:37:39.380 We're just gonna what I want to do is make sure that we're we're just creating the easiest 547 00:37:40.020 --> 00:37:42.020 like in and out 548 00:37:42.020 --> 00:37:47.380 Process for this database for this app. So like things are super well framed 549 00:37:47.620 --> 00:37:49.460 We've got our nice little tasker built out 550 00:37:49.460 --> 00:37:51.460 we've got a nice process in here so that 551 00:37:51.780 --> 00:37:55.700 All the tasks that are coming out of this are very well informed of what we're doing 552 00:37:56.020 --> 00:37:58.900 But you know with for the rest for this actual project 553 00:37:59.460 --> 00:38:05.140 Um so that you guys can plug in whatever tools you want and just rip through these tasks and projects as fast as possible 554 00:38:05.780 --> 00:38:06.900 um 555 00:38:06.900 --> 00:38:07.940 so 556 00:38:07.940 --> 00:38:12.260 Anyway, I think I think that's it's this is sort of the way I I worked on 557 00:38:12.900 --> 00:38:15.780 a ton of stuff last week, um for 558 00:38:16.740 --> 00:38:18.980 tribe, and I think all those like, um 559 00:38:20.180 --> 00:38:26.740 The reactive work that I put in. Um, that was all just on uh, let me see if I can pull some of it up 560 00:38:28.260 --> 00:38:30.260 This was march 561 00:38:30.980 --> 00:38:32.660 um 562 00:38:32.660 --> 00:38:35.060 So we had we had a bunch of tasks. Um 563 00:38:35.940 --> 00:38:38.420 That that I just kind of cleared out, uh 564 00:38:39.140 --> 00:38:44.980 where we were trying to deal with chat and had clients like texting us and editing stuff and I think there was like a 565 00:38:44.980 --> 00:38:46.980 really kind of hit like a uh 566 00:38:47.140 --> 00:38:49.780 Sweet spot where I was like eventually kind of finished up the week 567 00:38:49.860 --> 00:38:50.260 I was like man 568 00:38:50.260 --> 00:38:52.980 I feel like I did a ton in like three days 569 00:38:53.060 --> 00:38:58.020 I was like, yeah, because I probably did like maybe what would have taken a week or two, you know in a past season 570 00:38:58.580 --> 00:39:02.660 um, just kind of prompting stuff and uh, and then we added the um 571 00:39:02.980 --> 00:39:07.620 Maestro stuff which we didn't talk where we could talk about that as well. But um 572 00:39:08.500 --> 00:39:13.620 Now like I saw the release, you know yesterday that lucid did where he automated the 573 00:39:14.420 --> 00:39:18.420 All the apps getting built and then published it seemed like that works pretty well 574 00:39:18.980 --> 00:39:20.980 Hopefully it didn't take too much time 575 00:39:21.620 --> 00:39:25.220 Where credit is due that was janata automating this i'm just using his 576 00:39:26.340 --> 00:39:28.820 yeah, but it's really impressive when like 577 00:39:29.460 --> 00:39:30.420 um 578 00:39:30.420 --> 00:39:34.900 Like he built it and then he handed off a playbook and then you were able to run it because sometimes that he's like 579 00:39:34.900 --> 00:39:40.020 Oh, I made this really cool tool and then like no one knows how to use it. So just paying him when we need some push 580 00:39:40.740 --> 00:39:46.260 And it was funny because I was a bit afraid I was like when you said hey lucian go ahead and publish it 581 00:39:46.260 --> 00:39:50.660 and I was like man, I I didn't even send a message man if you need some help like 582 00:39:51.140 --> 00:39:53.860 Because I was hoping it was work out of the box 583 00:39:53.860 --> 00:39:59.780 But I wasn't sure because you know how this thing goes with environments and stuff, but i'm happy it worked 584 00:40:00.000 --> 00:40:07.200 That's great, but it creates like a peace of mind to like just push stuff in a confident. 585 00:40:07.200 --> 00:40:12.080 So I think that's to me is like, there's kind of getting a lot of really refined process 586 00:40:12.080 --> 00:40:16.200 on the inputs we're giving it, as far as that's where the clarity, because if you're not, 587 00:40:16.200 --> 00:40:20.140 so someone, there's such a great quote and I won't do it justice, but someone said something 588 00:40:20.140 --> 00:40:26.340 like all that AI is doing is helping people who either thought very clearly like to execute 589 00:40:26.340 --> 00:40:29.880 or people who are really fuzzy on how they're thinking about stuff to also execute. 590 00:40:29.880 --> 00:40:32.460 It's not like it's going to fix fuzzy thinking, right? 591 00:40:32.460 --> 00:40:36.860 It's like we have to fix that part of getting like really clear about the problems we're 592 00:40:36.860 --> 00:40:41.380 solving and the outcome and like how we're going to build it and breadboarding and thinking 593 00:40:41.380 --> 00:40:44.380 things through the human side of it. 594 00:40:44.380 --> 00:40:48.460 That's sort of like all the pre-work and then we like, you know, hand it off to go and then 595 00:40:48.460 --> 00:40:53.160 being able to observe it and kind of then sort of go along the journey of executing 596 00:40:53.160 --> 00:40:58.260 on that plan and then pivoting as little things pop up, little UI things that are going to 597 00:40:58.260 --> 00:41:01.760 pop up that like you thought it would work this way and now there's this kind of weird 598 00:41:01.760 --> 00:41:03.760 design problem you have. 599 00:41:03.760 --> 00:41:04.880 We kind of explore stuff. 600 00:41:04.880 --> 00:41:08.880 So yeah, I think it's, I think it's great. 601 00:41:08.880 --> 00:41:12.600 And then I was, I was saying there's the inputs and then there's of course this output layer, 602 00:41:12.600 --> 00:41:16.680 like right before it goes live, having all those automated tests and being able to kind 603 00:41:16.680 --> 00:41:21.680 of push with more confidence means that we can deploy more often. 604 00:41:21.680 --> 00:41:28.460 And we did, we pushed a bunch of stuff on, on 5.2.2 on Monday with like a new chat tab 605 00:41:28.460 --> 00:41:31.260 with like a bunch of UI changes. 606 00:41:31.260 --> 00:41:34.340 Andrew Daniels had put like a new login screen together. 607 00:41:34.340 --> 00:41:37.700 He's also got a new course UI that he finished up yesterday. 608 00:41:37.700 --> 00:41:44.500 So he's been going Figma, Figma MCP with Claude into the, into a branch. 609 00:41:44.500 --> 00:41:49.940 He's never used GitHub before, never used Claude before, like, and he's like pushing 610 00:41:49.940 --> 00:41:53.560 these features in and I'm doing the PR, PRs for it. 611 00:41:53.560 --> 00:41:55.480 And it's working pretty great. 612 00:41:55.480 --> 00:42:00.760 It's not as fast as like, you know, him doing it in Figma directly, but the cool thing is 613 00:42:00.760 --> 00:42:05.360 he's able to make the change and then play with it immediately and kind of click around 614 00:42:05.360 --> 00:42:09.800 on different groups and figure out like, oh, if I make that change here and I jumped to 615 00:42:09.800 --> 00:42:11.720 another group, it creates this other design problem. 616 00:42:11.720 --> 00:42:16.400 So I think that is the way to do it versus just sitting in Figma and kind of mocking 617 00:42:16.400 --> 00:42:17.400 stuff up. 618 00:42:17.900 --> 00:42:18.900 Yeah. 619 00:42:18.900 --> 00:42:22.460 So we're pushing a lot, a lot of cool, cool stuff. 620 00:42:22.460 --> 00:42:28.300 The group thing, very excited about, I made a video for it and we shared it with all the 621 00:42:28.300 --> 00:42:30.220 customers today. 622 00:42:30.220 --> 00:42:35.520 And yeah, I think that's going to open up a ton of options to just push random, like 623 00:42:35.520 --> 00:42:41.820 new tabs and features and pages and integrations, whatever you want to call them, you can push 624 00:42:41.820 --> 00:42:42.820 all of them. 625 00:42:42.820 --> 00:42:43.820 Things. 626 00:42:43.820 --> 00:42:44.820 You can call it things. 627 00:42:45.100 --> 00:42:49.520 Anything else you guys want to talk about? 628 00:42:49.520 --> 00:42:53.520 Janai, you have plenty to talk about. 629 00:42:53.520 --> 00:42:59.460 Oh, I wanted to show, I'll share this link. 630 00:42:59.460 --> 00:43:03.320 You shared this with me, Janai, but I'll put this in the team chat if you guys haven't 631 00:43:03.320 --> 00:43:06.360 checked this out. 632 00:43:06.360 --> 00:43:07.360 This was so encouraging. 633 00:43:07.360 --> 00:43:12.680 I said there's like a great post from Jason Fried last week on Friday. 634 00:43:12.860 --> 00:43:15.420 I spent like three days just doing nothing else. 635 00:43:15.420 --> 00:43:18.860 Like I just woke up, like went to the gym, came home and just sat in front of my computer 636 00:43:18.860 --> 00:43:22.300 for like six straight hours coding. 637 00:43:22.300 --> 00:43:26.420 And Jason Fried had posted something last week about bespoke software. 638 00:43:26.420 --> 00:43:27.420 Super encouraging. 639 00:43:27.420 --> 00:43:32.500 And then this post that came out earlier this month is really encouraging. 640 00:43:32.500 --> 00:43:37.700 And I thought this was just such a great little graph of like which domains are using agents 641 00:43:37.700 --> 00:43:38.700 the most. 642 00:43:38.720 --> 00:43:43.840 Obviously software, like it's like by a long shot. 643 00:43:43.840 --> 00:43:49.440 And then he had a whole thing on like, I think this first part here, is it this one? 644 00:43:49.440 --> 00:43:53.960 This is like first paragraph. 645 00:43:53.960 --> 00:43:58.440 Like yeah, it was basically just reinforcing like services where it's going to be at. 646 00:43:58.440 --> 00:44:02.080 Like doing this stuff as a service is where it's at. 647 00:44:02.080 --> 00:44:05.840 Building this thing, like kind of not vibe coding as a service, but that's sort of the 648 00:44:05.860 --> 00:44:06.860 gist of it. 649 00:44:08.580 --> 00:44:11.860 So I was anyway, it's like a few minute read. 650 00:44:11.900 --> 00:44:13.060 I'll drop it in the thing. 651 00:44:13.060 --> 00:44:14.980 But Janata sent this to me as well. 652 00:44:15.460 --> 00:44:20.100 So if you need some good content, like and subscribe to Janata and he will keep you guys 653 00:44:20.100 --> 00:44:22.980 up to date on all the good stuff. 654 00:44:25.980 --> 00:44:28.660 I need to create a YouTube channel too. 655 00:44:31.620 --> 00:44:34.340 Awesome. Well, we'll end it there. 656 00:44:34.360 --> 00:44:36.680 I'll end the stream and then we can chat if you guys have anything else. 657 00:44:36.680 --> 00:44:37.680 But this was good. 658 00:44:38.880 --> 00:44:39.400 See you guys.