codex - 💡(How to fix) Fix Remote Codex projects should render Markdown/HTML files like local projects

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

Codex App (remote projects and conversations; compared with local Codex projects)

What feature would you like to see?

Feature request: Improve remote file preview for Markdown and HTML files in Codex App

Current behavior: In local Codex projects, opening a Markdown file shows a rendered Markdown preview in the Codex App, which is very useful for reading documentation.

In remote Codex projects, opening a Markdown file shows the raw Markdown text instead of the rendered preview. Opening an HTML file also shows the raw HTML source instead of rendering it in the Codex in-app browser or an HTML preview view.

Also, in local Codex conversations, clicking http/https links opens them in the Codex in-app browser by default. In remote conversations, clicking the same kind of link opens the system default browser instead, and I need to right-click to choose the Codex browser.

Requested behavior: Please make remote projects match local project behavior for previewable files:

  • Markdown files opened from the remote project file view should use the Codex built-in Markdown preview renderer by default.
  • HTML files opened from the remote project file view should render in the Codex in-app browser or an HTML preview panel by default.
  • Provide an option to switch to raw source/text view when needed.
  • Remote conversation http/https links should open in the Codex in-app browser by default, matching local conversation behavior, with an option to open externally.

Why this matters: Remote project workflows often involve reading project documentation, generated reports, design docs, README files, HTML previews, test reports, and dev server pages. Viewing Markdown and HTML as raw text makes these documents harder to read and breaks the smooth preview workflow that local projects already have.

Expected behavior:

  • README.md opens as rendered Markdown in remote projects.
  • report.preview.html opens as a rendered web page in remote projects.
  • Users can still choose “View source” or “Open as text” when they need raw content.
  • Remote conversation links behave like local conversation links by default.

Additional information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING