How to publish HTML reports from Codex with Foliyo
To share a report made in Codex, connect Foliyo through MCP and ask Codex to publish the reviewed HTML. Foliyo hosts the browser page, applies your access settings and lets you revise the work at the same URL, without setting up a separate site deployment for each deliverable.
Turn the result of the work into something a client can use
Codex may finish a useful audit, implementation plan or project summary inside a working directory. Your client often needs the conclusion and its supporting evidence, not access to that repository. A Foliyo gives the final handoff its own visual identity and shareable address.
Use this workflow for a reviewed report, proposal or website handoff. Keep running applications on an appropriate application host. Foliyo publishes static HTML, so a working local app with a backend or arbitrary JavaScript is not automatically a supported deliverable.
1. Add the hosted MCP server
Install and sign in to Codex first. A free Foliyo account is enough for an initial page; your AI usage is billed separately. Run the following commands from your terminal, then complete the browser sign-in and workspace consent.
The first command adds Foliyo’s online server. The second requests the MCP and workspace-write permissions needed to publish. If a connection already exists, authenticate that entry instead of creating duplicate servers.
codex mcp add foliyo --url https://foliyo.io/mcp
codex mcp login foliyo --scopes 'mcp,workspace:write'2. Confirm the workspace before writing
Ask Codex to check Foliyo’s workspace and plan. In a shared project, review which account the connection belongs to before publishing anything. Do not paste credentials or an OAuth callback URL into your deliverable or repository.
Codex can require approval before calling a tool that writes data. If publication is waiting for approval, review the proposed Foliyo action and approve that specific operation. A refusal in an unattended run may be an approval requirement rather than a failed connection. Do not disable all approvals just to make the example run.
Use Foliyo to check my connected workspace and plan. Tell me which saved project context is available for the Northwind handoff. Do not create or publish anything yet.3. Assemble a client-safe source file
Give Codex a specific approved source file, such as handoff.md, instead of permission to publish everything in the repository. Include the outcome, what shipped, important limitations, maintenance instructions and the next decision. Remove credentials, private logs and internal conversations.
For a website handoff, link to a login page when useful, but never put passwords or recovery codes in the document. Confirm that supporting files are intentionally shareable. Foliyo’s HTML cannot resolve a path on your laptop; local images must be supplied through the supported asset workflow or replaced with usable hosted assets.
Create a Foliyo from the approved handoff.md in this project for Northwind. Include the summary, delivered scope, verified checks, known limitations, maintenance steps and next action. Use a scrolling web page in Northwind’s approved visual style, with my consultancy as sender. Do not include source code, secrets or internal notes. Ask missing questions using numbered choices. Show the draft before publishing and do not email anyone.4. Choose how the client should receive it
For a handoff with instructions, choose a scrolling page. For a call you will lead, choose fixed 16:9 slides. Flexible slides work when some sections need more space. Codex should load the relevant saved project and design context before producing a new layout.
Then choose the access rule. A PIN is available on Free. Pro offers email gates with optional verification. A personal recipient link attributes activity to that link, but a forwarded link is not proof of the viewer’s identity. Keep publication and sending email as separate choices.
| Your choice | Example reply |
|---|---|
| Format | 1. Scrolling page, so the client can read the maintenance checklist on a phone. |
| Brand | Use the Northwind guide. Keep my consultancy as the sender. |
| Access | PIN protection. Return the link and generated PIN for me to share. |
| Tracking | Use the agreed tracking setting. Show what my current plan supports. |
5. Check the complete HTML, then publish
Review the draft against the source file. Check every section, image, link and control. If Codex created tabs or collapsible sections, open each one. The content must remain usable after Foliyo’s supported-content checks, not only in the local preview.
Ask Codex to preflight the complete HTML and assets, resolve blocking issues and publish the checked version. A preflight response alone is not a published page. Wait for a successful publication response containing the actual URL. Inspect any tool approval prompt before continuing.
The draft is approved. Preflight the complete HTML and supplied assets. Resolve any blocking issues and publish this handoff with PIN protection. Return the published URL and generated PIN. Do not email anyone.6. Verify the recipient view and a revision
Open the link in a separate browser session. Check that content is hidden until you supply the PIN, then inspect the complete page on desktop and mobile. Free shows the Foliyo bar; Pro removes it. Verify that the live site and support links lead to the intended destinations.
Now make a small revision to the existing Foliyo and confirm the same link shows it. This is useful when a launch date moves or a maintenance instruction changes. Ask Codex to preserve the sender, access and tracking settings instead of rebuilding the page with new defaults.
Find the existing Northwind handoff and retrieve its current content. Update the maintenance review date to 12 October 2026. Preserve all other content, the existing URL, PIN, sender and tracking settings. Preflight and publish the update. Do not email anyone.7. Use the readership report with care
Free provides a basic read receipt. Pro adds recipient and section engagement reports and visible reading time. Ask Codex to find the published handoff and retrieve its report when you need to plan a follow-up.
The absence of an open does not prove the client ignored the work, and visible time does not prove understanding. Email attribution comes from a supplied recipient link or an email gate, not from Foliyo guessing an anonymous visitor’s address. The public template preview has tracking off.
What we verified
On 25 September 2026, the native Codex CLI used the hosted Foliyo MCP to prepare, preflight, publish, retrieve, update and report on a fictional PIN-protected page. Publication used a temporary, explicitly scoped approval. An initial unattended attempt correctly refused an unapproved write.
Independent checks confirmed the saved content, access gate and preservation of the URL and PIN after revision. Tracking and notifications were off, and the test page was deleted afterward. The linked handoff sample is a separate illustrative template. This workflow test does not establish public ChatGPT app-directory approval.
Product guidance from Foliyo. See current plans and limits, connection instructions and our privacy policy. Send corrections or questions to hello@foliyo.io.