Check if the file actually exists at that path. Open Finder, go to /Applications/Cursor Nightly.app/Contents/Resources/app/out/, and see if nls.messages.json is there. It’s possible the nightly build shipped without it.
Try reinstalling Cursor Nightly. Download a fresh copy from the site and replace the current one. This kind of ENOENT error for a bundled file usually points to a corrupted or incomplete install.
Does the error happen without the -w flag too? For example, try cursor-nightly df. I’m curious if it’s specific to --wait or a general issue.
❯ cursor-nightly df
Error reading NLS messages file /Applications/Cursor Nightly.app/Contents/Resources/app/out/nls.messages.json: Error: ENOENT: no such file or directory, open '/Applications/Cursor Nightly.app/Contents/Resources/app/out/nls.messages.json'
Thanks for checking. That means the issue isn’t with the -w flag, it’s with the CLI overall.
There are two more things from my last reply that should help us narrow it down:
Check whether the file exists at this path: /Applications/Cursor Nightly.app/Contents/Resources/app/out/nls.messages.json. You can run this in Terminal: ls -la "/Applications/Cursor Nightly.app/Contents/Resources/app/out/nls.messages.json".
If the file isn’t there, try reinstalling Cursor Nightly by downloading it again from the website. It looks like the file didn’t make it into the build, or the install is corrupted.
Still the issue “Error reading NLS messages file” on 2.7.0 pre 176.
Also I noticed that when I am trying to open file for editing, the new cursor isntance is ran then tab is switched to the current one. This process takes 10-15 seconds and becomes very annoying. File opening should not take more than half of the second.
Hey, thanks for checking and sharing the ls -la output. The nls.messages.json file really is missing in the Nightly build. This is a bug on our side in the Nightly build pipeline. I’ve passed it to the team.
A couple things:
We recently had issues publishing Nightly builds (they weren’t coming out since March 27), and that’s now fixed. Please try updating to the latest Nightly. There’s a chance the file is already included in the newest build.
About files opening slowly (10 to 15 seconds), is that a separate issue, or did it start at the same time as the NLS error? Can you share the full version from Help > About for your current Nightly?
❯ cursor-nightly xxxx.yml
Error reading NLS messages file /Applications/Cursor Nightly.app/Contents/Resources/app/out/nls.messages.json: Error: ENOENT: no such file or directory, open ‘/Applications/Cursor Nightly.app/Contents/Resources/app/out/nls.messages.json’
payment-domain/.github/workflows on feature/PC-18744_devqa_veem_trigger_pr_20260407 via v3.14.3 (.venv)
❯ cursor-nightly --version
Error reading NLS messages file /Applications/Cursor Nightly.app/Contents/Resources/app/out/nls.messages.json: Error: ENOENT: no such file or directory, open ‘/Applications/Cursor Nightly.app/Contents/Resources/app/out/nls.messages.json’
3.1.0-pre.12.patch.0
157ffe1c6dac02720a7c5d875229565305625f19
arm64
though on this version I do not see the delay.
Please include the file ASAP, this is not a complex problem.
I see that in 3.1.0-pre.12 the file still isn’t included in the build. It’s good that the delay when opening files is gone.
I’ve forwarded this to the team again and stressed that the issue has been ongoing for over a month. Unfortunately, I can’t give a specific ETA, but your report helps raise the priority.
Let me know if anything changes in the next Nightly update.
hint: Waiting for your editor to close the file... Error reading NLS messages file /Applications/Cursor Nightly.app/Contents/Resources/app/out/nls.messages.json: Error: ENOENT: no such file or directory, open '/Applications/Cursor Nightly.app/Contents/Resources/app/out/nls.messages.json'
I see that the file still hasn’t shown up in 3.2.0-pre.32. It’s frustrating that this has been going on for over a month.
I escalated this with a specific link to the Nightly build pipeline. nls.messages.json has consistently not been included in the build since version 2.7.0-pre.45. Unfortunately, I can’t give an ETA, but your report helps raise the priority.
v3.14.3 (.venv)