Node.js JavaScript Runtime Task

Support Bug Reports
1

When the Cursor IDE is closed, the “Node.js JavaScript Runtime Task” continues running, and starting Cursor again creates a new task. This leads to multiple processes running simultaneously, which consumes system RAM.

Where does the bug appear (feature/product)?
Editor

Expected Behavior
The Node task related to the Cursor should be closed as well.

Steps to Reproduce

  1. Open Cursor, then open Task Manager and filter by “node” to see two node tasks running.
  2. Close Cursor, filter by “node” again, and notice there are still two node tasks running.
  3. Open Cursor once more, check Task Manager, and now there are four node tasks running.
  4. This pattern keeps repeating.
2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

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!

6

Hey, thanks for the detailed report.

On Windows, “Node.js JavaScript Runtime” in Task Manager is any node.exe process. Cursor starts several of them (MCP servers from plugins like MongoDB or Firebase, plus the TypeScript language server), and some of them can stay running after you close Cursor. This is an issue we’re tracking.

To figure out which process is staying alive on your machine, can you collect this:

  1. Fully close Cursor via File > Exit.
  2. Open Task Manager > Details tab, right-click the column header > Select columns > enable Command line.
  3. End all remaining node.exe processes.
  4. Launch Cursor, open your project, wait about 1 minute.
  5. Close it again via File > Exit and wait 30 seconds.
  6. Check which node.exe processes are still running and copy their Command line values.

You can also get the same list in PowerShell after step 5:

Get-CimInstance Win32_Process -Filter "name='node.exe'" | Select-Object ProcessId, ParentProcessId, CommandLine | Format-List

Send over those command lines and your Cursor version from Help > About.

For now, ending the leftover node.exe processes in Task Manager after closing Cursor will free up RAM. If the command line mentions mongodb or firebase, disabling those plugins in Cursor Settings under Plugins / Tools & MCP when you don’t need them should also stop the memory build-up.