Pick a reading list you can finish this weekend
A good first Codex project solves one small problem. Try a personal reading list: paste an article address, add a title, and mark it as read. Keep everything in your browser instead of building accounts, a server, and a database.
Codex is an AI coding assistant that can help inspect a project, write code, and run development commands when its environment and permissions allow. Think of it as a collaborator that needs a clear brief, not a machine that automatically knows what you want.
Your finish line is simple: a working page you can use yourself. Sharing it publicly can wait until the core behavior works.
Write the brief before opening Codex
Create an empty project folder and write down the smallest useful version. A short brief gives Codex boundaries and gives you something concrete to check later.
- Purpose: Save articles to read later.
- Core actions: Add an address and title, mark an item as read, and delete an item.
- Storage: Keep the list in this browser using local storage.
- Not this weekend: Accounts, syncing, recommendations, payments, and browser extensions.
- Done means: Items remain after refreshing, empty titles are rejected, and the page works on a narrow screen.
Local storage is convenient for a prototype, but it is not a backup. Clearing browser data can erase the list, and another device will not automatically see it.
Give Codex a workspace and clear boundaries
Install Codex using its current official instructions, then open it in your project folder. If you already know a framework, use it. Otherwise, ask for a plain HTML, CSS, and JavaScript version with minimal setup.
Start with this prompt: “Build a personal reading list with the requirements below. First propose the files and explain how I will run it locally. Do not install dependencies or edit files until I approve the plan.” Paste your brief underneath.
Read the proposed plan before approving it. Ask what unfamiliar commands do, especially commands that install software, delete files, or access services. Keep API keys and personal files outside the workspace, and do not paste secrets into prompts.
Choose an API route without confusing it with the app
Your reading list does not need an AI feature. The model access is for Codex while you build, not for visitors using the finished page.
If you want a pay-as-you-go relay for your development tools, SwiftRelay works with Codex and OpenAI-compatible SDKs. Sign up for SwiftRelay to try it with the small gift credit provided to new accounts.
Follow the current Codex provider configuration instructions rather than guessing setting names. SwiftRelay’s API host is https://api.fastapirelay.com; OpenAI-compatible SDKs use https://api.fastapirelay.com/v1. Check whether the particular Codex provider field expects a host or a full base URL.
SwiftRelay bills per token. Longer prompts, larger file context, and repeated attempts can increase spending, so check usage as you work and ask Codex to focus on the relevant files.
Build one behavior and inspect each change
Ask Codex to implement adding and displaying items first. Run the page using its instructions and try it yourself. Then add persistence, read status, and deletion in separate steps.
After each step, ask: “Explain what changed, list the files you edited, and tell me how to verify this behavior.” Review the changes rather than accepting a successful-looking screen as proof. If you use Git, save a commit after each working milestone so you have a recovery point.
Finish with a refresh test and a clean stopping point
Add two articles, refresh the page, mark one as read, and delete the other. Try an empty title, an invalid address, and a narrow window. Report specific failures to Codex, including what you expected and what actually happened.
Finally, ask for a short README covering startup instructions, storage limitations, and unfinished work. Keep new ideas on a separate list. A finished weekend project is one useful loop that works, with enough notes to restart confidently next weekend.