codex - 💡(How to fix) Fix CLI TUI does not render Markdown pipe tables [1 participants]

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…
GitHub stats
openai/codex#22015Fetched 2026-05-11 03:20:59
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
1
Author
Participants
Timeline (top)
labeled ×3closed ×1

Root Cause

This matters because Codex often emits structured planning, comparison, review, and compliance notes in Markdown tables. In the TUI, those become hard to scan, especially when cells are long.

Fix Action

Fix / Workaround

Suggested implementation direction

I tested a conservative local patch against rust-v0.130.0:

Code Example

| Field | Value |
  |---|---|
  | IRS rule | Must be true, current, and compliant |
  | Proof | source note / asset manifest |
  | Placement | required before generation |
RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

codex-cli 0.130.0

What subscription do you have?

Plus

Which model were you using?

GPT 5.5

What platform is your computer?

macOS, Apple Silicon / arm64

What terminal emulator and version are you using (if applicable)?

Ghostty v1.3.1, Build 15212, Commit 332b2aefc

What issue are you seeing?

The Codex CLI TUI renders GitHub-style Markdown pipe tables as raw Markdown text instead of a readable terminal table.

Example input:

FieldValue
IRS ruleMust be true, current, and compliant
Proofsource note / asset manifest
Placementrequired before generation

Actual TUI output keeps the raw pipe table syntax.

Expected output should be rendered into a readable terminal-friendly layout, for example:

Field Value


IRS rule Must be true, current, and compliant Proof source note / asset manifest Placement required before generation

This matters because Codex often emits structured planning, comparison, review, and compliance notes in Markdown tables. In the TUI, those become hard to scan, especially when cells are long.

What steps can reproduce the bug?

  1. Start Codex CLI in the terminal TUI.

  2. Ask Codex to output a GitHub-style Markdown pipe table, for example:

    Please output this as a Markdown table:

    FieldValue
    IRS ruleMust be true, current, and compliant
    Proofsource note / asset manifest
    Placementrequired before generation
  3. Observe the assistant response in the Codex CLI TUI.

  4. The table is displayed as raw pipe-table Markdown text instead of being rendered into a readable terminal table.

What is the expected behavior?

Codex CLI TUI should render GitHub-style Markdown pipe tables into a readable terminal-friendly table layout instead of showing the raw | ... | Markdown syntax.

For example, this Markdown:

FieldValue
IRS ruleMust be true, current, and compliant
Proofsource note / asset manifest
Placementrequired before generation

should be displayed approximately as:

  | Field | Value |
  |---|---|
  | IRS rule | Must be true, current, and compliant |
  | Proof | source note / asset manifest |
  | Placement | required before generation |

For wide tables or cells with long text, it would also be acceptable to fall back to a vertical key-value layout, similar to:

Record 1

  • Field: IRS rule
  • Value: Must be true, current, and compliant

Record 2

  • Field: Proof
  • Value: source note / asset manifest

Additional information

Suggested implementation direction

I tested a conservative local patch against rust-v0.130.0:

  • Detect only strict pipe-table blocks where:
    • the header row starts and ends with |
    • the next row is a Markdown divider like |---|---|
  • Render those rows as padded terminal text.
  • Do not globally enable pulldown-cmark table parsing, because that can broaden parsing behavior and affect surrounding prose.
  • Keep normal Markdown rendering unchanged for non-table content.
  • Add a regression test for pipe table rendering.
  • Update the existing complex Markdown snapshot.

Local validation: RUST_MIN_STACK=8388608 cargo test -p codex-tui markdown_render::markdown_render_tests -- --nocapture

Result: 88 passed, 0 failed.

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