I’ve been working with Cursor to produce a specification document. However, when Cursor attempts to use any sort of ASCII diagramming, the content of the Markdown file is cut off at the point when the diagrams begin.
Explain how to reproduce the bug (if known)
This prompt appears to be effective:
Please write a brief spec for a Tic-Tac-Toe game in `tic-tac-toe.md`. Be sure to use diagrams.
Attach screenshots or recordings (e.g., .jpg, .png, .mp4).
did you indent the nested markdown blocks? it works if the nested markdown blocks are indented by 4 characters on every line. otherwise if its on the same level it ends markdown output.
I can confirm markdown diagrams are messed up, it can’t repair them no matter how you explain the feedback, it keeps drawing wrong paths and deletes correct paths.
yeah tables are so much easier. i had also no issues with tables. but complex cli/tui formatting isnt yet there in general. i found certain diagrams like mermaid and others helpful and AI seems to understand that. as it has to write only connections and not draw it
If you’re using some CMD or tend to just create this inside an .md file, make sure you’re using the asciimatics and figlet Python modules in order to have a proper ASCII CLI/TUI. This only applies when you’re using Python.
You might tend to use Markdeep to fix formatting issues inside Cursor since the Markdown compatibility is not that complete with the chat bubble.
Basically, you’ll be transcribing diagrams from Cursor, formatting them when creating diagrams directly, and then merging them into Cursor in order for it to work properly with Cursor current composer text formatting compatibility.
I mean, tell that to Claude. I didn’t ask it to make diagrams, just to write a spec. Now I have to explicitly ask it not to make diagrams. Sure I could make a rule for it, but this is clearly a bug in the LLM<->Cursor interface.
Oh, I should also mention that it was breaking the file output flow when trying to put fancy ASCII doodles on file tree schematics, so it’s not just diagrams. Again, I didn’t ask for any of this specifically, the LLM just volunteered the fanciness when asked to write a spec.
Provide a clear description of the bug
Explain how to reproduce the bug (if known)
Attach screenshots or recordings (e.g., 
Tell us your operating system and your Cursor version (e.g., 
Tell us if the issue stops you from using Cursor.
I didn’t ask it to make diagrams, just to write a spec. Now I have to explicitly ask it not to make diagrams. Sure I could make a rule for it, but this is clearly a bug in the LLM<->Cursor interface.