Prism to Codex migration guide

Prism is being retired. This guide helps you preserve the projects you own and continue working with their LaTeX source in Codex. Start before Prism shuts down to avoid disruption.

What happens to my data?

After shutdown, all Prism-related data will be deleted. Export your projects and save a backup before Prism shuts down. Once the data is deleted, it cannot be recovered.Codex supports many features available in Prism. It can work across the files in an exported project and help you edit, troubleshoot, and build it, but it does not reproduce Prism’s shared real-time editor. Project history, inline comments, collaborator permissions, and the live Zotero connection do not move with the project files. Most multi-file LaTeX projects also need a local TeX toolchain. Codex access and usage limits depend on your ChatGPT plan and workspace controls.

Before Prism shuts down

From the user or workspace menu, open Settings → Data Controls → Export all projects (zip) → Download zip. Alternatively, You can export individual projects from its project-title menu with Export (zip).
Unzip the downloaded archive.
Optionally open each important project, make sure its latest successful PDF preview is loaded, then select Download PDF in the PDF viewer. Keep that PDF for reference.
Drag and drop the folder into Codex and give it the prompt “setup and compile this pdf project”

The all-project archive may include a conversations folder for some projects. Keep those JSON files for reference; they do not recreate Prism chats in Codex automatically.For a shared project that you do not own, the project-menu ZIP preserves the project files but does not include your Prism conversation history.

Move one project to Codex

Extract the project into its own folder and preserve the directory structure.
Install or open the ChatGPT desktop app, sign in, and select Codex. See the Codex quickstart.
Choose Add new project or press Cmd+O on macOS, then select the project’s root folder. See Projects and chats.
Start the chat as Local / This computer so Codex can work with the files on your computer. Keep Ask for approval while you are getting started. See Codex environments and permissions.
Ask Codex to audit the project before changing anything.

_{Inspect this LaTeX project without changing it. Identify the root document, required TeX engine, existing build command, bibliography workflow, figures, custom packages, and missing prerequisites. Preserve the multi-file structure. Report what you find in plain language before running or editing anything.}
Ask Codex to run the project’s latexm.rc file. If none exists, ask it to identify the smallest suitable local setup first.

_{Compile the main document using the project’s existing build workflow. If it fails, explain the first actionable error in plain language and propose the smallest fix. Ask before installing software or changing files. Do not rewrite manuscript content to hide a build error.}
Open the generated PDF beside the chat and compare it with the last PDF from Prism. Codex can preview local files, but its built-in LaTeX compiler is for standalone .tex files, not a complete multi-file Prism project.

_{Compare the new PDF with the last PDF from Prism. Check the title and authors, section order, figures, tables, equation numbering, citations, bibliography, and page count. Report every difference before editing any source file.}
Resume editing only after the project builds and the output matches what you expect. Keep backups and choose a new history and collaboration workflow.

What changes after export

Prism capability	What to expect in Codex	Practical next step
LaTeX source, figures, and bibliography files	Codex can read and edit the exported files in a local folder	Verify every file before the Prism deadline
Hosted project compilation	Multi-file projects depend on a compatible local TeX toolchain or the project’s documented container	Ask Codex to identify and run the existing build; test every project
Shared live editing	A local Codex folder is not a shared real-time editor	Agree on one editor at a time or use a separate collaborative writing service
Project history and inline comments	They are not part of the project-file export	Copy important context and save milestone versions before shutdown
Prism conversations	Some all-project exports include conversation JSON for reference	Keep the files; treat them as an archive rather than an imported chat history
Zotero connection	The live connection and account metadata do not move with the files	Refresh or export the `.bib` file and manage Zotero separately
Collaborators and permissions	They are not recreated in Codex	Set up access again in the collaboration system you choose
Equation hover and PDF-to-source navigation	The experience is not equivalent to Prism	Search by equation label or text, or ask Codex to locate the source
Word count, spell check, and editor aids	Checks are deliberate rather than Prism’s continuous editor experience	Ask Codex for a focused check and review scientific terms manually
Backups	Codex works on the folder you select; it is not the project backup	Use an approved backup or version-control system
Cost and usage	Availability and limits depend on plan and workspace policy	Check the current Codex pricing and usage page

Useful first prompt

Create a short README that explains how to compile this project, including the main file, TeX engine, bibliography tool, required packages, and validation steps. Show me the draft before saving it.

Collaboration and backups

Codex edits the files in the folder you select. Before the first editing task, keep an untouched export and create a working copy. For a simple workflow, save dated milestone copies or use an approved institutional backup with file history. For teams comfortable with version control, Git can provide a more precise history, but it is optional.Because local Codex projects do not provide Prism-style live editing, collaborators should agree how files will be exchanged and avoid editing the same copy at the same time unless their chosen collaboration tool safely supports it.

If something goes wrong

An export fails: Check export-errors.json and retry using the project menu’s Export (zip) action. If a project is still missing or you need help, email support@openai.com.
The project does not compile: Ask Codex for the first actionable error and the required engine or package. Approve software installation only from an approved source.
Codex cannot open the folder: Review the Codex troubleshooting guide and approve operating-system access to the selected folder if prompted.