WEBVTT 00:00.320 --> 00:05.400 And very briefly, as I promised, I want to show you what it looks like if we restart everything. 00:05.400 --> 00:11.200 And now we go through and we put all on one worker as false, what does this mean exactly? 00:11.520 --> 00:18.040 So we are going to, of course, have the same message, the same hosted, uh, the same host that we 00:18.040 --> 00:20.520 start running on localhost at 551. 00:21.240 --> 00:26.840 And we use the same tools, the same instructions, we make the same agents. 00:26.840 --> 00:30.840 Our agent code isn't touched, but now it's going to be managed differently. 00:31.160 --> 00:34.920 We're now going to run this and we're going to be following this line right here. 00:35.040 --> 00:42.120 And this is actually going to create three different runtimes that I'm calling worker one, worker two, 00:42.120 --> 00:44.240 and worker and just worker for the third one. 00:44.520 --> 00:45.640 Uh, the judges one. 00:45.840 --> 00:51.360 And we're going to start each of these three, uh, gRPC worker runtimes. 00:51.600 --> 00:57.080 And then player one, we're going to register with worker one, player two with worker two. 00:57.320 --> 01:00.720 And the judge uh, with just the one that's just called worker. 01:00.920 --> 01:02.360 And so that is happening. 01:02.400 --> 01:03.480 And so what's the difference here. 01:03.480 --> 01:10.610 What we're saying is that instead of having, instead of having our three agents running in a remote 01:10.650 --> 01:18.490 worker on on our remote host, we now have three workers, and the three workers are each running one 01:18.490 --> 01:19.170 of our agents. 01:19.170 --> 01:21.490 So they're now in different runtimes. 01:21.490 --> 01:22.570 They're all on the same host. 01:22.570 --> 01:26.210 But you could imagine that this is now they're completely separate. 01:26.250 --> 01:30.690 This is something where things are interacting between runtimes. 01:30.890 --> 01:34.450 And so now we send the same go message. 01:34.730 --> 01:39.490 And presumably very similar messages are now crossing the ether. 01:39.730 --> 01:44.890 One agent is calling Gpt4 on many for the pros, one agent for the cons. 01:44.890 --> 01:50.810 And then as a result of that they will come back to the to the judge. 01:51.410 --> 01:58.210 And the judge has come I will we see pretty similar looking pros. 01:58.250 --> 02:00.090 The community and support is a new one. 02:00.090 --> 02:09.290 I think scalability is now put first the cons, um, limited customization that seems to slightly fly 02:09.290 --> 02:12.940 in the face of flexibility I guess our agents disagree. 02:13.300 --> 02:19.340 Uh, performance variability, cost considerations and ethical and content control. 02:19.380 --> 02:19.780 Okay. 02:20.060 --> 02:24.460 Uh, but nonetheless, the recommendation is to proceed. 02:24.700 --> 02:32.180 That is the view of even even when we distribute across multiple workers, it does still maintain that 02:32.180 --> 02:32.820 viewpoint. 02:33.060 --> 02:33.980 Uh, so there we go. 02:34.020 --> 02:37.620 That the example I wanted to show you, I know we've gone through it quickly, but it's just to get 02:37.620 --> 02:45.300 that sense that the powerful thing about this is that without changing your, your, your code with 02:45.340 --> 02:50.900 the same definitions of your classes, these can be running in different configurations and different 02:50.900 --> 02:52.100 kinds of runtimes. 02:52.140 --> 02:59.700 And basically, uh, the what Autogen is doing is it's handling message calling across process boundaries 02:59.740 --> 03:06.220 as transparently as if these were just simply classes with, with, uh, with methods calling each other 03:06.260 --> 03:09.860 directly in Python code, that abstraction is what it's doing. 03:09.900 --> 03:16.060 And when you think about a future when potentially there could be, uh, millions or maybe even Billions 03:16.060 --> 03:19.140 of agents interacting all over the place. 03:19.260 --> 03:22.820 What Microsoft is doing is putting their stake in the ground for this. 03:22.860 --> 03:24.820 This is a sort of playpen. 03:24.980 --> 03:29.380 This is a world where agents can live and interact. 03:29.580 --> 03:36.180 You just put your agent code within this wrapper, this agent wrapper, you make your versions of message, 03:36.420 --> 03:39.660 uh, the that that you declare the way that we have. 03:39.820 --> 03:44.580 And then your agents can interact with each other, no matter where they are in the world, and no matter 03:44.620 --> 03:46.900 what programming language they're written in. 03:46.940 --> 03:50.180 And with that, that brings us to the end of day four. 03:50.220 --> 03:52.300 It means we're getting on to day five. 03:52.460 --> 03:57.900 And in the spirit of the other things we've done this week, the project is going to be some something 03:57.900 --> 03:59.980 that's more a sort of an idea. 03:59.980 --> 04:04.140 It's more something to tease out some thinking, to give you some some insights. 04:04.140 --> 04:10.220 It's not as much of a kind of commercial banger, perhaps, as the prior week, which is really great, 04:10.220 --> 04:12.700 but I think it will intrigue you in new ways. 04:12.820 --> 04:17.540 And a lot of what we've been doing with Autogen is about stretching what you think might be possible, 04:17.540 --> 04:19.900 and that will be the plan for tomorrow. 04:20.060 --> 04:21.740 And I can't wait to show it to you.