ChatGPT Codex

“We put a lot of effort into making sure the agent, like, understand this hierarchy of instructions, right? You can put them in sub-directories, and it'll understand which ones take precedence over which others.”

“Good architecture is like even more important than ever. And like, I guess the fun thing is like for now, that's something that humans are really good at. So like, you know, kind of good, you know, important for the software engineers to do their job.”

“As long as you see humans and AI writing it, like maybe there's a world where it's only AI's maintaining a code base and the assumptions change, but the moment you start to break that fourth wall and a human's coming in, doing code review, deploying the code, …”

“For agents, I don't think you have really had to tell code style. It looks at your code base and just writes code that's consistent to that. Whereas like a human's not going to take its time sorry, their time to go through the code base and you know, follow al…”

“Our hard call is an hour right now, although don't hold us to that. It may change over time.”

“The way we see people who, like, love Codex the most using it is they don't, they think for, like, maybe 30 seconds max about their prompt. It's just like, oh, I have this idea, like, boom. Oh, like, there's this thing I wanna do, like, boom. Oh, like, I just …”

“Once the agent starts running, right what we actually do today, and we're hoping to like evolve on this, is we'll cut off internet access because we still don't fully understand what letting loose an agent in his own environment is going to do.”

“I think what we see as, like, the role of Codex here is to really push Frontier on that sort of single-shot autonomous software engineering.”

“Some of the items that are top of mind for me are, like, multimodal inputs. You know, we've talked, yeah, I know you find that, right? Yeah, like, another, another example would be, like, you know, just giving it a little bit more access to the world. You know…”