AI Engineer World's Fair 2026

I Turned Coding Agents Into a Strategy Game — Ido Salomon, AgentCraft

Read the talk

I Turned Coding Agents Into a Strategy Game

AgentCraft borrows the controls of strategy games to make agent work visible, move attention to blocked tasks, and share supervision. Its next experiment asks how much of that machinery a new user should need to see.

From a talk by Ido Salomon

At a glance

Ideas worth remembering

  • Multiple agents create a human coordination problem: each adds steering, direction, and review demands.

  • AgentCraft combines status, spatial file activity, heat maps, and an attention shortcut so users can understand work and intervene.

  • Quests and orchestrators reduce planning and supervision work; the review kit makes their completed changes easier to inspect and compare.

  • Shared rooms let specialists follow up on each other’s work while continuing in parallel, with activity updates connecting people and agents.

  • The experimental Loopers concept reduces required file-level detail, but accessibility depends on the person; customization remains part of the exploration.

An army of agents still needs someone to direct it

Coding agents can produce anything from cat memes to B2B SaaS applications. Why, then, doesn’t everyone have an army of them? Ido Salomon, creator of AgentCraft, starts with the gap between an agent’s capability and a person’s ability to use many agents at once. The imagined setup is easy: get enough monitors, start 25 agents, and let them work. The actual work begins after they start.

Source frame: An army of agents still needs someone to direct it
Source frame: An army of agents still needs someone to direct it

Each agent needs steering, direction, and review. Adding agents adds demands on the same person’s attention, until supervision becomes exhausting. Salomon’s diagnosis is that the human becomes the bottleneck. More work can run concurrently than one person can comfortably understand and guide.

Strategy games offer a familiar way to handle this problem. In Warcraft, or even The Sims, multiple units act while the player watches, intervenes, and decides what should happen next. AgentCraft takes that experience into work: a game-inspired orchestrator that represents agents spatially and gives their supervisor controls for understanding and directing them. The useful skill being borrowed is managing several active units without inspecting every action continuously.

0:210:24
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

0:21 · section reference included

Turn agent activity into a map you can act on

An AgentCraft unit represents an actual agent. The application can detect agents already running on the device or start new ones. Selecting a unit opens a side panel where the user can prompt it, including by voice. Buildings represent other work functions: managing plugins and skills, opening an integrated terminal, and using Git. The game vocabulary organizes ordinary tools into one space.

Source frame: Turn agent activity into a map you can act on
Source frame: Turn agent activity into a map you can act on

Visibility has several distinct jobs:

  • Agent status: The side panel shows each agent’s task, its last action, and what it is doing now. That gives the user a quick way to decide who needs attention.
  • Location of work: The file system can be projected onto the map. Files appear as runes, and agent activity is associated with the directories or files being worked on. Inspecting a file reveals what an agent did and when.
  • Activity overview: Those associations support heat maps, letting the user see where work is happening across the project.

A map helps only if the user can respond to what it reveals. AgentCraft borrows another game control: pressing the space bar jumps to the next nearby item needing attention. The supervisor can move between questions and plan approvals rather than repeatedly searching through every agent. Status tells the user what is happening; the shortcut turns that information into an intervention.

2:412:51
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

2:41 · section reference included

Quests start work; autonomy moves the burden to review

Seeing everything does not mean being able to hold everything in your head. Following agents at the level of files and tool calls remains tiring, and a large project creates another demand: deciding what to do next. AgentCraft lets an agent inspect the codebase and suggest tasks. Those tasks become quests that the user can accept with a button, after which an agent does the work.

Source frame: Quests start work; autonomy moves the burden to review
Source frame: Quests start work; autonomy moves the burden to review

Task suggestions relieve the user of inventing every next step, but accepting 20 quests can still leave 20 jobs to babysit. The next layer delegates coordination itself. A user supplies a general goal; an orchestrator breaks it down and runs the work. In the demonstrated setup, execution happens in a local container, which Salomon describes as keeping the work isolated while the agent handles supervision.

Loops extend that delegation to ongoing sources of work. The examples are scanning Twitter for things to build or scanning GitHub, then creating features in the background. This reduces how much the user must specify up front. It also creates a downstream problem: even five completed changes arriving together can be difficult to review.

The review kit packages the result for that decision. It offers the changes and changed files for file-by-file inspection, alongside images or videos showing what changed. It also supports comparing implementations produced by several parallel instances and choosing the preferred result. Visual evidence makes the visible consequence easier to inspect; the file view remains available for examining the underlying changes.

