share-codex-chat

Answer First

The share-codex-chat skill is a companion workflow for Codex users. After installation, reference `$share-codex-chat` in Codex to turn the visible conversation into a self-contained HTML page, deploy it with PreviewShip, and get a shareable URL for debugging context, implementation records, or review discussions.

Deploy build artifacts, not source-code zips.

If you upload a zip, build the project first and zip the static output folder such as dist, build, out, or public with index.html and assets. Do not zip raw React/Vue/Next source folders with package.json and node_modules. Single.html,.md/.markdown, and.pdf files are supported directly by console upload, CLI, MCP, and the VS Code/Cursor extension.

Key takeaways

Comparison snapshot

When to use the Codex chat sharing skill

Use this skill when the conversation itself is the artifact you want to share: a debugging trail, a code-review discussion, a step-by-step implementation record, or a handoff between people.

It is different from deploying a frontend build. PreviewShip still handles the final public URL, but the skill first reconstructs the visible Codex chat as an HTML page.

FAQ

Is share-codex-chat part of the main PreviewShip deploy flow?

No. It is an optional Codex skill for sharing conversations. Normal PreviewShip usage still focuses on HTML, Markdown, and static build artifacts.

What is the difference between global and local install?

The `-g` flag installs the skill globally for the user. Omitting `-g` installs it into the current project, usually under `.agents/skills/share-codex-chat`.

Does the skill require a PreviewShip API key?

Yes for deployment. If the CLI is not authenticated, run `npx previewship login` or configure `PREVIEWSHIP_API_KEY` before sharing.

Can it perfectly export every Codex message?

It aims to reproduce visible chat UI and known Codex message types. If earlier context is compacted or image files are unavailable, the exported page may note that limitation.