Summary
When agent output contains two em-dashes (—) in close proximity, the CLI's markdown renderer treats the span between them as strikethrough, even though the LLM did not intend strikethrough formatting.
Repro
Have the agent produce a line like:
The quick — brown — fox jumps over the lazy dog.
Observed: brown (and surrounding text) is rendered with a strikethrough.
Expected: em-dashes render literally; no strikethrough.
Likely cause
The markdown parser is probably treating — as a delimiter for some inline syntax it shouldn't be (cousin of #1936 where single-tilde was being treated as strikethrough).
Related
Why this matters
Em-dashes are extremely common in natural-language LLM output. Spurious strikethrough makes legitimate text look retracted or wrong.
Summary
When agent output contains two em-dashes (
—) in close proximity, the CLI's markdown renderer treats the span between them as strikethrough, even though the LLM did not intend strikethrough formatting.Repro
Have the agent produce a line like:
Observed:
brown(and surrounding text) is rendered with a strikethrough.Expected: em-dashes render literally; no strikethrough.
Likely cause
The markdown parser is probably treating
—as a delimiter for some inline syntax it shouldn't be (cousin of #1936 where single-tilde was being treated as strikethrough).Related
~is being used as markdown strikethrough markup when it should be double-tilde~~#1936 — single tilde~rendered as strikethrough (same class of parser misfire)Why this matters
Em-dashes are extremely common in natural-language LLM output. Spurious strikethrough makes legitimate text look retracted or wrong.