I saw that Codex launched Sites. And when I first saw the news, I was like, is this just a worse version of Replit or Lovable that's just inside Codex?
But the more I dug into it, the more I realized it's actually worth understanding
how to use it and how to get the most out of it. So
today is a full tutorial
on basically what the big announcement is around Codex Sites, how does it compare to the competition.
We're actually gonna go and live build using codec sites. And through that, I'm actually gonna teach you, uh, basically the best practices for using codec sites. So by the end of this episode, if you stick around,
uh, I'm gonna teach you how to build a how to build a shell using Codex Sites, how to add memory using Codex Sites, how to add what's called safe actions using Codex Sites,
and I'll explain what that means in in the episode. How to create skills with codec sites, how to save gate
using codec sites, and how to prove the loop using codec sites with which makes it,
uh, work autonomously.
Let's get into it.
So what is the difference between
Codec sites
and Replit and Lovable and and stuff like that? So
I will say, Replit and Lovable and and and those and those products are really good if you wanna like one prompt something and it has an editor, it has a database, it has server, it has hosting. A lot of them have connections to domains
as well too. Like, can just
register
a domain within it. Um, so that's really amazing.
Um, but Codex Sites, if you live in Codex,
and I'm starting to live in Codex. I mean, I think it was about a month ago I had Riley Brown on the podcast, and I I basically said, like, hey, convince me to use Codex. I'm in the Anthropic ecosystem.
Convince me to use Codex.
And now I will say it's a part of my daily driver. Yes. I still live in the Anthropic ecosystem, but I'm also using Codex.
And,
um, I think that if you are in Codex and you are putting just all your context there, what's really cool about Codex Sites
is,
uh, you can actually use that to go and build your ideas,
your apps, and stuff like that. And what's the coolest part about Codec Sites is it updates
your, uh, your app autonomously.
So what does that mean?
It means that, uh, you can have it, uh, basically
create a personal website, say, and, uh, you know,
and let's say, for example, go to my personal website.
Um, this is a static
this is a static website.
So I actually have to go in and and basically, you know, a 100 a 158,000
people enjoy reading my newsletter,
but, like, when it becomes a 160,000,
I have to go and update it. But with Codec Sites, you can actually have it so it automatically updates these things. It automatically creates,
for example, guides based on my content. It automatically,
you know, adds to different companies I work on. So it basically is this whole idea around autonomous
product building. I've talked about this on the podcast before,
but the idea around
you're going to have,
uh, in the future, and and the future is now the present, basically agents going and updating products autonomously.
But the thing is, it is missing auth. It's missing databases.
It's missing payments. It's missing email
sending. It's missing analytics,
and it's missing a vault for secrets. So a lot you know, if you want something more simple, everything is in there. You're gonna wanna use something like Rapid or Lovable.
But if you understand a little bit about auth, if you understand a little bit about database, payments, stuff like that,
and you live in the Codex ecosystem,
and you are really interested in this whole idea around autonomous apps,
Codex sites are really, really, really cool. And I also say one thing. Today,
you can't
publish these websites,
at least not to my knowledge, you can't publish these websites
on your own domain and go and deploy it publicly.
These are internal apps that you can share with your team right now. But obviously, that's gonna change very, very, very, very, very soon. So let's get right into it. So I I was thinking that we can create
a startup ideas OS. So basically, live board with columns,
inbox, researching, validating, building, and killed startup ideas.
And each card can have an idea, buyer, pain
proof,
next step, and score. So this is something that, you know, could be an internal internal tool that I would use. And we're gonna basically try to build it in six prompts. And like I said, as I build it, I'm gonna share,
uh,
sort of the big takeaway. So
the first, uh, first thing we're gonna do, let's go open
Codecs.
So I, uh, created a new project here.
I opened a, uh, a new chat
and,
you know, the first thing is, you know, if you wanna actually use sites, you have to
invoke it at sites. So it works basically as a plugin. So I said build a startup OS.
Um, I'm gonna go ahead and
send it.
Um, and,
yeah, it works as a plug in. You invoke it there.
And like I said, not everyone has access to it,
but I would imagine that access is probably coming really soon for for plus
plus people. And by the way, I have no affiliation with OpenAI.
I just think this is a really interesting product, and I wouldn't be making this episode if I didn't think that you can get a lot of value from it too.
So, um, what is the insight I have for you about this particular prompt
is that, you know, um, well, there's a few things.
Uh, Yeah. Invoke. The way to to to get it going is you wanna invoke sites.
You wanna actually ask it to use realistic sample data.
Um, you also wanna save it for review. So I noticed that, um, sometimes when I I prompt it an idea, it'll just try to deploy it. So a
really good tip is to save for review, do not deploy.
Um, and this basically unlocks
building a real product service, not a homepage. So, basically, I what I'm trying to do by building this is to build that whole idea around autonomously
being able to edit it and and work on it, um, because that's sort of sort of the dream state for me.
Um, so let's go ahead and go back to Codex.
Okay. While that is
being
worked on, I
just wanted to say that if you if you go to the plugin section over here, so you click plugins,
there's a bunch of plugins that are going to help you make your sites a lot better. Right? So,
um, you know, a lot of people aren't using these plugins,
um, but think about, like, Figma. Think about
Canva, think about HeyGen for avatar videos,
think about Remotion.
These are a
bunch of plug ins that could make your ideas for your sites a lot more interactive, a lot more a lot more interesting.
Uh, another really interesting one that's underrated, I think, is GameStudio.
So,
um, you know, one of the biggest problems that people have with vibe coding and agentic engineering is they build something and no one
no one's
no one's going to it. Well,
you know, if you build games, for example,
that actually generate buzz around what your the bigger you know, the the product you're building, that's a way to get attention, and then you bring those people into your core your core product. Now, of course, that needs to make sense for whatever it is you're building, and this works better with consumer apps. Right? So you go and create a,
you know, a paperboy competitor
that's fun to play, that you can kinda, like, news jack based on a particular
news topic, and then you bring those people
into,
you know, whatever your core experience is. Maybe it's an email newsletter or who knows. But the point is, like, I think a lot of people are sleeping on this idea that you can go and create little apps that could bring them into the core experience.
Alright. So it's built
the board.
I think it looks pretty pretty clean.
Got the inbox over here, researching,
validated,
building, kill. Definitely not the most beautiful, but clean,
minimalistic,
good enough for a first version.
So let's go back
and
keep going.
So how do we add memory? Right? Because on codec sites, it's it's not gonna add memory without us basically
getting it to to prompt it.
So let's go ahead and go back into codecs. I'm copying this prompt.
So I say, add persistent storage
so ideas save between visits stay saved between visits.
Before coding, show me the data model in which records action the app needs. And this is by the way, these prompts are similar prompts that you can use for when you're using Codec sites.
Um, so it says, I'll use the site's, uh, building guidance here because this is a hosted app with storage. Since you asked for the model first, I'm gonna inspect the existing schema and then layout the proposed records and mutations before touching code.
So it says it's actually gonna use Cloudflare.
Right? I'll use Cloudflare d one as the durable store with one main record type ideas. This already matches the project's current direction,
and OpenAI has d one DB data model.
So then it goes, and if you if you see here, it says the record the apps need. So it says it needs an idea, one one card on the board, it's thought it stores the full card content, the current column,
it store, uh, needs the owner email,
and then these are the actions
that the app needs. List ideas, add idea, update idea, move idea, scoring the idea, archive the idea, ensure ensure seated.
Um,
and then it says, I'll wait for your go ahead before coding the persistent
path pass.
So
this is the the whole idea of safe actions,
which are, you know
well, before I get into that, why add memory? Well, because we need for this to be a
productive piece of software, we needed to remember things. Right? So we wanna make sure that we've got that in there. But the whole idea around safe actions is is gonna be it's it's an unlock because we can be in other chats.
And because we live in Codex, we can basically say, hey, you know, maybe I'm, like, ping ponging with Codex, and then I it hits me back with a
an idea, startup idea, and I'm like, oh, this is really good. Let me just
let me just add add so let me just at add idea and it it'll directly add it to the application, which is so cool.
So, uh, you're gonna wanna create safe actions
because, you know, in order to get the most in in order to get the most out of it. So I'm just gonna go ahead and and copy that prompt, create safe actions for add idea, update idea.
And and the reason, you know, it's important to
that I, you know, I I I said show me the data model and which record and actions the app needs is, you might not know what safe actions to create, so you you might as well act ask Codex, and it'll give it to you right there.
So for people, nontechnical people especially like that, you might not know what your safe actions are, you just ask Codex what what they should be. So it says, I'll use the site's building workflow again since this is a worker d one service.
Um,
I'm gonna inspect the current action routing and tighten it into an explicit safe action boundary so the agent can only
call named mutations rather than the arbitrary SQL.
So you're starting to see that codex,
it does feel a little more technical than your your Lovable or your Replit or your Bolt.
But if you can stay with it,
the output, I think, is
super, super valuable. Like, the idea that you can have it self
self update, the the idea that you're in Codex and you can bring in all this stuff from Codex, the idea that you can go into the plug ins
and and just use all this stuff from the get go. Like,
these are some of the I mean,
FAL, AI and image generation, like, so much stuff. Hugging Face, these are all open source models, like, it's all built in from the get go.
It's pretty sweet.
So that's completed. So the next thing we're gonna wanna do is create a skill.
So we're gonna copy this here so that the chats, our future chats are gonna know how to use this app.
So create a codec skill called startup ideas admin.
It should explain how to read the board,
how to add ideas, how to move cards, how to score ideas, and include five example commands.
This is something that I think that is
you know, I I started seeing people use
codec sites, and they're not using Skills. And I'm like,
this is one of the greatest parts of of Codex Sites is the ability to create these skills. So you might as well might as well,
uh,
start adding some skills to get the most out of your application. So it says, I'll use the skill creator guidance for this since you're asking for a new codec skill.
I'm gonna read the skill instructions and create StartUp ID as admin in your local skill directories with the board action workflow and example commands.
The skill name is already valid, and the scope is clear. Operational guidance for this board,
and its safe actions.
So it's gone ahead and created the codec skill.
It's
done everything we've asked for, reading the board, adding ideas, updating cards, moving cards, scoring ideas, archiving ideas, five example
commands, and it says validation pass.
The skill is valid.
It's going to be helpful
for you to actually save gates. What do I mean by that? I mean, you know, the way I think about it is like a video game. Right? Like, you have, like, checkpoints as you go through a video game, and sometimes it'll auto save,
and you're you're happy it auto save. But the thing with Codex is it doesn't auto save.
Um, so it's helpful to go in there and just say, hey, just do a checkpoint here before a live URL.
So, uh, let's go ahead and go back into Codex,
and I'll say, save this as v one review. Do not deploy.
Confirm build status, storage choice, access setting, and the exact version I should review. And I'll include, by the way, all these prompts, I'll include in this show notes in the description for for people to download,
um, so that they can go ahead and and
and as they're building codec sites, they could
they can go and use some of this stuff. So it says, I'll use the site's hosting workflow for the save only review session. I'm gonna validate the current build, confirm the storage access config,
commit the latest safe action changes, and then save a site's version without deploying.
There you go. So prompt is done. It's saved for review. It isn't deployed. The build status is passed.
Um, the storage choice is still d one. The access setting is custom.
One thing to note here is at the top right, you can see, like, your whole environment here.
So you can see all the different changes you've made. You can see if you're working on locally or you're connected to Codec's web.
Here, I'm connected to the main branch.
And so, you know,
it's just all all up here on your top right.
The last prompt I wanna do is the whole proving the loop process. So what I'm gonna do is I'm gonna grab this prompt right here,
and I'm gonna say, in a new chat, important important that it's in a new chat, use startup ideas admin to add, here's the startup idea, AI agent SEO grader for local businesses,
put it in an inbox with a first pass score in the next step. And let's see if it actually can do that. Does it open up a new chat or do we actually have to go and open up a new chat? Let's see.
It says, I'll treat this as two pieces. Use the new startup ideas, admin skill instructions, and create a fresh chat thread to do the actual board update there. Yes. I'm loading the skill and finding the thread creation tool now. The skill says to only use
oh,
look, it's gone and opened.
It's gone and created the chat. I can open it right here.
So it says, I'm using the skill.
Um,
I'm gonna find out how the local app is meant to run. I'm gonna read the board. I'm gonna add the inbox card and the safe action and verify by reading again exactly what I wanted to do. The project is clean and looks like a Next style app with a worker and a verifiable script. I'm checking the API implementation now so I can call the same local service the app expects.
The app expo
exposes exactly the safe route the skill expects. Yeah. So this is doing exactly
what I want it to be doing,
and let's see if it works. Alright.
So the prompt is done. It says done using only the safe board API, which is what we wanted in the action layer. There's no raw SQL SQL, no generic database rights, and no deploy.
It's gone and did it. It went really, really fast.
So now I'm gonna say,
can you publish
now I'm gonna say, can you publish website and see what happens.
So it's gone ahead and, uh, deployed it. You'll notice that it's this crazy URL,
and that's a downside of Codec sites at the moment. I think this is gonna change. That's my prediction. It's gonna change
hopefully soon,
whether you're going to be able to have custom domains. But I can go and open it in Codex browser on the right here. It's got auth built in here.
I do have to sign up.
So let me go ahead and sign up.
So
as you can see, this is exactly what we wanted. We've got the inbox, the researching, the validated.
Um, if I make it bigger here, I can see more
the building, the killed.
And it's got everything I've asked for. Right? Um,
now, if I want a new idea, I can go and actually create a new idea or again, I can use a safe action to go and do it or I can have it run an automation,
like, every week to automatically
add to this board. So we've seen that you can actually do that. Um,
I can go more in-depth in a future video if people are interested in, like, how to do automations and cron jobs and stuff like that. But you can basically just,
you know, ask
Codec Sitesco and do that for you.
And I think what's really cool is that, like,
you know, if you listen to this channel, a lot of us are interested in creating
startups that,
you know, we don't need big teams to to manage. Right? And this whole what's so cool about this is we're getting to this with Codec Sites. We're getting to this if you can create agents that go and automatically update based on, you know, different, uh, criterias,
then and then and it were and these are products that work and are valuable to people, then,
um,
that's sort of sort of the dream. So this, you know, is it the most beautiful website on the planet? No. Does it work? Yes. Does it look decent? Yes. Could I get it to a point where it looks beautiful?
Um, I can.
And
and
that's
that's pretty cool.
So
to to to, like, t d TLDR it, like, are the main concepts to understand in
within Codec Sites is number one, you're gonna wanna
ask it to have memory. Right? You know, the app saves data, but without this,
it's just a demo. So you're gonna have to ask it to to save memory. You're gonna have to ask it to have a database.
A lot of people are starting to use Convex
with
with Codec sites, so it's something to look into.
I imagine
that over time,
it's just gonna be easier and easier to use Codec sites,
But now you do need to prompt it to do a lot of these things. The second thing is this concept called safe action. So this whole idea that you can have approved buttons,
um,
and and through that, you can have it
automate,
uh, adding,
removing,
editing your apps,
um, so that, you know, you are, as the human being, aren't doing everything, and you don't have to actually
edit
every, uh, every website or app you create.
You know? I
used to run a web design agency. It was one of my first jobs. And,
you know, one of the things I used to say was, a website is a living and breathing entity.
It isn't something that you hit publish and you can just, like,
walk away forever.
And,
you know, we're now in this era, 2026, where the agents are actually doing the the the
updating, the editing,
the
removing, and that's through things like safe actions.
And skills, like use skills with Codex. We saw how how it could be valuable in this in this episode, but a skill is basically this reusable instruction manual
so Codex knows how to operate the app later. So you're gonna need to create skills so you can use the safe action safe actions
and so that and obviously, you're gonna wanna store that in the memory so that it, you know, it it it does it safely
and and is giving the right information.
So
all this to say, the wow moment for me
is is building apps where I could do, like you know, in this example, I could open a new chat and say, add this idea to my startup ideas OS.
It shows it shows it in the live site updating. Right? So once it's published,
I could just be like,
do
this, and it's gonna add it. Or I can have an agent do it, and it's gonna add it. And it's gonna be all on
my live website, which is really cool.
Um, I think that a lot of people are gonna use Codex Sites to make, like, personal web pages,
to make, like, little apps and stuff like that.
But I actually think that the the real unlock here is to make products that Codex can keep operating for you. That is what's exciting me about Codex Sites is that it it
if we can create ideas and apps and websites that are automatically updated, automatically get better, are are autonomous,
I just find that so so interesting, and I think this is a trend that's only gonna get bigger, better. And it was interesting to see that Codec Sites
is is leading the charge.
So, yeah, this has been a inside look as to how to use Codec Sites, what I think is interesting about it, some best practices.
I hope it's been helpful. I'm just trying to share the most this the new tools that I think are are gonna make,
uh, increase.
I'm just trying to share the the new tools that are gonna increase the probability of success for you, whatever it is you're building,
and just share the best way to use these tools
and give you ideas along the way.
If this gave you an ounce of value, please
like, comment, and subscribe. I'll see you in the comment section. I read every single comment,
and
I'm I'm rooting for you. You know, whatever it is you're building, I'm rooting for you, and I can't wait to see what you build. I'll see you on the next one, and thank you for
joining
in the Startup Ideas podcast.