Read Codex Markdown files on Mac
Codex works on your code and often leaves traces in Markdown: a plan before it codes, a spec, decision notes, a tracking file in the project folder. Those .md files read poorly in a terminal or a raw preview. Marko opens them formatted on your Mac, so you can review and fix what the agent wrote.
Where Codex drops its files
Codex keeps its .md files among your project files, wherever your instructions ask for them: a plan, a spec, a tracking file. These are plain Markdown files. You open them like any .md, with File > Open, then switch to Visual mode to read the plan as a document.
Marko has no integration with Codex: no connection to the agent, no reading of the repository, no link to Git. You work on the file as it sits on disk. When Codex rewrites the file, reopen it in Marko to see the current version.
What to check in a plan
An agent plan commits the work that follows. Before you let Codex code, read it with a few questions in mind:
- Does the scope match what you asked, with no drift and no shortcut?
- Is the list of touched files complete, and is no sensitive file in there by mistake?
- Do the planned tests or checks cover the change?
- Do the agent’s assumptions hold, or is one of them wrong?
In Visual mode that structure becomes readable: you follow the reasoning, spot a missing step, check that a file table matches what you expected. Correct it as you read. Reword a vague step or add a constraint the agent forgot; the file stays Markdown that Codex reopens without surprises.
If you edit the plan while Codex is rewriting it, Marko catches the conflict on save: your version is not overwritten, and the other one is kept as a copy alongside. For the agent to read your corrections on its next pass, put them in the plan under a clear heading, say “Decisions” or “Out of scope”, rather than in a note it might skim past.
What stays exactly as written
| In the Codex file | In Marko |
|---|---|
| Headings, lists, checkboxes | Shown with their hierarchy; a checkbox toggles with a click |
| Tables of files or steps | Rendered, editable cell by cell |
| Code blocks | Highlighted per language, kept whole |
| Markup Marko does not know | Kept as is in the file |
Sign off and share the plan
Once the plan is reviewed, you sometimes want sign-off before the agent starts, from a colleague who will not open the repository. Choose File > Export as PDF…; the document comes out paginated as A4, ready to read and annotate. The .md stays in the project as the working reference. The PDF is produced on your Mac, with nothing sent out.
Frequently asked questions
Does Marko connect to Codex?
No. Marko has no integration with Codex. You open the .md files the agent left in the project folder, like any Markdown file.
Do I need to reopen the file after a Codex run?
Yes. When Codex rewrites a file, reopen it in Marko to see the current version. Marko works on the file on disk and does not touch Git.
Can I fix a plan without breaking the file?
Yes. Marko saves plain Markdown and keeps markup it does not know. The file stays readable by Codex and by another editor.
Try it on your own file. Open a .md your AI just wrote, fix it and export it. Marko runs on Apple Silicon Macs, macOS 12 or later.
Full 14-day trial, no account or credit card. See pricing