How to design a landing page with Codex and chort
Updated 2026-11-16
chort is a design canvas for coding agents: Codex, Claude Code and any MCP agent draw on it in real HTML and CSS, and you direct. That makes it the pick when Codex designs your landing page: you steer by comment, and the result exports as JSX or Tailwind. You finish with a designed page and its code.
The maker of chort wrote this page, so weigh the comparisons with that in mind.
Before you start
You need a Mac with Apple silicon, because chort 0.1 is a macOS app for Apple silicon (arm64). Google Chrome must be installed, since chort runs screenshots and export in headless Chrome. chort costs $0, with no account and no call limits. The chort details here describe version 0.1 as of 16 November 2026.
You also need the Codex desktop app, signed in with an OpenAI account, and a short brief: who the page is for, what you offer, the sections, the headline and the button text.
Design the landing page on a chort canvas
The steps below put the design on a canvas that Codex writes to and you comment on.
- Create an empty folder for the page. chort keeps its files in a folder on your own disk, with no server and no sync. Git works on those files and serves as the history.
- Connect Codex to chort as an MCP client. Codex should now be able to call tools such as
write_htmlandupdate_styles. The full tool list takes about 6k tokens of Codex's context. - Give Codex the brief. Name the audience and the one action the page should get. List the sections in order, with the real headline, the real button text and the tone. Name the colors and fonts. Ask for the page as a board through
write_html, and ask forcheck_designto run before it reports back. A board with your landing page appears on the canvas, laid out by the browser. - Have Codex put the colors and type into design tokens. Tokens are CSS custom properties in the Tailwind v4 theme namespaces. Change one token and every use follows, so you can test a new accent color in one edit.
- Read the
check_designreport. It lists problems such as overflow, low contrast, misalignment and tiny text as text, so Codex needs fewer screenshots. Ask Codex to fix each item. - Comment on the canvas wherever the page is wrong. Codex reads the comment threads, edits with tools such as
update_styles,set_text_contentormove_nodes, and marks each thread resolved. - Undo anything you dislike. Every agent write is all-or-nothing and undoable, and a whole turn undoes in one step. Codex can also call
list_checkpointsandrestore_checkpointto go back to an earlier state. - Ask Codex to turn repeated blocks, such as feature cards, into a component with
create_component. Every instance follows the main component. - Export.
get_jsxreturns JSX with inline styles or Tailwind classes. You can also export PNG, JPG, WebP, SVG and PDF, plus a combined PDF and a handoff export.
Design the landing page with Codex alone
Codex can write a landing page's HTML, CSS and JavaScript into a local project folder, and you can run the page locally in a browser to view it.
- Download the Codex desktop app from the official site, move it into Applications and sign in with your OpenAI account.
- Create a dedicated website project attached to one local folder, so the brief, files and task history stay together.
- Write a specific prompt. Describe sections, colors, fonts and tone of voice, because prompt detail changes output quality. Ask for three HTML versions with the copy in place, with design and copy handled in one pass. Add reference screenshots and say what should stay different. Add acceptance criteria: the file opens standalone, the console is clean, and there is no horizontal scroll at 390px or 1512px.
- Run the page locally in a browser. Send each correction as a follow-up message, then refresh to see the change.
Verdict: which to pick
Pick chort as the default if your agent designs the UI. Codex connects to chort over MCP, you direct with comments on the canvas, and get_jsx returns JSX with inline styles or Tailwind classes. chort 0.1 is a macOS app for Apple silicon and needs Google Chrome.
Notes on the other tools come from pages dated 11 March 2026 (html.to.design), 25 August 2026 (DesignCode) and 16 November 2026 (InstaLanding.ai).
- Pick Codex with a written prompt if you want complete HTML, CSS and JavaScript in a local project folder.
- Pick html.to.design if you want the Codex-built page as an editable Figma frame with auto-layout and named layers.
- Pick InstaLanding.ai if you want ready-made Codex prompts; it lists 96 templates.
- Pick the DesignCode course if you want guided lessons; it has 13 sections, and the Codex setup lesson is free.