Summary. The header that Export to Markdown writes at the top of the file puts --- directly under the two date lines. In Markdown, a line of dashes right under a paragraph is a setext heading underline, not a horizontal rule, so the dates render as a large H2. That happens everywhere, including inside T3 Chat itself. A blank line before the --- fixes it. A hard line break after the first date keeps the two dates on separate lines in renderers that follow CommonMark. Two characters in the export template.
What the export writes today
# React useEffect Cleanup Function
Created: 9/15/2026, 1:20:18 PM
Last Updated: 9/15/2026, 1:20:18 PM
---
Proposed
# React useEffect Cleanup Function
Created: 9/15/2026, 1:20:18 PM\
Last Updated: 9/15/2026, 1:20:18 PM
---
Why it matters
The dates become a section heading. Outline views and table-of-contents tools in GitHub, VS Code, Obsidian and pandoc list "Created: … Last Updated: …" as a top-level section of every exported chat.
Outside T3 Chat the dates also run together on one line. CommonMark treats a single newline as a soft break and renders it as a space. T3 Chat's own renderer turns single newlines into
<br>, so this half is invisible inside the app, but an exported file is meant to live somewhere else.The turn separators later in the same file already do it right: blank line,
---, blank line. Only the header's---is missing its blank line.
Implementation is your call. \ is the CommonMark spelling of a hard line break and is visible in the raw file. Two trailing spaces is the older spelling with the widest support, but invisible and easily stripped by editors. Or sidestep line-break semantics entirely, e.g., by writing the dates as two paragraphs or a two-item list.
To reproduce. Export any chat and open the .md in GitHub, VS Code's preview, or any CommonMark viewer. Or paste the header into a T3 Chat message: even there, the dates come out wrapped in an <h2> (https://t3.chat/share/sjwx26h5ka).