Bug: Composer window with escape characters

Bug Report
1

Hi, thanks for reporting an issue with Cursor.

Before you report this, we’d appreciate if you can search this forum to see if this issue has already been reported.

If you have done so, please check this box.
on

Describe the Bug

When composer output generates a markdown file with a usage section showing code syntax, it breaks the contents out of the normal ‘file context window’ into the normal chat context.

I believe this is due to the presence of escape characters based on what it showed me. I’ve attached a screenshot.

Steps to Reproduce

  1. Ask composer to generate a readme.md with escape characters to denote code (e.g. ```)
  2. Inspect output in chat window

Expected Behavior

The section that is marked in the code syntax should not break out of the ‘file context window’.

Screenshots / Screen Recordings

Screenshot 2025-01-01 at 10.55.02 AM.png
Screenshot 2025-01-01 at 10.55.02 AM.png636×487 38.8 KB

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 0.44.9
VSCode Version: 1.93.1
Commit: 316e524257c2ea23b755332b0a72c50cf23e1b00
Date: 2024-12-26T21:58:59.149Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 23.6.0

Additional Information

n/a

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

I’ve also seen this issue. As a workaround I asked cursor not to include the code sample, but it actually did add value so this made my generated documentation worse.

3

Because the Composer already outputs using Markdown, when the AI has a Markdown snippet to include, it can sometimes get the output wrong, causing it to render incorrectly in the composer output.

I’ve reported your example to our team, who can hopefully improve this for you soon!