Markdown Rendering Bug in Plan Mode Affects Safari, Chrome, and ChatGPT Atlas

Multiple users have reported a persistent rendering issue inside Plan Mode on Codex Web where markdown output intermittently fails to display properly. The bug is confirmed to occur on Safari, Google Chrome, and ChatGPT Atlas, which strongly indicates this is not a browser-specific glitch — but a rendering issue coming from the web application itself.

What’s Happening?

When Codex generates plans with multiple versions, Version 1 sometimes displays raw or unformatted markdown. After this happens, all subsequent versions inherit the same formatting problem. Users report that refreshing the browser or restarting Atlas does not reliably fix the issue.

👉 Learn How to Import Your Data (Bookmarks, Passwords, History) into ChatGPT Atlas

Steps to Reproduce

  1. Open Codex Web interface.
  2. Switch to Plan Mode.
  3. Generate a plan with multiple versions.
  4. Version 1 may show broken or unrendered markdown.
  5. Version 2–4 also appear broken with the same layout.

Expected Behavior

All versions should render markdown consistently, including bullet lists, headings, citations, tables, and inline code formatting.

Actual Behavior

  • Markdown appears as raw text.
  • Lists and styling do not render properly.
  • Formatting stays broken across all versions.
  • Refreshing, restarting browsers, or switching browsers has no effect.

👉 Learn How to Manage Site Permissions in ChatGPT Atlas

Browsers Tested

  • Safari (latest stable)
  • Google Chrome (latest stable)
  • ChatGPT Atlas

How Often Does It Happen?

This issue is reproducible in roughly 70–80% of sessions, making it a frequent and highly disruptive bug.

Why This Bug Matters

The broken markdown layout makes plans unreadable and prevents users from reviewing tasks or taking action. Since Codex is used for project planning and code execution steps, formatting is not optional — it’s required for productivity and accuracy.

👉 Learn How to Set ChatGPT Atlas as Your Default Browser on Mac

Possible Technical Cause (Analysis)

While no official statement has been issued yet, the symptoms suggest the rendering engine fails to convert markdown into HTML before display. This may involve:

  • Client-side markdown parser failing to initialize
  • A caching issue that stores the broken state across versions
  • Race conditions where the plan loads before the markdown engine executes
  • A server-side formatting error that outputs plain text rather than rich HTML

The fact that the issue appears in Atlas, Safari, and Chrome means the problem is likely happening at the application level, not within the browser’s rendering engine.

Possible Fixes Users Have Tried

  • Page refresh → No effect
  • Restart browser → No effect
  • Switch browser → No effect
  • Regenerate plan → Works sometimes, but inconsistent

👉 Hot issues: ChatGPT Atlas Is Not Supported on This Mac

Status

As of now, there is no confirmed official fix. However, because the bug impacts core workflow, it’s likely to be addressed in a future Codex or ChatGPT Atlas update.

What Users Can Do

If you’re experiencing the same problem, consider reporting it with screenshots and browser details. The more reports collected, the faster development teams can reproduce and patch the bug.

✅ Report or Check Release Notes

  • Submit a bug report through the OpenAI Support portal.
  • Monitor the latest ChatGPT Atlas and Codex Release Notes to see when the fix goes live.

👉 Learn How to Keep ChatGPT Atlas Up to Date

FAQ

Is this only happening in ChatGPT Atlas?

No. The issue has been confirmed on Chrome and Safari as well, meaning the root cause is coming from Codex Web rather than the browser.

Does clearing cache fix it?

So far, clearing cache does not help because the broken formatting appears to come from how Codex renders markdown, not browser storage.

Is there a reliable workaround?

Some users report that regenerating the plan occasionally restores formatting, but it’s inconsistent and not guaranteed.

Should users wait for an update?

Yes. Since the problem affects multiple browsers and blocks productivity, a fix is expected in upcoming releases.


Have you experienced this issue in ChatGPT Atlas or other browsers? Share your experience or check the latest release notes — improvements and bug patches are rolling out frequently.

Wawang Setiawan

Personal blog by Wawang Setiawan — a blogger from Lampung, Indonesia, sharing thoughts on technology, blogging, and digital life for global readers.

Post a Comment