Where does human attention go as more work becomes autonomous? The flow below shows two ways work enters execution: a general goal decomposed by an orchestrator, and background loops that find work. Both eventually produce changes for review. Delegating execution reduces continuous supervision, while making the presentation of completed work more important.

How it fits togetherFrom delegated work to a review decision

The user describes what they want.

Orchestrators and loops reduce ongoing direction, but their results still converge on a review step.

5:345:41
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

5:34 · section reference included

Let design and implementation continue together

Visibility and autonomy still leave one person responsible for the results. That person may also be the wrong reviewer for part of the work. AgentCraft’s next step is collaboration: locally hosted shared rooms, with tunnels allowing other people to join.

Source frame: Let design and implementation continue together
Source frame: Let design and implementation continue together

The concrete example is a product designer joining the room—in this case, Salomon’s wife. After he approves her entry, she works on a design. Her work becomes visible on his map, so he can follow up on the design and implement it while she continues working. The observable change is from one person supervising alone to two people advancing different parts of the same project concurrently.

The shared workspace supports handing off or forking work. Git remains usable, while coordination also happens inside the room. Chat connects people and agents, and a notice board records what each participant is doing. In the design example, the engineer can announce that he has taken on the design task, giving the others information about the follow-up rather than leaving them to infer it from changes.

How can implementation begin without making the designer stop? The diagram follows the example’s two paths: the designer continues designing while the engineer follows up on the visible work. The room’s activity information helps participants coordinate those paths. Access also extends to mobile devices and Telegram, so participation need not stay tied to the map on a desktop.

How it fits togetherA design becomes work the engineer can follow up on

Entry is approved, then design work begins.

Visibility enables a handoff while the designer continues; room updates tell others what work has been taken on.

8:118:13
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

8:11 · section reference included

A simpler game for people who do not want file-level controls

The combination of visibility, autonomy, and collaboration raises the ceiling for power users. The more surprising feedback concerns people who had not used agents before: parents reporting that their children enjoyed orchestrating agents, and a former StarCraft player finding a productive use for familiar skills. These are Salomon’s reported anecdotes; his estimate that roughly 90% of people need a lower entry point is an approximation, rather than a measured adoption result.

Source frame: A simpler game for people who do not want file-level controls
Source frame: A simpler game for people who do not want file-level controls

That feedback leads to a different interface experiment, tentatively called Loopers. Warcraft-style complexity can itself be daunting, especially for someone uninterested in which files an agent is editing. The proposed experience moves toward the level of a mobile game: projects users return to, autonomous loops that keep work going, and a basic interaction of prompting and receiving a result.

The tradeoff is how much execution detail the interface asks the user to manage. AgentCraft brings file activity forward; the simpler concept lets users focus on results and inspect the process when they want to. It relies more heavily on agents acting autonomously, while trying to make the experience inviting enough that people return to their projects.

A game interface will not feel easy to everyone. Something inviting to one person can be difficult for another. Salomon therefore treats this as an early experiment in customization: finding what a particular person needs to understand the tools and want to use them. Loopers is a very early draft, and its tentative name reflects that unfinished product direction.

10:3310:36
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

10:33 · section reference included

Choose the level of supervision you want

The closing invitation separates the two products’ stages. AgentCraft is already available to use. The simpler concept remains experimental, with Salomon seeking interest and feedback about the level of accessibility or capability people want. The next design decision depends on what users need to see, control, and return to—not on assuming that one game metaphor suits everyone.

The practical invitation is to take familiar skills from elsewhere in life and apply them to agent work. Strategy games supply one such vocabulary: watch units, notice what needs attention, delegate work, and coordinate with others. AgentCraft turns those actions into controls for coding agents; the simpler experiment asks which controls a person needs before the experience becomes useful rather than exhausting.

13:4613:49
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

13:24 · section reference included

