The Practice Room / Codex / Episode 5

Codex

Watch Codex build and illustrate a website

I gave Codex one sentence and asked it for a web page. It did not just write the page. It generated the photographs for it as well.

By MstimajPublished 10 November 2026Level TechnicalTool Codex

Sign in to save your place and mark this done. Free, no card.

The short answer

You can describe a web page in one ordinary sentence and have Codex build it, check its own work, and then make the photographs for it. Not stock photos. Photographs it generates, lit to match each other and the page they are going on.

The part worth watching is not that it writes the code. It is what it reaches for on its own.

Where this happens

This is Codex in the terminal, which on Windows means Command Prompt. Not the ChatGPT app and not the website. Same company, different door, and the door matters: this one can make files on your computer and the others cannot.

Keep your work in one place. Mine is a folder called Education Center, and inside it I made an empty folder for this. Open Command Prompt, walk into it with cd, type codex, and press enter. It opens in that folder and nowhere else, so everything it makes lands where you chose instead of scattering across your machine.

The prompt, and what is deliberately missing from it

The whole request is plain English: a one page site for a small bakery, a header, three things on the menu with prices, the opening hours, and a footer. Nothing about how it should look.

Notice what is not in there. No colours. No font. No layout instructions. That is the point, and it is the single most useful habit in this film.

Why describing the outcome beats dictating the steps

Describe the outcomea one page site for a bakeryit can match that against the skills it has, and reach for one
Dictate every stepuse cream, set the font, three columnsit does exactly what you said, and never reaches for the thing that would have done it better

It picks a skill by itself

Before writing anything it goes looking through its own skills, finds one called Sites, and says out loud that it is using it. Nobody pointed at it. The description of that skill matched the thing that was asked for.

Then it opens its own design notes and reads them: how to build a page that leads somewhere instead of stacking the same box five times down the screen. Every opinion in the finished page comes from there, not from the request.

Two files, and what each one is for

It writes index.html and style.css. Every website you have ever opened is made of these two, and keeping them apart is why you can change the whole look of a site without touching a single word of it.

  • index.html holds the words and the structure. This is a heading. This is a price. This is the footer.
  • style.css holds every decision about how that looks. The colours, the spacing, the type.

It checks its own homework

It counts the three menu items. It confirms the phone setting is in the page. It counts the opening and closing brackets in the stylesheet. If any of that had failed it would have stopped and said so.

That is smaller than it looks and it matters more than it looks. The usual complaint about these tools is that they hand you something broken with complete confidence. A check is the difference between being told it went well and being shown.

The bakery with no bread in it

The page comes back in cream, deep green and a rust accent, with a proper heading face and prices that line up. On a phone it stacks into one column with nothing hanging off the edge.

And something is missing before you can name it. It is a bakery with no bread in it.

So the second request is for the photographs, made with the image skill that came installed. Four of them, with one instruction that does most of the work: all four lit the same way, in the colours the page already uses. That is the difference between four pictures and a set of pictures. Four pulled from four places fight each other on a page no matter how good each one is, because the light is coming from four directions.

Then it wires them in itself and writes a real description for every one, so somebody using a screen reader hears what is in the photograph. Most people building a page skip that entirely.

Do it yourself

  • Make an empty folder somewhere you can find again.
  • Open Command Prompt, cd into it, and type codex.
  • Describe one page you actually want, in plain English. Say what is on it, not how it should look.
  • Stop and read what it says it is doing, especially which skill it reached for.
  • When it finishes, open the folder and double click the page. It opens in your browser like any other website.
  • Then ask for the one thing that is missing, rather than starting again.

Check yourself

You asked for a page and it started doing something else. Can you stop it?

Yes. Press the Escape key on your keyboard, top left, and it stops. Then say in plain English what you actually wanted and it picks up from there rather than starting the whole job again. Knowing you can interrupt is what makes it safe to ask for something ambitious.

It said it used a skill. Did you install that?

No. Codex comes with skills already in it, and it matched one against the description of your request. You never typed its name. That is also why a vague, outcome-shaped request often produces better work than a detailed, step-shaped one.

The page is finished. Is it a website now?

No, and this is the honest part. It is a file on your computer. You can open it, change it, or throw it away. Putting it somewhere other people can reach is a separate step with its own decisions.

What to carry forward

Describe the outcome, not the steps. Let it reach for its own skills and watch what it reaches for. Read the checks. And when something is missing, say that one thing instead of starting from nothing. The bakery was never the point.

Words used here

Go deeper

What she says in the film

I gave Codex one sentence and asked it for a web page. It did not just write the page. It generated the photographs for it as well.

Before anything happens, where we are. This is Codex in the terminal, which on Windows means Command Prompt. Not the ChatGPT app, and not the website.

And let me be accurate about the difference, because it is not that one makes files and the others do not. The desktop app can make files too, when you are on the Work side. What changes here is reach. Codex opens inside the folder you point it at, and it has to ask you before it touches anything outside that folder.

So the first thing is a folder. This is just your file manager, the same window you open every day. I keep my work in one place, a folder called Education Center, and inside it I have made an empty folder for the bakery and nothing else.

Then you open Command Prompt, you walk into that folder with cd, and you type codex, and you press enter.

