Coding for the Future Panel

[Music] Welcome to the future of AI coding panel. Thank you for reading the memo that you have to wear all black. Um uh okay so I I I do want to cover a little bit of introductions and I know each of you uh in in different ways. Uh but maybe the audience like fullfully doesn't quite uh matan why don't you go first? Uh uh what are you proudest of like what is facto's position to like the broader world on in AI coding? Yeah. So, uh, at Factory, our mission is to bring autonomy to software engineering.

Um, and what that means more concretely, we have built end-to-end software development agents called droids. They don't just focus on the coding itself, but really the entire end-to-end software development life cycle. So, things like documentation, testing, uh, review, kind of all the ugly parts. So, that you can also do the more fun parts like the coding itself. And for the parts of the coding you don't want to do, you can also have the droids do that. So we build droids. Build droids. Um and OpenAI uh obviously

needs no introduction, but uh you your your role on the Codex team. Uh I you know I saw I saw you pop up on the Codex video. That's how I that's how I knew it was you working on it. Uh but how do you think about Codex these days since it's expanded a lot? Yeah. So um earlier this year we launched our first coding agent um which I I worked on Codex CLI um bringing the power of our reasoning models into people's um computers. Um then we released Codex cloud where you could actually distribute and kind of delegate those tasks to work in the cloud and

over the last you know some odd months um we've been unifying these experiences so they work as seamlessly as possible. So a lot of our focus um is around how do we make the the fundamentals the primitives as useful as possible. We just released a dev day codeex SDK. So I think one of the key directions we've been seeing is not just using coding um or code executing agents for coding but also for general purpose tasks. And so whether it was CHBD agent which I worked on earlier this year that actually executes code in the background to accomplish some tasks but starting to enable our developers to build on top of

um not just the reasoning models but also things like sandboxing and all the other primitives that we built into codeex. Awesome. Um Vzero. Yeah. Um the goal of V0ero is to enable developers to do preview driven agentic programming. So today when you build web apps you probably have an agent open your IDE open so some kind of code and then a preview of what you're actually building. Usually you're running dev server with vzero our goal is to allow you to just have an agent running and directly prompt against your running

app. Uh and that's how we think the future of DX is going to is going to pan out. Okay. Awesome. Um and everyone has different like surface areas in which to access your coding agents. So I think one of the things that we kind of want to kick off with is how important is local versus cloud? Um you started local cloud, you started cloud went local. Your cloud only for now. Um what's the split? Is everyone just going to merge eventually? Yeah. So maybe uh maybe I can start there. So I think at the end of the day the point of these agents is that uh

they are as helpful as possible and they have a very similar silhouette to that of a human that you might work with. And you don't have local humans and remote humans that are like somehow, you know, this one only works in this environment, this one only works in that environment. Generally, humans can be helpful whether you're in a meeting with them and you come up with an idea or you're sitting like shoulder-to-shoulder at a computer. Um, so I guess asmtoically these need to become the same. But I think in the short term um remote is typically what

we're seeing is it typically more useful for smaller tasks that you're more confident that you can delegate reliably whereas local is when you want to be a little bit closer to the agent. Um it's maybe some larger task or some more complicated task that you're going to kind of actively be monitoring. Um, and you want it to be local so that if something goes wrong, you don't need to, you know, pull that branch back down and then start working on it, but instead you're right there to to guide it. Yeah. Yeah. Yeah. Maybe I'm just greedy, but I want