Videos am_oeAoUhew
Harness Engineering: How to Build Software When Humans Steer, Agents Execute — Ryan Lopopolo, OpenAI
Scene timeline
110 shot(s).
keyframes kept every frame deduplicated
What was stored
- cues
- 412
- whisperx 412
- chunks
- 81
- from 412 cues
- keyframes
- 83
- kept of 110 captured
- frames with text
- 83
- 962 lines read
- chapters
- 0
- from the source metadata
- keyframe bytes
- 12.2 MB
- word timings on 412 cues
Provenance
| stage | state | model | started | took |
|---|---|---|---|---|
fetch |
done | — | 2026-08-10 00:47 | 1m 34s |
stt |
done | — | 2026-08-10 00:49 | 48s |
chunk |
done | — | 2026-08-10 00:49 | 0s |
text_embed |
done | — | 2026-08-10 19:44 | 1s |
keyframe |
done | — | 2026-08-10 00:49 | 2m 26s |
ocr |
done | — | 2026-08-10 00:52 | 22s |
frame_embed |
done | — | 2026-08-10 19:44 | 14s |
Frames, and what the machine read
-
- PRESENTING SPONSOR0.98
- Google DeepMind1.00
-
- PLATINUMSPONSORS1.00
- # Braintrust0.96
- WorkOS OpenAI0.96
-
- AlEngineer0.97
- OpenAl0.94
- AlEngineer0.96
- EUROPE1.00
- EUROPE1.00
-
- RYAN1.00
- LOPOPOLO1.00
- MENBER OF TECHICE STAF0.87
- OpenAl0.92
-
- RYAN1.00
- AIE0.98
- LOPOPOLO1.00
- MEMBER OF TECHNICAL STAFF1.00
- AIE0.99
-
- RYAN1.00
- AELOPOLO0.94
- AIE0.99
- LOPOPOLO1.00
- MEMBER OF TECHNICAL STAFF1.00
- Or0.81
- AIE1.00
- AlEngineer0.96
- Google DepMind0.98
-
- MEMBER1.00
- TECHNICAL STAFF1.00
- enAl0.97
-
- EUROPE1.00
- therai1.00
- AlEngineer0.98
- Al0.79
- EUROPE1.00
- neer1.00
- Braintrust1.00
- AlEngineer0.97
- le DeepMind0.96
- AlEngineer0.98
- EUROPE1.00
- EUROPE1.00
- ize1.00
- AlEngineer0.98
- Micros1.00
- gineer1.00
- neo4j0.99
- All0.88
- EUROPE1.00
- ROPE1.00
- neer1.00
- Trigger.dev1.00
- AlEngineer0.96
- VorkOS0.95
- AlEngineer0.99
- EUROPE1.00
- EUROPE1.00
- lodal1.00
- AlEngir0.98
- tailscale1.00
- AlEngineer0.98
- Sonar1.00
- All0.90
- EUROPE1.00
- EUROPE0.99
-
- EUROPE1.00
- OpenAl0.95
- Harness Engineering:1.00
- ineer1.00
- qle DeepMin0.96
- OPE0.99
- How to Build1.00
- cro0.96
- ngineer1.00
- Software When1.00
- EUROPE0.97
- Humans Steer and0.99
- gineer1.00
- WorkOS1.00
- OPE1.00
- Agents Execute0.97
- Iscale0.99
- IEngineer0.97
- EUROP0.95
- Ryan Lopopolo1.00
- Member of Technical Staff1.00
- AlEngineer0.98
- INEERING: HOW TO BUILD SOFTWARE WHEN H0.98
- EUROPE1.00
- Google DeepMind1.00
- PRESENTED BY1.00
- RYAN LOPOPOLO / Member of Technical Staff0.99
- OpenAl0.96
-
- EUROPE1.00
- The way we build1.00
- eer1.00
- DeepMind1.00
- software has1.00
- osol0.94
- gi..eer0.85
- changed.1.00
- ROPE1.00
- eer1.00
- orkOS0.98
- cale1.00
- Engineer1.00
- EUROPE1.00
- OpenAl0.97
- Confidential and proprietary.1.00
- AlEngineer0.99
- S EXECUTE0.98
- HARNESS ENGINEERING: HOW T0.97
- EUROPE1.00
- PRESENTED BY1.00
- OpenAl0.94
- Google DeepMind1.00
- RYAN LOPOPOLO / Member of Technical Staff0.98
-
- gether.ai0.98
- The way we build1.00
- gineer1.00
- UROPE1.00
- software has1.00
- changed.1.00
- ENTI0.99
- osoft0.87
- ngineer0.99
- UROPE1.00
- NCORD1.00
- OpenAl0.97
- Confidential and proprietary.1.00
- AlEngineer0.98
- RE WHEN HUMANS STEER AND AGENTS EXECU0.99
- EUROPE1.00
- PRESENTED BY1.00
- OpenAl0.95
- Google DeepMind1.00
- RYAN LOPOPOLO / Member of Technical Staff0.98
-
- EUROPE1.00
- The way we build1.00
- Go0.95
- neepMind0.94
- software has1.00
- t0.99
- changed.1.00
- Eny0.96
- ·EURO0.90
- OpenAl0.93
- Confidential and proprietary.1.00
- AlEngineer0.98
- W TO BUILD SOFTWARE WHEN HUMANS STEER0.98
- EUROPE1.00
- PRESENTED BY0.99
- OpenAl0.94
- Google DeepMind1.00
- RYAN LOPOPOLO / Member of Technical Staff0.98
-
- EUROPE1.00
- orkOS0.96
- The models are0.97
- Code is free.0.99
- Your role is to1.00
- good enough.1.00
- unblock your1.00
- PE1.00
- team.1.00
- trust1.00
- ale1.00
- neer0.99
- OpenAl0.90
- Confidential and proprietary.1.00
- AlEngineer0.98
- WARE WHEN HUMANS STEER AND AGENTS EXI1.00
- EUROPE1.00
- PRESENTED BY1.00
- OpenAl0.97
- Google DeepMind1.00
- RYAN LOPOPOLO / Member of Technical Staff0.98
-
- EUROPE1.00
- -kOS0.88
- The models are0.99
- Code is free.0.99
- Your role is to1.00
- el0.53
- good enough.1.00
- unblock your1.00
- team.1.00
- ust1.00
- e1.00
- ngi0.94
- EURO1.00
- OpenAl0.94
- Confidential and proprietary.0.99
- AlEngineer0.99
- ND AGENTS EXECUTE1.00
- HARNESS ENGINEERI1.00
- EUROPE1.00
- PRESENTED BY1.00
- OpenAl0.94
- Google DeepMind1.00
- RYAN LOPOPOLO / Member of Technical Staff0.99
-
- AEngineer0.98
- Braintru1.00
- EUROPE1.00
- OpenAl0.89
- AlEngineer0.96
- EUROPE1.00
- The models are0.97
- Code is free.0.98
- Your role is to0.99
- good enough.1.00
- unblock your1.00
- AlEngin0.93
- orki0.85
- team.1.00
- EUROPE1.00
- SEN1.00
- AlEngineer0.98
- EUROPE1.00
- Sond0.90
- AlEngineer0.98
- EUROPE1.00
- OpenAl0.97
- Confidential and proprietary.1.00
- 31.00
- AlEngineer0.99
- AGENTS EXECUTE1.00
- HARNESS ENGINEERING1.00
- EUROPE1.00
- PRESENTED BY1.00
- Google DeepMind1.00
- # Braintrust0.93
- WorkOS1.00
- OpenAl0.94
-
- Braintrust1.00
- AI0.90
- The models are1.00
- Code is free.0.99
- Your role is to1.00
- good enough.1.00
- unblock your1.00
- team.1.00
- eer1.00
- TRY1.00
- ineer1.00
- Sonar1.00
- OpenAl0.96
- Confidential and proprietary.0.99
- R AND AGENTS EXECUTE0.99
- HARNESS ENGINE0.97
- # Braintrust0.95
- WorkOS1.00
- OpenAl0.94
-
- EUROPE0.99
- intrust0.92
- Human time.1.00
- Human and1.00
- Model context1.00
- eer1.00
- model attention.0.97
- window.1.00
- soft1.00
- 10.82
- En1.00
- =EUR0.87
- OpenAl0.93
- Confidential and proprietary.1.00
- Engineering the future of Al0.99
- AlEngineer0.98
-
- EUROPE0.99
- -intrust0.98
- Human time.1.00
- Human and1.00
- Model context0.99
- model attention.1.00
- window.1.00
- osoft1.00
- 10.71
- VE.0.61
- eer0.99
- EL0.97
- OpenAl0.94
- Confidential and proprietary.1.00
- AlEngineer0.98
- OFTWARE WHEN HUMANS STEER AND AGENTS1.00
- EUROPE1.00
- PRESENTED BY1.00
- OpenAl0.97
- Google DeepMind1.00
- RYAN LOPOPOLO / Member of Technical Staff0.98
-
- EUROPE0.96
- er1.00
- Praintrust0.96
- Human time.1.00
- Human and1.00
- Model context0.99
- Engineer1.00
- model attention.1.00
- window.1.00
- EUROPE1.00
- icrosoft1.00
- er1.00
- dal1.00
- gineer1.00
- IOPE0.93
- OpenAl0.90
- Confidential and proprietary.1.00
- AlEngineer0.99
- WARE WHEN HUMANS STEER AND AGENTS EXE1.00
- EUROPE1.00
- Google DeepMind1.00
- PRESENTED BY1.00
- RYAN LOPOPOLO / Member of Technical Staff0.98
- OpenAl0.96
-
- AlEngineer0.99
- Google De0.97
- EUROPE0.93
- AlEngin0.96
- EUROPE0.99
- Human time.1.00
- Human and0.99
- Model context0.99
- model attention.1.00
- window.1.00
- ze0.72
- AlEngin0.98
- EUROPE1.00
- :neo0.85
- AIEn0.87
- E0.64
- OpenAl0.98
- Confidential and proprietary.1.00
- AlEngineer0.99
- RE WHEN HUMANS STEER AND AGENTS EXECUT1.00
- EUROPE1.00
- PRESENTED BY1.00
- OpenAl0.93
- Google DeepMind0.99
- RYAN LOPOPOLO / Member of Technical Staff0.99
-
- engineer0.99
- GoogleDeepMi1.00
- EUROPE1.00
- gether-0.90
- AIEngineer0.83
- BOPE0.86
- Human time.1.00
- Human and0.99
- Model context0.99
- model attention.1.00
- window.1.00
- ed1.00
- Engin1.00
- EUROPE0.93
- ariz1.00
- EUROPE1.00
- neo4j0.96
- Engineer1.00
- EUROPE0.99
- OpenAl0.93
- Confidential and proprietary.0.99
- AlEngineer0.98
- OW TO BUILD SOFTWARE WHEN HUMANS STE0.99
- EUROPE1.00
- PRESENTED BY1.00
- OpenAl0.96
- Google DeepMind1.00
- RYAN LOPOPOLO / Member of Technical Staff0.98
-
- engineer0.95
- Google DeepMi0.97
- EUROPE1.00
- geterai0.80
- ineer1.00
- Human time.1.00
- Human and1.00
- Model context0.99
- model attention.1.00
- window.1.00
- Engine1.00
- EUROPE0.98
- arize1.00
- Engineer1.00
- EUROPE1.00
- OpenAl0.94
- Confidential and proprietary.1.00
- AlEngineer0.98
- ENGINEERING: HOW TO BUILD SOFTWARE WHE1.00
- EUROPE1.00
- PRESENTED BY1.00
- OpenAl0.95
- Google DeepMind1.00
- RYAN LOPOPOLO / Member of Technical Staff0.99
-
- Google DeepMind0.99
- AlEngineer0.99
- EUROPE1.00
- Human time.1.00
- Human and1.00
- Model context1.00
- model attention.0.99
- window.1.00
- Zed0.99
- AlEngineer0.98
- EUROPE1.00
- :neo4j0.89
- OpenAl0.96
- Confidential and proprietary.1.00
- AlEngineer0.99
- D SOFTWARE WHEN HUMANS STEER AND AGEN0.98
- EUROPE1.00
- PRESENTED BY1.00
- OpenAl0.97
- Google DeepMind1.00
- RYAN LOPOPOLO / Member of Technical Staff0.98
Transcript
412 cues· 7,692 words· 41,579 chars
- 0:15 speaker is here to speak about harness engineering, how to build software when humans steer and agents execute.
- 0:24 Please join me in welcoming to the stage, member of technical staff at OpenAI, Ryan Lepopolo.
- 0:40 Good morning, London.
- 0:46 I'm super excited to be here today.
- 0:47 I'm Ryan Lopopolo, and for the last nine months, I had the privilege of building software exclusively with agents.
- 0:56 I am a token billionaire, and I believe that in order for us to get into our AGI future, we want everybody to be token billionaires, to use the models to do the full job.
- 1:08 And what that means is
- 1:12 to lean into the idea that the models are capable of being a full software engineer.
- 1:17 And I've lived that experience by banning my team from even touching their editors to have to work through the models in order to get the job done.
- 1:25 And today I'm going to talk to you a little bit about what it means to lean into that and operationalize the way you work, the code spaces you live in, and the processes on your teams in order to get the agents to do the full job.
- 1:40 I believe I'm preaching to the choir here when I say that the way we build software has changed.
- 1:45 In the last six months, we have seen coding agents take over the world and capability has continually advanced at a super fast pace to have these models and the harnesses within which they live take more complex actions, do more complicated work with higher reliability over longer time horizons.
- 2:06 And the place we've gotten to here is that implementation is no longer the scarce resource of what it means to do the job of software engineering.
- 2:15 Code is free.
- 2:16 We have an abundance of code to solve the problems that we come across in our day to day as we run our teams, build software, and solve user problems.
- 2:27 Hiring the hands on the keyboards as part of our teams is only constrained by GPU capacity and token budgets.
- 2:35 And each engineer today in this room has access to five, 50, or 5,000 engineers worth of capacity 24-7 every day of the year.
- 2:47 The only thing that needs to happen, our roles, is to figure out how to productively deploy these resources into our code and into our teams to make use of this new capacity.
- 2:59 In this world, skill sets are shifting more towards systems thinking, system design, and delegation in order to make use of this abundant capacity to produce code to solve problems.
- 3:12 And there are three reasons that this happened, all of which happened in late 2025.
- 3:19 For me, the magic moment was GPT 5.2, which, when it came out, was able to do the full job of a software engineer.
- 3:26 The models at this point are good enough where they're isomorphic to you and I in terms of the ability to produce code at high quality that solve real user problems in real code bases.
- 3:39 Code is free, and I know this is maybe a scary thing to hear because code carries maintenance burden, but it's free to produce, free to refactor, and it is not a thing to get hung up on anymore.
- 3:54 We think of code as burden because it's a synchronous attention drain on the human engineers on our team.
- 4:01 But the models are incredibly patient.
- 4:04 They are infinitely parallel.
- 4:05 So the ability to produce, maintain, refactor, and delete code is no longer a forcing function on figuring out how to allocate resources on your engineering teams.
- 4:16 So sort of be AGI pilled here is to believe that the models are capable of producing every line of code we could ever possibly need, figuring out when to delete them, figuring out when to refactor them or make them more reliable.
- 4:30 And it's your role as software engineers to figure out how to unblock your team of agents and humans driving those agents from being able to drive them over long horizon work to do the full job.
- 4:44 The idea here is that every one of you is a staff engineer.
- 4:48 You have as many team members as you can possibly drive concurrently and have tokens to support.
- 4:55 And you need to look one day, one week, six months into the future to figure out what structures you need to put in place to productively harness this infinite capacity to produce code.
- 5:10 The scarce resources in this world that we see today are three things, human time, human and model attention, and model context window.
- 5:22 And in the world where human time and attention is scarce, the role is to think about where that time is going, figure out ways to productively automate it, and move that synchronous human time into higher leverage activities.
- 5:40 In a world where human time is scarce and human time is required to produce code, we have a stack rank.
- 5:48 Things are either P0s or P2s.
- 5:50 Those P3s will never get done.
- 5:53 However, in a world where code is free and infinitely abundant, all those P3s get kicked off immediately, maybe 4x in parallel.
- 6:02 We pick one that solves the problem, and in it goes.
- 6:07 I've had the privilege of building a ton of agents internally at OpenAI to improve the productivity of my coworkers.
- 6:15 When code is free, all these internal tools can have good localization and internationalization from day one.
- 6:23 I can make tools that my colleagues in London, Dublin, Paris, Brussels, Zurich, and Munich are able to experience in their native languages without really having to trade against any of my other team's capacity in order to make high quality tools.
- 6:40 We should be working with the assumption that the best parts of software engineering that we all know, live, and breathe are available in any product that we could ever build all the time.
- 6:52 Humans no longer need to concern themselves with implementation.
- 6:56 The important thing is not the code, but the prompt and the guardrails that got you there.
- 7:01 This is why leaving breadcrumbs, documentation, ADRs, persona-oriented documentation around what a good job looks like, all the historical logs of tickets and code reviews, this is the process that got you and your teams to the code and products that you have today.
- 7:17 And this is what needs to happen in order to get your agents there as well.
- 7:23 Your job is to build systems, software, and structures that enable your team to be successful.
- 7:29 And to do that, we need to make them legible to those agents that are driving the implementation.
- 7:36 That means structuring them in a way that's native to the agents,
loading