.env file changes need close Cursor and reopen to take effect

Describe the Bug

.env file changes need close Cursor and reopen to take effect

Steps to Reproduce

.env file changes need close Cursor and reopen to take effect

Expected Behavior

should take effect once I restart my local server

Operating System

MacOS

Current Cursor Version (Menu β†’ About Cursor β†’ Copy)

Version: 0.43.6
VSCode Version: 1.93.1
Commit: a846435528b4b760494a836f96f0739889253530
Date: 2024-12-06T05:11:55.168Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 24.0.0

Additional Information

No

Does this stop you from using Cursor

No - Cursor works, but with this issue

Same issue here!

One thing I will add is that this is not happening on VSCode so I do think it is caused at the cursor app level somehow.

I’m sorry to complain here, but this is becoming a decision point for me to consider go back to use VScode. Many hours spent trying to fix an issue just to find out this was a problem with the tool I was using. The terminal does NOT work as expected. I simply can’t trust it is running with the right .env. I lost data and had to recover things from backup after it reused the previous .env file. I understand that the team have priorities, but this is happening for 8 MONTHS already. It is a serious problem and nothing was done about. Can some attention be given to this, please?

Many complaints about the exact same issue in this forum.