Thanks for sending the examples, the screenshots show a few things right away. I’ll break it down.
-
Inline
$...$doesn’t render, that’s by design. Single$is intentionally disabled because it conflicts with normal text and money amounts, for example$1,500would break parsing. For inline math use\(...\), for block math use\[...\]or$$...$$they render fine. In your screenshots$e(t)$and$K_p$stay as plain text for this reason. -
When you see a rendered formula and then a duplicate as raw text right after it, that’s a known bug. The MathML annotation isn’t hidden, so the original LaTeX leaks out.
-
Matrix brackets pmatrix/bmatrix and
\sqrtthat sometimes disappear or look smaller are also a known visual bug, I mentioned it above. It’s been reported, there’s no fix timeline yet.
Your idea about having the agent output math that’s guaranteed to render makes sense, I’ll pass it along. For now you can add a User Rule Rules | Cursor Docs, something like:
When writing math, use \(...\) for inline and $$...$$ for block.
Do not use single $ for inline math. Avoid nesting delimiters (no \( inside \[...\]).
This reduces the number of broken formulas a lot. If anything still looks weird after that, send the Request ID right corner of the chat menu > Copy Request ID if Privacy Mode is off, and we can look at the specific case.