Claude desktop app, Code tab: inline math between single dollar signs (`$q_0$`) shows as raw text; only `$$...$$` on its own line renders

Context

Source(s): https://github.com/anthropics/claude-code/issues/65632 Status: reported working by source, not reproduced by us (workaround only; root fix not confirmed).

Problem

Claude often writes inline math with single dollar signs, so math-heavy answers in the Code tab are hard to read. Putting $$...$$ mid-sentence forces a line break, so it is not a substitute. In June a commenter found that \(...\) was ignored too, which left no way to get real inline math. The same messages rendered correctly in the iPad and iPhone apps and in regular Claude chat.

Error (redacted / normalized)

Symptom (no error text): in the Code tab, inline math such as $q_0$ appears as the literal text "$q_0$", dollar signs included, instead of a typeset formula. $$...$$ on its own line still renders, but only as a centered block.

Applies when

Claude desktop app, Code tab, on macOS (Claude Code 2.1.167, macOS 26.5.1) and Windows 11 on ARM64 (Claude Code 2.1.267); the closing comment says the fix also applies on claude.ai/code, though nobody in the thread reported the bug there; reported June to October 2026.

Confirm it is this problem

1. In the Code tab, have Claude reply with the identity $e^{i\pi}+1=0$ is famous → expect: the dollar signs and the raw formula are shown.
2. Show the same text in regular Claude chat → expect: it renders there (commenters), so the problem is the Code tab renderer, not the model's output.

Not this when / boundary

You are in regular Claude chat, not the Code tab. The formula is longer than 60 characters, starts with a digit ($5n$), or sits right next to quotes or letters; the closing comment says the fix leaves those as typed on purpose so shell text is not mistaken for math.

Root cause

A commenter, citing another issue's analysis, said the Code tab's markdown renderer did not turn on the single-dollar inline math rule while block math worked. The comment that closed the issue on 2026-10-16 says this is fixed: the Code tab now renders inline $...$ such as $q_0$ or $O(n)$, while shell variables and prices such as $HOME or $5 stay as typed. That comment says the fix shipped on September 17 with the web code the desktop app loads, so no app update is needed, and it also applies on claude.ai/code.

Variables

none.

Fix

1. Rerun confirm 1 → expect: per the closing comment, inline math now renders with no app update; nobody in the thread clearly confirmed this after it was closed, and a commenter on 2026-10-03, after the stated ship date, still said it was not fixed (no version or test given).
2. If it is still raw, have Claude write inline math as \(...\). The first part of a commenter's suggested CLAUDE.md section: For all mathematical expressions, use LaTeX. Use \( ... \) for inline math and $$ ... $$ on its own lines for centered display math. Never use single-dollar $...$ delimiters, never use \[ ... \], and never put LaTeX inside code blocks or backticks. → expect: the original poster confirmed on 2026-08-23 that \(...\) renders inline while $...$ stays raw; the commenter who first suggested it said inline math worked again after Claude saved the instruction to memory.

How to verify

Ask a question whose answer has inline math → expect: typeset formulas inline, with no visible dollar signs or backslashes.

What did not work

On Windows 11 ARM64 with Claude Code 2.1.267, a commenter said \(...\) lost its backslashes and showed as the literal text (P(H)), so step 2 did not work there. In June, \(...\) was also ignored on macOS (commenter).

Rollback

Remove the math line from CLAUDE.md.

Risks

Step 2 depends on the model following the instruction; a commenter said it sometimes still writes $...$. A commenter linked a third-party mod that patches the rendering; we have not reviewed it, so don't install it without checking what it changes (our inference).

Verified scope

Claude desktop app Code tab and claude.ai/code, June to October 2026.

Becomes obsolete when

Users confirm inline $...$ renders in the Code tab. Open question: whether the 2026-09-17 fix covers the Windows ARM64 case where \(...\) lost its backslashes; nobody reported back.