# Markdown file woes

**URL:** <https://forum.cursor.com/t/markdown-file-woes/147088>\
**Category:** Bug Reports\
**Created:** [December 23, 2025, 3:59am UTC](https://forum.cursor.com/t/markdown-file-woes/147088 "2025-12-23T03:59:40Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [December 23, 2025, 6:02am UTC](https://forum.cursor.com/t/markdown-file-woes/147088/2 "2025-12-23T06:02:02Z")

</div>

Hey, thanks for the report. This is a known issue related to the filesystem and markdown files created by the Agent.

Related thread: [Create/Update .md files -- Unable to open: Assertion Failed: Argument is ‘undefined’ or ‘null’](https://forum.cursor.com/t/create-update-md-files-unable-to-open-assertion-failed-argument-is-undefined-or-null/140018)

Your analysis matches what we’ve seen: the problem is in how Cursor handles files created by processes running in the Agent execution context.

Workarounds:

- Create the markdown files manually before running the Agent, then ask the Agent to edit them
- After the Agent creates a file, open it in another editor, then copy the contents into a new file in Cursor

The team is already tracking this. Let me know if you can share any additional details.

---

_[View the full topic](https://forum.cursor.com/t/markdown-file-woes/147088)._