Codex App renderer breaks when displaying inline code containing Rust-style `::` paths

Resolved 💬 5 comments Opened May 19, 2026 by neysofu Closed May 22, 2026

What version of the Codex App are you using (From “About Codex” dialog)?

26.513.31313 (2867)

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.4.0 arm64 arm

What issue are you seeing?

Codex Desktop sometimes renders valid Markdown incorrectly when the response contains Rust-style paths with ::, especially inside inline-code Markdown hyperlink labels.

In the attached screenshot, the response contains a source link that should render as one clickable Markdown link:

[`Hasher::write_u128`](https://doc.rust-lang.org/std/hash/trait.Hasher.html)

Instead, the Codex App UI breaks the formatting around ::write_u128, exposes parts of the Markdown link syntax / URL, and renders the surrounding text as fragmented inline-code chips.

Related issues

Possibly related, but not exact duplicates:

  • #20671 - Code-comment block not rendering properly
  • #23004 / #22985 - Directive-like text causing renderer failures
  • #13277 - VS Code extension hyperlink rendering regression

What steps can reproduce the bug?

  1. Open Codex Desktop.
  2. Ask a Rust question likely to produce docs links with Rust path syntax:

``text
give me the doc link for rust std Hasher::write_u128
``

  1. Have Codex produce a response containing a Markdown link whose label is inline code with a Rust path, for example:

``markdown
Here you go: [
std::hash::Hasher::write_u128](https://doc.rust-lang.org/std/hash/trait.Hasher.html)
``

  1. Observe the broken render.

<img width="771" height="223" alt="Image" src="https://github.com/user-attachments/assets/7cc1cce8-01fe-4a35-a729-44147be689d5" />

What is the expected behavior?

A single clickable link labelled std::hash::Hasher::write_u128 or similar, much like displayed by GitHub right here in this issue.

Additional information

_No response_

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