And Codex opens, inside that folder. The arrow near the bottom is where everything you type goes, and the blue line underneath tells you which model you are on and which folder you are in.

Now the prompt. Mine is ordinary English, and I want you to notice how plain it is. A one page site for a small bakery. A header, three things on the menu with prices, the hours, and a footer. That is the whole thing, and I have not told it anything about how it should look.

[thinking] Notice what is in there. The pieces I want, and the fact that it is one page. Notice what is not in there. I have not said what colours to use. I have not said what font. I have not told it how to lay anything out. I described the outcome and left the craft alone, and that is deliberate.

One thing to know before you send it. You are allowed to interrupt. If it starts doing something you did not want, you press the Escape key on your keyboard, the one at the top left, and it stops. Then you say in plain English what you actually wanted, and it picks up from there rather than starting the whole job again.

It goes looking through its own skills, finds one called Sites, and announces that it is using it.

That is the thing we talked about this week. A skill is a set of instructions the tool reaches for when the job matches. Nobody pointed at it. I never typed the word. The description of that skill matched what I asked for, and it picked it up by itself.

Which tells you something useful about how to ask. If you describe the outcome you want, it can match that against what it has. If you micromanage every step, it does what you said and never reaches for the thing that would have done it better.

[amused] Then it does something I did not expect the first time. Before writing a single line, it opens its own design notes and reads them. How to build a page that leads somewhere, instead of stacking the same box five times down the screen.

Then it writes the two files. The page, and the stylesheet.

Two files, and it is worth knowing which is which, because every website you have ever opened is made of these. The page holds the words and the structure: this is a heading, this is a price, this is the footer. The stylesheet holds every decision about how that looks. Keeping them apart is why you can change the whole look of a site without touching a single word of it.

And then it checks its own homework. It counts the three menu items. It confirms the phone setting is in the page. It counts the opening and closing brackets in the stylesheet to make sure none are missing. If any of that had failed it would have stopped and told me.

[deadpan] That is small and it matters more than it looks. The usual complaint about these tools is that they hand you something broken with total confidence. A check is the tool saying what it promised and then proving on screen that it kept the promise, which is a very different thing from being told it went well.

[pleased] Here is what came back. Cream, deep green, a rust accent. A proper heading face. Room to breathe. Prices that line up down the column instead of wandering.

[amused] None of which I asked for. I said bakery. The skill it picked carried opinions about what a good page looks like, and those opinions are what you are seeing.

And on a phone it stacks. One column, nothing hanging off the edge, no sideways scrolling. That is not decoration. More than half the people who will ever open your page are holding it in one hand.

But something is missing, and you can feel it before you can name it. It is a bakery with no bread in it.

[sassy] A page about pastry with no pastry on it. Lovely typography, nothing to eat.

So I go back and ask for the pictures, and this is where the words matter. I am not asking it to go and find photographs. I am asking it to generate them, with the image skill that came installed in it.

And that is the honest use for this. It is a prototype. When you are building a mock-up of a page, generated images let you see the thing finished before you have booked a photographer or bought a single stock photo.

Four of them. The inside of the shop in the morning light. The sourdough. The croissant. The bun. And I ask for one thing that does most of the work: all four lit the same way, in the colours the page already uses.

[pleased] And they do match. Same window, same warm light, same wooden counter behind every one of them.

That is the difference between pictures and a set of pictures. Four images pulled from four different places will fight each other on the page no matter how good each one is, because the light is coming from four directions. Asking for them together is what makes them look like one afternoon in one shop.

Then it wires them in itself. Into the header, above each item, and it writes a real description for every single one.

Those descriptions matter. Somebody using a screen reader hears that sentence instead of seeing the photograph, and a search engine reads it too. Most people building a page skip them entirely. It wrote them without being asked, because the skill it picked said to.

[pleased] And that is a finished prototype. Written, checked, illustrated and laid out, from one sentence and one follow up.

So here is the pattern underneath all of it, because the bakery is not the point. You describe the outcome, not the steps. You let it reach for its own skills and you watch what it reaches for. You read what it tells you it is doing, including the checks. And when something is missing you say the one thing that is missing, instead of starting again from nothing.

And here is the part people are never shown. Open that folder again. There they are. Index dot html, the stylesheet, and the four images, sitting in a folder on your computer like any other files. Double click the page and it opens in your browser.

Which brings me to the honest note. A page sitting in a folder on your own machine is not a website yet. It is a file. Putting it somewhere other people can reach is its own step, with its own decisions, and that is the next film.

If you want to try it today, you do not need the bakery. Make an empty folder, open it in Command Prompt, and describe one page you actually want in plain English. Then stop and look at what it reaches for on its own. That is the part worth watching.

Subscribe.

[no_permission] No permission required.

Next walkthroughThe two ways into Codex, and neither is hard
On your machineWant this set up on your own computer, with your own files?

Book a session and we do it together on a call.

Book an hour

Ask what did not make sense

Comments go through our own form and are read before they appear. Links are not allowed; describe it in words.

Comments are read before they appear.

The newsletter

Get the next walkthrough.

One email when something goes up. The argument, the film and the term, nothing else. One click to leave.

Have a question now? Ask Mstimaj, she knows the archive.