Codex Desktop Markdown tab becomes unclosable after editing from source view

Open
#34,539 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
markdown
Domain
desktop

Research direction

Reproduce the issue in Codex Desktop using the listed source-view transition, then trace the Markdown panel state after Codex edits the file. Check the rendered/source toggle and diff-view handling; done means the updated panel can be restored or shown as a diff and the Markdown tab remains closable.

Written by the indexing model from the issue text.

Description

app bug

Bug report

Reproduction
  1. Open a Markdown file in Codex Desktop and show its rendered Markdown preview in the right panel.
  2. Switch the preview to show Markdown source.
  3. Have Codex edit the Markdown file.
  4. Observe the Markdown panel.
Actual behavior

The panel becomes stuck showing the diff. Toggling the preview does not restore the normal view, and the tab cannot be closed.

Comparison

If the Markdown preview is still in rendered-preview mode when the edit happens, the panel may show the diff, but cycling hide/show restores it. The unclosable state specifically occurs after switching to source view before the edit.

Expected behavior

After the edit, the Markdown tab should either show the updated source/preview or a closable diff view. The tab should remain closable in all cases.

Environment
  • Codex Desktop version: 26.715.61943
  • macOS: 15.7.8 (24G817)

This appears distinct from a Markdown diff rendering issue because the failure is a stuck, unclosable tab after the source-view transition.

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.