Codex publishing
Give Codex a publishing and review loop, not just an output folder.
Codex can research, design, and build a complete HTML artifact inside a workspace. HTML Docs lets the agent publish that file, hand back a browser link, and continue working after a human leaves feedback. The output becomes a living collaboration object instead of a final attachment.
Agent output is more useful when the next action is review.
A file path is useful to the agent and invisible to the stakeholder. A deployment URL solves visibility but does not give Codex a structured channel for comments and revision requests. HTML Docs exposes both the page and its collaboration state through the CLI, skill, and API.
How it works
From local output to a reviewed artifact.
Create the artifact
Ask Codex for a complete responsive HTML page grounded in the source material.
Publish in the task
Run the HTML Docs CLI and return the live URL immediately.
Review in the browser
Stakeholders read the artifact and leave comments on the relevant content.
Continue the task
Codex reads the feedback, revises the page, and resolves addressed threads.
What changes when review is built into the page
Agent-native operations
Publish, read, edit, comment, and version through documented interfaces.
Visible progress
A stakeholder can follow the artifact without reading terminal output.
Durable decisions
The document, feedback, and changes remain available after the coding task ends.
HTML Docs vs. A repository artifact
Choose for the job you actually need to finish. This comparison focuses on workflow, not a blanket claim that one tool replaces another.
| Criterion | HTML Docs | A repository artifact |
|---|---|---|
| Audience | Technical and non-technical reviewers | People comfortable navigating the repository |
| Review surface | Rendered page with comments | Source diff or separate messages |
| Agent follow-up | Comments available through API | Feedback must be translated into a new prompt |
Frequently asked questions
How does Codex publish an HTML file?
Install the HTML Docs skill or run `npx @html-docs/cli publish page.html` from the workspace.
Can Codex read comments later?
Yes. The CLI and API can list document comments and update individual editable regions.
Does publishing modify the local file?
No. Publishing sends the HTML to HTML Docs and returns a hosted URL; the source file remains in the workspace.
Can I use the workflow for an implementation log?
Yes. Codex can keep one page current as it records decisions, progress, deviations, and open questions.
Publish the next artifact from where it was created.
npx @html-docs/cli publish page.html