Error when I use -w option

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

> cursor-nightly -w 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'

Steps to Reproduce

see aabove

Expected Behavior

no error

Operating System

Linux

Version Information

Version: 2.7.0-pre.45.patch.0
VSCode Version: 1.105.1
Commit: 447839e5318c8d58f2447eeeca8f440ae1b72d09
Date: 2026-03-10T05:34:36.213Z
Build Type: Nightly
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report.

A couple of things to try:

  1. 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.

  2. 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.

  3. 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.

Let me know how it goes.

āÆ 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:

  1. 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".

  2. 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.

Let me know what you find.

infrastructure on ī‚  feature/PC-18744_Centralize_pipelines [$!?] via :snake: v3.14.3 (.venv)
āÆ cd /Applications/Cursor\ Nightly.app/Contents/Resources/app/out/

Resources/app/out via  v24.13.1 via :snake: v3.14.3 (.venv)
āÆ ls -la
total 3232
drwxr-xr-x@ 8 eugenkonkov staff 256 Mar 10 05:46 .
drwxr-xr-x@ 13 eugenkonkov staff 416 Mar 10 05:46 ..
-rw-r–r–@ 1 eugenkonkov staff 19165 Mar 10 05:37 bootstrap-fork.js
-rw-r–r–@ 1 eugenkonkov staff 229206 Mar 10 05:37 cli.js
-rw-r–r–@ 1 eugenkonkov staff 1403383 Mar 10 05:37 main.js
drwxr-xr-x@ 13 eugenkonkov staff 416 Mar 10 05:46 media
drwxr-xr-x@ 7 eugenkonkov staff 224 Mar 10 05:46 vs
drwxr-xr-x@ 3 eugenkonkov staff 96 Mar 10 05:46 vscode-dts

  1. I am ok with a current nightly-cursor because this do not stop me from doing my tasks.

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:

  1. 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.

  2. 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?

Let me know how it goes after updating.

āÆ 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 :snake: 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.

1 Like

This is still the problem:

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'

3.2.0 pre 32

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.

I’ll post an update here as soon as I have one.