# Poorly formatted responses for the Cursor UI

**URL:** <https://forum.cursor.com/t/poorly-formatted-responses-for-the-cursor-ui/39622>\
**Category:** Bug Reports\
**Created:** [January 7, 2025, 6:24am UTC](https://forum.cursor.com/t/poorly-formatted-responses-for-the-cursor-ui/39622 "2025-01-07T06:24:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![john-savepoint](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/john-savepoint/32/15998_2.png) [@john-savepoint](https://forum.cursor.com/u/john-savepoint)\
**Post date:** [January 7, 2025, 6:24am UTC](https://forum.cursor.com/t/poorly-formatted-responses-for-the-cursor-ui/39622/1 "2025-01-07T06:24:57Z")

</div>

This was a problem in the past but it felt like it was updated and fixed but it’s back again now with the newest update. Where responses to prompt have really inconsistent and incompatible formatting with the Cursor sidebar.

So where a code block should be Filled with code it’s just being generated in the text sections and vice versa. And it’s not like there’s any rhyme or reason to when and where these sections stop it’ll just randomly stop being in a code block which makes it all extremely difficult to effectively copy and paste or even feed back into the prompt system

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [January 7, 2025, 10:58am UTC](https://forum.cursor.com/t/poorly-formatted-responses-for-the-cursor-ui/39622/2 "2025-01-07T10:58:38Z")

</div>

Hey, are you referring to rendering code blocks in Markdown? Since Composer already outputs its responses in Markdown, it can sometimes render incorrectly, causing incorrect output in Composer. We are aware of this issue and hope to resolve it soon.

---

<div class="post-metadata">

**Author:** ![john-savepoint](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/john-savepoint/32/15998_2.png) [@john-savepoint](https://forum.cursor.com/u/john-savepoint)\
**Post date:** [January 7, 2025, 11:18am UTC](https://forum.cursor.com/t/poorly-formatted-responses-for-the-cursor-ui/39622/3 "2025-01-07T11:18:27Z")

</div>

Love yas! THank you.

---

<div class="post-metadata">

**Author:** ![lx-0](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/lx-0/32/10656_2.png) [@lx-0](https://forum.cursor.com/u/lx-0)\
**Post date:** [February 12, 2025, 10:55am UTC](https://forum.cursor.com/t/poorly-formatted-responses-for-the-cursor-ui/39622/4 "2025-02-12T10:55:22Z")

</div>

This happens quite often when generating README.md files as these typically consist of formatted blocks itself. Cursor sometimes struggles with escaping triple backticks and therefore the whole file edit corrupts.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [December 21, 2025, 8:57am UTC](https://forum.cursor.com/t/poorly-formatted-responses-for-the-cursor-ui/39622/5 "2025-12-21T08:57:55Z")

</div>

Closed on December 21, 2025, 8:57am UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.