Search preview snippets display raw markdown syntax (**, #, ##, ---,``) instead of rendered text, while the same content renders correctly inside the actual conversation.
- Open any chat containing markdown-formatted text (bold, headings, dividers, inline code).
- Use the chat search feature.
- The preview snippet shows raw syntax tokens, unrendered. See the screenshots below
- Opening the same chat shows the content rendered correctly, confirming the content itself is fine, only this display path is affected.
Why this matters
Search is a high-intent moment, people are trying to locate something specific. Surfacing raw syntax at that moment adds friction, especially for non-technical users who won’t recognize **, --- or ## as formatting rather than a bug.
Suggested fix
Either render markdown in preview snippets to match the conversation view, or strip the syntax tokens so previews show plain readable text. For a compact row, stripping is probably the simpler, more scannable option.
Another Example.
Top comments (0)