In this panel‑style discussion, Speaker A introduces OpenAI’s latest Codex release, which adds a new “Sites” capability and role‑specific plugins that let users generate full‑stack interactive prototypes and share them via URLs. The conversation frames this as a shift from the traditional software development lifecycle (SDLC) to an “AI development lifecycle” (AI DLC) where rapid learning and shipping are paramount for AI‑native companies. By turning design concepts directly into working code with built‑in analytics, Codex enables non‑technical team members—designers, product managers, functional staff—to prototype, test, and iterate without a local server or separate tooling. The speakers compare Codex Sites to existing “vibe‑coding” platforms such as Lovable and Base44, noting that Base44’s opinionated, out‑of‑the‑box database and API integration is closer to Codex’s approach, while Lovable requires more manual wiring. They argue that Codex’s integrated, production‑grade pipeline will undercut these niche tools, forcing them to pivot. Overall, the discussion highlights the strategic business implications of Codex Sites: faster market discovery, a new on‑ramp for AI‑pilled employees, and a potential consolidation of the low‑code prototyping market under OpenAI’s platform.
Chapters
OpenAI just turned Codex into an OS for office workers with Sites and other updates and plugins in this latest release. 5 million weekly users are ready in less than 10 days, and here's what happened and what matters for AI builders, engineers, and engineering leaders whose non-technical colleagues are about to get a huge upgrade in their ability to create prototypes, sites with agents. OpenAI building apps has never been easier. So with Sites, Codex can turn your work, ideas, and plans into an interactive website or app your team can explore, use, and share with URL. So basically trying to go eat Lovable and Base44 and all the vibe coding application layer companies' lunch money. Rolling out to business and enterprise plans before expanding more broadly. Codex for every role, tool, and workflow. New role-specific plugins, sites, and annotations help teams do more with Codex. Jonathan, first takes on Sites.
Yeah, I thought it was an exciting feature. I haven't used it yet. I'd say it reminded me a bit of Anthropic's, uh, Artifacts when you use Claude. It feels a little bit more robust at the same time. One thing, you know, we talked about this product from, uh, Shopify called Qwik, which was an internal tool for sharing prototypes. And we've been doing like a lot of HTML generation. You know, then you have to like share the file and like use an internal server to like view the file. And so not having to use localhost server. Just by itself is a nice feature. So I can see that being useful. And I was curious if when you see this, do you think like, is Base64 obsolete? Um, you know, are these vibe coding tools for building sites like, uh, still going to be useful or you just do all that within Codex now?
Yeah, let me answer that from the broader perspective of the new AI development lifecycle. Instead of software development lifecycle, we're seeing AI builders move towards AI development lifecycle or AI DLC, which we've had some engagements on, uh, different clients. So how do you build faster. So taking a step back, why do we even build software? Software is an asset we create for the company to increase enterprise value and capture market share and reliably make money, cash flow, right? Like that's the whole point. So why do we ship a PR? Ideally, it's to increase our capability set or protect the asset we have to build a moat, to either capture more market share or protect the market share that we have. I think why sites matters is in the bigger play of I am trying to be an AI-native company where my new lifecycle is I learn as fast as I execute to capture market share. Which I think is the real goal of any AI-native company. Sites just brings the prototyping aspect, all that context. If you think about it, right, a designer could now go to Codex and they make a site with it and they could share the link to a user and there's some analytics built in. Now you could do a jobs to be done or Teresa Torres style opportunity solution tree style, you know, sort of interview, continuous discovery habits sort of interview, and then pointedly point to that prototype and get people to walk through it. You could do the mom test, right? Like, and all the analytics are there. That context is right there. When you go to engineering. And within Codex, you can just do all these things. And their latest model is so good at looking at a design and then taking that and shipping working code. I think their play is to kill Base44 and Lovable because those have remained as really quick and easy applications. But all the stories say once these scale to any level of production, they're going to have to like rebuild the whole thing, right? So it's been a faster way to learn from market what to build and even build an initial application you might monetize with these vibecoding tools. Base44 Base44, I would say I even prefer over Lovable, just like quick pro tip for the AI builders. The reason why is because they integrate database, API, all the contracts, like that stuff, all that stuff is out of the box versus Lovable, you got to integrate with like Supabase and stuff. So inherently you have a dependency chain, Base44 you don't. Codex, I think, is taking the Base44 path, which is an opinionated take that this is the way to like go from the initial discovery or like create some prototypes or sites or whatever to get an idea and then figure out what to productionize with Codex all the way to production-level engineering standards and quality. I think they also tangentially, like at the intersection of that for more functional colleagues, this is like an opening for more functional colleagues to come in and feel like a magic moment right away, similar to like a Lovable or a Base44, right? And once they have that magic moment, like what we're seeing in industry is product managers who are more functional from their careers come in, they have a Claude Code magic moment, they realize they could start shipping as well, which is what every tech company and executive wants. You want your people to like start getting AI-pilled, I think this is like an on-ramp to being AI-pilled. And then also going back to my original point and thesis, I think they're trying to make it to where everybody is using Codex for their AI DLC or AI native development lifecycle, moving from SDLC to learn as fast as you ship to capture market share and protect that market share. Those are some of my thoughts though. So yes, in short, killing Base44, killing Lovable. I see that happening with this move. I think those teams are going to have to pivot. That's my take. What do you think, Jonathan?
I tend to agree with you on the big picture, but I also wonder, is like OpenAI and Codex going to continue to support this specific functionality and keep it good? And like, when we come back a year from now, will this be something that was built once and shipped and they moved the engineers to another project? Or will this be something that like really, you know, takes on all the incremental feature requests that users will need to make it something powerful and part of their daily workflows? It's not clear, but Codex is releasing a bunch of features into the product and they're all worth playing with now. So it's good to see.
