Inline fenced Markdown blocks render inconsistently between Codex Desktop tasks
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.908.4834.0
What subscription do you have?
ChatGPT Pro
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
A predecessor Codex Desktop task emitted valid inline Markdown with fenced code blocks, but the blocks were not visible in the conversation timeline. Starting a fresh task on the same Windows machine made the same fenced-code test render correctly. The behavior appears task- or session-dependent.
What steps can reproduce the bug?
- Open a Codex Desktop task.
- Emit an inline Markdown item containing a fenced code block.
- Observe whether the code block is visible in the timeline.
- Start a fresh task on the same machine and repeat the same test.
Observed: the predecessor task omitted the visible block; the fresh task rendered it.
What is the expected behavior?
Valid inline fenced Markdown should render visibly and consistently in every Codex Desktop task.
Additional information
Impact: technical output can be invisible to the user even when the agent successfully emits valid Markdown, making review and delivery unreliable. No logs, session identifiers, or personal data are included. Please investigate whether rendering state is incorrectly scoped to a task or session, and consider exposing a renderer-health indicator or recovery path.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the inline fenced-Markdown steps in a predecessor task and a fresh Codex Desktop task on Windows, then compare whether the rendering state differs by task or session. Done means valid fenced code blocks appear consistently in every task; the payload names no files or tests to target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown, rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100