And also it automatically opens localhost links from terminals (e.g. when I run npm run dev) even though it is disabled (in system browser not cursor browser - does not happen in editor window):
And obviously no WSL support is missing but there is already thread for that.
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor
No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
Aaand I cannot change to Bug Report category because the thread has disallowed tags, not sure how to edit them
edit: works in full edit, but in the edit to change title it does not
Thanks for the detailed report with screenshots. I’ll go through each point:
Notification badge doesn’t reset - known issue, several reports in the last month, including this thread. Team’s aware, no ETA yet, but your report helps with prioritization.
No thinking model indicator - known thing too, mentioned here and here. Team’s on it. Workaround for now: in the model dropdown you can see thinking/non-thinking options.
Localhost links auto-open in system browser - I see “Show Localhost Links in Browser” is off. Small nuance: this setting controls links in Cursor’s Browser Tab, not the system browser. Issue’s likely in a separate mechanism for the agents window (doesn’t happen in editor window). Passed to the team. Workaround: run npm run dev etc. from the terminal in the editor window.
Good question about .env. It depends on what’s actually blocking access.
.env* is in the default ignore list, but that only applies to indexing (codebase indexing), not to agent tool calls (Read/Write file). If you don’t have a .cursorignore with an .env* pattern, the agent can technically read and edit those files, including in the editor window.
If the agent really can’t open .env in the editor window, but can in the agents window, that might be a bug. Can you confirm:
Do you have a .cursorignore in the project, and what’s in it?
Is Global Cursor Ignore List set up in Settings > General?
What exact error does the agent show in the editor window when it tries to open .env?
Workaround for now is to add this to .cursorignore in the project root:
.env
.env.*
Note that .cursorignore doesn’t block access via terminal commands like cat .env. It only affects Read/Write file tools. More details here: https://cursor.com/docs/context/ignore-files