Get started
Pretend you have never heard the word "programming". Everything below is explained in plain language.
Chapter 1 — What Codex really is
Think of Codex as a coding intern that never sleeps. You describe what you want in plain language and it writes the program for you.
In the past, building a desktop tool meant hiring engineers and waiting weeks. Now you describe your idea and Codex scaffolds it in minutes.
This tutorial covers only one thing: Windows or macOS apps that double-click to open. No websites, no servers, no mobile.
Chapter 2 — What you need
A Windows PC or Mac
Windows 10/11 or a recent macOS version. 8 GB RAM minimum, 16 GB is nicer.
A ChatGPT account
Codex Desktop signs in with an OpenAI account. If you already use ChatGPT, the same login works.
The Codex Desktop installer
Download the desktop app for your operating system from OpenAI and install it. Feels like installing Chrome.
You really do not need to code
Typing, copy-paste, double-click — that is the full skill list.
Chapter 3 — Opening Codex for the first time
On first launch, Codex asks you to sign in. Use your OpenAI credentials.
You see a chat-like interface. Left: projects. Middle: conversation. Right: preview.
Do not panic. Just three actions matter: new project, type a prompt, wait for the result.
Chapter 4 — Core actions in plain English
New project = new conversation
One app per project. Do not mix multiple apps in one project.
Prompt = what you tell Codex
The clearer you are, the better. Do not say "build a reconciliation tool". Say what the input is, what the output is, how the UI should look.
Wait = let it work
Codex writes files as it thinks. You do not have to read them. You only care whether it runs.
Run = see your app
It launches a window for you. That is your program.
Bugs = keep chatting
If something looks wrong, just say: "the button should be red", "Excel import crashed". It will fix itself.
Chapter 5 — Five plain-language rules for good prompts
1. Say who will use it
Finance team, support, your boss — different users need different UIs.
2. Say what problem it solves
Do not just list features. Explain why each feature matters and what pain it removes.
3. Give examples
"I have an Excel with columns Order ID, Amount, Date. After import, group totals by month." Beats "build a stats feature" ten times over.
4. Change one thing at a time
Ask for a new button, then a color change, then a font change. Do not stack requests.
5. Do not panic on errors
Copy the full error text and paste it back. Codex reads error messages better than anyone.
Chapter 6 — Common pitfalls
Pitfall 1 — The app will not start
Copy the full error and ask: "How do I fix this?" No need to Google it.
Pitfall 2 — Things get messy after many tweaks
If five changes have not helped, open a fresh project and rewrite requirements cleanly.
Pitfall 3 — You are asking for too much at once
Start with a minimum viable version: import one sheet, display one column. Get that working first.
Pitfall 4 — You cannot tell what it is doing
Ask: "What are you doing right now?" It will happily explain.