Cursor IDE cannot access UEFN project files after recent update

General Issues and Bug Reporting
, , , , ,
1

Summary

Cursor IDE cannot access UEFN project files after recent update.

Please select what you are reporting on:

Verse

What Type of Bug are you experiencing?

Verse

Steps to Reproduce

  1. Create or open any UEFN project in Cursor IDE
  2. Attempt to add any .verse file to Cursor’s AI chat feature
  3. Try to drag and drop files or use the file picker in Cursor
  4. Error appears: “path should be a ‘path.relative()’ string, but got [absolute path with @ symbol]”

Expected Result

UEFN project files should be accessible to external IDEs like Cursor IDE for development workflow integration. Files should be added to AI chat without path resolution errors.

Observed Result

Cursor IDE fails to process UEFN file paths containing @ symbols (e.g., /safia@fortnite.com/ProjectName/…), breaking AI chat integration and preventing file access. Error message indicates path resolution issue with workspace naming convention.

Platform(s)

Windown 11

Upload an image

{8E892469-98F5-488C-AF76-F23316B5132D}.png

2

I’m having this problem too. It occurs when opening the .code-workspace file of the project. It seems to work if you just open the folder with the .verse files, but this is a problem still, as that way you won’t see errors/problems in your code.

1 Like
4

Same issue here

1 Like
5

Same issue here, please bring back cursor :frowning:

6

Found a workaround, but please fix it :

1 Like
7

Writing this so maybe it can help Epic to fix the issue. The problem starts occurring only after building verse code after the new update.
It happens because the new build of the .code-workspace file in the project sets the name of the folders to a path, causing the issue.

Example:

 {
            "name": "Verse",
            "path": "C:/Users/user/AppData/Local/UnrealEditorFortnite/Saved/VerseProject/Project_Name/Verse"
        }

has become

 {
            "name": "/Verse.org",
            "path": "C:/Users/user/AppData/Local/UnrealEditorFortnite/Saved/VerseProject/Project_Name/Verse"
        }

And this causes the issue

2 Likes
8

You have not only broken Cursor, but other AI editors and AI plugins are all broken too, like Cursor, Windsurf, and Copilot Agent. You recently released a Developer Assistant, so I think your ecosystem really needs to be compatible with AI development.

9

Hi all:

Thanks for reporting the issue.

The reason we made this change was to better reflect the fact that Verse modules are defined at given Verse paths - these start with a forward slash by convention. The VS Code workspace specification should not require folder names to be relative paths, or indeed, be any type of filesystem path at all (Multi-root Workspaces)

We’re looking into ways for creators to allow customization of how the VS Code workspace is generated in order to more easily accommodate situations like these, and also how best to communicate this issue to other vendors who might be parsing these generated VS Code workspaces. Once we’ve figured that out, we’ll post an update here.

2 Likes
10

Thank you for this response. Indeed, all that’s needed is an option to change the name (or at least not have it reset with every build), as this doesn’t affect Verse’s functionality in the project. We hope to get this fix as soon as possible to avoid having to rely on a Python script all the time, haha.

Thank you for your transparency.
simnJS

11

If it didn’t overwrite the code-workspaces file every time we compile it would be easy to add multi-homed workspaces and would allow creators to use dynamic paths or work arounds like this easily.

For now by using duplicating the paths like:

        {
            "name": "/bizanator@fortnite.com/LuminaraSecrets_B",
            "path": "C:/P4/bizanator_Eros_Luminara_9679/LuminaraSecrets_B/Plugins/LuminaraSecrets_B/Content"
        },

and adding another entry ABOVE it so you have

        {
            "name": "LuminaraSecrets_B",
            "path": "C:/P4/bizanator_Eros_Luminara_9679/LuminaraSecrets_B/Plugins/LuminaraSecrets_B/Content"
        },
        {
            "name": "/bizanator@fortnite.com/LuminaraSecrets_B",
            "path": "C:/P4/bizanator_Eros_Luminara_9679/LuminaraSecrets_B/Plugins/LuminaraSecrets_B/Content"
        },
        {
            "name": "Verse",
            "path": "C:/Users/Biza/AppData/Local/UnrealEditorFortnite/Saved/VerseProject/LuminaraSecrets_B/Verse"
        },
        {
            "name": "/Verse.org",
            "path": "C:/Users/Biza/AppData/Local/UnrealEditorFortnite/Saved/VerseProject/LuminaraSecrets_B/Verse"
        },

Do this for every path that your AI agent needs access to.

This at least works around the problem. However the compiler will overwrite this so going to your project folder, in my case “C:/P4/bizanator_Eros_Luminara_9679/LuminaraSecrets_B/Plugins/LuminaraSecrets_B/”
in Windows explorer and right clicking the LuminaraSecrets_B.code-workspace file, select properties, and set it to Read-Only will prevent it from being overwritten. Of course this should be fixed long term and users will want to uncheck read-only after updates.

image
image2121×1095 162 KB

1 Like
12

FORT-920729 has been added to our ‘To Do’ list. Someone’s been assigned this task.

3 Likes