Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Codex Desktop: support live refresh for rendered Markdown documents

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…

Codex Desktop can open local Markdown documents from chat links, but the rendered view does not update when Codex edits the file. The user has to manually click away/reopen the file or otherwise force the view to refresh.

This makes document-backed workflows awkward. For example, we use gpt/canvas/model-in-progress.canvas.md as a working model that Codex edits while discussing design. The file is persistent, but the rendered document view is not live, so it is easy to read stale content after Codex patches the file.

Root Cause

Codex workflows increasingly use local Markdown files as shared working memory, design canvases, model documents, and commit notes. When Codex edits those files, users expect the open rendered view to reflect the latest content.

A live refresh path would make document-backed collaboration feel much more like an actual shared canvas instead of a static preview.

Fix Action

Fix / Workaround

This makes document-backed workflows awkward. For example, we use gpt/canvas/model-in-progress.canvas.md as a working model that Codex edits while discussing design. The file is persistent, but the rendered document view is not live, so it is easy to read stale content after Codex patches the file.

  1. User opens gpt/canvas/model-in-progress.canvas.md in Codex Desktop.
  2. User asks Codex to update the model.
  3. Codex patches the Markdown file.
  4. The rendered view still shows the old content.
  5. User has to manually click/reopen/refresh to see the update.
RAW_BUFFERClick to expand / collapse

Description

Codex Desktop can open local Markdown documents from chat links, but the rendered view does not update when Codex edits the file. The user has to manually click away/reopen the file or otherwise force the view to refresh.

This makes document-backed workflows awkward. For example, we use gpt/canvas/model-in-progress.canvas.md as a working model that Codex edits while discussing design. The file is persistent, but the rendered document view is not live, so it is easy to read stale content after Codex patches the file.

Expected Behavior

Codex Desktop should provide a way to refresh or live-update an open rendered document after the underlying file changes.

Possible designs:

  • A refresh button on rendered document tabs.
  • A "live view" toggle for rendered Markdown documents.
  • Automatic refresh when the file changes on disk.
  • A visible stale/out-of-date indicator with a refresh action.

Actual Behavior

The document can remain visually stale after Codex edits the file. The file contents are updated on disk, but the rendered view does not reliably refresh until the user manually reopens or otherwise nudges the view.

Why This Matters

Codex workflows increasingly use local Markdown files as shared working memory, design canvases, model documents, and commit notes. When Codex edits those files, users expect the open rendered view to reflect the latest content.

A live refresh path would make document-backed collaboration feel much more like an actual shared canvas instead of a static preview.

Example Workflow

  1. User opens gpt/canvas/model-in-progress.canvas.md in Codex Desktop.
  2. User asks Codex to update the model.
  3. Codex patches the Markdown file.
  4. The rendered view still shows the old content.
  5. User has to manually click/reopen/refresh to see the update.

Environment

  • Codex Desktop app
  • Windows
  • Local workspace Markdown files
  • Markdown rendered from files edited by Codex

Related

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