Read the complete timestamped transcript
  1. 0:21

    Okay. Hi everyone. Uh I'm Solomon. I am

  2. 0:24

    the creator of ATMCraft and I also

  3. 0:26

    created MCPUI which became MCP apps and

  4. 0:29

    MCP steering committee. I've done a

  5. 0:31

    bunch of other stuff. Uh but we're here

  6. 0:33

    to talk about why we're the bottleneck

  7. 0:36

    and why we don't have to be.

  8. 0:40

    So, uh as you all know and use every

  9. 0:43

    day, agents are amazing. There's so much

  10. 0:45

    they can do uh from generating cat memes

  11. 0:48

    to B2B SAS apps. So if they are so

  12. 0:52

    amazing, we have to ask why aren't we

  13. 0:54

    all unstoppable? Why doesn't everyone

  14. 0:56

    have an army of agents that just does

  15. 0:59

    whatever they want? So it should be

  16. 1:01

    relatively easy. I mean you just have a

  17. 1:04

    bunch of monitors and you spin up 25

  18. 1:06

    cloud code agents and you're done. So

  19. 1:09

    the reality is that it's just not that

  20. 1:12

    simple to do something like that. you

  21. 1:14

    need to a really want to use agents and

  22. 1:18

    secondly once you actually spin them up

  23. 1:21

    each one of these agents requires you to

  24. 1:23

    steer them direct them review them and

  25. 1:26

    when it's at scale especially it's just

  26. 1:28

    exhausting we need to find the skills to

  27. 1:31

    allow us to do it without burning out so

  28. 1:34

    in reality we are the bottleneck

  29. 1:38

    and the the cool thing here is that

  30. 1:41

    while we are the bottleneck

  31. 1:43

    The skills that we need to do these

  32. 1:45

    things to uh find ourselves not burning

  33. 1:48

    out every time we use an agent are with

  34. 1:51

    us all along. Uh if you try to compare

  35. 1:55

    it to other stuff that you've been doing

  36. 1:57

    outside of programming, for example,

  37. 2:00

    playing video games, it's not really

  38. 2:01

    that different. Like if if you're

  39. 2:03

    playing Warcraft, for example, or Sims,

  40. 2:05

    and you have a bunch of different uh

  41. 2:07

    units running around, you need to

  42. 2:09

    understand what they're doing and

  43. 2:10

    supervise all of it. How different is

  44. 2:12

    that from from actually inspecting

  45. 2:14

    agents? So I took this concept uh too

  46. 2:18

    far and I created agent uh which is a

  47. 2:22

    game inspired orchestrator uh that tries

  48. 2:25

    to bring all that good stuff together

  49. 2:28

    into work.

  50. 2:30

    So let's take uh a quick look of what

  51. 2:32

    that actually looks like and try and

  52. 2:34

    understand the journey that we can go

  53. 2:36

    through to really raise the ceiling of

  54. 2:38

    how humans and agents can collaborate.

  55. 2:41

    So, uh, this is AgentCraft. Uh, there's

  56. 2:44

    really a lot to unpack here. Uh, so

  57. 2:46

    we'll just go through the basics really

  58. 2:48

    quick. Um, what you see here is an

  59. 2:51

    agent. Uh, it's an actual representation

  60. 2:55

    of a cloud code or openclaw, whatever

  61. 2:57

    agent that you can imagine. Uh, it can

  62. 3:00

    be detected on your device or you can

  63. 3:02

    actually spawn new ones directly from a

  64. 3:05

    craft. Uh, so like I said, you have like

  65. 3:08

    codecs and uh, open code etc.

  66. 3:12

    at your command.

  67. 3:13

    >> Uh, and these agents can do everything.

  68. 3:16

    They're just normal agents. Uh, so I can

  69. 3:18

    just prompt them in this nice side panel

  70. 3:20

    that also has voice. So there's

  71. 3:23

    multimodality here. Uh, and just do

  72. 3:26

    something for me.

  73. 3:27

    >> Prompt. Prompt.

  74. 3:29

    >> And now these agents can do whatever.

  75. 3:33

    Uh, and if you look around you would see

  76. 3:35

    that the map has a a bunch of different

  77. 3:37

    elements. So you have buildings. These

  78. 3:38

    buildings represent functionalities. So

  79. 3:40

    for example, if you can manage your

  80. 3:42

    plugins or skills, uh you have like

  81. 3:44

    integrated terminal, integrated git, uh

  82. 3:47

    you can do in your all of your work from

  83. 3:50

    within this space.

  84. 3:52

    So now that we have this and we

  85. 3:54

    understand the basics, let's look at

  86. 3:56

    what we can do uh to raise the ceiling.

  87. 3:59

    So the first step is obviously

  88. 4:00

    visibility. I need to understand what's

  89. 4:02

    going on. What are my agents doing? So,

  90. 4:05

    I have this nice side panel and it shows

  91. 4:07

    me the different agents and what their

  92. 4:09

    task is and what the last thing they did

  93. 4:10

    is and what they're currently doing.

  94. 4:12

    Everything I need to quickly understand

  95. 4:14

    who needs my attention and who doesn't.

  96. 4:17

    The second part of it is we're not just

  97. 4:20

    limited to this. We have a map. So, I

  98. 4:22

    can take let's say my file system,

  99. 4:25

    project it onto the map, and now I can

  100. 4:27

    see exactly what my agents are doing.

  101. 4:30

    Not just by looking at a list of stuff.

  102. 4:32

    I can actually see okay this agent is

  103. 4:34

    now working on this directory or this

  104. 4:36

    file and these files are represented as

  105. 4:38

    runes on the map. So I can really look

  106. 4:41

    at each one and see exactly what each

  107. 4:43

    agent did and when. And now I can take

  108. 4:46

    this nice information because we are the

  109. 4:49

    orchestrator uh and use that to create

  110. 4:52

    linkages and now I can create cool stuff

  111. 4:54

    like heat maps. So I can really easily

  112. 4:57

    see what's going on. And the the other

  113. 5:02

    aspect is that now that we have this

  114. 5:04

    visibility, that's not really enough. We

  115. 5:06

    need to be able to react to what's going

  116. 5:08

    on. If someone needs my attention, I

  117. 5:10

    need to be able to quickly jump to it.

  118. 5:12

    So much like video games or RTS games or

  119. 5:16

    Civilization, whatever, you would click

  120. 5:18

    uh spacebar and it would just take you

  121. 5:20

    to the nearest thing that actually

  122. 5:21

    needed your attention. So you can really

  123. 5:23

    easily understand what's going on. and

  124. 5:26

    jump from one thing to the other and

  125. 5:28

    answer questions or approve plans, etc.

  126. 5:34

    That was nice. I mean, it's a nice step

  127. 5:36

    just to have that visibility, but it's

  128. 5:38

    not really enough. It's pretty

  129. 5:41

    exhausting to keep looking at what the

  130. 5:43

    agents are doing in the granularity of

  131. 5:46

    what files are they using and what tools

  132. 5:47

    are they using at the moment. So, we

  133. 5:49

    need something else. Uh and the reason

  134. 5:52

    is that we have like two two main

  135. 5:54

    problems here. Uh one is that there's

  136. 5:56

    just too much to hold in our heads. Even

  137. 5:58

    if I can understand what's going on and

  138. 6:00

    I can see everything, I can't really do

  139. 6:02

    like 20 things at the same time. I can't

  140. 6:04

    even think of the next thing I want to

  141. 6:06

    do if I have this, you know, huge coding

  142. 6:08

    project or whatever. So I need to find

  143. 6:11

    some way to fix that. Uh so we can I

  144. 6:13

    mean we can tell the agents uh you know

  145. 6:16

    go through my codebase, find out what

  146. 6:18

    the next things I need to do are, create

  147. 6:20

    these tasks for me and I just click a

  148. 6:21

    button, I accept the quest and there's

  149. 6:24

    some agent that does it for me which is

  150. 6:26

    fun. Uh it's cool. Uh but the next

  151. 6:30

    problem here is that okay now I have 20

  152. 6:32

    stuff going at the same time and I have

  153. 6:33

    to babysit each and every one and that

  154. 6:36

    is completely exhausting. So you could

  155. 6:39

    ask okay we have agents agents are

  156. 6:41

    amazing as we've established so I can

  157. 6:45

    just go ahead and tell the agent to do

  158. 6:47

    it for me now it's called software

  159. 6:49

    factories but at the time it was just

  160. 6:51

    doing stuff autonomously uh so you can

  161. 6:53

    give it like a general sense of what you

  162. 6:55

    want it would spawn an orchestrator and

  163. 6:58

    break it down for you and run it all in

  164. 7:00

    well in this case it's a local uh

  165. 7:03

    container so everything is just done in

  166. 7:05

    isolation and I don't need to do any

  167. 7:07

    babysitting the agent does it for me. On

  168. 7:10

    top of that, you have loops, which

  169. 7:12

    everyone really likes right now. So, you

  170. 7:14

    can do cool things like just tell it to,

  171. 7:16

    I don't know, scan Twitter for cool

  172. 7:18

    stuff you want to build or scan your

  173. 7:20

    GitHub, and it will just create these

  174. 7:22

    nice uh features for you in the

  175. 7:24

    background without you needing to do too

  176. 7:26

    much up front.

  177. 7:29

    The bad thing is that I mean this is

  178. 7:32

    nice uh but what do I do when I have

  179. 7:35

    again I don't know I would say 20 but

  180. 7:37

    even five things to review at the same

  181. 7:40

    time. Uh it's very very hard to get that

  182. 7:43

    out of the way. So what I did is create

  183. 7:47

    uh this like review kit. So I get the

  184. 7:49

    entire changes I need and I get uh what

  185. 7:52

    files changed if you want to go like

  186. 7:54

    file by file or you can get just get

  187. 7:56

    visual evidence. So you can actually see

  188. 7:58

    videos of what changed or photos of what

  189. 8:00

    changed so you can really quickly

  190. 8:02

    understand what you want or even run a

  191. 8:04

    few uh instances in parallel and just

  192. 8:07

    pick the best implementation out of

  193. 8:09

    these.

  194. 8:11

    So now that we have this we have uh

  195. 8:13

    visibility and we have autonomy uh it's

  196. 8:16

    pretty cool like we reached a pretty

  197. 8:17

    good place in raising the ceiling of

  198. 8:20

    what we can do with agents but it's

  199. 8:23

    still pretty exhausting. I mean it's it

  200. 8:25

    was fun. Uh, but now I have to ask

  201. 8:27

    myself, do I really need to be the only

  202. 8:30

    one doing this? It's pretty lonely to

  203. 8:32

    just talk to agents all day and trying

  204. 8:34

    to and you know, if you look at uh what

  205. 8:37

    a team does, for example, if it's just

  206. 8:39

    me, that's fine. But if I have a team, I

  207. 8:42

    might not even be the right person to

  208. 8:44

    review what's going on. So, I need

  209. 8:46

    something else. Uh, and that something

  210. 8:48

    is collaboration. We can just have other

  211. 8:52

    people join us. So the way that looks in

  212. 8:56

    agent craft is that I can create these

  213. 8:59

    uh you can call it you know war halls

  214. 9:01

    war room whatever uh host them it's like

  215. 9:04

    completely local but you can do like

  216. 9:06

    tunnels and people can join you h so I

  217. 9:09

    can create a room and let's say I have a

  218. 9:11

    product designer in my team in this case

  219. 9:13

    uh it's my wife and I can approve uh her

  220. 9:16

    otherwise she'll be mad uh so I can

  221. 9:18

    approve her and she does her thing she

  222. 9:21

    designs whatever and I as an engineer

  223. 9:24

    can not only see that that's that's her

  224. 9:28

    um I can not only see that on my map uh

  225. 9:31

    I can actually take that and follow off

  226. 9:34

    off of it

  227. 9:35

    >> prompt prompt

  228. 9:36

    >> yeah that's just like her um so I can

  229. 9:41

    take that design follow up on it

  230. 9:44

    implement it while she keeps working uh

  231. 9:46

    and the cool thing here is that not only

  232. 9:48

    can I hand off or fork and kind of have

  233. 9:50

    this shared workspace so I'm not really

  234. 9:52

    bound anymore or to Git. I can use Git,

  235. 9:54

    but I'm not really bound to something.

  236. 9:56

    Everyone is working together. Uh you can

  237. 9:58

    see that there's also some kind of chat

  238. 10:00

    between not only between the people

  239. 10:03

    within the room, but also between

  240. 10:05

    agents. So we can have this really nice

  241. 10:08

    notice board of exactly what each person

  242. 10:10

    is doing, what each agent doing. They're

  243. 10:11

    all aware of each other and they can

  244. 10:13

    collaborate much more closely uh than

  245. 10:15

    you normally would be able to do. Uh so

  246. 10:17

    for example, here I can say, okay, I

  247. 10:19

    took off this design task.

  248. 10:22

    Uh so now we have oh by the way this is

  249. 10:26

    also from devices you can have like

  250. 10:28

    mobile and and if you like telegram you

  251. 10:30

    can use telegram whatever floats your

  252. 10:33

    boat. So we have visibility and we have

  253. 10:36

    autonomy and we have collaboration so we

  254. 10:38

    managed to raise the ceiling. Uh it's

  255. 10:40

    now possible especially if you're power

  256. 10:43

    users to do really cool stuff and use

  257. 10:45

    more agents and do more things. But the

  258. 10:48

    interesting thing here was, you know, if

  259. 10:50

    I looked at the feedback I got, it's not

  260. 10:53

    just that power users were able to do

  261. 10:55

    more. The cooler thing for me was that

  262. 10:57

    people that had even nothing to do with

  263. 10:59

    agents or nothing to do with

  264. 11:00

    productivity, uh, come and say, uh,

  265. 11:03

    okay, my kids really loved it and they

  266. 11:06

    use it all the time to to orchestrate

  267. 11:08

    agents, which they didn't do until now.

  268. 11:10

    uh or you know someone that flunked out

  269. 11:13

    of college because he played Starcraft

  270. 11:15

    and now you can suddenly do really

  271. 11:16

    productive stuff with it. Uh and a bunch

  272. 11:19

    of other examples of kind of bringing

  273. 11:21

    communities that so far were kind of

  274. 11:23

    behind into this new world of

  275. 11:25

    productivity.

  276. 11:27

    So we need to raise the ceiling but we

  277. 11:30

    also need to uh lower the floor. We need

  278. 11:34

    to have some kind of way to take no

  279. 11:37

    probably around 90% of the people in the

  280. 11:39

    world and bring them into this hygienic

  281. 11:41

    future without having them burn out.

  282. 11:45

    So again, I took it too far. Um, and

  283. 11:48

    there's this uh currently named TBD um

  284. 11:53

    potentially loopers. Uh the idea here is

  285. 11:55

    okay why don't why do we need something

  286. 11:57

    like you know Warcraft which is

  287. 11:59

    potentially very complicated uh

  288. 12:01

    especially or might be even daunting if

  289. 12:03

    you're not into the granularity of what

  290. 12:05

    files are there are or how uh complex

  291. 12:07

    the UI is and kind of try to find a

  292. 12:10

    lower denominator of what makes stuff

  293. 12:12

    accessible especially now that agents

  294. 12:15

    are much more capable so instead of

  295. 12:17

    granularity or having like exactly what

  296. 12:20

    files they're working on maybe I can

  297. 12:22

    have it more of a mobile game level uh

  298. 12:25

    have projects that they keep returning

  299. 12:27

    to and use loops and other stuff that

  300. 12:31

    rely on agents being more autonomous to

  301. 12:33

    have like a very basic level of I prompt

  302. 12:36

    I get the result I don't really care

  303. 12:38

    perhaps about the way I can see it if I

  304. 12:40

    want to and I have this really nice

  305. 12:42

    interactive and cool experience that

  306. 12:44

    makes me want to come back to this and

  307. 12:47

    obviously I mean this is one

  308. 12:49

    visualization uh it can really resonate

  309. 12:53

    with some people but might not might not

  310. 12:55

    present to others because we're not all

  311. 12:57

    the same and what may appear like

  312. 13:00

    amazing and easy to one person can

  313. 13:01

    appear very difficult to another. Uh but

  314. 13:05

    here uh I'm trying to look at a way to

  315. 13:08

    make this more customizable. Try and

  316. 13:10

    understand what it is that you as a

  317. 13:12

    person need in order to understand and

  318. 13:15

    want to use these tools. So this is a

  319. 13:19

    very very early draft. Um but if you

  320. 13:22

    want to use it, please let me know. So

  321. 13:24

    we're the bottleneck. I think we've

  322. 13:26

    established that uh pretty well until

  323. 13:28

    now. But the skills that we need to stop

  324. 13:30

    being the bottleneck and enable this new

  325. 13:32

    future are already with us. So we are

  326. 13:35

    the bottleneck, but we don't have to be.

  327. 13:39

    And I hope that you all can take what's

  328. 13:42

    relevant to you and your life and apply

  329. 13:44

    it forward.

  330. 13:46

    So I would ask you for two things. One,

  331. 13:49

    agent is already out there. Like you can

  332. 13:50

    just npx install agent as a website uh

  333. 13:54

    and do your thing. Uh this new thing

  334. 13:56

    that I just showed you uh potentially

  335. 13:59

    loopers uh is still experimental. I'm

  336. 14:02

    still trying to understand the interest

  337. 14:05

    and what people are actually looking for

  338. 14:07

    to uh get the floor that they want or

  339. 14:09

    the ceiling that they want. So, please

  340. 14:12

    uh go here and express your interest and

  341. 14:14

    tell me what you're looking for so I can

  342. 14:16

    know what to do with this. And thank

  343. 14:19

    you.

  344. 14:33

    I got it.