{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidftimrtqtzg4wvncm5xntnzsffneynuzbzjqc5kj77v27fuwzi5e",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mmhxkiwiyzx2"
  },
  "path": "/t/prism-style-latex-scientific-writing-workflow-is-painful-in-codex-cli/1381606#post_1",
  "publishedAt": "2026-05-22T21:04:57.000Z",
  "site": "https://community.openai.com",
  "textContent": "I am on Linux, and I love using Codex (both cloud and CLI). I found out you are planning to end of life prism. But the integrated LaTeX rendering is incredibly useful.\n\nI found out this will come to Codex App. But the lack of availability on Linux puts another essential feature outside the use of Linux users.\n\nFor people working in scientific computing (almost all have access to a Linux machine, even if it isn’t their main machine), a nascent capability for scientific writing will be lost for good–especially notes to self or other people on your team.\n\nHere is ChatGPTs suggested post:\nCodex CLI can edit .tex and .bib files, but it lacks the workflow primitives that made Prism useful:\n\n  * live PDF preview\n  * equation-aware editing\n  * reference-aware writing\n  * paper/revision UX\n  * integrated compile-error navigation\n  * collaboration/project workspace affordances\n\n\n\nFor scientific LaTeX work, a terminal coding agent is not a sufficient replacement.\n\nRequested outcome:\nEither keep Prism available, or add a Codex surface optimized for LaTeX-native scientific writing.",
  "title": "Prism-style LaTeX/scientific writing workflow is painful in Codex CLI"
}