A canvas for what Codex builds.
midcode runs OpenAI’s Codex beside a live canvas of your site. You click an element, Codex gets its file and line, and every file it changes shows up on the canvas as a diff you can undo. It uses the Codex login already on your Mac, so there’s no second account and nothing extra to pay midcode for.
Free for 3 days, no card. Then one payment, yours for life.
- Status
- Available
- Account
- Your own Codex login
- Runs
- Chat, or the Codex CLI in a terminal
- Changes
- Diffs you can undo
01/What you can do
What midcode does with Codex.
Point instead of describing
Click an element and its file, line and surrounding components go into the prompt as a reference.
Its plan and its diffs
Codex’s plan, its tool calls and each file it writes are shown in the thread. Every change is one ⌘Z.
Model and effort in the prompt bar
The options Codex offers for the session are pickers in the chat, remembered for next time.
Comments become briefs
Review on the canvas, pin notes to elements, then hand Codex all of them at once.
Finish by hand
Spacing, copy and color are faster to change on the canvas than to prompt for.
Publish what you both did
Your edits and Codex’s are in the same list. Check the files, commit, push.
02/How it works
Three steps. No new workflow.
Step 1: Open your project
midcode starts Codex in your project folder, with the login it already has.
Step 2: Point and ask
Select, write, send. Permission requests show as cards in the thread.
Step 3: Review and publish
Every changed file is in Publish, whoever changed it.
03/FAQ
Codex questions. Short answers.
You need Codex set up on your Mac the way you already use it. midcode starts it with that login and never sees your credentials.
Yes. The chat lists every agent it finds on your Mac, and each one keeps its own model and mode.
04/Goes with
The rest of your stack.
Try midcode with Codex.
Download midcode, point it at your project folder and click something. Three days free, no card, nothing added to your code.